Why the Narrative is the hardest part of NCT
Most teams that adopt NCT find the Tasks easy — they already know how to track work. They find Commitments manageable — defining deliverables is familiar. But Narratives trip people up, because a Narrative requires something most goal-setting frameworks explicitly avoid: an opinion about the customer and a point of view on what matters.
Writing a good Narrative is part journalism, part strategy, part empathy. Done well, it becomes the single most powerful alignment tool your team has. Done poorly, it becomes a placeholder that nobody reads.
This guide will show you the difference.
What a Narrative actually is
A Narrative is a short description of a customer problem or strategic opportunity. It answers three questions:
- Who is experiencing this problem?
- What is the problem, in their terms?
- Why does solving it matter — for them and for us?
A Narrative is explicitly not a solution. It does not say "build feature X." It does not say "achieve metric Y." It describes the territory your team is entering, not the route you will take. This is intentional: it gives teams room to discover the best solution while keeping everyone pointed at the same real-world problem.
The anatomy of a strong Narrative
1. A specific customer or user type
Generic Narratives ("users want a better experience") are useless because they could justify almost anything. Strong Narratives name a specific customer segment: enterprise customers, power users, team admins, first-time users within 30 days of signup.
Specificity forces honesty. If you cannot say who is experiencing the problem, you probably do not understand the problem well enough to work on it.
2. A concrete problem, not a complaint
There is a difference between observing that something is "hard" and describing why it is hard and what that cost is. A good Narrative names the friction point and connects it to a real consequence: they churn, they do not expand, they do not recommend us, they waste hours, they make mistakes.
3. The opportunity if solved
A Narrative that describes a problem without articulating why it matters to the business is easy to deprioritize. The third element — the "why us" — connects the customer problem to the organizational reason to care. This is what makes a Narrative a strategic document, not just a user story.
4. Written in plain language
Narratives should be readable by anyone in the organization — not just the team writing them. Avoid jargon, acronyms, and technical shorthand unless your audience uses them naturally. The test: could you read this Narrative to a new hire on their first day and have them immediately understand why the team is doing what it's doing?
Five examples of real Narratives
Example 1: Onboarding / Retention
"New users who come from a referral or ad click are dropping off before they complete setup — often within the first 10 minutes. They don't see value early enough to justify the time investment. If we reduce time-to-first-value, we will significantly improve 7-day retention and reduce the cost of acquisition."
Example 2: Enterprise / Expansion
"Our enterprise customers are managing multiple teams in separate workspaces, which means admins have no cross-team visibility and cannot run company-wide planning cycles. This limits our expansion revenue because admins can't justify upgrading to Enterprise without the tools to manage at scale."
Example 3: Core Product Quality
"Power users who rely on our tool daily are hitting performance bottlenecks with large datasets. Slow load times erode trust in the platform and are a top complaint in our NPS verbatims. If we resolve the core performance issues, we expect to see measurable improvement in power user retention and NPS."
Example 4: Go-to-Market / Acquisition
"Teams searching for OKR alternatives are landing on competitor pages — not ours. We don't have content that speaks to people who have tried OKRs and been disappointed. This is our largest unaddressed acquisition segment, and we have a strong story to tell."
Example 5: Internal / Operations
"Our customer support team is spending 40% of their time answering questions that are already answered in our documentation — but the docs are hard to find and frequently out of date. If we fix documentation quality and discoverability, we can reduce support volume and improve customer satisfaction simultaneously."
Common Narrative mistakes
The solution-in-disguise Narrative
This is the most common mistake: writing a Narrative that describes a solution rather than a problem. "We need to build a dashboard for admins" is not a Narrative. "Admins lack visibility into team usage patterns, which prevents them from optimizing their team's workflow and demonstrating ROI to their organization" is a Narrative.
The test: can your Narrative be addressed by more than one solution? If so, it is a real Narrative. If there is only one obvious solution, it is probably a disguised feature request.
The too-broad Narrative
"Users want a more intuitive interface" is not actionable. It could justify a year of work in any direction. Good Narratives are specific enough that the team can write two or three Commitments that would meaningfully address them within a single cycle.
The metric-as-Narrative
"Improve retention by 15%" is a target, not a Narrative. Targets live in Commitments or success criteria, not in Narratives. A Narrative explains why retention is where it is and which specific customer problem you are going to address to move it.
The passive Narrative
Narratives written in the passive voice tend to be vague. "There is an opportunity to improve the checkout flow" tells you nothing about who is experiencing friction and why. Active, specific Narratives name the actor and the consequence.
How many Narratives per cycle?
Most teams work best with two to four Narratives per cycle. Fewer than two and you risk the cycle becoming a single-track project. More than four and the team loses focus — each Narrative gets diluted Commitments and shallow execution.
The constraint is valuable. If you have eight things that seem equally important, writing Narratives will force you to articulate which problems are most urgent and why. That process of prioritization is where NCT earns its keep.
Writing your first Narrative: a simple template
If you are writing your first Narrative and want a starting structure, try this template:
"[Customer segment] is experiencing [specific problem]. This leads to [concrete negative outcome]. If we address this, we expect [positive outcome for customer and for us]."
This template is a scaffold, not a formula. Once you have written a few Narratives, you will find your own voice — one that reflects your team's understanding of your customers and your strategic position.
Ready to put it into practice? Start a free cycle on ncts.app — or download the complete NCT Guide for a deeper walkthrough of the entire framework.