Module 02 · 3 lessons

The research lifecycle

Free — no account needed to read

A project has a shape, and knowing the shape tells you where you actually are.

Why it matters

People abandon research not because it is hard but because they lose track of which part they are in, and try to write while still discovering, or search while still undecided about the question.

What it teaches

• The stages of a research project
• Why the cycle loops rather than runs straight
• Where projects usually stall, and what that stall looks like
• What "done" means at each stage
• How to tell discovery from analysis

When you reach for it

• You have been reading for three weeks and do not feel closer to anything
• You cannot tell whether you should be searching for more sources or stopping
• The work feels enormous and you cannot see the next move

The common misreading

That the stages run once, in order. Every real project loops — a source you find in week six sends you back to the question, and that is the process working, not you failing.

What this module will not tell you

This module will not tell you how long any stage should take. That depends on the field, the question and the deadline, and any number given here would be invented.

Think first

Someone has 60 saved papers, no notes, and a document containing only a title. They say they are "still researching". Which stage are they actually in, and which stage do they believe they are in?

Think of a piece of research, coursework or investigation you have abandoned. Where exactly did it stop? Not why — where.

The lessons

• The stages, and what finishing each one looks like — Each stage has a finish condition. Not knowing yours is the most common reason work feels endless. (8 min)
• Why it loops, and when a loop is a warning — A loop should be able to name what it is for. If it cannot, you have found the stall rather than the next stage. (6 min)
• The four common stalls — Each stall has a characteristic symptom you can check for in your own project in about a minute. (7 min)

Practise it: Locate yourself

Take a project you have running — or one you abandoned — and place it honestly on the lifecycle.

1. Name the stage you believe you are in.
2. Write that stage's finish condition from the first lesson.
3. Check the evidence: can you meet that condition right now? If not, you are in it. If yes, you have already moved on and may not have noticed.
4. Check for the four stalls. Which symptom is most present?
5. Write the single next action, small enough to do in one sitting.

What a considered answer tends to contain (not a mark scheme): A considered answer names one stage, one finish condition, and one action that takes under an hour. If the action is "read more", it is usually worth asking what exactly you are looking for.

Use it on real work: Give one real project a stage and a stopping rule

Open a real project — in this product or outside it — and set its stage deliberately.

1. Set the project stage to the one you are honestly in.
2. Write its finish condition somewhere you will see it.
3. If you are in discovery, write a stopping rule now, before you want one.
4. Do the one next action you named.
5. Come back and record what actually changed.

Reflect

Which stage do you personally get stuck in, across projects? What does being stuck there feel like from the inside?