The Ten Minutes of Formative Struggle
A particular case illustrates the production-growth model distinction with painful clarity. An engineer who, before AI, spent roughly four hours a day on configuration and dependency management—tedious, mechanical work she did not miss—also encountered, within those four hours, perhaps ten minutes of unexpected difficulty. Something failed in an unfamiliar way. A connection between systems revealed itself through breakage. The failure forced understanding—not the kind you can read in documentation but the embodied, experiential knowledge that deposits itself in practitioner's judgment through years of encounter with the unexpected. When AI assumed the four hours of mechanical work, it also consumed the ten minutes of formative difficulty. The engineer noticed the loss only months later, when she found herself making architectural decisions with less confidence than she had previously felt and could not explain why. The production model accounted for four hours saved. The growth model accounted for ten minutes lost. Neither metric captured the full picture alone. Together, they reveal a trade being made across AI-augmented work: developmental experience for productive output.
In the AI Story
The ten minutes were not scheduled or predictable. They emerged from the friction of real work on real problems—the unexpected resistance that forces reckoning with gaps in understanding. This kind of formative difficulty cannot be replicated by adding ten minutes of deliberate practice to the end of the workday. Formative struggle is contextual. It occurs when the unexpected interrupts the expected, when the system behaves in ways the practitioner did not predict, when the failure forces attention to something that would otherwise remain invisible. You cannot schedule this. You cannot design a training module replicating it. It emerges from friction, and when friction is removed, emergence stops.
Franklin's framework identifies the ten minutes as the renewal mechanism—the process through which the practitioner's judgment is not merely maintained but deepened. The judgment that allows the engineer to feel when a system is wrong before she can articulate why, the architectural intuition that comes from years of encountering how systems actually fail rather than how they are supposed to fail—this knowledge is not transmitted through documentation. It is deposited through the specific experience of being surprised, being wrong, struggling with unexpected difficulty until understanding arrives. The AI removes this experience in the course of removing the tedium, and the removal is celebrated as efficiency while the consequence—the slow narrowing of the practitioner's independent judgment—is invisible until it manifests as reduced confidence.
The asymmetry between the time saved and the time lost is crucial. Four hours of tedium for ten minutes of formative difficulty is not an efficient trade by production metrics. But the ten minutes are worth more than the four hours by growth-model metrics because the ten minutes are the mechanism through which the capacity to direct the four hours intelligently is built. Remove the mechanism and the capacity depletes—not immediately, not visibly, but structurally. A society systematically trading formative difficulty for productive output is a society consuming its cognitive capital without replenishing it.
The case generalizes. In law, the research assistant using AI to draft briefs saves hours of citation work but loses the formative difficulty of discovering which cases actually matter, which arguments actually persuade, which logic actually holds under scrutiny. In medicine, the resident using AI diagnostic support saves time on differential diagnosis but loses the formative difficulty of reasoning through ambiguous symptoms until the pattern resolves. In writing, the author using AI to generate drafts saves the struggle of finding words but loses the formative difficulty through which thinking clarifies itself on the page. Every domain has its ten minutes embedded in its tedium, and every domain is currently trading the ten minutes for the four hours without noticing the trade.
Origin
The ten-minutes framework emerged from the Trivandrum training case documented in The Orange Pill—Edo Segal's observation of twenty engineers achieving twenty-fold productivity gains. The Orange Pill celebrated the four hours saved. Franklin's framework demands accounting for the ten minutes lost. The case became paradigmatic in the Franklin simulation because it captures with precision the gap between what the production model measures and what the growth model values. The example has been adopted in workplace training materials, technology ethics courses, and organizational frameworks attempting to preserve developmental opportunities within AI-augmented workflows.
Key Ideas
Formative difficulty is contextual, not schedulable. The ten minutes of unexpected resistance forcing understanding cannot be replicated by adding practice time—they emerge from friction of real work and stop when friction is removed.
Production model measures four hours; growth model measures ten minutes. The asymmetry reveals the trade: tedium for formative difficulty, efficiency for developmental experience, output for the mechanism through which judgment renews itself.
The loss is invisible until confidence erodes. The engineer notices the gap in her judgment only months later, when making architectural decisions with reduced confidence she cannot explain—the depletion delayed, the cause obscured.
The mechanism applies across domains. Law, medicine, writing—every knowledge domain has formative difficulty embedded in tedious work, and every domain is currently trading the mechanism for the output without recognizing the trade.
Cognitive capital consumed without replenishment. A society systematically eliminating formative difficulty is a society depleting the understanding built by previous generations without creating conditions for the next generation to build their own.
Appears in the Orange Pill Cycle
Further reading
- Ursula Franklin, The Real World of Technology (1989)
- K. Anders Ericsson, 'Deliberate Practice and Acquisition of Expert Performance' (1993)
- Robert Bjork and Elizabeth Bjork, 'Making Things Hard on Yourself, But in a Good Way' (2011)
- Patricia Benner, From Novice to Expert (1984)
- Gary Klein, Sources of Power (1998)