The New Technical Manager Manual

You just became a technical manager. Congratulations — and good luck.

Nobody hands you a manual when you get promoted. One day you fix things. The next, you’re responsible for the people who fix things — plus the process, escalations, headcount planning, and the emotional wellbeing of a team that expects you to have answers.

The skills that got you promoted — technical depth, personal output, being the go-to fixer — are not the skills that will make you successful as a manager. You need a different toolkit. This is the manual I wish I had.

                    ┌───────────────────┐
                    │   New Manager     │
                    └─────────┬─────────┘
                              │
      ┌──────────┬────────────┼────────────┬──────────┐
      │          │            │            │          │
      ▼          ▼            ▼            ▼          ▼
┌──────────┐ ┌────────┐ ┌──────────┐ ┌────────┐ ┌──────────┐
│Feedback  │ │Clarity │ │Incidents │ │Quality │ │Self-Care │
│   SBI    │ │ RACI   │ │   OODA   │ │Rubrics │ │  3 Rs    │
└────┬─────┘ └───┬────┘ └────┬─────┘ └───┬────┘ └────┬─────┘
     │           │           │           │           │
     └───────────┴───────────┴───────────┴───────────┘
                             │
                    ┌────────┴────────┐
                    │  Confident      │
                    │  Manager        │
                    └─────────────────┘

Why This Matters

Your first 90 days set a trajectory. Get the fundamentals wrong and you’ll spend a year digging out. Get them right and your team performs, your stakeholders trust you, and you don’t burn out by month six.

These five frameworks cover where most new managers stumble: feedback, role clarity, decisions under pressure, quality standards, and self-preservation.

1. Give Feedback Without Judgment — SBI

Most new managers either avoid feedback or deliver it like a performance review they read online. Neither works.

SBI — Situation, Behavior, Impact — is the most useful tool I’ve found for clear, non-judgmental feedback.

Instead of “you need to communicate better” (vague, accusatory), say: “Yesterday in standup, when you gave the infrastructure update, you used several acronyms without explaining them. I noticed two new team members looked confused.”

That’s specific, factual, and opens a conversation instead of shutting one down.

Use SBI for positive feedback too. It makes praise equally concrete, which is what actually reinforces good behavior.

2. Make Role Clarity a Habit — RACI

The most common source of team friction isn’t skill gaps — it’s role confusion. Who decides? Who does the work? Who needs to be consulted before we ship?

RACI is your answer. For every key activity or decision:

• Responsible: Does the work
• Accountable: Signs off (only one)
• Consulted: Input needed before deciding
• Informed: Needs to know after the decision

New managers skip this because it feels bureaucratic. Then they spend weeks untangling who dropped the ball. A five-minute RACI conversation at the start saves fifty hours of confusion later.

3. Run Incidents, Don’t Fix Them — OODA

When a major incident hits, your instinct as a former individual contributor is to grab the nearest terminal and start debugging. Resist it.

Your job during an incident is not to fix the problem. Your job is to ensure the right people work on it, stakeholders know what’s happening, and the loop keeps turning.

The OODA loop — Observe, Orient, Decide, Act — is the framework for this. As Incident Commander, your only job is keeping the team cycling through OODA faster than the system breaks. You do not touch logs. You assign a Tech Lead to troubleshoot, a Comms Lead for updates, and a Scribe to log everything.

Mantra: the team that cycles through OODA faster, wins.

4. Define Quality, Don’t Assume It

Define what good looks like explicitly. In technical support, that means a rubric: comprehension, accuracy, language, documentation. Score consistently and calibrate regularly.

When quality is defined, feedback becomes objective. “Your ticket scores 3/5 on documentation because the resolution steps weren’t recorded” is a data point, not an opinion.

5. Protect Your Own Energy — The Three Rs

Nobody tells you how emotionally draining management is. You absorb team stress, deliver hard news, navigate politics, and still need to show up composed the next day.

The HBR research on leadership recovery ¹ suggests three practices:

• Reflect: After a hard moment, pause and ask what you’re feeling and why. Write it down. Processing is maintenance, not weakness.
• Reframe: Find the learning opportunity. This isn’t denial — it’s choosing a narrative that lets you move forward.
• Restore: Intentionally detach from work. Block time for restoration the same way you block meetings. An empty tank helps nobody.

Common Mistakes New Managers Make

• Over-helping: Solving problems for your team instead of coaching them to solve it themselves. You’re not the fixer anymore.
• Avoiding hard conversations: Letting performance issues slide because you don’t want to be the bad guy. The team knows. They’re waiting for you to act.
• Going it alone: Not building a peer network of other managers. Management is lonely by design — fight it.
• Losing the craftsman mindset: Stopping your own learning because you’re too busy managing. The best managers are still students of their craft.

Putting It All Together

Let me ground this in a real scenario.

It’s 3 PM. A P1 incident hits — payment processing is down. You declare, assign roles, and run OODA from the IC chair, not from a terminal.

Two hours later, the incident is resolved. In the postmortem, one engineer took too long to escalate. You use SBI to address the handoff delay — specific, factual, not personal. You update the on-call RACI for faster escalation. Your evening deep-work block is shot — you take 10 minutes to Reflect and Reframe before heading home.

Five frameworks in one afternoon. That’s the manual.

Further Reading

• Incident Response with the OODA Loop — Deep dive on applying Boyd’s loop to major incidents
• The Incident Manager’s OS — A complete system for running incidents with OODA, RACI, and the Incident Commander framework

Summary

The move from individual contributor to manager is one of the hardest transitions in any technical career. These five frameworks — SBI for feedback, RACI for clarity, OODA for incidents, rubrics for quality, and the Three Rs for self-care — won’t cover everything, but they’ll cover the gaps that sink most new managers.

You don’t need to be perfect on day one. You just need a system for getting better.