Article
What to do when you get stuck on a step
2 min read
On this page
An abandoned project rarely looks like a decision. It looks like a step you stopped at on a Thursday and never reopened.
Getting stuck isn't a sign the plan is wrong. It's normal. What matters is recognising which kind of stuck you are, because each kind has a different fix.
The four kinds of stuck
1. You don't understand what's being asked. The step is ambiguously written, or it assumes something you don't have. The fix is a question, not more effort.
2. You're missing an input. You're waiting on a document, a reply, an access. That's not a blocker, it's a dependency — and it should be handled as one: write down what you're waiting for, chase it explicitly, and move on to something else.
3. You're afraid of the step. The call you don't want to make, the message you don't want to send, the price you don't want to say out loud. This is the most common and the best disguised: you will always describe it as "I didn't have time".
4. It's genuinely hard. The step really does need a skill you don't have yet. This is the only case where the answer is "go learn" — and even then, learn exactly as much as this step requires.
What to actually do
Restate the step out loud. If you can't say in two sentences what has to come out of it, the problem is clarity, not capability.
Split it into three. A step you're afraid of becomes three small ones, the first of which is harmless.
Set a twenty-minute timer. You're allowed to stop afterwards. You usually don't, but the contract makes starting possible.
Ask someone who has been there. Not "how is this done in general" — but "I got here, I tried this, what's next".
Mark it as blocked, explicitly. A blocked step that's written down is a problem. A blocked step that's forgotten is a dead project.
About skipping ahead
Sometimes skipping a step and coming back is right. The rule: you can skip a step if it doesn't produce something later steps depend on. If it does, you save nothing — you build on air and come back anyway, with more rework.
The question that unblocks most often
The most useful question isn't "how do I do this?", it's:
What did the last person through this step do?
That's why the community around a process matters more than it looks. You don't need an expert to teach you a course; you need someone who was on step 7 two months ago and remembers exactly what tripped them.
If you're working from a guide, ask right at the step you're on — that's how the community part is designed: targeted help, not a feed where your question disappears in ten minutes.
