In 1995, Steve Jobs sat down with the technology journalist Robert Cringely for what was supposed to be a routine documentary interview. Jobs was 40. He was running NeXT. He had not yet returned to Apple. The bulk of the interview was shelved when only a small portion aired in the 1996 PBS documentary Triumph of the Nerds: The Rise of Accidental Empires.
The full 70-minute tape was rediscovered in a garage in 2011, one month after Jobs died. It was released as a theatrical documentary called Steve Jobs: The Lost Interview. Buried in it is a story about accounting practices at Apple in the late 1970s that turns out to be the sharpest available framework for enterprise AI transformation in 2026.
The story
Cringely asked Jobs how he learned to run a company. Jobs answered with a specific story about how Apple’s accountants recorded costs when the company first moved out of the garage and into a proper factory in the late 1970s.
The accountants used a method called standard cost. They would set an estimated cost for a product at the beginning of a quarter. At the end of the quarter, they would reconcile that estimate against reality using something called a variance account. The method was standard practice across American manufacturing at the time. Every serious accountant used it. Every business school taught it.
Jobs kept asking a question that nobody could answer. Why do we do this?
The answer he kept getting was: Well, that’s just the way it’s done.
The six-month dig
Jobs did what almost no executive does. He spent six months digging into the actual reason behind the accounting practice. The answer he eventually reached was uncomfortable and clarifying.
The reason companies used standard cost accounting was that their information systems were not good enough to track actual costs in real time. The variance account was, in a specific technical sense, a workaround. The company was guessing at costs because it could not measure them. Then reconciling the guesses against reality at quarter-end.
Jobs’s specific observation: Nobody said it that way.
The accountants did not say we are guessing because our information systems are inadequate. They said this is how we do standard costing. The workaround had, over decades, hardened into an apparently self-justifying practice. The underlying limitation had become invisible. The response to the limitation had become the standard.
The Macintosh factory reset
When Apple designed the automated factory for the Macintosh in the early 1980s, Jobs made a specific decision. The factory would not carry forward the standard-cost workaround. It would be built with information systems capable of tracking actual costs in real time. It would know the cost of every component, every assembly step, every finished unit.
In Jobs’s own phrasing from the interview: we were able to get rid of a lot of these antiquated concepts and know exactly what something cost to the second.
The Macintosh factory in Fremont, California, opened in January 1984. It was, at the time, one of the most highly automated computer factories in the world. Its cost accounting was correspondingly precise. Because the underlying information problem had been solved, the workaround was no longer required. Because the workaround was no longer required, the folklore that had grown up around it was no longer required either.
The generalization Jobs made
Jobs then made a broader claim that is the reason this quote has survived thirty years and is the reason I am writing about it in 2026.
In business, a lot of things are — I call it folklore. They’re done because they were done yesterday and the day before.
The standard cost / variance accounting workaround was not unique. It was a specific example of a general pattern. Most business practices, in most companies, are folklore. They exist because they existed yesterday. The original reasons — the specific limitations they were designed to work around — have been forgotten. The workarounds have hardened into standards.
The corollary Jobs offered: if you’re willing to sort of ask a lot of questions and think about things and work really hard, you can learn business pretty fast. It’s not the hardest thing in the world. It’s not rocket science.
What Jobs was pointing at is that business execution is not intrinsically complicated. What makes it seem complicated is the accumulated folklore. Strip the folklore, and the underlying logic is tractable.
Folklore, mapped to the Mutation Readiness framework
In the Mutation Readiness diagnostic — the operational instrument of the Mutation transformation practice we run for enterprise leaders — folklore preservation shows up as a compound failure across three of the six dimensions the framework measures.
Signal Sensitivity — the ability to detect weak signals before lagging metrics confirm them. Jobs’s original signal was the accountants’ inability to explain why standard cost accounting existed. That was the weak signal. Six months of digging turned it into a lagging metric — a concrete finding about information systems. Organizations that suppress the why question at the standard-cost level are already scoring low on Signal Sensitivity. They will discover their folklore only when a competitor eliminates it.
Structural Flexibility — the ability to reshape faster than competitors can retool. The Macintosh factory reset in 1984 is Structural Flexibility made physical. Apple did not automate the workaround. Apple built a new structure without the workaround in it. Organizations that automate their existing processes with AI are, in this framework’s language, scoring high on speed and low on Structural Flexibility. They are producing the same organization, faster.
Ambidextrous Capital — the balance between exploiting proven operations and exploring uncertain bets. Jobs’s six-month dig was Ambidextrous Capital in action. The exploit path was to accept standard cost accounting and ship the Apple II. The explore path was to fund the six-month investigation that produced the Macintosh factory design. Most enterprises fund exploit exclusively and call the imbalance focus. The Mutation Readiness Index catches this imbalance directly.
The signals your organization is missing right now
The Jobs framework — folklore preservation — is not a diagnosis you receive from a consulting deliverable. It is a diagnosis you produce by asking, dimension by dimension, which weak signals your organization is currently ignoring.
The signals to look for, this quarter, in the language of the Mutation Readiness framework: which of your approval chains no longer connects to a real limitation. Which of your report formats has not been re-examined since the information system that required them was replaced. Which of your escalation trees preserves a routing pattern for a communication constraint that no longer exists. Every one of these is a Signal Sensitivity failure. Every one is producing a Mutation-Blind band on the diagnostic. And every one is fixable this quarter, if the six-month dig is authorized.
The 2026 application
Almost every process running inside almost every enterprise in 2026 is a folklore layer that was originally a workaround for a specific pre-AI limitation.
Approval chains exist because we could not verify decisions in real time. Managers had to review because there was no system that could check.
Standardized report formats exist because we could not query data dynamically. Reports had to be pre-defined because ad-hoc analysis was expensive.
Meeting cadences exist because we could not share context asynchronously. Weekly stand-ups existed because there was no other way to align.
Handoff protocols exist because we could not hold shared state across teams. Documentation had to exist because otherwise context was lost.
Escalation trees exist because we could not surface issues automatically. Someone had to know who to call because no system routed intelligently.
Vendor selection processes exist because we could not evaluate options at scale. Committees had to meet because there was no faster way.
Every one of these was, at its origin, a workaround for a specific limitation of the information systems of the era. Every one has hardened, over decades, into an apparently self-justifying practice. And in 2026, most enterprise AI transformations are automating each of these workarounds rather than eliminating them.
The specific failure mode
The failure mode is that most enterprise AI transformations preserve the folklore and speed it up.
The approval chain that existed because managers had to review is now faster because AI drafts the review. The standardized report is now produced automatically because AI generates the format. The meeting cadence is now supported because AI summarizes each session. The handoff protocol is now automated because AI carries the state.
None of this is transformation. This is folklore preservation with better tooling. The original limitation — the reason the process existed at all — has been solved. But because nobody asked why does this process exist?, the process itself was preserved and merely accelerated.
The Jobs framework says: the transformation is not to make the workaround faster. The transformation is to notice that the workaround is no longer required, and to build the new system without it. In the Mutation Readiness framework, that specific move — retire, don’t automate — is the shortest path from a Mutation-Blind band to a Mutation-Ready band. It is measurable. It is the Mutation Readiness Index moving in the right direction.
Three practical questions
One: for each major process in your organization, what specific pre-AI limitation was it originally designed to work around? If your team cannot answer this, the process is folklore. The people running it have forgotten the original reason. The workaround has hardened into a standard.
Two: which of those limitations has AI now removed? If the limitation is gone, the workaround is no longer required. Automating the workaround preserves the folklore. Eliminating the workaround produces the transformation.
Three: who in your organization is willing to do the six-month dig? Jobs’s specific discipline was that he was willing to spend half a year asking why about one accounting practice. Most executives are not willing to spend half a day. The willingness to dig is the rare capability. Not the intelligence. Not the tools. The willingness.
The closing thought
Jobs’s line at the end of the passage is the one I keep coming back to: It’s not the hardest thing in the world. It’s not rocket science.
Business, once the folklore is stripped, is tractable. What makes it feel impossible is the accumulated layer of practices that no one can defend on their merits — practices done because they were done yesterday and the day before. The Jobs discipline is to ask why, accept the six-month dig, find the actual answer, and then build the new system without the workaround the old answer required.
In 2026, enterprise AI transformation is being sold to senior leaders as an unprecedented, uniquely complex, technically demanding endeavor requiring specialized frameworks and expensive consultants. This framing is itself folklore. The underlying discipline was named by a 40-year-old Steve Jobs in 1995, on a tape that sat in a garage for sixteen years, referring to a story from a factory that opened in 1984.
Ask why. Do the dig. Find the workaround. When you build the new system, don’t carry the workaround forward.
The world has changed. The leaders who notice will be the ones the next decade is built around.
