One way door decisions

Shreyas Prakash headshot

Shreyas Prakash

There are moments in life when you hit slow-burn-max mode, when you know a big decision is coming, and you can feel the weight of it. You stop everything else and think deeply about the problem you’re about to face.

Jeff Bezos calls these “one-way doors.” Most decisions are two-way doors, you can go through, try it out, and walk back if it doesn’t work. But some aren’t like that. They’re irreversible, or feel that way from where you’re standing. These decisions look different for everyone, but for me, they’ve shown up at inflection points: moving countries, choosing a first job, getting married.

You could argue none of these are truly irreversible. But zoom out to the perspective of a full lifetime, say, 100 years, and the cost of reversing such choices starts to feel steep. By 30, you’re probably halfway through your productive output. So these one-way doors feel even harder. There’s no silver bullet. The best you get is a series of tradeoffs—some heavy on one side, some on the other.

I still struggle with these decisions. I’m not claiming mastery. But I do have a general approach that helps me move forward when I’m staring down one of these one-way doors.

I start with “explore” mode. I gather inputs, talk to people, look for frameworks, test small hypotheses. Only once I’m confident that I’ve mapped enough of the space do I switch to “exploit” mode—where I narrow down and commit.

This mindset mirrors the secretary problem:

You’re interviewing candidates one by one, in random order, for a single role. After each interview, you must decide on the spot—hire or move on. You can’t go back. The optimal strategy is to reject the first 37% of candidates to gather a baseline, and then hire the next one who’s better than everyone you’ve seen so far. This gives you the best chance of hiring the top candidate.

I use the same logic when seeking opinions or inputs. If I plan to speak to 20 people before making a call, I treat the first 7 as pure exploration. I gather everything, say yes to all the ideas, take detailed notes—but I don’t commit. Only after that first phase do I shift into selection mode, looking for the best fit that exceeds the baseline I’ve now formed.

You never really know what you don’t know. And you can’t learn everything, time’s limited. So this 37% rule offers a structure. If I’ve got 6 months before a major decision, I spend the first 1.5 months on deep exploration. I talk to people with different lived experiences and world views. I soak in their pros and cons, their assumptions, their logic.

And when I hear a new viewpoint, I try to hold it as “true,” just for a while. I let it challenge whatever internal direction I’ve started drifting toward. This takes effort. The temptation is to build a fortress around early ideas—to protect them from challenge. But the harder (and better) path is to seek disconfirmatory evidence. Poke holes in your own arguments before someone else does.

As you gather more input, you’ll start to feel a tension between conflicting views. That’s a good thing. You can stretch your thinking, add nuance, let your stance evolve.

Eventually, after enough of these conversations—human or otherwise (ChatGPT, Perplexity, Deepseek, etc.), you arrive at something stable. You marinate on it. For me, that settling phase takes 4–7 days. The emotional churn quiets down, and something clear starts to take shape.

Subscribe to get future posts via email (or grab the RSS feed). 2-3 ideas every month across design and tech

