NCT Goals

What it teaches, and what we carry

The Narrative is the headline contribution: making written strategic context a mandatory, structural part of the goal rather than a preamble people skip. That is the same conviction behind Key Result narratives, arrived at independently, and V2MOM got there by a third route. When three systems built by different people in different decades all conclude that a goal without its story is half a goal, treat it as a finding of the field. The Tasks layer earns its keep the same way: keeping activities visibly downstream of goals is the wall we build between Key Results and initiatives, and both walls guard against the same drift, the task-based Key Result.

Two honest answers to the same question

NCT's most interesting move is its answer to sandbagging. Everyone on the shelf meets the problem: when goals carry consequences, targets get pre-negotiated. NCT answers with reliability: make commitments deliberately achievable, and promises mean something again. We answer with consequence design: keep the stretch, label it as aspirational, and grade the quarter on judgment so honesty costs nothing, the argument of That Worked #3. These are two legitimate solutions with different fits: teams whose credibility depends on delivery dates (platform, infrastructure, agencies) often thrive on commitment-style goals, while teams pushing into the unknown need the reach that the research shows difficulty buys. A healthy portfolio can run both, knowingly, the same commitments-and-bets mix described in EOS and Traction.

The natural hybrid

NCT's narrative discipline sits happily on top of OKR mechanics, and an NCT team scaling up can add confidence assessment, the Issues and Obstacles Log and alignment without giving up its stories or its promises.

One line to keep: NCT proved the goal needs its story; the portfolio decides where the promises stop and the bets begin.