“I need to know the full plan before I begin”

The Invisible PrerequisiteYou're holding a project brief—a real one, not hypothetical. Before you open the document, you run through it once more: what's the scope, where does it connect to other work, what could go wrong, who needs what by when. It feels like due diligence. It feels like respect for the time you're about to spend. But the brief is already in your hands. You're not gathering information anymore. You're rehearsing a checklist of unknowns you believe must be resolved first. The rule underneath is simple: clarity precedes action. Move before you have it, and you'll waste effort or look unprepared. So you wait for the moment when the path from here to…

Why the Wait Feels ProtectiveA full plan doesn't actually exist. Projects unfold in stages; information emerges as you move. But research on implementation intentions—the if-then structure that links a trigger to a specific action—shows that people who use vague readiness criteria (feeling ready, having enough time, understanding the whole arc) wait much longer than those who pick one concrete condition and start when it arrives. Your brain isn't being irrational. It's following a plausible rule: if I don't know what comes next, I might fail. The cost of starting small and learning as I go feels higher than the cost of waiting and preparing. That trade-off is the…

One Condition That Breaks the ChainPick the smallest true component of this project—not a guess about the whole shape, but one thing you do know needs doing. Set one concrete if-then rule: 'If I finish this meeting, then I open the planning doc and write only the first section.' Not the whole plan. Not even a draft. One section, under five minutes. Do this once and notice what you learn that waiting never taught you. The unknowns don't disappear; you find out which ones actually matter and which ones dissolve once you're inside the work.