In the twentieth century, two groups of people figured out how to turn ordinary performance into extraordinary results.
One group studied people. The other studied processes. For over a hundred years, they never talked to each other.
That gap—between developing people and designing work—is the most expensive problem in business today. It's also the problem that Deliberate Work was built to solve.
Lineage One
The Practice Tradition: How Do I Get Better?
The question is older than you'd think.
In 1869, Sir Francis Galton published Hereditary Genius, the first systematic attempt to study exceptional performance scientifically. His conclusion: genius is inherited. Eminence runs in families because of biology, not effort. Galton surveyed the lineages of judges, statesmen, scientists, and military commanders, and declared that natural ability was passed down under the same limitations as physical traits.
Galton was wrong about the answer. But he asked the right question: What makes some people exceptional? And by asking it with data instead of philosophy, he launched the scientific study of expertise. He also, without intending to, established the orthodoxy that would take a century to dismantle—the idea that exceptional performance is fundamentally about who you are, not what you do.
1897–1899 — Bryan & Harter
Three decades later, two researchers in Indiana started chipping away at Galton's orthodoxy. William Lowe Bryan and Noble Harter published the first empirical study of skill acquisition in a real work environment. They tracked telegraph operators at railroad dispatch offices and Associated Press bureaus as they learned to send and receive Morse code.
What they documented changed the conversation. Skill develops in distinct phases. Operators first learned individual letters, then automated letter recognition to perceive words, then automated word recognition to grasp entire sentences and message meaning. Each phase produced a measurable learning curve—rapid improvement followed by a plateau where progress seemed to stall. But the plateaus weren't walls. They were transitions. The operator was automating lower-level skills to free cognitive capacity for higher-level pattern recognition.
Bryan and Harter called it a "hierarchy of habits"—the idea that mastery requires building layers of automated skill, each one freeing mental bandwidth for the next. This was the first evidence that expertise isn't just "more of the same." Getting better requires qualitative shifts in what you're paying attention to. And mere repetition isn't enough to produce them.
1973 — Simon & Chase
Nearly seventy years later, Herbert Simon picked up the thread. Simon was arguably the most cross-disciplinary thinker of the twentieth century—a political scientist, economist, computer scientist, and psychologist who won a Nobel Prize, a Turing Award, and contributed foundational ideas to half a dozen fields. In the early 1970s, working with William Chase at Carnegie Mellon, Simon turned his attention to expertise.
Chase and Simon studied chess players, comparing how masters and novices perceived the same board positions. They discovered that masters didn't think more moves ahead or calculate faster. They saw the board differently. Where a novice saw individual pieces, a master saw meaningful patterns—"chunks" of pieces that formed recognizable strategic configurations. Experts accumulate thousands of these chunks over years of intensive study, which is why there was no chess grandmaster who had achieved mastery without roughly a decade of dedicated effort. The "ten-year rule" was born.
What makes Simon essential to the Deliberate Work story goes beyond his expertise research. Simon's other career was organizational theory. His 1947 book Administrative Behavior is foundational to management science. His concept of "bounded rationality" shaped how we think about work, coordination, and system design. His Sciences of the Artificial proposed a "science of design" for building rational, implementable systems. Simon was simultaneously feeding both intellectual traditions—the practice tradition through his expertise work with Chase, and the systems tradition through organizational theory. He was the person best positioned to connect them. He didn't. They stayed in separate compartments.
1985 — Benjamin Bloom
A decade after Chase and Simon's chess studies, Benjamin Bloom led a landmark investigation into talent development. Published as Developing Talent in Young People, Bloom's team interviewed 120 elite performers across six domains—concert pianists, sculptors, Olympic swimmers, tennis players, mathematicians, and neurologists—to understand how world-class ability actually develops over a lifetime.
Bloom identified three phases. In the first, children explored playfully, guided by encouraging parents and early teachers. In the second, they became serious, working with technically skilled coaches and committing substantial time to structured practice. In the third, they pursued mastery with master-level teachers, dedicating themselves fully to their craft. Bloom showed that excellence follows a developmental architecture—not a random accumulation of hours, but a structured progression through stages, each with different requirements for mentorship, motivation, and commitment. He mapped the journey but didn't define what specific kind of practice actually drives improvement at each stage.
1993 — K. Anders Ericsson
Then, in 1993, a Swedish psychologist named K. Anders Ericsson published the paper that would reshape how the world thinks about expertise. Ericsson had come to Carnegie Mellon in the late 1970s as a postdoctoral fellow, where he worked with Herbert Simon on verbal protocol analysis—rigorous methods for studying how people actually think through problems—and with Bill Chase on memory expertise, the famous digit-span experiments that showed ordinary college students could achieve extraordinary memory through structured practice. Simon gave him the methodological toolkit. Chase gave him the direct catalyst: if structured practice could produce a thousand-percent improvement in memory, what else could it do?
But Ericsson took the question further than anyone before him. Chase and Simon had shown that expertise requires roughly ten years of intensive study. Bryan and Harter had shown that improvement requires breaking through plateaus. Bloom had shown that development follows phases with increasing demands. Ericsson asked the sharper question: What specific characteristics of practice actually drive improvement?
Studying violinists at a Berlin music academy, he found that what separated the best from the merely good wasn't total hours of playing. It was the accumulated hours of a very specific kind of practice—practice that was individualized, coach-directed, focused on weaknesses, and structured around immediate feedback. He called it deliberate practice. The idea was powerful and precise: expertise isn't born, it's built. And it's built through a process that can be defined, measured, and replicated. Ericsson had answered Galton. Ability isn't inherited. It's constructed—deliberately.
Malcolm Gladwell turned this into the "10,000 hour rule" in Outliers in 2008, which oversimplified the research but put "deliberate practice" into the mainstream vocabulary. Geoff Colvin's Talent is Overrated extended it into business settings. Angela Duckworth connected it to grit. Cal Newport wove it into his Deep Work philosophy. Daniel Coyle studied "talent hotbeds" where disproportionate skill development occurred. James Clear's Atomic Habits came the closest to bridging toward systems thinking—his framework for environment design, habit stacking, and identity-based change gestures at the system level—but ultimately his unit of analysis remained the individual building better personal habits, not the organization designing better work. Tim Ferriss approached from the opposite direction: The 4-Hour Workweek was fundamentally about designing systems—automation, delegation, elimination—to remove the human bottleneck. His later The 4-Hour Chef explicitly engaged with meta-learning and deliberate practice principles. Ferriss touched both traditions, but his lens was always personal optimization, not organizational design.
All of these thinkers made valuable contributions. But they all shared one fundamental assumption: the unit of analysis is the individual. The question they were all trying to answer was the same:
How do I get better?
And for structured domains—music, chess, athletics, surgery—the framework worked beautifully. These are domains with clear performance metrics, established training methods, qualified coaches, and immediate feedback.
Then people tried to apply it to business. And the framework hit a wall.
Ericsson himself used a telling example in a 2007 Harvard Business Review article. Radiologists, he observed, have been diagnosing breast cancer at roughly 70% accuracy for decades. Young radiologists learn by working alongside more experienced ones—who are themselves only 70% accurate. Individual practice without system redesign produces a ceiling, not a trajectory.
Ericsson's proposed solution was still individual: practice with a verified case library for immediate feedback. A better version of individual practice, but individual practice nonetheless.
By 2019, in what would be one of his final major papers, Ericsson acknowledged that the conditions required for true deliberate practice—structured domains, qualified teachers, established training methods—"were rarely met" outside the domains where his research originated. Business, with its ambiguity, delayed feedback, and ill-defined success metrics, simply didn't fit the model.
A major meta-analysis by Hambrick, Macnamara, and Oswald in 2020 landed an even harder blow: across 25 years of accumulated research, deliberate practice accounted for only 14% of the variance in performance. Environment, tools, cognitive factors, and system design accounted for the rest.
The most honest assessment came from Cedric Chin, a business practitioner and writer at Commoncog, who in 2019 publicly admitted that despite years of effort, he could not make deliberate practice work for his career. The framework, he concluded, was designed for structured domains and simply didn't map to the messy reality of knowledge work and business.
Here's the pattern every "deliberate practice at work" article follows: This framework is amazing → here's how it works for musicians and athletes → now let's apply it to business → it's really hard and doesn't map cleanly. Every author stalls at the same point. They all keep the unit of analysis as the individual and never make the leap to the system level.
Nobody asked the next question: What if the problem isn't the people? What if it's the work?
Lineage Two
The Systems Tradition: How Does the Process Get Better?
While Ericsson was studying violinists in Berlin, a completely separate intellectual tradition had been asking a different question for nearly a century.
There's an irony worth noting. The two traditions were entangled from the very beginning, and neither noticed.
Galton—who launched the practice tradition by asking what makes individuals exceptional—simultaneously contributed to the systems tradition without knowing it. His statistical innovations, including the correlation coefficient and regression to the mean, became foundational tools for Walter Shewhart's statistical process control at Bell Labs in the 1920s, which directly influenced W. Edwards Deming, which directly influenced Toyota. Galton's methods migrated into the systems lineage even as his conclusions about innate talent defined the orthodoxy that the practice lineage would eventually overturn.
And Bryan and Harter—the earliest researchers to study expertise empirically—were studying skilled workers inside a designed technological system. Telegraph operators worked in railroad dispatch offices with productivity demands, time pressure, and engineered infrastructure. Bryan and Harter looked at the individual and saw learning curves. They never looked at the system and asked whether the work itself could be designed to accelerate those curves. The insight was sitting right there. Nobody picked it up.
Instead, the systems tradition developed on a separate track entirely—and it goes back much further than most people realize.
~1320 — The Venice Arsenal
Six hundred years before Ford's Highland Park plant, the Venetian Republic was mass-producing warships on what may have been the first assembly line in history. The Arsenal employed standardized parts, specialized work groups, division of labor, and a sequential flow process: hulls were towed through a canal past a series of stations—one for masts, another for sails, another for arms—in what a visiting Spanish traveler described as early as 1436. At its peak in the early 1500s, the Arsenal employed 16,000 workers and could produce a fully equipped warship in a single day. It was the largest industrial complex in Europe before the Industrial Revolution.
The Arsenal proved that systematic work design could produce extraordinary output at scale. But the insight didn't travel. For centuries, shipbuilding remained the only industry to approach this level of systematic production.
1776 — Adam Smith
Smith gave the systems tradition its intellectual birth certificate. In the opening pages of The Wealth of Nations, he described a pin factory where ten workers, each performing a specialized operation, could produce 48,000 pins per day—compared to fewer than twenty pins each if working alone. Smith's insight was the division of labor itself: that breaking work into specialized steps doesn't just speed things up, it fundamentally transforms what's possible. Every systems thinker who followed—Whitney, Taylor, Ford—built on this foundation.
1798 — Eli Whitney
Whitney proposed manufacturing muskets with completely interchangeable parts—each component identical and swappable, rather than hand-fitted by a skilled gunsmith. Whether or not Whitney fully achieved interchangeability in practice, the principle was transformative. It meant that work could be decomposed into standardized, repeatable steps. Without interchangeable parts, there could be no assembly line. Whitney gave the systems tradition its critical enabling mechanism.
1867 — Chicago Meatpacking
The Chicago meatpacking houses of Swift and Armour created the disassembly line—carcasses moved along an overhead trolley past a series of workers, each performing a single cutting or packing operation. Ford engineer William "Pa" Klann visited Swift & Company's slaughterhouse, saw the efficiency of one person removing the same piece over and over, and brought the idea back to Highland Park. Ford himself later acknowledged: "The idea came in a general way from the overhead trolley that the Chicago packers use in dressing beef." Ford's great innovation wasn't the concept of a moving line—it was reversing the direction. Instead of taking apart, he put together.
1911 — Frederick Winslow Taylor
Taylor did for work design what Ericsson would later do for practice: he made it scientific. His Principles of Scientific Management proposed that every task could be studied, measured, optimized, and standardized. Time and motion studies broke work into its smallest components. Managers would design the optimal method; workers would execute it.
Taylor's contribution to the systems tradition was immense—he proved that work itself could be engineered. But his blind spot was equally immense, and it would define the systems tradition's recurring failure for the next century. Taylor explicitly separated thinking from doing: managers design, workers execute. The knowledge lives in the system, not in the person. This dehumanizing split—brilliant process design that treats people as interchangeable mechanisms—runs like a fault line through Ford, through early McDonald's, through every Lean implementation that optimizes the flowchart while ignoring the humans inside it.
1913 — Henry Ford
Ford took every thread—Smith's division of labor, Whitney's interchangeable parts, the meatpackers' moving line, Taylor's scientific optimization—and wove them into something none of his predecessors had achieved. The moving assembly line at Highland Park combined continuous flow, specialized stations, and standardized components into a single integrated system. Model T assembly time dropped from 12.5 hours to 93 minutes. Ford didn't invent any single element. He synthesized them. And the synthesis was what made the assembly line revolutionary.
Ford proved something the practice tradition never considered: you can design work so the system delivers consistent results, regardless of individual talent.
But Ford's insight came with a brutal cost. The work was so dehumanizing that in 1913 alone, Ford had to hire 52,000 workers to maintain a workforce of 14,000. His famous $5/day wage wasn't generosity—it was a retention band-aid for work that consumed people. Ford designed extraordinary systems but treated people as interchangeable components.
1948 — The McDonald Brothers
Richard and Maurice McDonald closed their profitable drive-in restaurant for three months and reopened with something radically different: the Speedee Service System. They slashed the menu to nine items. Standardized every order down to the number of pickles. Specialized every task. Redesigned the kitchen for flow.
The result: faster service, lower prices, higher volume, and zero dependence on finding skilled short-order cooks. The McDonald brothers proved that Ford's principles weren't limited to manufacturing. You could systematize service delivery.
1955 — Walt Disney
Disney took it further still—into experience design. Every touchpoint orchestrated. Backstage and onstage separated. "Cast members" following carefully designed scripts and systems. The magic wasn't in finding magical people. It was in designing an environment where the experience was consistently excellent.
1984 — G. Lynn Shostack
Shostack formalized this thinking in a Harvard Business Review paper titled "Designing Services That Deliver." She argued that services fail not because of human incompetence, but because of the lack of systematic method for design and control. She named only two organizations who had gotten it right: McDonald's and Walt Disney.
Shostack's diagnosis was prophetic. She saw the problem with perfect clarity forty years ago. But her solution—service blueprinting—remained a design tool. It mapped services. It never became an operating system for running them.
1950s–70s — Toyota
The Toyota Production System took Ford's systems thinking and fixed its fatal flaw. Toyota added two principles Ford never considered: continuous improvement (kaizen) and respect for people. Workers weren't just executing the process—they were empowered to stop the line, identify problems, and improve the system itself. Standard work wasn't a ceiling imposed on people; it was a baseline from which they drove improvement.
Toyota came the closest to synthesis. But even Toyota, which came closer than anyone to bridging the gap, never connected its operational philosophy to the expertise research happening in cognitive psychology. The Toyota Production System inherited Ford's mechanical lineage and enriched it with human agency—but it did so independently, without reference to what Ericsson, Bloom, or Simon's expertise research had discovered about how people actually develop skill. And translating TPS from the factory floor to services and knowledge work has remained the great unsolved challenge of the Lean movement for decades.
The systems tradition had its own wall: extraordinary process thinking that struggled to cross the boundary from manufacturing to the domains where most people actually work.
The Gap Between the Lineages
Here's what happened over more than a century: both traditions failed at exactly the same boundary, for opposite reasons.
The Practice Tradition's Failure
From Galton through Ericsson, the unit of analysis was always the individual. No matter how much you train the radiologist, the roofing crew, or the sales team—if the work itself isn't designed to apply, reinforce, and build on what they learn, the training doesn't transfer. Individual development without system design produces heroes who burn out, not organizations that sustain excellence.
The Systems Tradition's Failure
Often treated people as interchangeable components in a machine. Taylor separated thinking from doing. Ford's assembly line and McDonald's Speedee System produced remarkable consistency, but at the cost of dehumanizing the work. And when Lean consultants tried to bring factory thinking into services, the translation broke down.
The Bridge That Was Never Built
The person best positioned to connect both traditions was Herbert Simon. His chess expertise work with Chase shaped the practice tradition's understanding of how experts think. His organizational theory influenced the systems thinking that runs through operations research, management science, and the quality movement. And his methodological collaboration with Ericsson gave a young postdoc the tools he would later use to define deliberate practice. Simon literally worked in both worlds—but he kept them in separate notebooks. The bridge figure never built the bridge.
The practice people knew how to develop people but had no framework for the work surrounding them. The systems people knew how to design processes but often ignored the humans inside them.
Each tradition held half the answer. Neither alone could solve the problem that matters most to business owners: How do you produce excellent outcomes consistently, without depending on heroic effort from a few exceptional people?
The Convergence
Where the Two Lineages Meet
I didn't discover this gap by reading about it. I lived on both sides of it.
The Practice Lineage, Lived
As a competitive speed skater, I trained at the national level, finishing as the national championship overall runner-up and setting national records along the way. Every session structured. Every stride analyzed. I lived what Ericsson described. Later, as a ski racing coach, I applied those same principles to developing young athletes—and won a Michigan state championship doing it.
The Systems Lineage, Lived
In high school, I spent half of every school day in Pinckney, Michigan's cooperative Robotics and Automation program—programming industrial robots and PLCs, designing workcells. Two years in a row, our workcells won Best of Show. From there I went straight into industrial automation. The lesson was always the same: in a well-designed system, the outcome is precise because the system is precise.
When I moved into building and consulting with businesses, the gap between these two worlds became impossible to ignore. I would see business owners pour money into training their teams—better sales training, better project management courses, better leadership development—and watch the investment evaporate within weeks because the work itself wasn't designed to absorb or reinforce any of it. The training was deliberate. The work was not.
I would also see companies implement Lean or process improvement initiatives that optimized workflows on paper but ignored the people executing them. The processes looked efficient. The results were mediocre. Because the systems were designed for compliance, not for development.
Deliberate Practice asks
How do I get better?
Systems Design asks
How does the process get better?
Deliberate Work asks
How does the work itself get better?
The work is not just the process, and it's not just the people. It's the system, the people, and the feedback loops that connect them. Design all three together, and you get something neither tradition could produce alone: an organization where the system produces excellence and the people within it continuously develop.
What Deliberate Work Looks Like in Practice
This isn't abstract theory. Deliberate Work is built on specific, implementable principles drawn from both traditions.
Value Stream Design
Maps the work from trigger to outcome across two parallel dimensions: the customer experience—every touchpoint, interaction, and moment of value delivery that the customer sees—and the organizational experience—every step, handoff, and decision that produces it behind the scenes. Disney understood this intuitively: the guest experience (onstage) and the operational system (backstage) are two views of the same architecture. Shostack formalized it with service blueprinting, diagramming both what the customer encounters and the invisible processes that support it.
Deliberate Work takes this further. A Value Stream Design doesn't just map both experiences—it connects them. Every internal step has a clear purpose tied to a specific customer outcome. Every feedback mechanism serves double duty: it tells the person executing the work how they're performing and it surfaces whether the customer is actually receiving what was promised. Toyota would recognize the flow. Shostack would recognize the blueprint. But instead of stopping at the map, Deliberate Work turns it into the operating system for daily execution—one where the system that delivers the customer experience and the system that develops the people inside it are the same system.
Standard Work as Baseline, Not Ceiling
Ford and McDonald's used standardization to constrain workers. Toyota used it as a foundation for improvement. Deliberate Work follows Toyota's lead: standard work captures today's best known method, and then provides the structured environment for people to improve it. This is where Ericsson's practice principles re-enter the picture—embedded in the work itself rather than isolated in a training program. Bryan and Harter's hierarchy of habits, built into the design of the work.
Embedded Feedback Loops
Ericsson identified immediate feedback as essential to deliberate practice. In most businesses, feedback is delayed, ambiguous, and disconnected from the work. Deliberate Work builds feedback into the workflow—not as a performance review, but as a natural property of how the work operates.
Consider the radiologists stuck at 70% from earlier. Ericsson's solution was individual: practice with a verified case library. A Deliberate Work approach asks a different question entirely—not "how do we get each radiologist to practice better?" but "how do we redesign the work so that feedback is a natural property of the system, not something individuals have to seek out on their own time?" The specific answer depends on the domain. The shift in question is what matters.
Workflow Orchestration
Connects these elements into a coherent operating rhythm. The work flows. People develop. The system improves. Not because someone heroically manages all of it, but because the work was designed to produce these outcomes.
Geoff Colvin described a company that created a simulation of its own operations—production, packing, shipping. Teams ran 12 weeks of simulated operations in five-hour sessions, experimenting with new solutions. Monthly revenue loss dropped from $700,000 to under $50,000 within two years. Colvin framed this as organizations "applying deliberate practice." But look closer: what actually happened was systematic work redesign with embedded practice. That's not deliberate practice applied to organizations. That's Deliberate Work.
Why This Matters Now
The lineage matters because it reveals that Deliberate Work isn't a buzzword or a new spin on existing ideas. It's the resolution of a conversation that two intellectual traditions have been having—separately—for over a century.
Deliberate Practice proved that expertise is built, not born. That was revolutionary. Systems Design proved that excellence can be engineered into the work itself. That was equally revolutionary. But for decades, the people studying how individuals improve and the people studying how systems improve never connected their work—even when, as with Simon, the same person worked in both traditions.
The result is the landscape most business owners inhabit today: they invest in training that doesn't transfer, implement processes that ignore the humans executing them, and depend on heroic effort from a few key people to hold it all together. They're stuck choosing between developing their people and designing their systems—when the answer requires both.
Design the work deliberately, and you don't have to choose between great people and great systems. You get both.
That's not genius. It's not a brilliant flash that can never be duplicated—which is exactly what Shostack said breakthroughs in service delivery always seemed to be. It's a methodology. It can be learned, applied, and scaled. And it's long overdue.
Go Deeper
The methodology. The book.
Deliberate Work: Designing How Your Business Actually Runs takes these principles and turns them into a playbook. Value stream design, standard work, workflow orchestration—everything you need to move from heroics to systems.
Get Early AccessSee the framework in action
The blog applies Deliberate Work thinking to real companies—the same ones that shaped these two lineages.
🚗
Henry Ford: The Assembly Line
The system that started it all.
🍟
McDonald's: The Original OS
From factory to service delivery.
📖
Introducing Deliberate Work
The full methodology explained.
References
Bloom, B. S., Ed. (1985). Developing Talent in Young People. Ballantine Books.
Bryan, W. L. & Harter, N. (1897). "Studies in the Physiology and Psychology of the Telegraphic Language." Psychological Review, 4(1), 27–53.
Bryan, W. L. & Harter, N. (1899). "Studies on the Telegraphic Language: The Acquisition of a Hierarchy of Habits." Psychological Review, 6(4), 345–375.
Chase, W. G. & Simon, H. A. (1973). "Perception in Chess." Cognitive Psychology, 4(1), 55–81.
Chin, C. (2019). "The Problems with Deliberate Practice." Commoncog.
Clear, J. (2018). Atomic Habits: An Easy & Proven Way to Build Good Habits & Break Bad Ones. Avery/Penguin.
Colvin, G. (2008). Talent is Overrated: What Really Separates World-Class Performers from Everybody Else. Portfolio/Penguin.
Coyle, D. (2009). The Talent Code: Greatness Isn't Born. It's Grown. Here's How. Bantam Books.
Duckworth, A. (2016). Grit: The Power of Passion and Perseverance. Scribner.
Ericsson, K. A., Krampe, R. Th., & Tesch-Römer, C. (1993). "The Role of Deliberate Practice in the Acquisition of Expert Performance." Psychological Review, 100(3), 363–406.
Ericsson, K. A., Prietula, M. J., & Cokely, E. T. (2007). "The Making of an Expert." Harvard Business Review, July–August 2007.
Ericsson, K. A., & Harwell, K. W. (2019). "Deliberate Practice and Proposed Limits on the Effects of Practice on the Acquisition of Expert Performance." Frontiers in Psychology, 10, 2396.
Ferriss, T. (2007). The 4-Hour Workweek: Escape 9–5, Live Anywhere, and Join the New Rich. Crown Publishers.
Ferriss, T. (2012). The 4-Hour Chef: The Simple Path to Cooking Like a Pro, Learning Anything, and Living the Good Life. Houghton Mifflin Harcourt.
Galton, F. (1869). Hereditary Genius: An Inquiry into Its Laws and Consequences. Macmillan and Co.
Gladwell, M. (2008). Outliers: The Story of Success. Little, Brown and Company.
Hambrick, D. Z., Macnamara, B. N., & Oswald, F. L. (2020). "Is the Deliberate Practice View Defensible? A Review of Evidence and Discussion of Issues." Frontiers in Psychology, 11, 1134.
Newport, C. (2016). Deep Work: Rules for Focused Success in a Distracted World. Grand Central Publishing.
Ohno, T. (1988). Toyota Production System: Beyond Large-Scale Production. Productivity Press.
Shostack, G. L. (1984). "Designing Services That Deliver." Harvard Business Review, January–February 1984.
Simon, H. A. (1947). Administrative Behavior: A Study of Decision-Making Processes in Administrative Organization. Macmillan.
Simon, H. A. (1969). The Sciences of the Artificial. MIT Press.
Smith, A. (1776). An Inquiry into the Nature and Causes of the Wealth of Nations. W. Strahan and T. Cadell.
Sonnenberg, M., & Seidel, V. (2022). "Expertise Development in the Business-to-Business Sales Domain." Vocations and Learning, 16, 63–91. Springer.
Taylor, F. W. (1911). The Principles of Scientific Management. Harper & Brothers.
Joe Minock is the founder of The Deliberate Company and creator of the Deliberate Work methodology. His background spans competitive athletics at the national level, industrial robotics and automation, and twenty-five years of building and consulting with businesses across industries. He writes at DeliberateWork.com.