Management Trainer

---
name: management-trainer
description: Train new and practicing managers in 1:1s, hiring, delegation, performance management, and team rituals.
category: career
---

## Overview

Most managers are promoted for individual excellence and then left to figure out management alone.
This skill is a practical training curriculum for the actual job: running 1:1s that matter, hiring
well, delegating without abdication, handling performance issues, and building team rituals that
scale. Less theory, more scripts and checklists.

## When to use

- Onboarding into a first management role

- Fixing a struggling team dynamic

- Learning to hire, fire, or run performance reviews

- Improving 1:1s, standups, retros, and other rituals

- Preparing for management interview loops

## Core concepts

- - **The 1:1 is the manager's core product.** Weekly 30 minutes, owned by the report (their agenda
  first), covering: what's on their mind, feedback both ways, career growth. Cancel it and you
  cancel the relationship's maintenance window.
- - **Hire for slope, not just y-intercept.** Past achievement matters less than trajectory,
  learning speed, and values fit. Structured interviews (same questions, scored rubric) beat gut
  feel by a wide margin.
- - **Delegate outcomes, not tasks.** "Own the migration; success is zero-downtime cutover by Q3"
  empowers. "Run these commands" micromanages. Match delegation depth to the person's competence and
  the decision's reversibility.
- - **Performance management is a year-round practice.** Clear expectations in writing, frequent
  feedback, documented check-ins. By review time there should be zero surprises — for stars or
  strugglers.
- - **The manager's output is the team's output.** Your leverage comes through others: unblocking,
  prioritizing, hiring, and creating focus. If you're the bottleneck on decisions, you're failing at
  the job even if you're working hard.
- - **Psychological safety is built in small moments.** How you react to bad news, who gets credit,
  whether dissent is welcomed — these micro-behaviors compound into the team's culture.

## Practical workflow

1. 1. **Audit current state.** For each direct report: engagement level, clarity of goals, growth
   trajectory, any concerns. For rituals: which meetings exist, which add value, which are habit.
2. 2. **Fix the 1:1s first.** Highest leverage intervention. Set the format: report's topics first,
   then your items, then career development (at least monthly). Take notes, track commitments,
   follow through visibly.
3. 3. **Set written expectations.** Every role gets: 3-5 outcome-based goals per half, how success
   is measured, and what "great" looks like versus "fine." Ambiguity is the root of most performance
   disputes.
4. 4. **Build the hiring muscle.** Write scorecards before sourcing (must-haves, nice-to-haves,
   anti-signals). Run structured panels, debrief with scores before discussion, check references
   with specific behavioral questions.
5. 5. **Address performance issues early.** The conversation ladder: informal feedback → explicit
   expectations with timeline → formal PIP → exit. Document each step. Waiting never improves the
   situation.
6. 6. **Design team rituals.** Weekly team sync (decisions and blockers, not status), retros with
   action owners, planning with clear commitments, and lightweight celebrations. Kill or fix rituals
   nobody would miss.
7. 7. **Develop each person.** Know every report's 12-month aspiration. Connect their current work
   to it, assign stretch opportunities, and advocate for them in rooms they're not in.

## Common pitfalls

- - **Being a super-individual-contributor.** Doing your old job plus management means doing both
  badly. Your code commits are not your output anymore.
- - **Avoiding the hard conversation.** Hoping performance issues resolve themselves. They don't —
  they metastasize into team resentment.
- - **Hiring in your own image.** Cloning yourself creates blind spots. Hire for complementary
  strengths and diverse perspectives, scored against the role's actual needs.
- - **No written expectations.** "I thought it was obvious" is the epitaph of many failed
  performance cases. Write it down, confirm understanding, revisit quarterly.
- - **Meeting theater.** Rituals run on autopilot long after they stop helping. Every quarter, ask
  the team: which meeting would you kill? Then kill or fix it.
- - **Forgetting to manage up.** Your manager needs: no surprises, clear team status, and explicit
  asks when you need air cover or resources. Manage up or get managed.