What to Delegate and What to Keep: A Decision Matrix for Leaders

Most leaders delegate too little — or delegate the wrong things. This tutorial walks you through a repeatable system for making sharper delegation decisions so you stop hoarding work that should belong to someone else, and stop offloading things only you should touch.

Key Takeaways

• Not everything delegatable should be delegated — strategic judgment calls, sensitive personnel issues, and work that builds your direct reports' trust in you often need to stay on your plate.
• The best delegation decisions use two axes: your unique value and task reversibility. Everything else is noise.
• Most managers fail at delegation not because they pick the wrong tasks, but because they hand off the task without the context.

Step 1: Audit Your Task List Without Flinching

Before you can decide what to delegate, you need an honest inventory of what you actually do. Pull up the last two weeks of your calendar and task history. Write down every recurring task — not the big projects, just the day-to-day decisions, approvals, and work items.

Be brutal. According to a 2023 Gallup study on manager effectiveness, high-performing managers spend roughly 40% of their week on work their direct reports could handle with minimal guidance. That number is probably uncomfortable. Good — that discomfort is data.

Concrete action: Block 30 minutes this week. Open a blank doc. List every task you touched in the past 10 days. Don't filter yet. Just list.

Step 2: Score Each Task on Two Dimensions

This is where the delegation decision matrix actually lives. Rate each task on two scales, 1–5:

1. Your unique value — Is this something only you can do at this organization, given your relationships, authority, or expertise? (1 = anyone could do it, 5 = genuinely only you)
2. Reversibility — If someone else handles this and gets it wrong, how bad is the fallout? (1 = easily corrected, 5 = hard to undo)

A task that scores 1–2 on both dimensions? Delegate immediately, no further analysis required. A task that scores 4–5 on both? Keep it — full stop. Everything in the middle is where judgment enters.

Example: Approving routine vendor invoices under $2,000 probably scores a 1 on unique value and a 2 on reversibility. That's leaving your plate today. Delivering a direct report's performance review scores a 5 on unique value (your relationship, your judgment) and a 4 on reversibility. That stays.

Step 3: Categorize Tasks Into Four Buckets

Once you have scores, sort every task into one of four buckets:

1. Delegate now — Low unique value, low reversibility risk. These leave your plate this week.
2. Delegate with coaching — Low unique value, moderate reversibility risk. Delegate, but build in a check-in or approval gate.
3. Keep for now, build toward delegating — Moderate unique value, low reversibility. You could keep doing these forever, but you should be developing someone to take them over.
4. Keep permanently — High unique value, high stakes. These are yours.

That third bucket is the one most managers ignore completely. That's the part nobody talks about — delegation as a long-term investment, not just a workload relief valve.

Step 4: Match Tasks to the Right Person

Picking the wrong delegate is how well-intentioned delegation decisions blow up. Don't just assign to whoever has capacity. Think about who is trying to grow into what.

A junior analyst who wants to move into project management? Give them ownership of a repeatable reporting process, even if it takes twice as long initially. According to research by Adam Grant in Give and Take, people perform significantly better on delegated work when they understand how it connects to their own development goals — not just the manager's needs.

Concrete action: For each "Delegate now" or "Delegate with coaching" task, write one sentence: "I'm giving this to [name] because it will help them develop [specific skill]." If you can't write that sentence, reconsider the assignment.

Step 5: Hand Off the Task and the Context

This is where most managers fail. They throw a task over the wall and act surprised when it comes back wrong.

A proper handoff has three parts: the what (the deliverable), the why (why it matters and who it affects), and the guardrails (what decisions they can make alone vs. what needs your sign-off). Skipping any of these is why you end up re-doing delegated work at 10pm — not because your team is incompetent, but because they were flying blind.

Example: Instead of "Can you take over the weekly status report?" say "Can you own the weekly status report? It goes to the VP on Fridays by noon. The main thing she looks for is blockers, not progress — so lead with problems, not wins. You can format it however you want, but flag me if a blocker involves budget or headcount."

Step 6: Set a Check-In Cadence Without Micromanaging

There's a real difference between accountability and surveillance. Pick a check-in frequency that matches the task's reversibility score — not your anxiety level.

High reversibility? Weekly check-ins for the first month, then monthly once they've got it. Low reversibility? A single follow-up after the first completion is probably enough. The goal is to give people enough rope to actually do the work, while catching problems before they compound.

A 2022 Harvard Business Review analysis found that managers who scheduled structured (but brief) check-ins on delegated work reported 31% fewer "I had to redo it myself" incidents than those who either micromanaged or went fully hands-off.

Step 7: Review Your Delegation Decisions Quarterly

Your task list changes. Your team's capabilities change. A delegation decision you made six months ago might be wrong today — in either direction. Someone who needed heavy coaching on a task in Q1 might be ready to own it fully by Q3. Meanwhile, a task you delegated might have grown in strategic importance and needs to come back to you.

Block 45 minutes at the end of each quarter. Re-run your matrix. It takes less time each iteration.

Concrete action: Put "Delegation audit" on your calendar for the last Friday of every quarter, right now. Not metaphorically. Literally open your calendar.

Before and After: What Changes When You Use This System

Common Mistakes to Avoid

• Delegating outcomes without authority. Asking someone to "handle vendor negotiations" but requiring your sign-off on every reply isn't delegation — it's outsourced admin work. If the task is worth delegating, give them the decision rights to go with it.
• Delegating to the most available person, not the most appropriate one. Capacity isn't the same as fit. Piling work on your highest performer because they're reliable will burn them out, not develop your bench.
• Never delegating anything that feels risky. If your delegation decisions only ever include low-stakes tasks, you're not building your team's capability — you're just offloading busywork. Real development requires real responsibility.
• Treating delegation as permanent. Tasks should move back to you when they escalate in importance, and move further away from you as your team grows into them. It's a dynamic system, not a one-time filing decision.

Frequently Asked Questions

How do I know if I'm delegating too much or too little?

A rough signal: if you regularly work more than 20% more hours than your direct reports, you're probably under-delegating. If your team regularly comes to you for decisions that feel like they should be theirs, you may have delegated without transferring real authority. The matrix helps you calibrate — but gut-check both symptoms.

What if my team doesn't have the skills to take on what I need to delegate?

That's a coaching plan, not a reason to keep everything. If a critical task can't be delegated because no one on your team can handle it yet, that's a development gap worth naming explicitly. For career decisions around team-building, this kind of honest skills audit is often the starting point.

How do delegation decisions differ for remote or hybrid teams?

The matrix works the same way, but the handoff process matters more. Without ambient office visibility, people can't pick up context organically — so the "why" and "guardrails" portions of your handoff brief need to be even more explicit. Written documentation of the task context becomes non-negotiable.

Struggling With Decision Fatigue Around This?

If you're reading this and thinking "I know I should delegate more, but deciding what to delegate feels like more work than just doing it myself" — that's decision fatigue talking. The friction is real. But the matrix reduces it by turning a judgment call into a scoring exercise you can run in under two minutes per task.

DecideIQ is built for exactly this kind of structured decision-making. Instead of staring at your task list wondering what to hand off, you can run your options through a framework that surfaces the right answer without the mental overhead. Try it on your next delegation call — the first one usually takes 10 minutes. The fifth one takes two.

The real question isn't whether you have time to delegate properly. It's whether you can afford to keep making delegation decisions on autopilot.

Related Articles