Free Calculator

What "I'll Just Do It Myself" Is Actually Costing You

Every hour a manager spends doing IC work is paid twice — once in salary, once in the management leverage that did not get produced. Plus the development your team did not get, plus the queue waiting at your desk, plus the burnout risk you are quietly accruing. The calculator shows what hero mode actually costs.

$

Used for the loaded hourly cost of your time

$

Roughly — pick the team average

0 hr 12 hrs/wk 30 hr
1 5 people 15
1 mo 6 months 24 mo

How much value a mgmt hour produces vs an IC hour

Cost of hero mode so far

$87,000

Significant. You are not getting paid to do IC work.

The bill runs every week you stay in this pattern. Each IC hour is paid twice: once at your salary, once in the management leverage that did not get produced.

Running per month

$14,500

current burn rate

Your total weekly load

52 hrs

management + IC

Team hours waiting

10 hrs/wk

stalled behind you

Your burnout risk

8%

probability of exit

Where the cost is coming from

What You're Choosing Between

Doing the IC work yourself feels faster in the moment and is dramatically more expensive across a quarter. Letting someone else struggle through it costs you patience now and buys you a competent team in three months.

Cost of teaching the work

$4,500

one-time, mostly your time + their early mistakes

What hero mode has cost so far

$87,000

running every week, no upper bound

What This Number Means for You

Hero mode is not a delegation problem. It is an identity problem.

If you knew how to delegate, you would already be doing it. The fact that you keep doing the work yourself, week after week, means something underneath the pattern is rewarding the behavior — usually the relief of doing work you know you are good at versus the discomfort of doing work you are still learning. The article on why you're addicted to being the hero covers the four underlying needs the pattern actually meets and why no delegation framework will solve a need-based pattern on its own.

Your team is not growing because you are doing their growth-stage work.

Every IC task you absorb is a task your direct report did not learn to do. Over six months, the difference between a team where everyone grew 5 percent per month and a team that stayed flat is enormous — and the team that stayed flat has a manager who is exhausted, while the team that grew has one who is increasingly free to lead. The leadership skill at work here is style flexibility — specifically the Pacesetting trap covered in the article on six leadership styles and how to know which one your team needs.

The math gets worse with every month, not better.

Most managers tell themselves "I'll fix this next quarter, the team isn't ready yet." Next quarter arrives and the team is still not ready — because nothing about the pattern produced readiness. The pillar guide on leadership skills for new managers covers the ten skills that close this gap, with a two-gap protocol that tells you which two to work on first instead of trying to fix everything at once.

About the numbers: Loaded labor cost = salary × 1.3 (benefits and overhead). Manager hours/year = 2080. Management leverage multipliers (2-5x) are calibrated against Gallup and McKinsey research on manager effectiveness — high-performing managers consistently produce 2-4x the value of an equivalent IC hour. Team development debt uses a conservative 5 percent foregone growth per direct report per month, valued at loaded labor cost. Burnout risk activates beyond 50 hours/week of total load (Microsoft Work Trend Index threshold), scales linearly, caps at 35 percent probability. Bottleneck cost assumes 2 hours per direct report per week of waiting time when manager is doing 10+ IC hours/week. These are planning baselines, not guarantees. Your real numbers may differ; adjust the inputs.

Why "I'll Just Do It Myself" Costs More Than You Think

The intuitive math on doing IC work as a manager is wrong in a specific way. When you sit down to write the report yourself instead of letting your direct report try it, the cost you feel is the hour you just spent. The cost you do not feel is the four other costs that are running quietly in the background: the management leverage you are not producing, the development your direct report is not getting, the queue of decisions stalling at your desk while you are heads-down, and the compounding load on your own schedule. None of those four show up in your project tracker. All of them add up to something the project tracker is going to surface six months from now, in the form of a team that is not growing and a manager who is exhausted.

The Gallup research base on management effectiveness has held up for over a decade: the highest-performing managers consistently produce 2-4x the value of an equivalent IC hour, because their hour shapes the next five to ten people-hours instead of just producing one hour of output. That ratio is the actual cost of every IC hour you absorb. Your hour is paid twice — once at your salary, and once in the leverage that did not happen while you were producing IC output.

