Business novel as pedagogy is Ching's deliberate adoption and extension of the teaching format eliyahu-goldratt pioneered with "The Goal" (1984). Rather than presenting management theory as abstraction, both Goldratt and Ching embed it in narrative — following characters through recognizable workplace crises, letting readers learn through story rather than lecture.
Goldratt's Innovation
"The Goal" was a genuine publishing anomaly when it appeared: a novel about a plant manager whose factory is failing, written as page-turning fiction, structured to teach the Theory of Constraints through drama rather than exposition. The protagonist, Alex Rogo, learns TOC through conversations with his mentor Jonah — a thinly disguised Goldratt — across the course of a crisis.
The format works because stories embed concepts in context. Readers don't just learn what the five focusing steps are; they watch a character discover why they matter, feel the frustration of improving the wrong thing, and experience the relief of finding the actual constraint. Abstract principles become emotionally anchored.
Ching's Adoption and Variations
Ching makes this format central to his practice from his first substantial publication. His variations on the form:
The Pedagogical Commitment
Ching explicitly positions the format as a choice, not just a preference. The alternative — technical TOC writing of the kind produced by practitioners like William Dettmer or Eli Schragenheim — is rigorous but inaccessible to most working managers and developers. Ching's argument is that if the goal is to get more people using TOC, accessibility matters more than comprehensiveness.
The format also reflects the influence of Ching's mentor-figure relationship with Goldratt himself, documented in six-lessons-with-eli-goldratt. Goldratt taught through questions and dialogue; the business novel format is the written analogue of that Socratic approach.
This connects to bottleneck-thinking as brand strategy: Ching's books are designed to be the entry point for audiences who would never pick up a management textbook, turning toc-for-software-development into something a developer can recommend to their project manager without a follow-up explanation.