The Unstuck Ladder: Switching Tracks When One Isn't Working

AA substantial project is not one task, it is a rotating cast of very different ones: reading, writing, building, designing experiments, organising what you already have, and standing back to see the shape of the whole thing. "I'm stuck" almost never means all of those are stuck at once — it usually means one specific kind of work has stopped moving, while several others are sitting there fully available. The single most useful move when you're stuck is often not to push harder at the thing that isn't working, but to notice which other kind of work is still open to you, and switch to that instead.

This isn't just a comforting story. A meta-analysis of the psychology literature on incubation found a genuine, measurable benefit to setting a problem aside and working on something else for a while, particularly for the kind of open-ended, generative thinking a project involves — though the size of that benefit depends on what you switch to: filling the gap with another high-effort, high-concentration task gave a smaller benefit than a genuine change of pace ^[1]. The ladder below is one concrete way to act on that: a sequence of fallback moves, each one worth trying before you conclude the whole project is stuck rather than just one task within it. It's a companion to Getting Unstuck, which covers the psychology behind why this works; this page is the practical checklist for the moment itself.

Rung 1: Stuck Reading? Reflect on What You've Already Read

LiteratureLiterature review stalls often aren't really about the reading — they're about not being sure the reading is going anywhere. Before reaching for another paper, stop and ask a more pointed question of the ones you've already read: what do they actually tell you about how your project should be designed? Not "what does this paper say" in the abstract, but "does this change what I should build, measure, or argue" in the specific project sitting in front of you. That reframing turns a passive pile of reading into an active input to a decision, which is usually enough to show you what's actually missing — and it's a far more targeted way to find the next paper worth reading than continuing to read broadly in the hope that relevance will eventually show up on its own.

Rung 2: Still Stuck? Start Writing Up What You Have

IfIf reflecting on the literature doesn't unstick you, the next move is to start writing — not the finished literature review chapter, just notes, in whatever form gets words down: what each source claims, how the sources disagree with each other, where the gap in the existing work actually sits. Writing is not simply a way of recording thinking that has already happened; putting a half-formed idea into sentences routinely exposes exactly where it was actually half-formed, in a way that re-reading the same sources one more time does not. Treat this as genuine project progress, not a placeholder to be redone later — a rough note written honestly today is very often 80% of the polished paragraph you'll want in the final report anyway.

Rung 3: Stuck on Writing? Switch to Building or Designing

IfIf the words still won't come, that's the signal to change task type entirely rather than stare at the same blank page for longer. For a project that involves code, this is exactly the moment to go and build something — implement the next small piece, fix the bug you've been putting off, get one thing working end to end. For a project built around an experiment or a study, this is the moment to work on its design instead: what exactly will you measure, what would count as a meaningful result, what could go wrong with the setup as currently planned. This is a deliberate application of the same idea behind John Perry's "structured procrastination" ^[2]: when the top task on your list has stalled, the productive response isn't to do nothing, it's to do the next genuinely useful thing on the list instead of nothing at all. The trick that makes it work rather than becoming an excuse is honesty about the word "genuinely" — this only counts if the thing you switch to is actually project work, not a reason to disappear for the rest of the day.

Rung 4: Still Stuck? Collate and Triangulate

IfIf both writing and building have stalled, it's worth stepping back further still: gather what you actually have — code, data, notes, drafts, results, however partial — in one place, and look at it as a whole rather than as separate, disconnected fragments. This is exactly the moment to apply the triangulation technique covered in Project Navigation & the Art of Triangulation: fix your position using your implementation and data, the literature, and the domain problem together, as three independent bearings on the same point. Being stuck on every individual task at once is frequently a symptom of having lost track of where the project as a whole actually stands — and that is precisely the situation triangulation exists to fix.

Rung 5: Still Stuck? Consider Generalising the Solution

IfIf you're stuck even after collating and triangulating, it can be worth questioning the shape of the solution itself rather than any particular task within it. Is what you're building necessarily one specific, singular thing — or could it instead be a more general framework, with your original specific solution repositioned as one case study that demonstrates it? This is not a trick to make a stuck project sound more impressive; it's a real, well-established move in design-oriented research. Hevner, March, Park and Ram's influential account of design science research in information systems treats exactly this pattern — building a general artifact and evaluating it through a concrete instantiation — as the core structure of rigorous design work, not a fallback for projects in trouble ^[3]. Sometimes generalising also genuinely unsticks the project practically, not just conceptually: a requirement that felt arbitrary when you were building one fixed thing can suddenly become a natural, well-motivated parameter of a framework, and the awkward special case you were stuck on turns out to be exactly the case study that shows the framework's value.

And Always: Life Goes On

EveryEvery rung above assumes you're still able to work, just on the wrong task. Sometimes the actual problem is that you need to stop working altogether for a while, and that is not a failure of discipline — it's a precondition for the rest of this page to keep working at all. See your friends. Talk about complete nonsense that has nothing to do with the project. Try to fix the world, or at least argue about it over dinner. See your family. Go outside and, yes, talk to the trees if you feel like it — time spent in natural environments has a measurable restorative effect on exactly the kind of sustained, directed attention a project demands, precisely because it lets that attention recover rather than depleting it further ^[4]. And underneath all of that: hydrate, exercise, eat properly, and above everything, sleep. The evidence here isn't just folk wisdom — regular aerobic exercise measurably improves the cognitive functions a project draws on most heavily, including memory and executive control ^[5], and sleep loss has a well-documented, direct negative effect on learning capacity and academic performance, the two things a stalled project needs most ^[6]. Treating your own basic functioning as outside the scope of "project work" is not the disciplined choice; it's the one most likely to make every rung above harder than it needs to be.

Putting This Into Practice

• Stuck reading: stop and ask what the papers you've already read imply for your own project's design, before reaching for the next one.
• Still stuck: start writing rough lit-review notes from what you've got. Treat it as real progress, not a placeholder.
• Stuck on writing: switch to building, or to experimental design — but only if it's genuinely project work, not an excuse.
• Stuck on those too: collate everything you have and triangulate against your implementation, the literature, and the domain problem.
• Still stuck: ask whether your specific solution could become a case study of a more general framework.
• Always: notice when the real problem is that you need to stop, not switch — and then actually stop. Friends, family, nature, food, water, exercise, sleep. All of it is project work too, in the sense that none of the rest of this works without it.

References

1. Sio, U. N., & Ormerod, T. C. (2009). Does incubation enhance problem solving? A meta-analytic review. Psychological Bulletin, 135(1), 94–120. https://doi.org/10.1037/a0014212
2. Perry, J. (2012). The Art of Procrastination: A Guide to Effective Dawdling, Lollygagging and Postponing. Workman Publishing.
3. Hevner, A. R., March, S. T., Park, J., & Ram, S. (2004). Design Science in Information Systems Research. MIS Quarterly, 28(1), 75–105. https://doi.org/10.2307/25148625
4. Kaplan, S. (1995). The restorative benefits of nature: Toward an integrative framework. Journal of Environmental Psychology, 15(3), 169–182.
5. Hillman, C. H., Erickson, K. I., & Kramer, A. F. (2008). Be smart, exercise your heart: Exercise effects on brain and cognition. Nature Reviews Neuroscience, 9(1), 58–65. https://doi.org/10.1038/nrn2298
6. Curcio, G., Ferrara, M., & De Gennaro, L. (2006). Sleep loss, learning capacity and academic performance. Sleep Medicine Reviews, 10(5), 323–337. https://doi.org/10.1016/j.smrv.2005.11.001