The Four Costs Most Managers Never Count

Cost 1: Lost management leverage. The biggest line in the calculator, and the one most managers cannot see. If your loaded hourly rate is $75 and your management work produces 3x the value of an equivalent IC hour, then every hour you spend doing IC work is $150 of unproduced management value. Twelve hours a week is roughly $1,800 of foregone leverage every week, $7,200 a month, $43,000 over six months. That is the line on the bill nobody is showing you.

Cost 2: Team development debt. Every IC task you absorb is a task your direct report did not learn to do. The compounding effect is brutal in both directions. A team where each person grows 5 percent more capable per month is worth 30-40 percent more six months from now. A team where the manager is doing their development-stage work instead of letting them struggle through it stays exactly where it is. The development debt is invisible because the team's output today still looks fine — you are doing the work. The shortfall shows up six months later when you need them to step up and they cannot, because nothing about the last six months produced the capability you now need.

Cost 3: The bottleneck queue. When you are heads-down doing IC work, the team is not just waiting for you to finish — they are waiting for the decisions, reviews, signoffs, and unblocking that only you can do. Two hours per direct report per week of "stalled, waiting on the manager" is conservative for a team where the manager is heads-down on IC work. On a team of five, that is ten hours a week of team-level waste. Valued at loaded labor cost, the bottleneck alone runs to roughly $400-$600 a week — for nothing produced.

Cost 4: Your own burnout risk. The fourth cost is the one that lands on you personally. When your total weekly load creeps past 50 hours, the burnout probability starts to scale, and the people most likely to ignore the signal are the ones who tell themselves "I just need to push through this quarter" for four quarters in a row. Microsoft's Work Trend Index has consistently surfaced this threshold. Stanford research on knowledge-worker productivity confirms that hours past 50 produce diminishing returns and rising error rates. The risk premium in the calculator is the expected replacement cost weighted by burnout probability — a planning number, not a prediction.

Why Knowing the Cost Does Not Fix the Pattern

Most managers reading this calculator's output for the first time have one of two reactions. The first is "I knew it, I just did not want to look at the number." The second is "the number is real but I cannot stop doing it." Both reactions are correct, and the second is the one this calculator cannot solve.

The reason "I'll just do it myself" persists despite the math is that it is not a knowledge problem. New managers know they should delegate. They have read the RACI charts. They can recite the authority-levels framework. What they cannot do is sit through the discomfort of watching someone else do, slowly and imperfectly, the work the manager could have done in half the time. The discomfort is not laziness or impatience; it is grief for an identity (the high-performing IC) that the new role requires you to put down. The deeper version of this analysis is in the brand article you're not bad at delegation, you're addicted to being the hero.

The calculator does one specific thing: it puts a number on the cost of not solving that identity problem. The number is not the solution. The number is the leverage that creates the conditions for the solution.

What to Do This Week

Three concrete moves, in order:

  1. Pick one IC task on your plate and assign it to the most plausible direct report by Friday. Not the easiest one. Not the one with the lowest risk. The one that has been sitting on your plate longest. Brief them in 15 minutes, set a Friday check-in, and refuse — to yourself — to take it back if it comes in 80 percent of where you would have done it.
  2. Block 90 minutes on your calendar next week for management work that has been waiting. One-on-ones you have been keeping short. Development conversations you have been postponing. The career check-in with your best performer that you have been meaning to have for two months. Use the time that frees up. Do not let it disappear back into IC work.
  3. If hero mode is a pattern you keep falling back into, the underlying issue is usually identity, not technique. The pillar guide on leadership skills for new managers covers the ten skills that compound on a small team, including the self-awareness skill that lets you notice when you are reaching for the IC work as relief instead of for the management work as job.

One task delegated this week. 90 minutes of management work next week. The bill stops compounding the moment the pattern breaks.

Frequently Asked Questions

