elliot-stack 1.0.29 → 1.0.33

package/skills/estack-leadership-coach/references/grove_high-output-management.md

@@ -0,0 +1,95 @@
+---
+name: grove_high-output-management
+title: High Output Management
+author: Andrew S. Grove
+work_type: book
+type: synthesis
+last_fetched: 2026-05-20
+---
+
+# High Output Management — Synthesis
+
+Andrew S. Grove's *High Output Management* (Vintage Books, reissued 2015; originally 1983) is the canonical text on the mechanics of managerial leverage. For the leadership-coach skill, its load-bearing contribution is the **Task-Relevant Maturity (TRM)** framework and the operating discipline that follows from it: match management style to the subordinate's maturity on the specific task, monitor in proportion to that maturity, and never confuse delegation with abdication.
+
+This synthesis pulls from Chapter 4 (Meetings), Chapter 12 (Task-Relevant Maturity), Chapter 13 (Performance Appraisal), Chapter 16 (Why Training Is the Boss's Job), and the Foreword by Ben Horowitz.
+
+---
+
+## Core Principles
+
+### 1. Task-Relevant Maturity (TRM) is task-specific, not person-specific
+
+Grove's foundational claim is that the "right" management style is determined by a variable he calls task-relevant maturity, and TRM is local to the task — not a global trait of the subordinate.
+
+> "Some researchers in this field argue that there is a fundamental variable that tells you what the best management style is in a particular situation. That variable is the task-relevant maturity (TRM) of the subordinates, which is a combination of the degree of their achievement orientation and readiness to take responsibility, as well as their education, training, and experience. Moreover, all this is very specific to the task at hand, and it is entirely possible for a person or a group of people to have a TRM that is high in one job but low in another." (Ch 12)
+
+Grove illustrates this with a sales manager promoted to run a factory who performed badly: "we confused the manager's general competence and maturity with his task-relevant maturity" (Ch 12). He also uses a driving analogy — an experienced country-road driver can be a novice on a metro freeway — and an army-sergeant analogy where peacetime competence reverts in sudden combat. **TRM is a property of the person-task-context triple, and it can drop suddenly when the context changes.**
+
+**Implication for coaching:** Never assess "how senior is this person?" Always assess "how mature is this person on *this specific task* in *this specific context*?"
+
+### 2. Three management styles map to three TRM levels
+
+Grove gives an explicit table mapping TRM to the appropriate style (Ch 12). Reproduced here in the spirit of the original:
+
+| Subordinate's TRM | Effective management style |
+|---|---|
+| Low | Structured; task-oriented; tell "what," "when," "how" |
+| Medium | Individual-oriented; emphasis on two-way communication, support, mutual reasoning |
+| High | Involvement by manager minimal: establishing objectives and monitoring |
+
+The progression is **structured → communicating → monitoring**, and the manager is supposed to migrate down the table as TRM grows. Grove warns that managers consistently over-rate their own position on this ladder: "Some 90 percent of the supervisors saw their style as more communicating or delegating than their subordinates' view" (Ch 12). The coach should expect the manager's self-report to be one notch looser than reality.
+
+### 3. The difference between delegating and abdicating is monitoring
+
+This is the single most-quoted line in the book and the one that anchors the leadership-coach's monitoring phase:
+
+> "The presence or absence of monitoring, as we've said before, is the difference between a supervisor's delegating a task and abdicating it." (Ch 12)
+
+Horowitz reinforces it in the Foreword with a sharper version:
+
+> "The subordinate did poor work. My associate's reaction: 'He has to make his own mistakes. That's how he learns!' The problem with this is that the subordinate's tuition is paid by his customers. And that is absolutely wrong." (Foreword, Horowitz)
+
+**Implication for coaching:** When a manager says "I delegated it," the first diagnostic question is "what's your monitoring cadence and what does it look like?" If the answer is "I trust them," that is not delegation in Grove's sense — it is abdication. The customer pays the tuition.
+
+### 4. One-on-ones are the primary monitoring instrument, and their cadence is set by TRM
+
+Grove treats the one-on-one as the load-bearing infrastructure for delegation. Frequency is not a personal preference; it is a function of TRM on the work currently in flight.
+
+> "How often should you have one-on-ones? Or put another way, how do you decide how often somebody needs such a meeting? The answer is the job- or task-relevant maturity of each of your subordinates… the most effective management style in a specific instance varies from very close to very loose supervision as a subordinate's task maturity increases. Accordingly, you should have one-on-ones frequently (for example, once a week) with a subordinate who is inexperienced in a specific situation and less frequently (perhaps once every few weeks) with an experienced veteran." (Ch 4)
+
+The one-on-one is also where teaching happens. Grove is explicit that "Training is, quite simply, one of the highest-leverage activities a manager can perform" and that "the *who* of the training is *you*, the manager" (Ch 16). Monitoring and teaching are the same activity at low and medium TRM.
+
+**Implication for coaching:** When designing a delegation brief, the cadence question is downstream of the TRM question. Low TRM → weekly or more. Medium TRM → biweekly with a defined midpoint review. High TRM → objectives plus light monitoring on outcomes.
+
+### 5. Monitor what you understand — delegate from a position of familiarity
+
+Grove never uses the exact phrase "delegate what is familiar," so this principle is a faithful synthesis of his repeated argument rather than a verbatim teaching. The argument runs through the book:
+
+- The sales-manager-in-the-factory failure (Ch 12) happens because the manager cannot monitor what he does not understand. He has no instinct for the leading indicators or the "windows in the black box" (Ch 2) that would let him spot drift early.
+- Grove's "linearity indicator" and "leading indicators" chapters (Ch 2) assume the manager has internalised the work well enough to know what a healthy process looks like *before* the result lands.
+- The army-sergeant analogy works precisely because the sergeant knows his soldiers and the routine cold; when the environment shifts, his familiarity-based monitoring breaks down with it.
+
+**Implication for coaching:** A manager who wants to delegate a task they have never personally done should be flagged. They can still delegate, but their monitoring will be shallow and their abdication risk is elevated. The brief should compensate with stricter check-in structure, written deliverables at the midpoint, and a named second reviewer who *does* know the work. **This principle is paraphrased from Grove's broader argument, not a direct quote — flag it as synthesis when citing.**
+
+---
+
+## How This Reference Feeds the Leadership-Coach Phases
+
+- **1-intake** — Use Principle 1 to redirect any "is this person senior enough?" framing toward "what is their TRM on this specific task in this specific context?"
+- **2-trm-assessment** — Principles 1 and 2 are the assessment spine. The TRM table (Principle 2) is the rubric. The 90% self-overrating finding tells the coach to probe for evidence, not accept the manager's self-report at face value.
+- **4-build-brief** — Principle 2's style table determines the brief's tone (directive vs. collaborative vs. objectives-only). Principle 5 determines whether the manager needs scaffolding because they themselves are unfamiliar with the work.
+- **5-monitoring** — Principles 3 and 4 are the operating rules. Cadence by TRM, one-on-ones as the vehicle, monitoring as the non-negotiable that distinguishes delegation from abdication.
+- **7-diagnose** — When a delegation has gone sideways, Principle 3 is the first diagnostic ("did you monitor?") and Principle 1 is the second ("did you assess TRM on the actual task, or on the person in general?"). The sales-manager-in-the-factory pattern recurs constantly.
+
+---
+
+## Sources
+
+Primary content for this synthesis was extracted directly from the full text of *High Output Management* supplied by the user as a source PDF (Vintage Books reissue edition). Citations are by chapter; page numbers are intentionally omitted because pagination varies between print and reissue editions.
+
+Canonical publisher and retail URLs (fetched 2026-05-20):
+
+- Penguin Random House (Vintage Books imprint): https://www.penguinrandomhouse.com/books/72467/high-output-management-by-andrew-s-grove-former-chairman-and-ceo-of-intel/
+- Amazon (ISBN 9780679762881): https://www.amazon.com/High-Output-Management-Andrew-Grove/dp/0679762884
+
+Chapters cited in this synthesis: Foreword (Ben Horowitz), Chapter 1 (The Basics of Production), Chapter 2 (Managing the Breakfast Factory), Chapter 4 (Meetings), Chapter 12 (Task-Relevant Maturity), Chapter 13 (Performance Appraisal), Chapter 16 (Why Training Is the Boss's Job).

package/skills/estack-leadership-coach/references/hormozi-alex_followthrough.md

@@ -0,0 +1,152 @@
+---
+name: hormozi-alex_followthrough
+title: Team follow-through (The Game Ep 882 + related)
+author: Alex Hormozi
+work_type: podcast and video
+type: extraction
+last_fetched: 2026-05-20
+sources:
+  - https://podcasts.apple.com/ky/podcast/the-5-reasons-your-team-isnt-following-through-ep-882/id1000706788997
+  - https://pod.wave.co/podcast/the-game-with-alex-hormozi/the-5-reasons-your-team-isnt-following-through-ep-882-6b860d66
+  - https://www.youtube.com/shorts/C0ou8865CQo
+---
+
+# Alex Hormozi — *The 5 Reasons Your Team Isn't Following Through (The Game Ep 882)* and *Why Your Employees Aren't Doing What You Want (YouTube short)*
+
+## Overview
+
+Hormozi presents a five-point diagnostic framework — the **STAR system** — for figuring out why a person on your team didn't follow through on something. He frames it as the one tool he reaches for any time he is about to have a hard performance conversation. The five points map to the five (and only five) reasons someone fails to execute, and the framework is designed to keep the conversation on the same side of the table rather than turning it into a character attack.
+
+## Why this is in the vault
+
+This reference feeds Phase 4 (build-brief) and Phase 7 (diagnose). Phase 4 uses STAR as a pre-delegation checklist — every brief should make all five points unambiguous before handoff. Phase 7 uses STAR as the diagnostic ladder when follow-through has already failed: walk the rungs in order (did they know it was a task → what done looks like → how → when → what was blocking), because mis-skipping a rung leads to the wrong intervention (e.g., training when the real issue was an undefined deadline).
+
+A scope note: the reference slug and earlier wire-ups mentioned a "scorecard" reference, but the actual material in Ep 882 is about the STAR follow-through framework, not scorecards. Phase files should be updated to point here.
+
+## The five-point STAR framework — verbatim
+
+Hormozi states the framework explicitly:
+
+> "Listen, there's only 5 reasons someone doesn't do anything."
+> — Ep 882, ~4:12
+
+The five points, in the order he runs them:
+
+**1. They didn't know that you wanted them to do it.**
+
+> "It's either number one, you didn't know that I wanted you to do it. So did you know that I wanted you to give me that TPS report? And he might be like, oh, I thought we were just talking."
+> — Ep 882, ~4:17
+
+> "One of the things that we have internal acquisition.com is if it isn't written, it never happened. So if you just have a verbal conversation that exists IRL, just in the air, it doesn't ever matter because no one has proof of it."
+> — Ep 882, ~5:03
+
+**2. They didn't know what you wanted them to do (the "what" — defined by behavior or outcome).**
+
+> "Did you not know what I wanted you to do? Because he did send me something that. OK, what's the that versus the what?"
+> — Ep 882, ~6:12
+
+> "You want to define what you're asking someone to do in terms of behavior or outcomes. So if I wanted that TPS report right now... does that mean it's going to be printed out? Does that mean I want it printed on my desk? Does that mean it's an e-mail?... It probably takes like two or three extra minutes for you to be very clear. And then someone's going to take that two or three extra minutes and then save themselves like two or three extra hours."
+> — Ep 882, ~6:30–7:04
+
+> "Clarity is high leverage work."
+> — Ep 882, ~7:10
+
+**3. They didn't know how to do it.**
+
+> "Did they know how to do it?... I told you to do that. But I was like, honestly, you asked me to, but I don't know how to put a TPS report together... It's like, oh, OK, well, the solution to this is training."
+> — Ep 882, ~10:00–10:40
+
+> "Everything is trainable... it's just that some things are more trainable, take longer to train than others."
+> — Ep 882, ~10:56
+
+> "Document, demonstrate, duplicate, which means that I do it in front of you, I write it down, I do it in front of you, you do it in front of me, and then sign R."
+> — Ep 882, ~13:15
+
+**4. They didn't know when you wanted it done by (deadline).**
+
+> "Did they know when I wanted it done by? And this sounds so silly, but the reality is that the solution for this is deadlines."
+> — Ep 882, ~14:48
+
+> "If I say, hey, Kyle, when can you get me the TPS reports by? He might say Monday... I like to push on this. And I say, cool, how long do you think it will take you in order to get the TPS report done? The actual work itself, not from now until you can deliver it, but how long will the work take?"
+> — Ep 882, ~15:14
+
+> "End of day is better than end of week. I want end of day to be my default... an end of month organization will literally work at 1/30th the pace of an end of day organization."
+> — Ep 882, ~16:48–17:16
+
+**5. Something was blocking them (circumstances / obstacles).**
+
+> "What's the last thing that could stop them? And I'm going to take motivation out of this and I'll tell you why, but the last thing that could stop them is circumstances."
+> — Ep 882, ~20:21
+
+> "If I asked the best chef in the world, hey, can you make me an omelette? You know how to make an omelette... and I want you to make it for me right now — that guy might not do it. I'll be like, why didn't you make me an omelette? You might be like, I don't have the eggs."
+> — Ep 882, ~20:41
+
+> "We go through the other four first because as soon as you mention this fifth one, everyone blames this one. But why? Because it's not that... people's egos are protected when they say, oh, I've got this other thing."
+> — Ep 882, ~21:23
+
+> "This is where the real leadership starts comes in. Because this is where we say like, well, how hard would it have been for you to go get eggs? It's been 3 days. Like how hard was it to get eggs?"
+> — Ep 882, ~21:45
+
+## The "every failure traces to one of five" framing
+
+> "There's only 5 reasons someone doesn't do anything."
+> — Ep 882, ~4:12
+
+> "The first four are what I would consider very standard business practices. But the here's the thing that's really clever with this is that by asking the 1st 4, you basically give many opportunities for it to not be attack on the person when you have the circumstances."
+> — Ep 882, ~22:30
+
+> "By framing it that way, it completely shifts the whole vibe of the conversation... compared to what I believe you're capable of. So I'm basically weaving in a compliment saying I think you're capable of more."
+> — Ep 882, ~2:01
+
+> "Both of you are basically attacking the problem on the same side of the table, trying to figure out how to get the person to their potential."
+> — Ep 882, ~2:34
+
+## The YouTube short — punchy encapsulation of the same idea
+
+> "If you ever have a conversation where you're like, why is my employee not doing anything you say, hey John, I asked you to do this, and then you didn't do this, and so help me understand, was it that you didn't know that I wanted you to do it... was that part unclear, is it that you didn't know how to do it, when to do it by, why to do it, and let me give you the bonus number five, was there something blocking you."
+> — *Why Your Employees Aren't Doing What You Want* (YouTube short)
+
+> "I could have the best chef in the world, he understands what making omelette is, he knows how to do it, and I say make it for me right now he's motivated, cuz he's on live television, what's the problem, he ain't got no eggs."
+> — *Why Your Employees Aren't Doing What You Want* (YouTube short)
+
+> "A lot of times as a as a boss, an owner, you have to see what are the things that are blocking, because most people do want to do their jobs, or you find out that you've got somebody who despite all of these things still chooses not to do it, in which case maybe it's not a good fit for them."
+> — *Why Your Employees Aren't Doing What You Want* (YouTube short)
+
+## Notable cases / illustrations from the source
+
+### The Kyle / TPS report scenario
+
+Hormozi walks the framework end-to-end against a recurring example: he has asked an employee named Kyle for a "TPS report" by Monday. Monday arrives and Kyle hasn't delivered. Hormozi runs Kyle through the five points in sequence:
+
+- *"Did you know that I wanted you to give me that TPS report?"* Kyle might say "Oh, I thought we were just talking." Solution: write it down. *"If it isn't written, it never happened."* (Ep 882, ~4:17–5:25)
+- *"Did you not know what I wanted you to do?"* Kyle sent something, but it wasn't the right format. Solution: define behavior/outcome — printed, on the desk, by Monday, on nice paper, or as a specific email. (Ep 882, ~6:12–8:18)
+- *"Did you not know how to do it?"* Kyle: "I don't know how to put a TPS report together." Solution: training via document-demonstrate-duplicate. *"He knew how to do 8 of the nine steps. You just couldn't do the last step."* (Ep 882, ~10:00–13:48)
+- *"Did you know when I wanted it done by?"* Hormozi presses further: not just the deadline, but how long the actual work takes, and what else is on the plate. (Ep 882, ~15:14–16:36)
+- *"Was something blocking you?"* The omelette / eggs analogy. And then: *"How hard would it have been for you to go get eggs?"* This is where Hormozi judges agency and ability to solve problems independently. (Ep 882, ~20:21–22:12)
+
+### The "Courtney" / harassment scenario — why behavioral specificity matters
+
+Hormozi illustrates the *"what"* step with a harassment scenario to show why telling someone to "be less creepy" or "stop harassing Courtney" fails: those are not behaviors. The manager has to drill down to what Courtney actually witnessed versus what the other person actually did — *"she might describe his behavior as interesting. He might describe his behavior as being cordial."* Until the manager forces both parties to describe the specific behavior (good morning + wave vs. squeezing) they can't course-correct. *"No one wakes up and says I want to be creepy today. Creepy people act in ways that they don't think is creepy. And so by telling them to stop, be creepy, they don't know what the fuck that means."* (Ep 882, ~8:33–9:45)
+
+### The mother / weight-loss reframe — motivation as relative value
+
+When the framework gets to the 5th point and the real issue is motivation, Hormozi says you can't ask "were you not motivated?" directly — no one answers honestly. Instead you change the relative value of the outcome. His example: his mother tried to lose weight for 30 years and couldn't. The line that worked was her doctor telling her she wouldn't live to see her grandkids. *"That was the line... He was able to motivate her because that was the one thing for her."* (Ep 882, ~25:05–25:44)
+
+### Why the 5th point goes last (ego protection)
+
+Hormozi is explicit about the sequencing: the circumstances/obstacles point comes last on purpose, because if you lead with it, everyone hides behind it. *"As soon as you mention this fifth one, everyone blames this one. But why? Because it's not that... people's egos are protected when they say, oh, I've got this other thing."* Running the first four in order surfaces the real cause and also lets the employee admit a real obstacle without it being the first available excuse. (Ep 882, ~21:23–22:51)
+
+## Where this is used in the skill
+
+- `phases/4-build-brief.md` — STAR as the pre-delegation checklist (replaces stale link to `hormozi-alex_scorecard.md`)
+- `phases/7-diagnose.md` — STAR as the diagnostic ladder for failed follow-through (replaces stale link to `hormozi-alex_scorecard.md`)
+
+## Sources (live-fetched on 2026-05-20)
+
+- [The 5 Reasons Your Team Isn't Following Through | Ep 882 — Apple Podcasts](https://podcasts.apple.com/ky/podcast/the-5-reasons-your-team-isnt-following-through-ep-882/id1000706788997)
+- [The 5 Reasons Your Team Isn't Following Through | Ep 882 — pod.wave.co](https://pod.wave.co/podcast/the-game-with-alex-hormozi/the-5-reasons-your-team-isnt-following-through-ep-882-6b860d66)
+- [Why Your Employees Aren't Doing What You Want (YouTube short)](https://www.youtube.com/shorts/C0ou8865CQo)
+
+## Note on episode numbering
+
+The episode is canonically titled and numbered **Ep 882** ("The 5 Reasons Your Team Isn't Following Through") across the official podcast feed, Apple Podcasts, and the Wave podcast page. The earlier hand-off note suggesting it may appear as Ep 854 on Apple Podcasts did not match what was findable on 2026-05-20 — Ep 854 surfaces as a different episode ("STOP Following Your Passion"). If a downstream reader sees an "Ep 854" citation for this material, treat it as a numbering anomaly and verify against the title "The 5 Reasons Your Team Isn't Following Through."

package/skills/estack-leadership-coach/references/hormozi-leila_4-stages.md

@@ -0,0 +1,146 @@
+---
+name: hormozi-leila_4-stages
+title: The Art of Delegation — Four Stages
+author: Leila Hormozi
+work_type: blog and video
+type: extraction
+last_fetched: 2026-05-20
+sources:
+  - https://leilahormozi.com/p/the-art-of-delegation
+  - https://www.youtube.com/shorts/2X2TPGJsYzs
+---
+
+# Leila Hormozi — *The Art of Delegation*
+
+## Overview
+
+Leila Hormozi (CEO of Acquisition.com) lays out a four-stage progression for delegating work to a teammate: Investigation, Informed Progress, Informed Results, and Complete Ownership. Her core claim is that delegation is not binary — most leaders fail because they jump straight to full ownership instead of stair-stepping a teammate up through earned stages, per task and per person.
+
+## Why this is in the vault
+
+This reference backs the coach's Task Readiness Model (TRM) assessment in Phase 2 and the misdiagnosis work in Phase 7. When a user is treating delegation as "I either do it or they do it," the four stages give the coach a concrete progression to map a task onto — and Leila's explicit warning that "you must earn each stage with each person on each task" is the precise antidote to the "they should just own it" failure mode that shows up in diagnose conversations.
+
+## Key extractions
+
+> "They think delegation is **binary** — either **you** do it or **someone else** does."
+> — Blog post, paragraph 6
+
+> "But after years of getting this wrong, I finally understood there are actually four distinct stages of delegation."
+> — Blog post, paragraph 7
+
+> "Everyone typically jumps to stage 4, but in reality, you need to stair-step your way there."
+> — Blog post, paragraph 8
+
+> "Stage 1: Investigation"
+> — Blog post, section header
+
+> "You delegate the research process to someone and have them summarize their findings to you."
+> — Blog post, Stage 1 body
+
+> "Example: 'Go research three manufacturers for our product line and bring me a report.'"
+> — Blog post, Stage 1 example
+
+> "You're not asking them to make decisions. You're asking them to gather information. This is where trust begins."
+> — Blog post, Stage 1 closing line
+
+> "Stage 2: Informed Progress"
+> — Blog post, section header
+
+> "You delegate a task, then the teammate gives you regular updates at specific milestones."
+> — Blog post, Stage 2 body
+
+> "Example: 'Set up our influencer marketing campaign and check in with me at these three points so I can give feedback.'"
+> — Blog post, Stage 2 example
+
+> "They're executing, but you're still in the loop. You're building their confidence and yours."
+> — Blog post, Stage 2 closing line
+
+> "Stage 3: Informed Results"
+> — Blog post, section header
+
+> "You give a task to your teammate. They update you once it's complete. No action required on your behalf until delivery is done."
+> — Blog post, Stage 3 body
+
+> "Example: 'Launch the new product line. I don't need updates. Just bring me the results when it's done.'"
+> — Blog post, Stage 3 example
+
+> "They own the process. You just see the outcome."
+> — Blog post, Stage 3 closing line
+
+> "Stage 4: Complete Ownership"
+> — Blog post, section header
+
+> "You assign a task/project and don't need any further reporting."
+> — Blog post, Stage 4 body
+
+> "Example: 'This is your department now. Run it as if it's your own company.'"
+> — Blog post, Stage 4 example
+
+> "This is ownership — where that person's not just owning the task, but they're owning the outcome without any oversight from you at all."
+> — Blog post, Stage 4 closing line
+
+> "You can't go from doing everything yourself straight to Stage 4. That's like teaching someone to swim by throwing them in the ocean."
+> — Blog post, "The mistake everyone makes" section
+
+> "Each person starts at Stage 1 on each task. As they prove themselves, you move them up. Some people on some tasks might never get past Stage 2. That's fine. Others will race to Stage 4 in weeks."
+> — Blog post, "The mistake everyone makes" section
+
+> "The point is: **You must earn each stage with each person on each task.**"
+> — Blog post, "The mistake everyone makes" section (Leila's bold)
+
+> "if i'm feeling like i can't get done what i said, i'm gonna get done for that day, then i'm not thinking strategically enough, what i'm typically not doing is, i'm not thinking who else can do this besides me"
+> — YouTube short, 00:00:00–00:00:30
+
+> "i can absolutely get these things done, if i focus on the most important ones that only i can do, so what i'll do is, i'll look at my list, if i have like 17 things and i'll say these are all the things i'm going to delegate, and here's what i'm going to delete too"
+> — YouTube short, 00:00:30+
+
+## Notable cases / illustrations from the source
+
+### Leila's own pattern: take it back and re-do it yourself
+
+Leila opens the blog post with the failure mode the framework is designed to fix:
+
+> "When I first started hiring people, I tried to delegate **everything** at once. It was complete chaos. I'd hand someone a project, disappear, and come back to find... nothing like what I expected. Or worse, nothing at all :) So I'd take it back. Do it myself. Tell myself 'nobody can do this like me.'"
+> — Blog post, opening
+
+This is the trap the four stages exist to interrupt — the swing from "delegate everything" straight to "take it back and do it myself," with no intermediate stages of structured progress.
+
+### The "swim by throwing them in the ocean" warning
+
+Leila's vivid illustration for why Stage 4 cannot be a starting point:
+
+> "You can't go from doing everything yourself straight to Stage 4. That's like teaching someone to swim by throwing them in the ocean. Not gonna f*ckin work! (atleast for most of us lol)"
+> — Blog post, "The mistake everyone makes" section
+
+She follows this with the empathy reframe: *"if someone came to you today with zero context and said 'just own this completely,' you'd probably fail too. Not because you're incompetent, but because you don't have the foundation yet."*
+
+### The "pick one thing this week" call to action
+
+Leila ends the blog with a concrete starting move for readers:
+
+> "Look at everything on your plate. Pick ONE thing you've been meaning to delegate but haven't because 'nobody can do it like you.' Start them at Stage 1. Just investigation. See what happens."
+> — Blog post, closing
+
+### The strategic-thinking trigger (from the YouTube short)
+
+In the short, Leila names the in-the-moment signal that she's under-delegating:
+
+> "if i'm feeling like i can't get done what i said, i'm gonna get done for that day, then i'm not thinking strategically enough, what i'm typically not doing is, i'm not thinking who else can do this besides me"
+> — YouTube short, 00:00:00–00:00:30
+
+Her response is to take her list, mark which items to delegate, and which to delete — not just to delegate more, but to triage. The short pairs naturally with the blog post: the blog gives the *how* (four stages), the short gives the *trigger* (the felt sense of running out of day).
+
+## Where this is used in the skill
+
+- `phases/2-trm-assessment.md` — TRM assessment uses the four stages as the progression scaffold for matching task complexity to teammate-readiness
+- `phases/7-diagnose.md` — Diagnose phase uses the "stair-step / earn each stage" principle as the primary lens for "they should just own it" failure patterns
+
+## Sources (live-fetched on 2026-05-20)
+
+- [The Art of Delegation — leilahormozi.com](https://leilahormozi.com/p/the-art-of-delegation)
+- [How To Delegate In Your Business — YouTube Short](https://www.youtube.com/shorts/2X2TPGJsYzs)
+
+## Known gaps
+
+- The user-supplied framing for this reference included the phrase *"Informed Results is the most teaching level."* That exact phrasing does **not** appear in either fetched source. Leila's own framing of Stage 3 (Informed Results) is *"They own the process. You just see the outcome."* — a delivery/ownership framing, not a teaching-intensity framing. If the skill body currently leans on the "most teaching level" wording, it should be rewritten to match what Leila actually says, or hedged as a coach-side interpretation.
+- The YouTube short transcript is brief (~30 seconds of speech) and does not enumerate the four stages — it only frames the trigger for delegating. The blog post is the canonical source for the stage names and definitions.

package/skills/estack-leadership-coach/references/oncken-wass_monkeys-hbr-1974.md

@@ -0,0 +1,128 @@
+---
+name: oncken-wass_monkeys-hbr-1974
+title: "Management Time: Who's Got the Monkey?"
+author: William Oncken, Jr. and Donald L. Wass
+work_type: article
+type: extraction
+last_fetched: 2026-05-20
+sources:
+  - https://hbr.org/1999/11/management-time-whos-got-the-monkey
+  - https://store.hbr.org/product/management-time-who-s-got-the-monkey/99609
+---
+
+# Oncken & Wass — *Management Time: Who's Got the Monkey?*
+
+## Overview
+
+Originally published in HBR's November–December 1974 issue and reissued in 1999 as an HBR Classic with a commentary by Stephen R. Covey, this article introduces the "monkey-on-the-back" metaphor for how subordinates' problems migrate onto a manager's back during routine interactions. Oncken and Wass argue that a manager's discretionary time collapses when they take on "subordinate-imposed time," and they prescribe specific rules and five degrees of initiative to keep ownership where it belongs.
+
+## Why this is in the vault
+
+This reference feeds Phase 6 (reverse-delegation) and Phase 7 (diagnose). The monkey metaphor is the single sharpest lens for spotting reverse delegation in coaching conversations, and the five degrees of initiative provide a precise dial for renegotiating ownership without dumping. The five "Care and Feeding" rules give concrete behavior change to assign as homework.
+
+## Key extractions
+
+> "Subordinate-imposed time begins the moment a monkey successfully leaps from the back of a subordinate to the back of his or her superior and does not end until the monkey is returned to its proper owner for care and feeding."
+> — Section: *Where Is the Monkey?*
+
+> "In accepting the monkey, the manager has voluntarily assumed a position subordinate to his subordinate. That is, he has allowed Jones to make him her subordinate by doing two things a subordinate is generally expected to do for a boss—the manager has accepted a responsibility from his subordinate, and the manager has promised her a progress report."
+> — Section: *Where Is the Monkey?*
+
+> "Why does all of this happen? Because in each instance the manager and the subordinate assume at the outset, wittingly or unwittingly, that the matter under consideration is a joint problem. The monkey in each case begins its career astride both their backs."
+> — Section: *Where Is the Monkey?*
+
+> "He now sees, with the clarity of a revelation on a mountaintop, that the more he gets caught up, the more he will fall behind."
+> — Section: *Who Is Working for Whom?*
+
+> "The purpose of each interview is to take a monkey, place it on the desk between them, and figure out together how the next move might conceivably be the subordinate's."
+> — Section: *Getting Rid of the Monkeys*
+
+> "At no time while I am helping you with this or any other problem will your problem become my problem. The instant your problem becomes mine, you no longer have a problem. I cannot help a person who hasn't got a problem."
+> — Section: *Getting Rid of the Monkeys* (the manager's ground-rules speech)
+
+> "When this meeting is over, the problem will leave this office exactly the way it came in—on your back. You may ask my help at any appointed time, and we will make a joint determination of what the next move will be and which of us will make it."
+> — Section: *Getting Rid of the Monkeys*
+
+> "Before developing initiative in subordinates, the manager must see to it that they have the initiative. Once the manager takes it back, he will no longer have it and he can kiss his discretionary time good-bye."
+> — Section: *Transferring the Initiative*
+
+> "There are five degrees of initiative that the manager can exercise in relation to the boss and to the system: 1. wait until told (lowest initiative); 2. ask what to do; 3. recommend, then take resulting action; 4. act, but advise at once; 5. and act on own, then routinely report (highest initiative)."
+> — Section: *Transferring the Initiative*
+
+> "In relation to subordinates, the manager's job is twofold. First, to outlaw the use of initiatives 1 and 2, thus giving subordinates no choice but to learn and master 'Completed Staff Work.' Second, to see that for each problem leaving his or her office there is an agreed-upon level of initiative assigned to it, in addition to an agreed-upon time and place for the next manager-subordinate conference."
+> — Section: *Transferring the Initiative*
+
+> "Rule 1. Monkeys should be fed or shot. Otherwise, they will starve to death, and the manager will waste valuable time on postmortems or attempted resurrections."
+> — Section: *The Care and Feeding of Monkeys*
+
+> "Rule 2. The monkey population should be kept below the maximum number the manager has time to feed. Subordinates will find time to work as many monkeys as he or she finds time to feed, but no more. It shouldn't take more than five to 15 minutes to feed a properly maintained monkey."
+> — Section: *The Care and Feeding of Monkeys*
+
+> "Rule 3. Monkeys should be fed by appointment only. The manager should not have to hunt down starving monkeys and feed them on a catch-as-catch-can basis."
+> — Section: *The Care and Feeding of Monkeys*
+
+> "Rule 4. Monkeys should be fed face-to-face or by telephone, but never by mail. (Remember—with mail, the next move will be the manager's.) Documentation may add to the feeding process, but it cannot take the place of feeding."
+> — Section: *The Care and Feeding of Monkeys*
+
+> "Rule 5. Every monkey should have an assigned next feeding time and degree of initiative. These may be revised at any time by mutual consent but never allowed to become vague or indefinite. Otherwise, the monkey will either starve to death or wind up on the manager's back."
+> — Section: *The Care and Feeding of Monkeys*
+
+## The "next move" rule
+
+The article's structural test for who owns a problem is to ask, after any encounter, whose move is next. Oncken and Wass walk through four parting lines a manager might use and show how each one transfers the next move onto the manager:
+
+- "Let me think about it, and I'll let you know." — manager now owes the answer.
+- "Fine. Send me a memo on that." — the memo will land in the manager's in-basket; next move is the manager's.
+- "Just let me know how I can help." — the subordinate can't proceed without approval, so the next move is effectively the manager's.
+- "I will draw up an initial draft for discussion with you." — the subordinate is immobilized until the manager drafts.
+
+The remedy in *Getting Rid of the Monkeys* is to ensure that every encounter ends with the next move on the subordinate's back, captured by appointment on the manager's calendar.
+
+## Notable cases / illustrations from the source
+
+### The manager who can't get out the door (Jones in the hallway)
+
+> "Let us imagine that a manager is walking down the hall and that he notices one of his subordinates, Jones, coming his way. When the two meet, Jones greets the manager with, 'Good morning. By the way, we've got a problem.'"
+
+The manager knows enough to get involved but not enough to decide on the spot. He defers ("let me think about it"), and the monkey leaps. Jones reinforces the transfer by later "cheerily" asking, "How's it coming?" — which Oncken and Wass label, drily, "supervision."
+— Section: *Where Is the Monkey?*
+
+### Sixty screaming monkeys by Friday
+
+If four subordinates each transfer three monkeys per day for a week, the manager has acquired 60. The article describes him closing his office door late Friday afternoon while subordinates wait outside, then arriving Saturday morning to catch up — only to see his subordinates playing golf across from his office window. "He now knows who is really working for whom."
+— Section: *Who Is Working for Whom?*
+
+### Monday morning: handing the monkeys back
+
+The manager returns Monday and calls each subordinate in one by one. The purpose of each meeting is to "take a monkey, place it on the desk between them, and figure out together how the next move might conceivably be the subordinate's." For monkeys where the subordinate's next move is "elusive," the manager lets the monkey "sleep on the subordinate's back overnight" and reconvenes the next day. By 11 AM the manager realizes he doesn't have to close his door — the monkeys are gone, and will return "but by appointment only."
+— Section: *Getting Rid of the Monkeys*
+
+## Covey's 1999 commentary — *Making Time for Gorillas*
+
+Stephen R. Covey was asked to provide an afterword for the 1999 Classic reissue. Key points he adds:
+
+> "When Bill Oncken wrote this article in 1974, managers were in a terrible bind. They were desperate for a way to free up their time, but command and control was the status quo."
+
+> "Bosses cannot just give a monkey back to their subordinates and then merrily get on with their own business. Empowering subordinates is hard and complicated work."
+
+> "When you give problems back to subordinates to solve themselves, you have to be sure that they have both the desire and the ability to do so."
+
+> "Effective delegation—the kind Oncken advocated—depends on a trusting relationship between a manager and his subordinate. Oncken's message may have been ahead of his time, but what he suggested was still a fairly dictatorial solution. He basically told bosses, 'Give the problem back!' Today, we know that this approach by itself is too authoritarian."
+
+> "If subordinates are afraid of failing in front of their boss, they'll keep coming back for help rather than truly take initiative."
+
+> "Many managers may subconsciously fear that a subordinate taking the initiative will make them appear a little less strong and a little more vulnerable."
+
+> "Managers who live with integrity according to a principle-based value system are most likely to sustain an empowering style of leadership."
+
+Covey also reports that executives tell him "half or more of their time is spent on matters that are urgent but not important … they're often too busy to spend the time they need on the real gorillas in their organization" — which is the source of his afterword's title.
+
+## Where this is used in the skill
+
+- `phases/6-reverse-delegation.md` — primary backing reference; the monkey metaphor, the five degrees of initiative, and the five Care and Feeding rules are the operative tools for this phase.
+- `phases/7-diagnose.md` — diagnostic lens for managers whose discretionary time has been consumed by subordinate-imposed time; Covey's commentary on trust and fear-of-failure is the bridge to deeper diagnosis.
+
+## Sources (live-fetched on 2026-05-20)
+
+- [Management Time: Who's Got the Monkey? (HBR, Nov–Dec 1999 reissue of the 1974 Classic)](https://hbr.org/1999/11/management-time-whos-got-the-monkey)
+- [HBR Store product page, reprint #99609](https://store.hbr.org/product/management-time-who-s-got-the-monkey/99609)