One way door decisions
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
2026
2025
- Legible and illegible tasks in organisations
- L2 Fat marker sketches
- Writing as moats for humans
- Beauty of second degree probes
- Read raw transcripts
- Boundary objects as the new prototypes
- One way door decisions
- Finished softwares should exist
- Essay Quality Ranker
- Export LLM conversations as snippets
- Flipping questions on its head
- Vibe writing maxims
- How I blog with Obsidian, Cloudflare, AstroJS, Github
- How I build greenfield apps with AI-assisted coding
- We have been scammed by the Gaussian distribution club
- Classify incentive problems into stag hunts, and prisoners dilemmas
- I was wrong about optimal stopping
- Thinking like a ship
- Hyperpersonalised N=1 learning
- New mediums for humans to complement superintelligence
- Maxims for AI assisted coding
- Personal Website Starter Kit
- Virtual bookshelves
- It's computational everything
- Public gardens, secret routes
- Git way of learning to code
- Kaomoji generator
- Style Transfer in AI writing
- Copy, Paste and Cite
- Understanding codebases without using code
- Vibe coding with Cursor
- Virtuoso Guide for Personal Memory Systems
- Writing in Future Past
- Publish Originally, Syndicate Elsewhere
- Poetic License of Design
- Idea in the shower, testing before breakfast
- Technology and regulation have a dance of ice and fire
- How I ship "stuff"
- Weekly TODO List on CLI
- Writing is thinking
- Song of Shapes, Words and Paths
- How do we absorb ideas better?
2024
- Read writers who operate
- Brew your ideas lazily
- Vibes
- Trees, Branches, Twigs and Leaves — Mental Models for Writing
- Compound Interest of Private Notes
- Conceptual Compression for LLMs
- Meta-analysis for contradictory research findings
- Beauty of Zettels
- Proof of work
- Gauging previous work of new joinees to the team
- Task management for product managers
- Stitching React and Rails together
- Exploring "smart connections" for note taking
- Deploying Home Cooked Apps with Rails
- Self Marketing
- Repetitive Copyprompting
- Questions to ask every decade
- Balancing work, time and focus
- Hyperlinks are like cashew nuts
- Brand treatments, Design Systems, Vibes
- How to spot human writing on the internet?
- Can a thought be an algorithm?
- Opportunity Harvesting
- How does AI affect UI?
- Everything is a prioritisation problem
- Now
- How I do product roasts
- The Modern Startup Stack
- In-person vision transmission
- How might we help children invent for social good?
- The meeting before the meeting
- Design that's so bad it's actually good
- Breaking the fourth wall of an interview
- Obsessing over personal websites
- Convert v0.dev React to Rails ViewComponents
- English is the hot new programming language
- Better way to think about conflicts
- The role of taste in building products
- World's most ancient public health problem
- Dear enterprises, we're tired of your subscriptions
- Products need not be user centered
- Pluginisation of Modern Software
- Let's make every work 'strategic'
- Making Nielsen's heuristics more digestible
- Startups are a fertile ground for risk taking
- Insights are not just a salad of facts
- Minimum Lovable Product
2023
- Methods are lifejackets not straight jackets
- How to arrive at on-brand colours?
- Minto principle for writing memos
- Importance of Why
- Quality Ideas Trump Execution
- How to hire a personal doctor
- Why I prefer indie softwares
- Use code only if no code fails
- Personal Observation Techniques
- Design is a confusing word
- A Primer to Service Design Blueprints
- Rapid Journey Prototyping
- Directory Structure Visualizer
- AI git commits
- Do's and Don'ts of User Research
- Design Manifesto
- Complex project management for product
2022
2020
- Future of Ageing with Mehdi Yacoubi
- Future of Equity with Ludovick Peters
- Future of Tacit knowledge with Celeste Volpi
- Future of Mental Health with Kavya Rao
- Future of Rural Innovation with Thabiso Blak Mashaba
- Future of unschooling with Che Vanni
- Future of work with Laetitia Vitaud
- How might we prevent acquired infections in hospitals?