Stop reading, start cycling
There is a trap in learning about NCT: spending too long in theory and not enough time in practice. NCT is a simple framework. The best way to understand it is to run one cycle — imperfectly, quickly, and with the explicit expectation that you will get better at it over time.
This guide walks you through your first NCT cycle from start to finish. From choosing your Narratives to wrapping up and learning. It should take under 30 minutes to complete the planning phase. The cycle itself takes however long you set it — typically 6 weeks to 4 months, depending on the nature of the work.
Step 1: Set your cycle length and dates
Before you write a single Narrative, decide how long your cycle will run. For your first cycle, 8 weeks is a reasonable starting point — long enough to do real work, short enough to learn quickly. Many product teams find that 3–4 months works better once they are up and running, because it gives space for discovery, delivery, measuring impact, and adapting. A standard quarter is often too short when you need all four.
Pick a start date (ideally the Monday of a new week) and an end date. Write them down. This is your cycle boundary.
Avoid the temptation to make your first cycle fit a rigid quarterly calendar. Start when you are ready, end when it makes sense for the work.
Step 2: Write two to three Narratives
Sit down with your team (or alone, if you are a founder) and identify the most important customer problems or opportunities in front of you right now. Not the most interesting — the most important.
For each one, write a short narrative in this structure:
"[Who] is experiencing [what problem]. This leads to [negative outcome]. If we address it, we expect [positive outcome]."
Write two or three. Not five, not eight. Two or three.
If you cannot choose, ask: which of these problems, if solved, would have the biggest impact on the metrics that matter most to your organization right now? Start there.
Time required: 20–30 minutes
Step 3: Write two to four Commitments per Narrative
For each Narrative, identify the concrete deliverables that your team can commit to completing within the cycle. These are your Commitments.
A Commitment should be:
- Specific — clear enough that the team knows when it is done
- Achievable — genuinely possible within the cycle, not aspirational
- Meaningful — actually addresses the Narrative it belongs to
Write each Commitment as a deliverable statement: "Build X," "Ship Y," "Complete Z." Avoid vague Commitments like "Improve the onboarding experience" — that is a Narrative, not a Commitment.
Two Commitments per Narrative is usually right for a first cycle. You are still calibrating your capacity.
Time required: 15–20 minutes
Step 4: Break Commitments into Tasks
For each Commitment, list the individual work items that will complete it. These are your Tasks. They should be small enough to complete within a day or two — if a Task takes longer than that, break it down.
Assign Tasks to individuals. Add rough effort estimates if your team uses them. Do not over-engineer this step — the goal is to make the work visible, not to create a perfect Gantt chart.
If you are using ncts.app, this is the step where you add Tasks directly under each Commitment, and they inherit the full Narrative context automatically.
Time required: 20–30 minutes
Step 5: Run the cycle
Your cycle is now planned. The running part is simple in principle and hard in practice: do the work, track progress on Tasks, and update Commitments as things change.
A few practices that help:
- Weekly sync — a 30-minute review of Commitment status. Not a status update meeting — a problem-solving meeting. Which Commitments are at risk? What needs to change?
- Mid-cycle check — at the midpoint of your cycle, review each Narrative. Is the team still pointed at the right problems? Has anything changed externally that shifts priorities?
- No new Narratives mid-cycle — unless something genuinely critical changes, resist the urge to add new Narratives during the cycle. Stability is a feature.
Step 6: Wrap up and learn
At the end of the cycle, run a retrospective. For each Narrative and Commitment, answer:
- Was the Commitment delivered? If not, why not?
- Did delivering the Commitment actually address the Narrative? (Sometimes it does not — and that is useful to know.)
- What would we write differently next time?
The wrap-up meeting should take 60 to 90 minutes. It is one of the highest-leverage conversations your team will have. Do not skip it.
What your first cycle will teach you
Almost every team discovers the same things in their first cycle:
- They committed to too much — first cycles are almost universally over-committed. Cut your commitments in half for cycle two.
- Their Narratives were too vague — the first cycle usually reveals which Narratives were actually solution-disguises. Rewrite them before cycle two.
- Context is more valuable than they expected — when individual contributors can see why their Task exists, they make better decisions autonomously. This is often the biggest surprise.
These are not failures. They are exactly the calibration data that makes cycle two better than cycle one.
Ready to start?
ncts.app is built specifically for NCT cycles. You can create your first workspace, set up a cycle, and add your Narratives and Commitments in about 10 minutes. Start for free — no credit card required.
If you want a more detailed walkthrough of the entire framework before you begin, download the complete NCT Guide. It covers everything from first principles to running multi-team cycles.