All Things Workplace

Stop Doing IC Work Detox How-to

Sep 10, 2026 | How-tos, Leading Others

Your old job will fill every vacuum unless you rename success. Manager success is team outcomes and people development, not personal ticket count. Force a written line agreed with your manager: “I will be measured by…” Then detox the calendar so the sentence can be true.

This play is a 45–60 minute audit and plan, not a guilt trip and not a demand that every company role drop all craft overnight. Player-coach roles exist. Name the split. Cap personal IC scope. Deep reads: From IC to manager, First-time manager playbook, New Manager hub.

Play card

Field Detail
Time box 45–60 minutes audit + plan (then 2 weeks of execution)
Players New/early manager; their manager; teammates who receive delegated work
Goal Detox plan: keep/delegate/drop/delay grid + handoffs + protected manager blocks
Done looks like Calendar shows named 1:1 and planning blocks; at least three IC items have owners or end dates

When to use

  • First 30–90 days as a manager (First 90 days as a new manager).
  • Your calendar is still IC-heavy and 1:1s slip.
  • Your director is coaching you through the transition (Director / VP hub).
  • You are the hero on every fire and the team waits for you.

When not to use

  • Do not abruptly drop critical IC work with no owner. Detox includes coverage.
  • Do not disappear from real emergencies with no plan. Rename coverage; do not ghost.
  • Do not shame craft expertise. Keep enough sharpness to coach; stop being the default bottleneck.
  • Do not run a secret night shift of IC work and call it balance. That is the trap with nicer branding.

Prep inside the time box

  1. Export or skim the last two weeks of calendar + task list (10 min). Meetings, tickets, Slack heroics, reviews only you do.
  2. Inventory in a table (15 min). One row per recurring chunk of work.
  3. Score each row (10 min) with the decision grid below.
  4. Draft renegotiation notes for your boss (10 min).
  5. Pick first three handoffs and schedule them (10–15 min) using Delegation without dumping.

Decision grid: keep / delegate / drop / delay

Option Use when Example move
Keep Only you can bind the company, or short bridge with end date Final customer escalation this month; name exit week
Delegate Outcome can move with context and decision rights Own FAQ, on-call primary, weekly metrics draft
Drop Low value, zombie meeting, report nobody reads Cancel vanity sync; archive unused dashboard
Delay Important but not this sprint; needs an explicit revisit date Internal tool rewrite → revisit after hiring

Every Keep needs an end condition or a reason that survives scrutiny. Forever-keep of your old job means you never took the new one.

Steps (run order)

  1. Fill inventory.
  2. Force each row into one grid choice. No “maybe.”
  3. Write the success sentence with your manager in mind: team delivery, people development, stakeholder clarity, hiring quality, or whatever your company actually rewards.
  4. Book a 20-minute renegotiation with your boss.
  5. Run handoff plays for Delegate rows.
  6. Put recurring manager blocks on the calendar: 1:1s, planning, hiring/admin, thinking. Protect them like customer meetings.
  7. Review in weekly 1:1s for two weeks: what snapped back?

Scripts

Renegotiate with your boss

“If I keep owning [IC work X], [manager work Y] slips: 1:1 quality, hiring, or unblocking the team. I propose I delegate X to [name] by [date], keep [narrow bridge] until [date], and protect [N] hours weekly for management. I’ll be measured by [team outcomes / people development]. Where do you disagree?”

Expectation reset with the team

“I’m shifting from default executor to owner of team outcomes. For [work streams], [names] will own. Come to me for priorities, blockers, and coaching, not as the first hands on every ticket.”

When someone tries to hand it all back

“I can help you think it through. Ownership stays with you unless we explicitly reassign.”

Output artifact: 2-week detox plan

I will be measured by:
Keep (with end dates):
Delegate (owner + handoff date):
Drop (what dies this week):
Delay (revisit date):
Protected weekly blocks:
Handoffs scheduled:
Check-in with my manager on:

Sample inventory (fictional): Priya, new eng manager. Keep: architecture veto on payments (revisit in 6 weeks). Delegate: on-call primary to Alex; release notes to Sam. Drop: optional vendor demo series. Delay: rewrite of internal lint rules to next quarter. Blocks: 5×30-min 1:1s, 2-hour planning, hiring Thursday.

Success after 2–4 weeks (qualitative)

You should see fewer default @mentions for routine craft, 1:1s happening on schedule, at least one visible owned outcome by someone else, and an honest conversation with your boss about how you are measured. You will still touch craft. You should not be the only path to progress.

Watch-outs

  • Identity loss: Grief is normal. Replace “I shipped it” with “we shipped it because the system worked.”
  • Secret night IC work: Hidden heroics keep the bottleneck alive.
  • Delegating only grunt work: People notice. Give real outcomes with clean handoffs.
  • No coverage plan: Detox without owners is abandonment.
  • Universal myths: Not every org needs zero IC work. Name the player-coach split instead of pretending.

Related hubs and plays