Your manager heard about your team's overload from someone else. What should you change?

Share significant risks early — before they're certain — and bring options with a recommendation and a clear ask, so your manager can use their levers in time.

What does a good escalation to your manager contain?

The problem and its impact, two or three options with trade-offs, your recommendation, what you need from them, and by when.

How should you use 1:1s with your own manager?

For decisions, support and your growth — with status shared in writing beforehand — and to ask for feedback on your leadership.

Managing Up — The Team Lead Handbook

Scenario

Example team: the checkout team lead only talks to her manager in their bi-weekly 1:1, mostly about status. When a key engineer resigns and the team is clearly overloaded, the manager hears about it from the product manager first and asks why he wasn't told.

What you see on the team

The manager learns about problems from other people.
Requests for help (headcount, priorities, budget) come too late to act on.
1:1s with the manager are status reports.
The lead feels the manager "doesn't understand" the team's situation.

The common mistake

Treating your manager as an audience for status rather than a partner with context and levers you don't have — and waiting until problems are certain before mentioning them.

Why it happens

Leads want to appear in control, so they solve problems alone and report successes. Managers have limited time and see many teams, so they rely on what they're told. Project Oxygen's list of great-manager behaviours includes "Communicate effectively" (re:Work) — and communication runs both ways.

The playbook

No surprises. Tell your manager about significant problems early, even before you have a solution: attrition risks, conflicts, delivery risks, incidents.

Bring options and a recommendation, not just problems:

Problem: Ana resigned; payment-provider migration has no owner; team at 120% load.
Options:
 1. Delay the migration by 6 weeks (product impact: partner launch slips).
 2. Borrow an engineer from the platform team for 2 months.
 3. Drop the admin-UI rework this quarter.
Recommendation: 3, plus start backfill hiring now.
Need from you: agreement on 3, and approval to open the role this week.

Learn what your manager cares about — their goals, their pressures, how they like information (written, short, detailed?) — and adapt.

Use your 1:1 for decisions and support, not status. Send status in writing beforehand.

Ask for feedback on your own leadership regularly.

Represent the team honestly: workload, morale and wins.

What to say

Early warning:

"Heads-up — nothing decided yet, but I think there's a real risk Ana leaves in the next few months. I'm working on it; I wanted you to know now rather than be surprised."

Asking for a decision:

"I need a decision by Friday on the migration — here are three options and my recommendation. Can we use ten minutes of our 1:1 on it?"

Trade-offs

Early warnings may turn out to be false alarms; label them clearly as risks, not certainties.
Too much detail wastes your manager's time; lead with the decision needed and keep details linked.
Escalating too often can look like you can't handle the role; escalate what genuinely needs their levers.

Signals it's working

Your manager hears about significant issues from you first.
Requests for help arrive while there's still time to act.
1:1s with your manager focus on decisions, support and your growth.
Your manager advocates for the team with an accurate picture.

Key points

No surprises: share significant risks early, labelled as risks.
Bring options and a recommendation, plus exactly what you need.
Learn your manager's goals and preferred communication style.
Use 1:1s for decisions and support; send status in writing.