Read more

  1. My agentic engineering workflow (step by step)agentic-coding
  2. Every darn thing is a kekulean loop if you notice itdesign-thinking
  3. Hammock driven developmentagentic-coding
  4. Peculiar ways number three fits into our funny little brainsmental-models
  5. AI sandwich as a defacto principle for anything agentic engineering relatedagentic-coding
  6. How I write essays in 2026writing
  7. Authority in the guise of evidencecritical-rationalism
  8. Map is not the territoryphilosophy
  9. Self hypnosis as a manifestation ritualmeditation
  10. Hegelian dialectic for structured reasoning with AI agentsphilosophy
  11. How I prepare for tough negotiations nowadaysnegotiation
  12. When should we steelthread somethingproduct-development
  13. Learning and re-learning my mother tongue in Malayalam
  14. Breadboarding, shaping, slicing, and steelthreading solutions with AI agentsproduct-management
  15. Healthy conflict in teams have a tipping pointteam-building
  16. How I deslopify AI writingwriting
  17. How I started building softwares with AI agents being non technicalagentic-coding
  18. Read raw transcriptswriting
  19. Legible and illegible tasks in organisationsproduct
  20. L2 Fat marker sketchesdesign
  21. Writing as moats for humanswriting
  22. Beauty of second degree probesdecision-making
  23. Boundary objects as the new prototypesprototyping
  24. One way door decisionsproduct
  25. Finished softwares should existproduct
  26. How I periodically rank my rough draftsobsidian
  27. Flipping questions on its headinterviewing
  28. Vibe writing maximswriting
  29. How I blog with Obsidian, Cloudflare, AstroJS, Githubwriting
  30. How I build greenfield apps with AI-assisted codingagentic-coding
  31. We have been scammed by the Gaussian distribution clubmathematics
  32. Classify incentive problems into stag hunts, and prisoners dilemmasgame-theory
  33. I was wrong about optimal stoppingmathematics
  34. Thinking like a shipmental-models
  35. Hyperpersonalised N=1 learningeducation
  36. New mediums for humans to complement superintelligenceagentic-coding
  37. Maxims for AI assisted codingagentic-coding
  38. Virtual bookshelvesaesthetics
  39. It's computational everythingtrends
  40. Public gardens, secret routesdigital-garden
  41. Git way of learning to codeagentic-coding
  42. Style Transfer in AI writingagentic-coding
  43. Understanding codebases without using codeagentic-coding
  44. Vibe coding with Cursoragentic-coding
  45. Virtuoso Guide for Personal Memory Systemsmemory
  46. Writing in Future Pastwriting
  47. Publish Originally, Syndicate Elsewhereblogging
  48. Poetic License of Designdesign
  49. Idea in the shower, testing before breakfastsoftware
  50. Technology and regulation have a dance of ice and firetechnology
  51. How I ship "stuff"software
  52. Writing is thinkingwriting
  53. Song of Shapes, Words and Pathscreativity
  54. How do we absorb ideas better?knowledge
  55. Read writers who operatewriting
  56. Brew your ideas lazilyideas
  57. Trees, Branches, Twigs and Leaves — Mental Models for Writingwriting
  58. Compound Interest of Private Noteswriting
  59. Conceptual Compression for LLMsagentic-coding
  60. Meta-analysis for contradictory research findingsdigital-health
  61. Proof of workproduct
  62. Gauging previous work of new joinees to the teamleadership
  63. Task management for product managersproduct
  64. Beauty of Zettelswriting
  65. Stitching React and Rails togetheragentic-coding
  66. Exploring "smart connections" for note takingwriting
  67. Deploying Home Cooked Apps with Railssoftware
  68. Repetitive Copypromptingwriting
  69. Questions to ask every decadejournalling
  70. Balancing work, time and focusproductivity
  71. Hyperlinks are like cashew nutswriting
  72. Brand treatments, Design Systems, Vibesdesign
  73. How to spot human writing on the internetwriting
  74. Can a thought be an algorithm?product
  75. Opportunity Harvestingcareers
  76. How does AI affect UI?design
  77. Everything is a prioritisation problemproduct-management
  78. How I do product roastsproduct
  79. The Modern Startup Stacksoftware
  80. In-person vision transmissionproduct
  81. How might we help children invent for social good?social-design
  82. The meeting before the meetingmeetings
  83. Design that's so bad it's actually gooddesign
  84. Lessons learnt interview prepping for product rolesinterviewing
  85. Obsessing over personal websitessoftware
  86. English is the hot new programming languagesoftware
  87. Better way to think about conflictsconflict-management
  88. The role of taste in building productsdesign
  89. Dear enterprises, we're tired of your subscriptionssoftware
  90. Products need not be user centereddesign
  91. World's most ancient public health problemsoftware
  92. Pluginisation of Modern Softwaredesign
  93. Let's make every work 'strategic'consulting
  94. Making Nielsen's heuristics more digestibledesign
  95. Startups are a fertile ground for risk takingentrepreneurship
  96. Insights are not just a salad of factsdesign
  97. Minimum Lovable Productproduct
  98. Methods are lifejackets not straight jacketsmethodology
  99. How to arrive at on-brand colours?design
  100. Minto principle for writing memoswriting
  101. Importance of Whytask-management
  102. Quality Ideas Trump Executionsoftware
  103. Why I prefer indie softwareslifestyle
  104. Use code only if no code failscode
  105. Self Marketing
  106. Personal Observation Techniquesdesign
  107. Design is a confusing worddesign
  108. A Primer to Service Design Blueprintsdesign
  109. Rapid Journey Prototypingdesign
  110. Visualise detailed file structures on CLIcli
  111. Do's and Don'ts of User Researchdesign
  112. Design Manifestodesign
  113. Complex project management for productproducts
  114. How might we enable patients and caregivers to overcome preventable health conditions?digital-health
  115. Pedagogy of the Uncharted — What for, and Where to?education
  116. Future of Ageing with Mehdi Yacoubiinterviewing
  117. Future of Tacit knowledge with Celeste Volpiinterviewing
  118. Future of Rural Innovation with Thabiso Blak Mashabainterviewing
  119. Future of Equity with Ludovick Petersinterviewing
  120. Future of work with Laetitia Vitaudinterviewing
  121. Future of Mental Health with Kavya Raointerviewing
  122. Future of unschooling with Che Vanniinterviewing
  123. How might we prevent acquired infections in hospitals?digital-health
  124. The why to endure any howentrepreneurship
  125. Design education amidst social tribulationsdesign
  126. How might we assist deafblind runners to navigate?social-design