The Transition Phase (IC to Manager)

🧭 You still have IC work to do. And you’re already responsible for the team. That tension is the job right now — not a problem to fix.

What this chapter is for

The transition from individual contributor to manager is not a single moment. It’s a period — usually 8 to 12 weeks — where you’re doing two jobs at once.

Most people try to brute-force their way through it. That doesn’t work. This chapter gives you a structure instead.

What you’ll find here:

• A principle for what’s allowed during the transition and what isn’t
• A three-phase plan to move through it without burning out
• Clear exit criteria so you know when it’s over

The core principle

You can keep doing IC work — but only if you’re not in the critical path.

The critical path means: your team cannot move forward without waiting for you.

That’s the line. If your IC work makes you the bottleneck, it’s not IC work anymore. It’s a management problem.

Depending on your company, hands-on work may still be expected from you - that’s fine. The question isn’t whether you do it — it’s how you do it without blocking others.

The three phases

Phase 1 — Stabilize (weeks 1–4)

You don’t drop your current work when you step into the role. You make it visible and start moving it out.

Create a list of everything you currently own. For each item, decide:

• Do I keep this for now?
• Do I transfer it — and to whom?
• Does someone need to know what I’m doing here, or can they just take it?

Don’t transfer everything at once. Pick one thing, document it clearly, hand it off.

Phase 2 — Transfer ownership (weeks 4–8)

Now you start moving recurring work off your plate.

• Hand off reviews, releases, support rotation
• For any decision you make repeatedly, write the rule instead of making the decision again
• Stop being the default person. Make someone else the default.

The goal isn’t to disappear. It’s to stop being the only person who knows how something works.

Phase 3 — Build the system (weeks 8–12)

This is where the transition becomes sustainable.

• Set up your core cadences: 1:1s, planning, retrospectives
• Make ownership explicit: who decides, who executes, who needs to be informed
• Replace open loops with documented agreements

You’re not building bureaucracy. You’re building calm.

Two rules that hold this together

Rule 1: Timebox your IC work.

Decide in advance how many hours per week you’ll spend on hands-on work. Protect it. When the time is up, switch.

Rule 2: If it happens twice, build a system.

If you’re making the same decision or doing the same task repeatedly, that’s a signal. Write the rule, delegate the task, or remove it entirely.

These two rules don’t require more discipline. They require less decision-making in the moment — because you already made the decision.

What to keep doing (for now)

• Work that’s timeboxed and doesn’t block anyone
• Work that helps others learn — pairing, reviewing, enabling tools
• Work that’s genuinely yours and has no natural home yet

What to stop first

• Work where you’re the default because it’s “faster” when you do it
• Work that requires you to be online for others to move forward
• Decisions that could be documented as a rule instead

How you know you’re done

You’re through the transition phase when:

• The team ships without waiting for you most days
• Recurring decisions are documented, not stored in your head
• Your calendar is mostly leverage: coaching, alignment, removing blockers

None of these require a perfect system. They require a working one.

Questions to reflect on

• What’s the one piece of work that would block the team most if you disappeared tomorrow?
• What recurring decision do you keep making that you haven’t written down yet?
• Are you timeboxing IC work — or letting it expand into whatever space is left?