The New New Product Development Game
Source: https://hbr.org/1986/01/the-new-new-product-development-game ↗
The HBR article that introduced the "rugby" metaphor for product development — overlapping phases, shared responsibility, the whole team moving down the field together — which Jeff Sutherland and Ken Schwaber would later crystallise as Scrum.
Takeuchi and Nonaka studied Japanese companies (Fuji-Xerox, Honda, Canon, NEC) and described a pattern that had emerged there: not the sequential relay of specifications handed off between departments, but overlapping self-organising teams with ambiguous goals and high autonomy.
Reading it today is illuminating for two reasons: the practice they describe is more demanding than the lightweight Scrum that inherited its label, and its roots in Japanese management culture explain why it often degrades in translation.
Required reading on how contemporary product organisations took their shape.
Central argument
Takeuchi and Nonaka argue that the dominant sequential model of product development — where each functional department completes its stage before handing off to the next — is being displaced by a superior approach observed in leading Japanese companies like Honda, Canon, and NEC. In this alternative, cross-functional teams operate with overlapping phases, self-organise around ambiguous goals, and carry collective responsibility for the outcome, much as a rugby team advances the ball together rather than through a relay handoff. Their central finding is that this model produces faster development cycles and higher adaptability precisely because it tolerates and exploits the creative tension of concurrent, partially-redundant work rather than eliminating it through rigid specification.
Critique
The paper draws its evidence entirely from large Japanese manufacturers in a specific cultural and institutional context — lifetime employment, deep organisational loyalty, strong internal knowledge transfer norms — and does not adequately interrogate how much of the model's effectiveness depends on those conditions rather than on the structural features Takeuchi and Nonaka abstract from them. This creates a real tension: the practices they describe (high autonomy, ambiguous goals, peer pressure as the coordination mechanism) may be load-bearing in ways that only work when the underlying cultural substrate is present, which partly explains why the Scrum lineage that borrowed the framework often produces the form without the substance.
Why it matters for product
For a CPO, the paper offers a precise diagnostic for a failure mode that is pervasive in digital organisations: teams that call themselves agile but are running a disguised waterfall, where the overlapping phases exist on paper but coordination still happens through handoffs between specialisms rather than through shared ownership of the outcome. More specifically, Takeuchi and Nonaka's emphasis on 'subtle control' — where management sets direction and tolerates ambiguity but holds teams accountable for self-correction — maps directly onto the unresolved tension in product orgs between strategic alignment and team autonomy, a tension that neither rigid roadmaps nor unconstrained empowerment resolves well.