Grove's TRM Framework: The Core of Effective Delegation
In High Output Management, Andy Grove introduces Task-Relevant Maturity as the key variable for determining how to manage any given work situation. TRM is not general competence. It's not seniority. It's not intelligence or even domain expertise. It is the person's experience and prior performance on this specific type of task, and it determines everything about how the work should be delegated and monitored.
The Three TRM Levels and Their Management Implications
- Low TRM: Tell what, when, and how. The person lacks sufficient experience with this task to make reliable judgments. Your role is directive: specify the task clearly, explain the expected output, define the timeline, and explain the how. Check in frequently. This is not micromanagement; it's appropriate supervision calibrated to the actual risk.
- Medium TRM: Two-way dialogue and coaching. The person has enough experience to have valid perspectives, but also enough to know the complexity they're facing. They need a sounding board, not a directive. Ask before telling. Explore options together. Provide emotional support, as medium TRM is where self-doubt and imposter syndrome peak.
- High TRM: Agree on objectives, stay out of the way. The person has demonstrated reliable performance on this type of task. Agree on the expected output and timeline. Trust their judgment on execution. Monitor results at the agreed-upon checkpoint. Intervening before that checkpoint on a high-TRM task is the definition of micromanagement.
"How often you monitor should not be based on what you believe your subordinate can do in general, but on his experience with a specific task and his prior performance with it." Andy Grove, High Output Management
The most common delegation error Grove identifies: using a person's overall seniority as a proxy for TRM on a specific task. A decade-long veteran joining a new project type, moving into a new function, or taking on a responsibility they've never held before has low TRM for that specific work, regardless of their general capabilities. Treating them as high TRM because of their title sets them up to fail and leaves them without the support they need.
Walsh's "Delegate Abundantly" and the Condition That Makes It Work
"Delegate abundantly." Bill Walsh, The Score Takes Care of Itself
Late in his career at Stanford and in his post-NFL advisory work, Walsh identified excessive holding-on as the most common failure mode of experienced leaders. They'd built their expertise by doing the work themselves, and letting it go felt like losing control of quality. His prescription: delegate abundantly.
But Walsh was explicit about the condition that makes abundant delegation work: you must first install the Standard of Performance. Walsh spent years building an explicit behavioral standard for every role in his organization: not just what the output should be, but how the work should be done, what excellence looked like in each function, and what was non-negotiable. Only after that standard was in place, taught, demonstrated, and internalized, could you delegate with confidence.
His phrase captures the failure modes on both sides of the balance: "Delegation without teaching is abdication. Teaching without release is micromanagement." The one-on-one meeting (Grove) is where the teaching happens. The Standard of Performance (Walsh) is what the teaching is aimed at. Delegation is the release that follows both.
What Actually Blocks Effective Delegation
The barriers to effective delegation are rarely technical. They're psychological and systemic:
- "I can do it faster myself": True in the short run. False in the long run. Grove's leverage calculation: the cost of doing it yourself once vs. the value of a person who can now do it reliably without you. The short-term efficiency cost of delegation is the long-term efficiency investment.
- Fear of losing control: Resolved by calibrating monitoring to TRM rather than eliminating monitoring. High-TRM delegation isn't unmonitored; it's monitored at agreed-upon checkpoints. Low-TRM delegation is monitored frequently. Control is retained through the system, not through doing the work yourself.
- Unclear expectations: Resolved by Walsh's Standard of Performance approach: before delegating, be explicit about what the expected output looks like and how it should be produced. Vague delegation produces vague results and then blaming.
- No follow-through system: Resolved by Allen's waiting-for list. Every delegation goes on it. Without a trusted system, follow-up relies on memory and anxiety, and neither is reliable.
The Anatomy of a Good Delegation
Every effective delegation contains five elements. Missing any one of them creates predictable problems:
The Five-Element Delegation Framework
- 1. What: The specific task and the expected output. Not "handle the client relationship" but "send the client a proposal by Thursday with three options priced between $X and $Y."
- 2. Why: The context: why this matters and how it fits the larger picture. People execute better when they understand purpose. The "why" also helps them make good judgment calls when they encounter situations the "what" doesn't cover.
- 3. By when: An exact deadline, not "ASAP" or "soon." "ASAP" means different things to different people. A specific date and time removes ambiguity and creates shared accountability.
- 4. Resources: What they have access to: budget, data, people, tools, authority. Don't delegate a task without also delegating the resources required to complete it.
- 5. Check-in: When and how you'll monitor progress, calibrated to their TRM for this task. "I'll check in Wednesday at 2pm" is clear. "Let me know if you need anything" is not, because it puts the burden of communication on the person least likely to ask for help.
Try alfred_
See what this looks like in practice
alfred_ applies these principles automatically — triaging your inbox, drafting replies, extracting tasks, and delivering a Daily Brief every morning. Theory becomes system. $24.99/month. 30-day free trial.
Try alfred_ freeStep-by-Step: Delegate Effectively Using TRM
Assess TRM: This Person, This Task
Before delegating, ask: what's this person's experience and prior performance on this specific type of task? Not in general. Not in their domain overall. This task. Have they done it before? With what result? If you're uncertain, err toward lower TRM, as it's easier to back off monitoring than to recover from a missed deliverable that could have been caught early.
Choose Your Management Style Based on TRM
Low TRM: directive. Tell them what, when, and how in detail. Set frequent check-in points. Medium TRM: coaching. Ask what they're planning to do before telling them what you'd do. Provide emotional support. High TRM: agree on objectives and stay out of the way until the agreed checkpoint. The style follows the TRM level, not the person's seniority or your preference for a particular management style.
Delegate Using All Five Elements
Use the five-element framework for every delegation: what, why, by when, resources, check-in. Write it down, either in an email or a message, so there's a shared record of what was agreed. Verbal-only delegations are ambiguous by the next morning. Written delegations create shared accountability and give the person a reference to return to if they're uncertain.
Add to Your Waiting-For List Immediately
The moment you delegate, add it to your waiting-for list: person, task, expected completion date. Allen's trusted system principle applies: don't rely on memory to follow up. alfred_ helps here: when you delegate via email, it monitors the thread and alerts you if the deadline arrives without a response or delivery. The waiting-for list is the difference between delegation and abdication.
At the Check-In: Assess, Adjust TRM, Update Your Approach
At the agreed check-in point, review performance against expectations. If they exceeded expectations, adjust TRM up and reduce monitoring frequency for next time. If they fell short, assess why. Was the task unclear? Did they need support they didn't get? Adjust TRM down and increase monitoring accordingly. TRM is a living assessment, not a permanent label. It updates with each performance data point.
Delegation Template
A sample delegation email using the five-element framework:
Subject: Q2 Competitive Analysis: Delegating to You Hi [Name], I'm handing off the Q2 competitive analysis to you. Here's the full picture: WHAT Produce a 3-5 page competitive analysis covering our top 5 competitors. For each: pricing changes since Q1, product updates, and any notable customer wins or losses we're aware of. WHY The leadership team is using this for our Q2 strategy session on April 8. It directly informs our pricing and positioning decisions for the half. This is a high-visibility piece. Do it well. BY WHEN First draft to me by April 3 (5 days before the leadership session). I'll give feedback within 24 hours. Final version due April 5. RESOURCES You have access to: our competitive intelligence folder in Drive, the G2 and Capterra review monitoring tool (login in 1Password), and up to $200 for any data purchases you need (expense it normally). I can connect you with our sales team if you need intel from the field. CHECK-IN I'll check in with you Monday (March 31) to see how it's progressing. Flag anything you're stuck on before then; don't wait for Monday. Questions? Let me know. [Manager]
The Monitoring Paradox
Most managers monitor either too much or too little, and both failures have the same cause: using the wrong variable to calibrate monitoring. They use time-in-role, seniority, or their personal relationship quality as proxies for how closely to monitor. Grove's insight is that the right variable is always TRM for this task.
TRM-calibrated monitoring solves the paradox: check in frequently on low-TRM tasks, rarely on high-TRM tasks, regardless of how long the person has been on the team. This means you may monitor a 5-year veteran closely when they're doing something genuinely new to them, and a 1-year employee loosely when they're doing work they demonstrably excel at. This is not inconsistency. It's precision.
Tracking Delegated Work Without Micromanaging
Allen's waiting-for list is the operational tool that makes systematic follow-through possible without constant interrupting. Every delegation goes on the list with the person's name and the expected completion date. The list is reviewed weekly during the weekly review and daily during the shutdown ritual. When something is past due, you follow up, not because you're anxious, but because the system surfaced it.
alfred_ extends this capability to email-based delegations: when you assign a task via email, alfred_ monitors the thread and alerts you if the expected response date passes without a reply or confirmation of completion. This removes the common experience of discovering two weeks later that something was never done, because the system flagged it the day after it was due.
The goal of the system is consistent, timely follow-through without the psychological overhead of holding every delegation in your head. That overhead (the low-level anxiety of "is that thing getting done?") is its own form of attention residue. Externalizing it into a trusted system frees cognitive capacity for the work that requires it.
Try alfred_
You Just Got Promoted
alfred_ is your AI executive assistant. It monitors your delegated tasks, flags anything that goes past deadline, and tracks follow-up threads so nothing falls through the gap between your delegation and their delivery. Build the systematic follow-through that turns delegation from wishful thinking into reliable output. $24.99/month. Works while you sleep.
Track Every Delegation with alfred_Frequently Asked Questions
How do you know what to delegate?
Apply Grove's leverage test: what activities produce high output for the organization that require your specific skills, authority, or judgment? Those are yours to keep. Everything else is a candidate for delegation. A useful secondary question from Drucker: 'What would happen if I did not do this activity at all?' If the honest answer is 'nothing significant,' consider eliminating rather than delegating. If the answer is 'someone else would need to handle it,' that's your delegation candidate.
What do you do when someone doesn't complete a delegated task?
First, assess why. Did the task have all five elements: clear what, why, deadline, resources, and check-in? If not, the failure may be the delegation quality, not the person's performance. If the delegation was clear and complete, the conversation is about performance: what happened, what was the obstacle, what will be different next time? Document the pattern. If it repeats, it becomes a coaching issue (medium TRM), then a performance issue (formal process), not just a missed task.
How do you delegate without micromanaging?
Calibrate your monitoring to TRM, not to anxiety. Set explicit check-in points at the time of delegation ('I'll check in Wednesday') and then don't check in before that time unless there's a specific reason. The check-in point is your scheduled review; checking in earlier signals distrust. For high-TRM tasks, the check-in may be just before the deadline. For low-TRM tasks, check-ins might be daily or every two days. The frequency follows the TRM level, not your comfort level.
Can you delegate to peers (not just direct reports)?
Yes, with a different dynamic. Peer delegation is a request backed by shared goals rather than authority. The five-element framework applies: be clear about what, why, by when, resources needed, and how you'll check in, but the framing is collaborative rather than managerial. 'I need your help with X because you're the right person for this' is more appropriate than 'I'm delegating X to you.' The waiting-for list still applies: track what you asked for and follow up if it stalls.
How do you delegate if you're not a manager?
Individual contributors delegate differently: to vendors, to contractors, to support staff, to peers with complementary skills, and to tools and systems. The TRM framework and five-element structure apply equally to all of these. Delegating to alfred_ for email triage is delegation in this sense: clear what (triage), why (reclaim attention), and the system handles the rest. Building the practice of delegation as an IC, rather than waiting until you're a manager, is itself a high-leverage professional development activity.
What's the difference between delegating and dumping?
Dumping is delegation without the why, without calibrated monitoring, without resources, and often without a clear deadline. It transfers work but not the context or support needed to do it well. The person receiving dumped work either fails (because they lacked what they needed) or succeeds despite the abdication (and resents the lack of support). Effective delegation includes the full five-element framework and monitoring calibrated to TRM. If you're not providing those, you're dumping, regardless of how senior the person is.