Why does "I'll just do it myself" cost more than the hours it takes?
Because the hours you spend doing IC work as a manager are paid twice: once at your salary, and once in the management leverage you did not produce while doing them. A manager paid $110k a year is paid roughly $75 an hour loaded. If management leverage produces 2-3x the value of equivalent IC work (the standard finding in any leverage research), then every IC hour the manager works is an IC hour at $75 plus $75-$150 of management value that did not get produced. Across 12 IC hours per week for six months, the unproduced leverage runs into five figures fast. The calculator surfaces this directly because most managers never put a number on it.
My team is small. Why does team size matter so much?
Because the management leverage you are not producing scales with the size of the team you are not leading. A manager of three who spends 12 hours a week doing IC work has three direct reports getting roughly 12 fewer hours of coaching, feedback, decision-making, and unblocking per week. A manager of seven has seven direct reports getting the same shortfall. The cost compounds with team size: more people stalled, more decisions backed up at your desk, more development conversations that never happen. Small teams have lower absolute cost but proportionally identical pain.
Isn't doing IC work sometimes the right call? My team is junior.
Sometimes yes, briefly. The calculator is built around "stuck in this pattern" — IC work as a default, week after week, not as a deliberate one-off. A new hire ramping for two weeks where you do the work alongside them is investment. Doing the same IC work six months later because "they are still not quite ready" is the trap. The honest question: if a new manager replaced you tomorrow with the same team, would they still be doing those 12 hours of IC work in six months? If the answer is no, the gap is yours, not the team's.
What counts as "IC work" for this calculator?
Any work where you are personally producing the output rather than enabling someone else to produce it. Writing the report yourself instead of editing theirs. Building the slide deck instead of reviewing the draft. Doing the analysis instead of coaching them through it. Sending the email instead of letting them send it. The test is "could a competent direct report have done this if I had set them up to?" If yes, it was IC work you did instead of management. The calculator works for any role: tech, ops, sales, customer success, creative. The math is the same.
How is the manager leverage multiplier calibrated?
The default of 3x is conservative for most knowledge-work environments. Research on manager effectiveness (Gallup, McKinsey) consistently finds that high-performing managers produce 2-4x the value of an equivalent IC hour because their hour shapes 5-10 people's hours instead of just one. Set it to 2x if your role has unusually thin management leverage (very small team, very senior reports who need almost no input). Set it to 4x if you lead a team of mid-level people where your coaching, decisions, and unblocking have outsized impact. The default lands where most new managers actually are.
Why is team development debt a real cost?
Because every week one of your direct reports does not grow is a week they will not be carrying more in three months. The compounding works both ways: a team where each person picks up 5 percent more capability per month is worth 30-40 percent more six months from now. A team where you are doing their development-stage work instead of letting them struggle through it is a team that does not grow. The development debt cost in the calculator uses a conservative 5 percent foregone growth per month per person, valued at loaded labor cost. Most managers underestimate this because the team's output today looks fine — they do not see the team that would have existed if you had been managing instead of producing.
How does the manager burnout risk premium work?
After about 50 hours of total weekly load (your management work + the IC work you absorbed), the probability of you burning out and either leaving or breaking starts to scale. The calculator activates the burnout premium beyond 50 hours/week of total load, scales linearly to a cap, and uses your loaded annual cost as the replacement value if you exit. The threshold matches research from Microsoft's Work Trend Index and Stanford on knowledge-worker sustainability. The risk is real, the cost is real, and the people most likely to hit it are the ones who say "I just need to push through this quarter" for four quarters in a row.
I am the bottleneck — work waits on me. Is that in the math?
Yes. The bottleneck cost captures the hours per week your team spends waiting for your input, your review, your decision, or your signoff because you are too busy doing IC work to clear the queue. Two hours per teammate per week of "blocked waiting for the manager" is conservative for a team where the manager is doing 10+ hours of IC work. The hours are valued at loaded team labor cost. This is the cost most managers feel but never quantify: their team going slower because they are the constraint.

The Bill Stops the Moment You Hand Off One Task.

Pick the one that has been on your plate longest. Brief in 15 minutes. Friday check-in. Do not take it back at 80 percent.

Read: You're Addicted to Being the Hero → Pillar: Leadership Skills for New Managers →

Related: Delegation ROI → Related: Manager Leverage →

← All Calculators