New support-manager 30-60-90 plan

This is a plan for your first 90 days running a support team — new to management, or an experienced manager new to this team. It is not a rep onboarding plan; the work here is people, metrics, and stakeholders, not the queue. If you are ramping a new rep instead, use the 30-day onboarding plan.

The structure is deliberate: Listen, then Diagnose, then Act. The single most common way a new manager fails is doing all three in week one — arriving with answers, changing things they don't understand, and spending trust they haven't earned. Go in the other order. There is time; the whole point of 90 days is that you have it.

Why the restraint is worth it: Gallup finds managers account for at least 70% of the variance in team engagement across business units (Gallup, State of the American Manager). You are now the biggest single lever on whether this team is a good place to work. That is a reason to get the first quarter right, not fast.

Replace everything in [brackets] before you start.

Your context

---

Days 1-30 — Listen and learn

Goal: build an accurate map of the team, the work, and the numbers before you touch anything. For 30 days, your default answer to "should I change this?" is not yet. You are drawing the map, not redrawing the territory.

People

• Hold a first 1:1 with every direct report — same three questions each (script below)
• For each rep, learn: tenure, what they're good at, what frustrates them, their career goal
• Ask each one: "If you had my job, what's the first thing you'd change?" — log the patterns
• Spot the informal leaders: who the team actually goes to when they're stuck
• Shadow 2-3 reps on live tickets or calls for an hour each

Metrics — freeze a baseline

• Pull and write down, dated the current numbers: volume, [CSAT], response time, resolution time, backlog, reopen rate, QA score, attrition
• For each number, learn how it's defined — and how it's gamed — before you trust it
• Note which metrics have targets, and who set them
• Work a handful of tickets yourself to feel the real job (not to clear the queue)

Systems and process

• Map the stack: [helpdesk], [KB], [chat], [phone], status page, reporting
• Read the team's docs: SLAs, escalation paths, tone guide, schedule, on-call
• Learn the escalation route to [engineering / billing] and who owns each hop
• Find the top 5 ticket drivers and where they actually originate

Stakeholders

• Meet your manager: agree how you'll be measured and lock the 1:1 cadence
• Meet the leads of Product, Engineering, and Sales/CS — ask each: "Where does support let you down?"
• Find out what leadership currently believes about support — fair or not

Exit criteria — end of Day 30

• Held a first 1:1 with every direct report
• A written, dated baseline of every core metric exists
• Can name each rep's strength, frustration, and goal from memory
• Have a shortlist of recurring themes from "what would you fix first?"
• Have made no major structural change yet — this is a pass condition, not a failure

---

Days 31-60 — Diagnose and plan

Goal: turn what you heard into a point of view. Form a few hypotheses about what's actually wrong, test them against the baseline, pick the small number of things worth changing — and ship one visible quick win to earn trust.

Diagnose

• Write 2-3 hypotheses about the biggest problems, each backed by both a number and a quote
• Sort each into load (understaffed, volume spike), process, or skill — they need opposite fixes
• Sanity-check with trusted reps: "Here's what I think is going on — what am I missing?"
• Pick one quick win: visible, low-risk, and something the team already complained about

Plan

• Draft a priority list of 2-3 things, not ten — for each: the problem, the metric it moves, the owner, what "done" looks like
• Decide what you will explicitly not do this quarter, and say so out loud
• Set your operating rhythm: weekly 1:1s, a team meeting, and how you'll review the queue

People

• Stand up recurring 1:1s with every rep — booked, protected, not cancelled when it's busy
• Fix anything urgent from month 1 (a broken tool, an unfair rota, a rep on the edge)
• Start coaching, not just managing: one strength + one growth area per rep

Exit criteria — end of Day 60

• 2-3 written, evidence-backed priorities agreed with your manager
• One quick win shipped — and credited to the team who flagged it
• Recurring 1:1s running with everyone
• A clear "not this quarter" list exists

---

Days 61-90 — Act and commit

Goal: move from listening to leading. Ship your first real improvement, set goals the team owns, and put a plan in front of leadership that you'll be held to. By day 90 you should be running the team, not auditing it.

Deliver

• Execute the top priority from your plan — a real change, measured against the frozen baseline
• Set 1-2 team goals for next quarter, each with a named owner and a target
• Convert any firefighting you've been personally absorbing into a process someone else can run

Team

• Give every rep clear expectations and an honest read on where they stand
• Have a growth conversation with each rep (anchor it to the career ladder)
• Name who's ready for more and who's a flight risk — and act on both

Leadership

• Deliver a 90-day readout: what you found, what you changed, what's next, what you need
• Reset any target the baseline proved unrealistic — with evidence, not opinion
• Agree how support's contribution gets reported upward from here

Exit criteria — end of Day 90

• At least one improvement shipped and measured against baseline
• Next-quarter goals set, owned, and understood by the team
• 90-day readout delivered to leadership
• You're making the day-to-day calls without pushing them upward — you're the manager now

---

At a glance

The first-1:1 script

Ask every rep the same three questions. The repetition is the point — patterns only show up when the questions are identical.

1. What's working that I should protect?
2. What's the most frustrating part of your week?
3. If you had my job for a day, what's the first thing you'd change?

Listen more than you talk, take notes in front of them, and promise nothing you can't deliver. "I don't know yet, I'm still learning the team" is a completely acceptable answer for the first month.

Traps to avoid

• Staying an IC. Clearing the queue yourself feels productive and is the fastest way to neglect the actual job. Your output is now the team's output.
• Changing everything in week one to look decisive. You'll break things you don't understand and spend trust you haven't earned.
• Trying to be everyone's friend — especially if you were promoted from within. Be fair and warm; accept that you are not their peer anymore.
• Trusting the dashboard before you know how each number is defined and gamed.
• Skipping 1:1s because the queue is busy. The queue is always busy. The 1:1 is the job.
• Badmouthing your predecessor. Inherit the team, not the grudge.

Promoted from within? Your hardest week is the one where you have to give a former peer difficult feedback. Do it early, do it kindly, and do it directly — the team is watching to see whether the role changed you into a fair manager or an awkward one.