The problem with most goal frameworks
Most teams that adopt a goal-setting framework start the same way: with optimism. They write their OKRs, align on quarterly targets, and schedule the quarterly reviews. Six months later, the goals are forgotten, the spreadsheet is stale, and nobody is quite sure whether the work they are doing connects to anything strategic.
This is not a discipline problem. It is an architecture problem. Most goal frameworks ask teams to translate strategy into numbers and then trust that those numbers will communicate the intent. They rarely do.
NCT takes a different approach. It starts with language, not metrics.
What NCT stands for
NCT stands for Narratives, Commitments, and Tasks. It is a three-layer framework that connects organizational strategy — the "why" — to the day-to-day work that actually gets done.
- Narratives describe the customer problem or strategic opportunity the team is pursuing. They are written in plain language, not as metrics.
- Commitments are the concrete bets a team makes to address a Narrative. They define what the team commits to delivering within a cycle.
- Tasks are the individual actions that fulfill a Commitment. They are the ground-level work.
Each layer is a child of the one above it. Tasks roll up to Commitments. Commitments roll up to Narratives. Narratives roll up to the organization's strategy. The result is a hierarchy where every piece of work has a reason, and every strategy has a visible path to execution.
The three layers explained
Narratives — the strategic "why"
A Narrative is the most important element in the NCT framework. It describes a customer problem or a strategic bet in the form of a short, human story. A well-written Narrative explains why the team is focused on something, not just what they plan to do.
A good Narrative sounds like this:
"Our enterprise customers are spending too much time onboarding new team members. This creates churn risk in the first 90 days and prevents teams from reaching value quickly. If we can reduce onboarding time by 50%, we will increase 90-day retention and unlock expansion revenue."
Notice what is missing: a specific metric target, a specific solution, a deadline. Narratives intentionally leave room for teams to discover the best approach while staying anchored to the real problem.
Commitments — the team's bets
A Commitment is a specific deliverable that the team is committing to complete within a cycle. Commitments are the connection point between strategic intent and real work. They answer: "Given this Narrative, what are we going to ship or change?"
A Commitment might look like:
"Build a guided onboarding checklist that walks new users through their first five key actions, with progress tracking visible to team admins."
Commitments are deliberately called "commitments" rather than "goals" or "objectives" — because they represent a professional promise that the team is making, not an aspirational target. This changes the culture around the work.
Tasks — the ground-level work
Tasks are individual work items that fulfill a Commitment. They look like a traditional task manager: design the checklist UI, write the copy, implement the API endpoint, write tests. Tasks are the familiar, granular work that every team already tracks.
The difference in NCT is that every Task has context. A developer working on an API endpoint can see, in one click, which Commitment that endpoint serves and which Narrative the Commitment is tied to. This context is often invisible in traditional task management, which is why individual contributors frequently lose the connection to strategy.
Where NCT came from
The NCT framework emerged from within high-performing product and engineering teams, particularly in the Silicon Valley ecosystem. It was designed as a response to several well-documented frustrations with OKRs — particularly the overhead of metric-setting, the tendency to game key results, and the difficulty of capturing qualitative strategic intent in a number.
NCT deliberately leans into narrative reasoning. The name itself signals that: a Narrative is not a KPI. It is a story about a customer, a problem, and an opportunity. This makes NCT more accessible to teams that struggle to translate vision into measurable objectives.
NCT cycles
NCT work happens within time-boxed Cycles. A cycle is typically 6 weeks to 4 months — long enough to complete meaningful discovery and delivery, short enough to stay responsive to change. Many product teams find that 3–4 months is the sweet spot: a standard quarter is often too short when you factor in discovery, delivery, tracking impact, and adapting. At the start of each cycle, the team selects the Narratives they will pursue and writes the Commitments they will make. At the end, they review what was delivered and carry forward what matters.
Cycles give NCT its operational rhythm. Unlike annual planning, which is often disconnected from reality by the time work begins, NCT cycles maintain a tight loop between strategy and execution.
Who uses NCT
NCT is most common in product and engineering organizations, but it works well for any team that needs to connect strategy to delivery. Marketing teams use Narratives to describe audience problems. Sales teams use them to align on customer segments. Operations teams use them to frame process improvements.
The framework scales from a 3-person startup all the way to multi-team product organizations. At small scale, the overhead is minimal. At larger scale, the hierarchy becomes a coordination mechanism — teams can see how their work connects to the work of adjacent teams.
NCT vs OKR: the headline difference
The most common question about NCT is how it differs from OKRs. The short answer: OKRs measure progress through quantified key results; NCT motivates progress through narrative reasoning.
OKRs ask: "What does success look like numerically?" NCT asks: "What is the customer problem, and what are we committing to do about it?"
Neither is universally better. OKRs work well when you have reliable metrics and a culture that responds to numerical targets. NCT works better when work is qualitative, when teams benefit from narrative alignment, or when metric-gaming is a recurring cultural problem.
Read the full NCT vs OKR comparison →
Getting started with NCT
The fastest way to experience NCT is to pick a single Narrative that matters to your team right now. Write it as a customer problem story — one or two sentences. Then write two or three Commitments that represent your team's bets for the next cycle. Break each Commitment into the Tasks your team will work on this week.
That is the entire framework. The nuance comes in writing good Narratives — ones that inspire without over-constraining — and honest Commitments — ones your team actually believes it can deliver.
If you want a structured starting point, download the complete NCT Guide →. Or if you are ready to try the tool, start for free on ncts.app — no credit card required.