Key Principle
A well-articulated job spec functions as military "commander's intent" — it enables autonomous decision-making at every level because employees share a common understanding of what progress the customer is trying to make. The job simultaneously tells you what to pursue and what NOT to pursue; the "not" side is equally valuable because it eliminates wasted deliberation. (Chapter 9)
This produces four organizational benefits: distributed decision-making without micromanagement, resource optimization through clear tradeoff criteria, employee inspiration grounded in customer struggle rather than abstract missions, and measurement aligned to customer progress rather than internal activity.
The primary threat is organizational drift. Start-ups organically organize around the customer's job, but growth forces specialization — layers of management, functional silos, efficiency metrics. The organizing unit silently shifts from the customer's job to internal products and processes. "Efficiency is only value creating when it is in the performance of a process that is creating customer value by fulfilling a high-priority job." (Chapter 9)
Why This Matters
Without a job as the organizing principle, companies default to products, features, and competitors as their unit of analysis. This produces three failure modes:
- Feature chase — Teams survey customers for desired features, receive expansive wish lists, then spend weeks debating prioritization with no compass. The debate is unresolvable because there is no shared understanding of what the customer is actually hiring the product to do. (Chapter 9)
- Misaligned metrics — Companies measure "all the stuff that was easy to measure because it rolled off our servers" rather than "whether we were improving customers' lives." (Chapter 9)
- Strategic drift — Internal metrics stay green while the company loses sight of what those metrics were originally designed to serve. Drift is invisible and is the mechanism by which the correlation-causation gap reopens inside successful companies.
Good Examples
OnStar's fifteen-second decision. During Hurricane Rita, OnStar employees autonomously decided to offer all services free to callers from crisis areas — a decision that took "about a fifteen-second conversation" with the CEO because it was so clearly aligned with the peace-of-mind job. Engineers voluntarily solved a complex algorithm for transmitting crash severity data to 911 responders — not because they were told to, but because "they knew what was at stake." (Chapter 9)
Amazon's minute-by-minute monitoring. Amazon monitors vast selection, low prices, and fast delivery in near-real-time. A shopping robot scours competitor prices twice daily and automatically lowers Amazon's price. This is extreme efficiency — but focused squarely on delivering the job, not on internal convenience. (Chapter 9)
SNHU's one critical metric. Southern New Hampshire University tracks one question above all: Would graduates do it all over again? As of early 2016, 95 percent said yes. The metric tracks customer progress, not institutional activity. (Chapter 9)
Counterpoints
Intuit's TurboTax trap. The team spent years optimizing the tax "interview" tool based on customer feature requests, when the actual job was to get taxes done without needing the interview at all. New GM Sasan Goodarzi reframed the job as "completing customers' taxes without their having to answer any questions or input any data," triggering immediate creativity. Even prefilling just one section of the questionnaire produced a noticeable uptick in completion rates. (Chapter 9)
Mission statements as false compasses. Organizations substitute noble-sounding generalities ("To help all people live healthy lives") for actionable direction. Employees cannot derive what to build, what to cut, or how to prioritize. A job spec provides the specific circumstance, struggle, and desired progress that employees can actually innovate against. (Chapter 9)
Unilever's too-broad mission. Helping children in emerging markets live to age five was too abstract to guide product design. But understanding the specific job — children need to kill germs but wash for only seven seconds — led to color-changing soap that turns color at ten seconds, making handwashing both effective and fun. The job's specificity made innovation possible. (Chapter 9)
Key Quotes
"We got into feature chase. Too often we'd go look at what customers were asking for and build it." — Scott Cook (Chapter 9)
"We weren't measuring what was most important to our customers. Because it's hard to measure. But it matters profoundly." — Scott Cook (Chapter 9)
"Efficiency is only value creating when it is in the performance of a process that is creating customer value by fulfilling a high-priority job." (Chapter 9)
Rules of Thumb
- The fifteen-second test: If a decision aligned to the job cannot be made quickly by a front-line employee, the job is not well-articulated enough to serve as commander's intent.
- Measure progress, not activity: The right metric is not "what is easy to measure" but "what tells us whether the customer is making progress."
- The "not" side is half the compass: A job spec that only tells you what to do is incomplete. It must also tell you what to refuse, cut, or ignore.
- Watch for invisible drift: When internal metrics are green but customer outcomes are declining, the organizing unit has silently shifted from the job to internal processes.
- Mission statements are not jobs: If you cannot derive daily tradeoff decisions from your guiding statement, it operates at the wrong level of abstraction.
Related References
- Building a Purpose Brand - External expression of job alignment
- core framework - Theory foundation
- Designing Experiences Around the Job - Designing experiences around the job
- What Makes a Valid Job - How to properly define and validate a job