elliot-stack 1.0.30 → 1.0.33

package/skills/estack-leadership-coach/references/doerr_measure-what-matters.md

@@ -0,0 +1,154 @@
+---
+name: doerr_measure-what-matters
+title: Measure What Matters
+author: John Doerr
+work_type: book
+type: synthesis
+last_fetched: 2026-05-20
+sources:
+  - https://www.whatmatters.com/
+  - https://www.whatmatters.com/the-book
+  - https://www.whatmatters.com/faqs/okr-meaning-definition-example
+---
+
+# John Doerr — *Measure What Matters*
+
+## Overview
+
+John Doerr's 2018 book formalizes the Objectives and Key Results (OKR) goal-setting system he learned from Andy Grove at Intel in the 1970s and later carried to Google, the Gates Foundation, Bono's ONE Campaign, and dozens of other organizations through Kleiner Perkins. The book argues that ideas are easy and execution is everything, and presents OKRs — paired with their people-side complement CFRs (Conversations, Feedback, Recognition) — as a structured, transparent, and verifiable system for turning ambition into outcomes.
+
+## Why this is in the vault
+
+This reference grounds the leadership-coach skill's stance on what a "good objective" looks like in a delegation brief, what counts as a real success criterion (vs. a vague aspiration), and how progress should be tracked between intake and post-mortem. Doerr's "Objective = WHAT" / "Key Result = HOW" framing is the cleanest available articulation of the principle the skill enforces in Phase 4 (build-brief) and Phase 5 (monitoring), and his "committed vs aspirational" distinction directly informs how the coach should respond when a leader sets a stretch goal versus a contractual deliverable. The book also provides the canonical narrative link between Doerr and Andy Grove, which connects this reference to `grove_high-output-management.md`.
+
+## Synthesis — core principles
+
+### Principle 1: Objectives are the WHAT; Key Results are the HOW
+
+Doerr's bedrock definition: an Objective is "simply WHAT is to be achieved, no more and no less. By definition, objectives are significant, concrete, action oriented, and (ideally) inspirational. When properly designed and deployed, they're a vaccine against fuzzy thinking — and fuzzy execution." Key Results "benchmark and monitor HOW we get to the objective. Effective KRs are specific and time-bound, aggressive yet realistic. Most of all, they are measurable and verifiable." Marissa Mayer's enforcement rule, quoted by Doerr: "It's not a key result unless it has a number."
+
+The practical test Doerr inherits from Grove: at the end of the period — typically a quarter — you can look at a Key Result and, "without any arguments," say yes or no. There is no gray area. If a stack of completed Key Results does not deliver the Objective, the OKR was poorly designed in the first place. This is the standard the leadership-coach uses when pressure-testing whether a delegation brief actually has a success criterion or just a wish.
+
+### Principle 2: Measure what matters — and only what matters (Focus & Commit)
+
+Superpower #1 in Doerr's framework is focus. OKRs force leaders to make hard choices about what matters most and equally hard choices about what doesn't. Doerr cites a 2009 Harvard Business School paper, "Goals Gone Wild," that catalogued destructive goal pursuit (Ford Pinto fuel tanks, Sears auto-repair gouging, Enron's inflated targets, the 1996 Everest disaster) — and concedes its caveats are real. The answer is not fewer goals but better-bounded ones: a short list of objectives, each with a small number of measurable key results, refreshed quarterly.
+
+The corollary, drawn from Edwin Locke's half-century of goal-setting research: "hard goals" outperform easy goals, and specific hard goals produce higher output than vaguely worded ones. The leadership-coach's bias against vague success criteria ("get the website launched," "improve the customer experience") is downstream of this evidence base.
+
+### Principle 3: Transparency and alignment — public OKRs from the CEO down
+
+Superpower #2 is alignment via transparency. In Doerr's words, "In an OKR system, the most junior staff can look at everyone's goals, on up to the CEO." Research he cites: 92 percent of working adults say they'd be more motivated to reach their goals if colleagues could see their progress; companies with highly aligned employees are more than twice as likely to be top performers; only 7 percent of employees fully understand their company's strategies. The fix is public, written, transparent goals that knit individual work to team efforts to the overall mission — vertically and horizontally.
+
+This is the structural argument for why a delegation brief should not live in the manager's head. If the goal isn't written and visible, the people doing the work cannot align with it, and the people watching it cannot meaningfully help when it goes off track.
+
+### Principle 4: Track for accountability — periodic check-ins, not annual reviews
+
+Superpower #3: OKRs are driven by data and animated by periodic check-ins, objective grading, and continuous reassessment — "all in a spirit of no-judgment accountability." When a key result is endangered, that triggers action: get it back on track, or revise, or replace it. The leadership-coach's monitoring phase is built on this rhythm. Sundar Pichai's Google still kicks off each quarter by grading the prior quarter's OKRs in front of the whole company; Larry Page personally spent two days per quarter, in Google's early years, reviewing every engineer's OKRs.
+
+The key move: tracking is decoupled from blame. The question at a check-in is "what does this key result need from us right now?" — not "who failed?"
+
+### Principle 5: Stretch — committed vs. aspirational OKRs
+
+Superpower #4 is stretch. Doerr explicitly distinguishes two baskets of OKRs at Google:
+
+- **Committed objectives** are tied to operational metrics (product releases, bookings, hiring, customers). They are set top-down or at the department level, and "in general, these committed objectives — such as sales and revenue goals — are to be achieved in full (100 percent) within a set time frame."
+- **Aspirational (stretch) objectives** "reflect bigger-picture, higher-risk, more future-tilting ideas. They originate from any tier and aim to mobilize the entire organization. By definition, they are challenging to achieve. Failures — at an average rate of 40 percent — are part of Google's territory."
+
+This is the principle that resolves the most common coaching tension between "set the bar high" and "set a bar you can hit." The answer is: pick which kind of OKR this is, and make that choice explicit. A leader who labels every objective "aspirational" loses operational discipline. A leader who labels every objective "committed" loses the ability to swing big without it being a referendum on competence.
+
+Doerr's framing of stretch, via Larry Page's "gospel of 10x": "The way Page sees it, a ten percent improvement means that you're doing the same thing as everybody else. You probably won't fail spectacularly, but you are guaranteed not to succeed wildly."
+
+### Principle 6: CFRs — Conversations, Feedback, Recognition — are the people-side of OKRs
+
+Part Two of the book introduces the complement to OKRs: continuous performance management via CFRs. Doerr defines them as:
+
+- **Conversations:** an authentic, richly textured exchange between manager and contributor, aimed at driving performance.
+- **Feedback:** bidirectional or networked communication among peers to evaluate progress and guide future improvement.
+- **Recognition:** expressions of appreciation to deserving individuals for contributions of all sizes.
+
+His thesis: OKRs without CFRs is metrics without humanity; CFRs without OKRs is conversation without a target. "If a conversation is limited to whether you achieved the goal or not, you lose context… On the other hand, if you don't have goals, what the heck are you talking about?" (Doug Dennerline, BetterWorks CEO, quoted by Doerr.) The five questions Doerr offers for ongoing manager-contributor conversations are directly usable as a check-in script:
+
+1. What are you working on?
+2. How are you doing; how are your OKRs coming along?
+3. Is there anything impeding your work?
+4. What do you need from me to be (more) successful?
+5. How do you need to grow to achieve your career goals?
+
+CFRs are also why Doerr recommends decoupling OKRs from compensation. When goals drive bonuses, contributors sandbag — they stop stretching and start playing defense.
+
+## Verbatim extracts
+
+> "An OBJECTIVE, I explained, is simply WHAT is to be achieved, no more and no less. By definition, objectives are significant, concrete, action oriented, and (ideally) inspirational. When properly designed and deployed, they're a vaccine against fuzzy thinking — and fuzzy execution.
+>
+> KEY RESULTS benchmark and monitor HOW we get to the objective. Effective KRs are specific and time-bound, aggressive yet realistic. Most of all, they are measurable and verifiable. (As prize pupil Marissa Mayer would say, 'It's not a key result unless it has a number.') You either meet a key result's requirements or you don't; there is no gray area, no room for doubt."
+> — Doerr, *Measure What Matters*, Chapter 1 ("Google, Meet OKRs")
+
+> "Ideas are easy. Execution is everything."
+> — Doerr, *Measure What Matters*, Chapter 1
+
+> "Now, the two key phrases . . . are objectives and the key result. And they match the two purposes. The objective is the direction: 'We want to dominate the mid-range microcomputer component business.' That's an objective. That's where we're going to go. Key results for this quarter: 'Win ten new designs for the 8085' is one key result. It's a milestone. The two are not the same. . . . The key result has to be measurable. But at the end you can look, and without any arguments: Did I do that or did I not do it? Yes? No? Simple. No judgments in it."
+> — Andy Grove, quoted by Doerr in Chapter 2 ("The Father of OKRs")
+
+> "Google divides its OKRs into two categories, committed goals and aspirational (or 'stretch') goals. It's a distinction with a real difference. Committed objectives are tied to Google's metrics: product releases, bookings, hiring, customers… these committed objectives — such as sales and revenue goals — are to be achieved in full (100 percent) within a set time frame. Aspirational objectives reflect bigger-picture, higher-risk, more future-tilting ideas… By definition, they are challenging to achieve. Failures — at an average rate of 40 percent — are part of Google's territory."
+> — Doerr, *Measure What Matters*, Chapter 12 ("Stretch for Amazing")
+
+> "The way Page sees it, a ten percent improvement means that you're doing the same thing as everybody else. You probably won't fail spectacularly, but you are guaranteed not to succeed wildly."
+> — Steven Levy, quoted by Doerr in Chapter 12
+
+## Notable cases / illustrations
+
+### The Grove origin story — Intel 1975
+
+Doerr arrived at Intel in the summer of 1975 as an intern, looking (in part) for an ex-girlfriend. He was invited into Intel's iOPEC seminar, taught by Andy Grove himself, where he first encountered formal OKRs. Doerr's own first OKR at Intel:
+
+> **Objective:** Demonstrate the 8080's superior performance as compared to the Motorola 6800.
+> **Key Results (as measured by…):**
+> 1. Deliver five benchmarks.
+> 2. Develop a demo.
+> 3. Develop sales training materials for the field force.
+> 4. Call on three customers to prove the material works.
+
+He typed it on an IBM Selectric and pinned it to his carrel for anyone walking by to read. He recalls feeling both focused and liberated: when colleagues came mid-quarter with new asks, "I felt I could say no without fear of repercussion. My OKRs backed me. They spelled out my priorities for all to see."
+
+Grove had built the system in 1971, three years into Intel's life, drawing on Peter Drucker's "management by objectives and self-control" from the 1954 book *The Practice of Management* but explicitly improving on classical MBOs: where MBOs were annual, private, top-down, and tied to compensation, Grove's OKRs were quarterly or monthly, public and transparent, often bottom-up, and (mostly) divorced from compensation. Doerr coined the acronym "OKR" from Grove's terminology and carried the system to Sun Microsystems in the early 1980s, then to ~50 Kleiner Perkins portfolio companies, then — in fall 1999 — to Google.
+
+This case is the load-bearing narrative link from this reference to `grove_high-output-management.md`. Doerr did not invent OKRs; he learned them from Grove and proselytized them.
+
+### Google's adoption, 1999
+
+In the fall of 1999, Doerr presented OKRs to roughly the entire Google company — about thirty people including Larry Page, Sergey Brin, Marissa Mayer, Susan Wojcicki, and Salar Kamangar — around a ping-pong table that doubled as their boardroom. Doerr's own OKR for the day:
+
+> **Objective:** Build a planning model for their company.
+> **Key Results:** (1) finish my presentation on time; (2) create a sample set of quarterly Google OKRs; (3) gain management agreement for a three-month OKR trial.
+
+Sergey's reaction, per Doerr: "Well, we need to have some organizing principle. We don't have one, and this might as well be it." Doerr stopped talking at the ninety-minute mark, on time. Nearly two decades later, every quarter at Google still opens with a company-wide OKR review.
+
+### Operation Crush — Intel, 1979–80
+
+The textbook stretch-goal case in the book. Faced with losing the 16-bit microprocessor market, Bill Davidow and Jim Lally set a single-year goal of 1,000 design wins for the 8086 — which got revised up to 2,000 (one win per salesperson per month, triple the prior year's pace). Reps were incentivized with a trip to Tahiti for two, and Lally added the stipulation that if any single rep in a district missed quota, the entire district lost the trip. Full-color Tahiti brochures arrived in salespeople's home mailboxes mid-year. Final count at year-end: 2,300+ design wins. The 8086 won the market and "Intel's future was assured."
+
+### Bono's ONE Campaign
+
+Doerr introduced OKRs to Bono and the ONE Campaign / DATA after the two organizations merged. Bono's account: "We had so many brilliant, gifted people, but our problem was way too many goals. A green revolution in Africa. Girls' education. Energy poverty. Global warming. We were all over the map." OKRs imposed the discipline of picking fights one at a time. David Lane, ONE's former CEO: "We needed a process of discipline to keep us from trying to do everything." Outcomes Doerr credits to the disciplined goal-setting era: ~$50 billion delivered for global health initiatives, 21 million people on antiretroviral therapy by 2017, AIDS-related deaths down 45% in a decade.
+
+### Gmail and 10x
+
+Original target for Gmail at launch: 100MB of storage (already an enormous upgrade over the 2–4MB norm). Larry Page pushed the team toward a true stretch objective. Gmail launched in 2004 with **1GB** of storage — up to 500x more than competitors. The category was reinvented. Doerr uses this as the canonical example of an aspirational OKR that nobody would have committed to but that, when set as a stretch, reshaped an entire market.
+
+## Where this is used in the skill
+
+This reference is new and not yet wired into phase files. Recommended placements (see report).
+
+## Sources (live-fetched on 2026-05-20)
+
+- [What Matters: Home (whatmatters.com)](https://www.whatmatters.com/)
+- [What Matters: Buy 'Measure What Matters'](https://www.whatmatters.com/the-book)
+- [What Matters: What is an OKR? Meaning, Definition & Examples](https://www.whatmatters.com/faqs/okr-meaning-definition-example)
+
+Primary content was synthesized from the full text of John Doerr, *Measure What Matters* (Portfolio/Penguin, 2018), supplied by the user as a PDF source file. All verbatim quotes are extracted from that source. Page numbers are not cited because the source PDF's pagination does not reliably map to the print edition.
+
+## Known gaps
+
+- No page numbers cited (PDF pagination unreliable against print edition).
+- Did not extract the full Adobe / Zume Pizza / Lumeris / MyFitnessPal / Intuit / Nuna / Remind chapters — these would deepen the "case library" if the coach ever wants more domain-specific real-world cases beyond Google, Intel, ONE, and the Gates Foundation.
+- The book's Resource appendices (Google's OKR Playbook, A Typical OKR Cycle, performance conversation scripts) were not extracted in detail — future pass could pull the Playbook verbatim as an operational artifact for Phase 4.

package/skills/estack-leadership-coach/references/ferriss_4hww.md

@@ -0,0 +1,189 @@
+---
+name: ferriss_4hww
+title: The 4-Hour Workweek (Expanded and Updated)
+author: Timothy Ferriss
+work_type: book
+type: synthesis
+last_fetched: 2026-05-21
+sources:
+  - https://fourhourworkweek.com/
+  - https://www.penguinrandomhouse.com/books/49081/the-4-hour-workweek-expanded-and-updated-by-timothy-ferriss/
+  - https://en.wikipedia.org/wiki/The_4-Hour_Workweek
+---
+
+# Timothy Ferriss — *The 4-Hour Workweek (Expanded and Updated)*
+
+## Overview
+
+Ferriss's 2007/2009 book pitches a "lifestyle design" alternative to the deferred-life plan. Its operating system is the **DEAL** framework — Definition, Elimination, Automation, Liberation — and within that framework, the most operationally useful idea for delegation is a strict ordering: **eliminate first, automate next, delegate last**. The book argues that handing a task to a person before stripping waste and applying systems is how managers convert their own bottleneck into someone else's billed hours.
+
+## Why this is in the vault
+
+This reference feeds **`phases/1-intake.md`**, where the coach pressure-tests whether a task is actually delegate-ready. Ferriss's sequence (eliminate → automate → delegate) is the canonical articulation of "don't delegate something that shouldn't exist or that a system can handle." It gives the coach explicit language to push back on leaders who jump to "I need to hand this off" without first asking *should this even be done?* and *can a rule, template, or tool do it?* The book also supplies a richly documented field case (Ferriss's own outsourcing experiment, and AJ Jacobs's *Esquire* piece embedded inside Chapter 8) that demonstrates what actually shows up on a leader's task list when they finally examine it — most of it should not have been on the list at all.
+
+## Synthesis — core principles
+
+### Principle 1: DEAL — the four-step lifestyle reset
+
+Ferriss frames the entire book around an acronym, laid out in the preface ("My Story and Why You Need This Book"):
+
+- **D for Definition** "turns misguided common sense upside down and introduces the rules and objectives of the new game."
+- **E for Elimination** "kills the obsolete notion of time management once and for all. It shows exactly how I used the words of an often-forgotten Italian economist to turn 12-hour days into two-hour days … in 48 hours. Increase your per-hour results ten times or more with counterintuitive NR techniques for cultivating selective ignorance, developing a low-information diet, and otherwise ignoring the unimportant."
+- **A for Automation** "puts cash flow on autopilot using geographic arbitrage, outsourcing, and rules of nondecision."
+- **L for Liberation** "is the mobile manifesto for the globally inclined."
+
+Ferriss notes that employees should *implement* the sequence as **DELA** (Liberation before Automation) but *read* it as DEAL — because the entrepreneurial logic is that eliminating waste must precede automating income, and automating income must precede the freedom-of-location move.
+
+### Principle 2: Eliminate before you automate, automate before you delegate
+
+This is the operational rule the leadership-coach skill draws on most. Ferriss states it directly in Chapter 8 ("Outsourcing Life"), under the section header "Delegation Dangers: Before Getting Started":
+
+> "Eliminate before you delegate.
+> Never automate something that can be eliminated, and never delegate something that can be automated or streamlined. Otherwise, you waste someone else's time instead of your own, which now wastes your hard-earned cash. How's that for incentive to be effective and efficient?"
+
+He says it twice on the same page for emphasis ("Did I mention to eliminate before you delegate?"). The logic is sequential and unforgiving:
+
+1. **Eliminate** — If the task produces no meaningful output, kill it. A task that shouldn't exist cannot be "delegated well" — it can only be propagated.
+2. **Automate** — If the task must exist but follows a rule, encode the rule. "Rules of nondecision" — templates, filters, autoresponders, standing policies — are cheaper and more reliable than a human running the same loop.
+3. **Delegate** — Only what survives elimination *and* resists automation is a legitimate handoff. Delegating earlier in the sequence converts the manager's wasted time into the assistant's wasted time, at real cash cost.
+
+Ferriss also opens the same section with Bill Gates: *"automation applied to an inefficient operation will magnify the inefficiency."* The point lands the same way whether the next link is a script or a person.
+
+### Principle 3: Pareto and Parkinson as the elimination engine
+
+Chapter 5 ("The End of Time Management: Illusions and Italians") makes the case that elimination is not optional and supplies two specific tools.
+
+**Pareto / 80-20.** Ferriss tells the story of discovering Vilfredo Pareto while working "15-hour days seven days per week" running BrainQUICKEN and applying two questions to everything in his life:
+
+> "Which 20% of sources are causing 80% of my problems and unhappiness?
+> Which 20% of sources are resulting in 80% of my desired outcomes and happiness?"
+
+The result, in his own description: *"I stopped contacting 95% of my customers and fired 2%, leaving me with the top 3% of producers to profile and duplicate. Out of more than 120 wholesale customers, a mere 5 were bringing in 95% of the revenue. I was spending 98% of my time chasing the remainder."* Two large customers who were "professional ball breakers" but contributed about 10% of revenue were also cut — *"The effect on my self-esteem and state of mind just wasn't worth the financial gain."*
+
+**Parkinson's Law.** Same chapter:
+
+> "Parkinson's Law dictates that a task will swell in (perceived) importance and complexity in relation to the time allotted for its completion. It is the magic of the imminent deadline. If I give you 24 hours to complete a project, the time pressure forces you to focus on execution, and you have no choice but to do only the bare essentials."
+
+Ferriss explicitly pairs the two: *"Limit tasks to the important to shorten work time (80/20). Shorten work time to limit tasks to the important (Parkinson's Law). The best solution is to use both together: Identify the few critical tasks that contribute most to income and schedule them with very short and clear deadlines."*
+
+For a delegation coach, this is diagnostic firepower for intake: most "I need to hand this off" tasks survive only because the calendar has space for them and no one has asked the 80/20 question.
+
+### Principle 4: Low-information diet and selective ignorance
+
+Chapter 6 ("The Low-Information Diet: Cultivating Selective Ignorance") extends elimination from tasks to inputs. The chapter's opening confession:
+
+> "I never watch the news and have bought one single newspaper in the last five years … I usually check business e-mail for about an hour each Monday, and I never check voicemail when abroad. Never ever."
+
+The principle, stated directly:
+
+> "It is imperative that you learn to ignore or redirect all information and interruptions that are irrelevant, unimportant, or unactionable. Most are all three."
+
+And the line that matters most for delegation coaching:
+
+> "Problems, as a rule, solve themselves or disappear if you remove yourself as an information bottleneck and empower others."
+
+Ferriss's counter-question to anyone who claims they need to "stay informed" is implicit but sharp: *informed for what specific decision?* If no decision rides on the input, the input is waste. Leaders who keep tasks on their plate "because I need to be in the loop" are usually claiming a loop they never close.
+
+### Principle 5: Interrupting interruption — batching and rules of nondecision
+
+Chapter 7 ("Interrupting Interruption and the Art of Refusal") catalogs three offenders — **time wasters** (ignorable with no consequence), **time consumers** (necessary but repetitive), and **empowerment failures** (someone needs approval to make something small happen). The third category is the delegation hinge: every time a subordinate has to ask permission for a small thing, the leader has failed to write the rule.
+
+The chapter's most famous prescription is email batching:
+
+> "Check e-mail twice per day, once at 12:00 noon or just prior to lunch, and again at 4:00 P.M. … Never check e-mail first thing in the morning. Instead, complete your most important task before 11:00 A.M. to avoid using lunch or reading e-mail as a postponement excuse."
+
+The chapter also models a template autoresponder that *trains* the rest of the world to batch with you ("Beg for forgiveness; don't ask for permission"). The underlying move — converting a stream of interruptions into a scheduled, bounded touch — is the same move that elimination and automation make on tasks.
+
+### Principle 6: Outsourcing as the *last*, not first, lever
+
+Chapter 8 ("Outsourcing Life: Off-loading the Rest and a Taste of Geoarbitrage") is the chapter that made the book famous, but it is also where Ferriss insists outsourcing must come *after* the prior two filters:
+
+> "Delegation is to be used as a further step in reduction, not as an excuse to create more movement and add the unimportant. Remember — unless something is well-defined and important, no one should do it."
+
+The chapter's structural argument is that hiring a remote assistant is, first and foremost, *"small-scale training wheels for the most critical of NR skills: remote management and communication"* — *"It is also a litmus test for entrepreneurship: Can you manage (direct and chastise) other people?"* The point is not the labor arbitrage. The point is that delegating forces the leader to write down what they actually want, which surfaces every task that shouldn't exist.
+
+The chapter is grounded in field cases (see "Notable cases" below) — Ferriss's own use of Brickwork and Your Man In India (YMII), and AJ Jacobs's *Esquire* article "My Outsourced Life" reprinted in full at the start of the chapter.
+
+## Verbatim extracts
+
+> "Never automate something that can be eliminated, and never delegate something that can be automated or streamlined. Otherwise, you waste someone else's time instead of your own, which now wastes your hard-earned cash."
+> — Ferriss, Chapter 8 ("Outsourcing Life"), section "Delegation Dangers: Before Getting Started"
+
+> "Eliminate before you delegate."
+> — Ferriss, Chapter 8, "Delegation Dangers: Before Getting Started"
+
+> "As soon as I remove myself as a bottleneck, profits increase 40%."
+> — Ferriss, preface, "Chronology of a Pathology" (entry: July 2004–2005)
+
+> "Problems, as a rule, solve themselves or disappear if you remove yourself as an information bottleneck and empower others."
+> — Ferriss, Chapter 6 ("The Low-Information Diet")
+
+> "Which 20% of sources are causing 80% of my problems and unhappiness? Which 20% of sources are resulting in 80% of my desired outcomes and happiness?"
+> — Ferriss, Chapter 5 ("The End of Time Management"), section "Pareto and His Garden"
+
+> "Parkinson's Law dictates that a task will swell in (perceived) importance and complexity in relation to the time allotted for its completion. It is the magic of the imminent deadline."
+> — Ferriss, Chapter 5, section "The 9–5 Illusion and Parkinson's Law"
+
+> "Limit tasks to the important to shorten work time (80/20). Shorten work time to limit tasks to the important (Parkinson's Law). The best solution is to use both together."
+> — Ferriss, Chapter 5
+
+> "Doing something unimportant well does not make it important. Requiring a lot of time does not make a task important."
+> — Ferriss, Chapter 5, section "Being Effective vs. Being Efficient"
+
+> "Check e-mail twice per day, once at 12:00 noon or just prior to lunch, and again at 4:00 P.M. … Never check e-mail first thing in the morning."
+> — Ferriss, Chapter 7 ("Interrupting Interruption"), section "Time Wasters: Become an Ignoramus"
+
+> "Becoming a member of the NR is not just about working smarter. It's about building a system to replace yourself."
+> — Ferriss, Chapter 8 ("Outsourcing Life")
+
+## Notable cases / illustrations
+
+### The BrainQUICKEN bottleneck — Ferriss's own elimination experiment
+
+In the preface's "Chronology of a Pathology," Ferriss describes 2004: BrainQUICKEN LLC was generating roughly $40K/month, but he was working "12-hour-plus days 7 days a week," took a "vacation" to Florence that he spent in an internet café "freaking out," and had a nervous breakdown his first morning in London after buying a one-way ticket out. The turn comes in the July 2004 entry:
+
+> "Four weeks turn into eight, and I decide to stay overseas indefinitely for a final exam in automation and experimental living, limiting e-mail to one hour each Monday morning. As soon as I remove myself as a bottleneck, profits increase 40%."
+
+Before the elimination experiment, an attempted sale of BrainQUICKEN had forced him to "simplify, eliminate, and otherwise clean house to make myself expendable. Miraculously, BQ doesn't fall apart, but both deals do." The deal collapse turned out to expose what mattered: he had already proven the business ran better without him in the loop, but he hadn't acted on it. The one-hour-Monday email rule was the action.
+
+The lesson for intake: the leader staring at a task list and asking *who should I hand this to?* is asking the wrong question. The first question is *does this need to happen at all, and does it need me involved?* Ferriss's own case is the cleanest illustration — the work that felt most urgent to delegate turned out to be work that produced more profit when nobody (including him) was doing it.
+
+### AJ Jacobs outsources his life — *Esquire*, reprinted in Chapter 8
+
+Chapter 8 opens with AJ Jacobs's "My Outsourced Life," reprinted in full from *Esquire* (Jacobs is editor-at-large). Jacobs hires two firms:
+
+- **Brickwork** (Bangalore) — CEO Vivek Kulkarni — assigns him **Honey K. Balani** as his "remote executive assistant" for *Esquire*-related work (research, formatting memos).
+- **Your Man In India (YMII)** — recommended by his friend Misha at dinner — assigns **Asha** to his personal life (paying bills, drugstore.com purchases, vacation reservations, even calling Cingular about his cell phone plan).
+
+Jacobs's case material is specifically valuable because it's mundane:
+
+- Honey produces a research file on *Esquire*'s Sexiest Woman Alive with "charts … section headers … a well-organized breakdown of her pets, measurements, and favorite foods (e.g., swordfish)." Jacobs's reaction: *"America is f*cked."*
+- Asha fields routine errands: bill paying, finding a Tickle Me Elmo for his son (she buys a Chicken Dance Elmo when the store is out — *"good decision"*).
+- Honey writes a polite rejection note to the Colorado Tourism Board, which keeps emailing Jacobs press releases: *"Currently, these mails are not serving right purpose for both of us. Thus, we request to stop sending these mails. We do not mean to demean your research work by this."* Jacobs calls it "the best rejection notice in journalism history."
+- Jacobs experiments with outsourcing arguments with his wife Julie ("she has lost her wallet twice in the last month. And she forgot to buy nail clippers for Jasper"). Asha softens the message into a love note and adds an e-card of two teddy bears hugging. Julie replies: "That's nice, sweetie. I forgive you."
+- Jacobs outsources his *worrying* to Honey about a stalled business deal. Honey responds: *"I will worry about this every day. Do not worry."* Jacobs: *"this alone was worth it."*
+
+What makes this case material useful for the coach: it is a complete inventory of what actually sat on Jacobs's task list — and almost all of it was either eliminate-able (the Colorado press releases), automate-able (bill pay, drugstore orders), or low enough stakes that a stranger in Bangalore could do it as well as he could. The cases are not heroics; they're a forensic accounting of work that didn't need to exist or didn't need him.
+
+### Ferriss's morning-in-Buenos-Aires snapshot — full automation
+
+Later in Chapter 8 ("At a Glance: Where You Will Be"), Ferriss describes a Monday morning routine — one hour of email after a Buenos Aires breakfast — with named assistants: **Sowmya** (finds a lost high-school classmate), **Anakool from YMII** (compiles Excel reports on retiree happiness and average annual hours worked), a third Indian VA (sets interviews, finds Kendo schools in Japan and salsa teachers in Cuba), plus **Beth** in Tennessee (fulfillment account manager, resolved ~24 client issues, coordinated California sales tax filing) and **Shane** at the credit card processor (handling deposits). Ferriss's costs: *"$4 U.S."* breakfast, *"$4–10 U.S. per hour"* for Indian outsourcers, domestic outsourcers paid on performance. *"Negative cash flow is impossible."*
+
+The snapshot is a worked example of what the eliminate → automate → delegate sequence looks like once it stabilizes: a leader whose remaining decision surface is one hour, once a week.
+
+## Where this is used in the skill
+
+- `phases/1-intake.md` — backs the question "is this task something to eliminate, automate, or delegate?" with Ferriss's explicit sequencing rule, the verbatim Chapter 8 quote, and the BrainQUICKEN / Buenos Aires case material as the inline "Real-world case" for Phase 1.
+
+## Sources (live-fetched on 2026-05-21)
+
+- [The 4-Hour Workweek — official site](https://fourhourworkweek.com/)
+- [The 4-Hour Workweek, Expanded and Updated — Penguin Random House](https://www.penguinrandomhouse.com/books/49081/the-4-hour-workweek-expanded-and-updated-by-timothy-ferriss/)
+- [The 4-Hour Workweek — Wikipedia](https://en.wikipedia.org/wiki/The_4-Hour_Workweek)
+
+Primary content (DEAL framing, "Chronology of a Pathology," Chapter 5 Pareto/Parkinson material, Chapter 6 Low-Information Diet, Chapter 7 email batching, Chapter 8 "Delegation Dangers" and the AJ Jacobs *Esquire* reprint) is drawn directly from the full user-supplied .docx of the Expanded and Updated edition (Crown Publishers, 2009). The URLs above were live-fetched in this session to confirm canonical author/title attribution and publisher metadata.
+
+## Known gaps
+
+- Page numbers were not preserved in the docx extraction, so citations are by chapter title and section heading rather than page. This is consistent with the skill's hard rule against fabricating page numbers.
+- "Your Man In India" / YMII later became GetFriday; the original *Esquire* article from AJ Jacobs uses the YMII name, which is the name used in Chapter 8. Ferriss's later blog material under tim.blog/outsourcing-life updates the brand but is not required to source the chapter content.

package/skills/estack-leadership-coach/references/gallup_engagement-research.md

@@ -0,0 +1,105 @@
+---
+name: gallup_engagement-research
+title: Gallup engagement research (body of work)
+author: Gallup, Inc.
+work_type: body of work
+type: synthesis
+last_fetched: 2026-05-20
+sources:
+  - https://www.gallup.com/workplace/349484/state-of-the-global-workplace.aspx
+  - https://www.gallup.com/workplace/697904/state-of-the-global-workplace-global-data.aspx
+  - https://news.gallup.com/businessjournal/182792/managers-account-variance-employee-engagement.aspx
+  - https://www.gallup.com/workplace/645416/key-insights-global-workplace.aspx
+---
+
+# Gallup — *Engagement research (body of work)*
+
+## Overview
+
+Gallup has measured employee engagement globally since 2005 via the Gallup World Poll, with the State of the Global Workplace annual report as its flagship publication and the Q12 engagement framework as its core instrument. The research consistently finds that the majority of workers worldwide are not engaged at work, that managers (not policies or pay) are the dominant variable explaining variance in engagement, and that engagement is causally tied to business outcomes including profitability, retention, and resilience during downturns.
+
+## Why this is in the vault
+
+This reference feeds Phase 3 (Enrollment), where the coach helps an owner-operator decide whether to give a person a real shot at running something — and how to frame the ask. Gallup's data backs three coaching moves: (1) framing engagement as a manager-shaped outcome rather than a personality trait of the team member, (2) anchoring the stakes (engagement gaps cost real money and real retention), and (3) reminding operators that "we need a better job market" or "we need better policies" is not the lever — the manager relationship is.
+
+## Synthesis — core principles
+
+### Principle 1: Engagement is a minority condition, globally
+
+In 2025, only 20% of employees worldwide were engaged at work, down from a peak of 23% in 2022–2023. 64% were not engaged (showing up, doing the minimum) and 16% were actively disengaged. The disengaged-majority pattern is not a recent phenomenon — Gallup's 2015 article reported 13% global engagement and noted the figure had been roughly stable for 12 years prior.
+
+The practical implication for an owner-operator: when you delegate to someone and they perform like a default employee — present but uninspired — that is the statistical baseline, not a personal failure of the team member. Doing nothing produces disengagement. Engagement requires deliberate design.
+
+### Principle 2: Managers account for ~70% of the variance in team engagement
+
+This is the headline finding from Gallup's analysis of business-unit engagement scores: "managers account for at least 70% of the variance in employee engagement scores across business units." The 2024 follow-up reinforces it — engagement is "driven more by having great managers at the business-unit level than by macroeconomic factors such as countries' labor policies and the vibrancy of their job markets."
+
+For the owner-operator, this is the lever. The person you delegate to will be engaged or disengaged primarily based on the quality of management they receive — which, until you build a managerial layer, is you. Hiring "better people" is not the first-order fix; managing them differently is.
+
+Gallup also finds that conventional promotion practices miss managerial talent in roughly 82% of hiring decisions for management roles, and that only about 18% of those currently in management roles demonstrate high natural talent for managing others. The implication: if the operator is trying to enroll someone into a leadership role, raw past performance is a weak predictor — explicit assessment of management aptitude matters more.
+
+### Principle 3: Engagement compounds into business outcomes
+
+Gallup's meta-analysis across 183,000+ business units in 53 industries and 90 countries finds teams in the top quartile of engagement achieve 23% higher profitability than those in the bottom quartile. The mechanism is downstream: better retention, better customer service, higher-quality output. For companies averaging 40% or lower turnover, bottom-quartile-engagement business units have 51% higher turnover than top-quartile — a gap that widened after 2020.
+
+The 2026 report estimates the global cost of low engagement at $10 trillion in lost productivity; the 2024 report (when engagement was at 23%) put the figure at $8.9 trillion. The number drifts with the underlying engagement rate, but the order of magnitude — trillions, not billions — has been consistent.
+
+For an enrollment conversation, this is the "why does this matter" frame: the cost of running an unengaged team is not abstract. It shows up as turnover, lost customers, and lower profit.
+
+### Principle 4: Engagement matters more in hard times, not less
+
+Gallup finds the relationship between engagement and business performance strengthens during recessions and disruptions. Engaged employees "double down" when the environment gets harder; disengaged employees feel like victims of circumstance and lose agency. Engaged-team business units are more resilient in turbulent environments and retain people better when retention gets difficult.
+
+The coaching implication: an operator who treats engagement as a "nice to have we'll get to after the next quarter" is exactly inverting the priority. The harder the operating environment, the more engagement determines who survives.
+
+### Principle 5: Job markets reduce active disengagement; only managers create engagement
+
+From the 2024 piece: in countries with better job markets, active disengagement is lower (bitter workers can leave). But the engagement rate itself isn't materially higher. Improving economic conditions shifts workers "from anger to indifference — from actively disengaged to not engaged — but not from indifference to inspiration."
+
+Translated to the operator's context: a hot labor market doesn't make a team engaged. It only changes whether the disengaged ones are leaving you for a competitor or staying and quietly resenting you. Engagement still has to be built locally, by the manager.
+
+### Principle 6: Managers themselves are increasingly disengaged
+
+The 2026 report flags a specific risk: manager engagement fell nine points since 2022, from 31% to 22%, with a five-point drop in the most recent year alone. In best-practice organizations, 79% of managers remained engaged — nearly four times the global average — which Gallup attributes to deliberate management development.
+
+For an operator promoting their first manager, this is a warning: the default trajectory of "promote and forget" produces a disengaged manager, who then produces a disengaged team. Enrolling someone into a leadership role is the beginning of a development relationship, not the end of a hiring decision.
+
+## Verbatim extracts (when sources support them)
+
+> "managers account for at least 70% of the variance in employee engagement scores across business units."
+> — Gallup, *Managers Account for 70% of Variance in Employee Engagement* (2015) — https://news.gallup.com/businessjournal/182792/managers-account-variance-employee-engagement.aspx
+
+> "engagement is driven more by having great managers at the business-unit level than by macroeconomic factors such as countries' labor policies and the vibrancy of their job markets."
+> — Jim Harter, *3 Key Insights Into the Global Workplace* (2024) — https://www.gallup.com/workplace/645416/key-insights-global-workplace.aspx
+
+> "Not engaged and actively disengaged employees, in aggregate, account for $8.9 trillion in lost productivity worldwide."
+> — Jim Harter, *3 Key Insights Into the Global Workplace* (2024) — https://www.gallup.com/workplace/645416/key-insights-global-workplace.aspx
+
+> "teams in the top quartile of employee engagement achieve 23% higher profitability than those in the bottom quartile."
+> — Jim Harter, *3 Key Insights Into the Global Workplace* (2024) — https://www.gallup.com/workplace/645416/key-insights-global-workplace.aspx
+
+> "Highly inspiring and engaging jobs are driven by what happens locally, driven by great managers. Macro-level job markets and policies have little to do with high levels of employee engagement."
+> — Jim Harter, *3 Key Insights Into the Global Workplace* (2024) — https://www.gallup.com/workplace/645416/key-insights-global-workplace.aspx
+
+(The 2026 report statistics — 20% engagement, $10T cost, manager-engagement collapse from 31% to 22% — are paraphrased in the source files this synthesis was built from, not captured verbatim. See Known Gaps.)
+
+## Notable cases / illustrations
+
+The fetched material is statistical and conceptual; it does not contain specific company case studies in retrievable form. The "best-practice organizations with 79% manager engagement" figure from the 2026 report is the closest thing to a case finding, but the source files do not name the organizations or describe the practices in detail. A future pass could pull the underlying *State of the Global Workplace* full PDF for case material.
+
+## Where this is used in the skill
+
+- `phases/3-enrollment.md` — backs the "engagement is shaped by the manager, not the person" framing and the cost-of-disengagement stakes
+
+## Sources (live-fetched on 2026-05-20)
+
+- [State of the Global Workplace — 2026 Report Landing](https://www.gallup.com/workplace/349484/state-of-the-global-workplace.aspx)
+- [State of the Global Workplace — 2026 Global Data Summary](https://www.gallup.com/workplace/697904/state-of-the-global-workplace-global-data.aspx)
+- [Managers Account for 70% of Variance in Employee Engagement (2015)](https://news.gallup.com/businessjournal/182792/managers-account-variance-employee-engagement.aspx)
+- [3 Key Insights Into the Global Workplace (Jim Harter, 2024)](https://www.gallup.com/workplace/645416/key-insights-global-workplace.aspx)
+
+## Known gaps
+
+- The four source files this synthesis draws from were produced via WebFetch, which auto-summarizes pages rather than returning verbatim HTML. The statistics in those files are accurate (engagement percentages, the 70% manager variance, the $10T and $8.9T productivity figures, the 23% profitability gap, the 51% turnover gap), but most prose is paraphrase, not verbatim Gallup language. The 2024 *3 Key Insights* page was the cleanest fetch and is the source of most verbatim quotes above. A future pass could re-extract the 2015 and 2026 pages via `curl` or a non-summarizing fetcher to retrieve direct Gallup prose for those statistics.
+- The underlying *State of the Global Workplace 2026* full PDF report was not fetched. It likely contains case studies, regional deep-dives, and methodology detail not present in the landing-page summaries.
+- The Q12 engagement instrument itself (the 12 questions Gallup uses to measure engagement) is referenced obliquely but not captured. If a coaching session needs the actual Q12 items, a targeted fetch would be needed.

package/skills/estack-leadership-coach/references/gerber_e-myth-revisited.md

@@ -0,0 +1,118 @@
+---
+name: gerber_e-myth-revisited
+title: The E-Myth Revisited
+author: Michael E. Gerber
+work_type: book
+type: synthesis
+last_fetched: 2026-05-20
+sources:
+  - https://www.harpercollins.ca/9780060839246/the-e-myth-revisited/
+  - https://harpercollins.co.in/product/e-myth-revisited/
+---
+
+# Michael E. Gerber — *The E-Myth Revisited: Why Most Small Businesses Don't Work and What to Do About It*
+
+## Overview
+
+Gerber argues that most small businesses fail because their founders are great technicians who mistakenly believe technical mastery of the work equates to the ability to run a business that does that work. The book lays out a path from being trapped *inside* the work to building a system-driven business by working *on* it like a franchise prototype, with the owner stepping into Entrepreneur and Manager roles rather than defaulting to Technician.
+
+## Why this is in the vault
+
+This reference feeds **Phase 1 (intake)** and **Phase 7 (diagnose)**. The coaching workflow uses Gerber's vocabulary to surface two failure patterns: (1) the founder who is doing technical work that should be delegated because they confuse "I am the best at this" with "I should be the one doing this," and (2) the founder who has hired help but practices **management by abdication** — handing work off without supervision until the employee drops the ball, then concluding "nobody cares about my business the way I do." Both patterns block real delegation. Gerber's Technician/Manager/Entrepreneur split is the diagnostic lens.
+
+## Synthesis — core principles
+
+### Principle 1: The Fatal Assumption
+
+The founding error of most small businesses, in Gerber's framing, is this: *"if you understand the technical work of a business, you understand a business that does that technical work. Wrong! The technical work of a business and a business that does that technical work are two totally different things!"* This is why a great baker who opens a bakery is not, by virtue of being a great baker, equipped to run a bakery. The skill set of doing the work is unrelated to the skill set of building the system that does the work at scale, without the founder present.
+
+For coaching, this is the root cause of most "I can't delegate this, only I can do it right" objections. The objection is true at the technical level and irrelevant at the business level.
+
+### Principle 2: The Technician, the Manager, and the Entrepreneur
+
+Every business owner is three people in one, in conflict. The **Technician** is the doer — happiest when executing the craft. The **Manager** is pragmatic, plans, keeps order, cleans up the Technician's and Entrepreneur's messes. The **Entrepreneur** is the visionary, "creates a great deal of havoc," and sees most people as obstacles to the dream.
+
+Gerber's claim is that in a struggling small business, the Technician dominates and the Manager and Entrepreneur are starved. The owner spends the day producing — because that's what feels productive and familiar — and the business never develops the systems and vision required to run without them. As the business grows, *"as a business grows, it invariably exceeds its owner's ability to control it"*: the Technician's boundary is what they can do alone, the Manager's is how many technicians they can supervise, the Entrepreneur's is how many managers they can engage in a vision. A founder stuck in Technician mode hits the lowest of these ceilings first.
+
+### Principle 3: Management by Abdication
+
+This is the specific phrase the leadership-coach skill cites, and Gerber's treatment is direct. **Adolescence** in a business begins when the owner finally hires help — and then Gerber names the trap: *"Management by Abdication – let somebody else do it without supervision until your employee begins dropping the ball. As the balls continue to fall, you begin to realize that no one cares about your business the way you do. No one is willing to work as hard as you."*
+
+The mechanism is delegation collapsing into dumping. The owner, exhausted from being the Technician, hands work off but supplies no system, no standard, no supervision, and no feedback loop. When work fails, the lesson the owner draws is the wrong one — *people are the problem* — when in fact the absence of a system is the problem. This is the diagnostic moment where most founders either build a real management approach or retreat back into doing everything themselves.
+
+### Principle 4: Working ON the business, not IN it
+
+Gerber's prescription: *"your business is not your life – they are two totally separate things. The primary catalyst from this point forward is to work on your business not in it."* The mental device is to pretend you are going to franchise it. If you had to hand the business to a franchisee tomorrow and have it produce the same result, what would have to be true? That gap — between what your business currently requires of you personally and what a franchise-ready version would require — is the work.
+
+The three guiding questions:
+- How can I get my business to work, but without me?
+- How can I get my people to work, but without my constant interference?
+- How can I own my business, and still be free of it?
+
+### Principle 5: The Franchise Prototype and the Turn-Key Revolution
+
+Gerber's positive model comes from McDonald's. Ray Kroc's insight, in Gerber's reading, was to build *"a systems-dependent business, not a people-dependent business. A system that can work without you."* The Business Format Franchise sells not the product but the *way* the product is produced and delivered — a documented, repeatable, orchestrated system.
+
+Gerber's six rules for franchising your own business: the model provides consistent value beyond expectation; it can be operated by people with the lowest possible level of skill (because the system, not the person, carries the quality); it is systems-dependent rather than people-dependent; it stands out as a place of impeccable order; all work is documented in the Operations Manual (the company's "How-To-Do-It Guide"); and it delivers a uniformly predictable service. The throughline: *"The system runs the business. The people run the system."*
+
+### Principle 6: Innovation, Quantification, Orchestration
+
+The ongoing Business Development Process has three habits. **Innovation** asks "what is standing in the way of my customer getting what he wants?" and "what is the best way to do this?" — and crucially, *"It should make things easier for your people, or it's not innovation."* **Quantification** measures everything related to how you do business so that you know whether an innovation worked. **Orchestration** is *"the elimination of discretion, or choice, at the operating level of your business"* — once a way works, it gets locked in. *"If you haven't orchestrated it, you don't own it. And if you don't own it, you can't depend on it."*
+
+The cycle never ends: you innovate, quantify, orchestrate, then start again.
+
+## Verbatim extracts
+
+> "If you understand the technical work of a business, you understand a business that does that technical work. Wrong! The technical work of a business and a business that does that technical work are two totally different things!"
+> — *The E-Myth Revisited*, Part I, "The Entrepreneurial Myth"
+
+> "Management by Abdication – let somebody else do it without supervision until your employee begins dropping the ball. As the balls continue to fall, you begin to realize that no one cares about your business the way you do. No one is willing to work as hard as you."
+> — *The E-Myth Revisited*, Part I, "Adolescence: Getting Some Help"
+
+> "The point is: your business is not your life – they are two totally separate things. The primary catalyst from this point forward is to work on your business not in it."
+> — *The E-Myth Revisited*, Part II, "Working On Your Business, Not In It"
+
+> "The system runs the business. The people run the system."
+> — *The E-Myth Revisited*, Part II, "The Franchise Prototype"
+
+> "A systems-dependent business, not a people-dependent business. A system that can work without you."
+> — *The E-Myth Revisited*, Part II, on Ray Kroc and McDonald's
+
+> "As a business grows, it invariably exceeds its owner's ability to control it."
+> — *The E-Myth Revisited*, Part I, "Beyond the Comfort Zone"
+
+> "If you haven't orchestrated it, you don't own it. And if you don't own it, you can't depend on it."
+> — *The E-Myth Revisited*, Part III, "Orchestration"
+
+> "The purpose of going into business is to get free of a job so you can create jobs for other people."
+> — *The E-Myth Revisited*, Part I, "Infancy: The Technician's Phase"
+
+## Notable cases / illustrations
+
+### Ray Kroc and McDonald's as the Franchise Prototype
+
+Gerber's anchoring illustration of the Turn-Key Revolution is Ray Kroc, "founder" of McDonald's in the franchise-system sense. Kroc set about *"the task of creating a foolproof, predictable business"* — a system that integrates every element required to make a business work, leaves the franchisee with as little operating discretion as possible, and sends them through rigorous training before they ever operate the franchise. The franchisee licenses the right to use the system, learns how to run it, and *"turns the key. The business does the rest."*
+
+The data point Gerber uses to justify the model: while approximately 80% of new small businesses fail in the first five years, roughly 75% of Business Format Franchises succeed. The difference, in Gerber's reading, is the system — not the people, not the product.
+
+### Sarah and the pie shop
+
+Note: the source material provided for this reference is a summary/outline of the book's structure and key claims and does not include the full Sarah narrative. Gerber's book itself uses Sarah, owner of "All About Pies," as the running protagonist through which the Technician/Manager/Entrepreneur split, the collapse into management by abdication, and the rebuild around a franchise prototype are dramatized. A future pass should pull Sarah's specific dialogue and turning points directly from the book chapters if the verbatim text becomes available.
+
+## Where this is used in the skill
+
+- `phases/1-intake.md` — diagnostic vocabulary for spotting the Technician-trapped founder during intake
+- `phases/7-diagnose.md` — the **management by abdication** failure pattern, used when a founder has "delegated" but their employee keeps dropping balls without supervision or system
+
+## Sources (live-fetched on 2026-05-20)
+
+- [The E-Myth Revisited — HarperCollins Canada](https://www.harpercollins.ca/9780060839246/the-e-myth-revisited/)
+- [E-Myth Revisited — HarperCollins India](https://harpercollins.co.in/product/e-myth-revisited/)
+
+Primary content for this reference was synthesized from the user-supplied structured outline of the book (chapter-by-chapter notes covering Parts I–III, including the Fatal Assumption, the Technician/Manager/Entrepreneur split, Management by Abdication, the Franchise Prototype, and the Business Development Process). Publisher pages above are cited for canonical bibliographic identity (title, author, edition, ISBN 9780887307287, Harper Business imprint).
+
+## Known gaps
+
+- The source provided is a structured outline rather than full verbatim chapters. Quotes above match the outline's wording, which closely tracks Gerber's prose, but a future pass should confirm exact wording against the published text where possible and add page citations.
+- The Sarah / All About Pies running case is referenced in the book but not present in the source outline. Pull her dialogue and turning points from the book itself in a future pass.
+- The Business Development Program (Primary Aim, Strategic Objective, Organizational Strategy, Management Strategy, People Strategy, Marketing Strategy, Systems Strategy) is captured at a structural level in the outline but is treated only briefly in the synthesis above — expand if Phase 4 (build-brief) ever wants to draw on Gerber's Position Contract / Organization Chart machinery.