How-to: Give Upward Feedback to Your Manager
Upward feedback is how you help your manager manage. It is not a roast, a vent thread, or a hostage note in an engagement survey. Done well, it is specific, timely, and aimed at a behavior they can change: meeting design, prioritization, feedback cadence, or decision clarity. Done poorly, it becomes personal, piled-on, or so vague they cannot act.
Time box: 20–30 minutes to prep and 10–15 minutes to deliver in a 1:1 (or a scheduled slot you request). Do not ambush them in a hallway after a bad meeting.
This lives in the Individual Contributor hub and still applies when you manage others and report to a director; see New Manager and Director / VP. If the issue is harassment, discrimination, ethics, or safety, skip DIY upward feedback and use how HR works channels.
When to use / when not
Use when:
– You have a repeating pattern (not one bad day)
– You can name impact on work quality, speed, or team health
– Relationship safety is decent enough for a direct ask
– You are willing to propose a change, not only criticize
Do not use when:
– You are primarily angry and have not cooled down
– The issue requires HR, Legal, or Ethics involvement
– You only have gossip about how they treat others and no first-hand examples
– You are trying to force a reorg, promotion, or peer’s punishment through “feedback”
Upward feedback is not a substitute for documenting serious misconduct.
Prep
Write answers to these before you speak:
- Situation: when and where (meeting, Slack, planning cycle)
- Behavior: what they did or did not do (observable)
- Impact on you / the work: blockers, rework, confusion, morale risk
- Request: one concrete change to try for the next two weeks
- Offer: how you will support the change (agendas, pre-reads, escalation norms)
- Plan B: if they are not receptive, what you will do (clarify expectations in writing, involve skip-level appropriately, or use formal channels)
Skim how departments work together if the friction is cross-team prioritization your manager owns.
Steps
- Pick one theme. Priority whiplash, unclear decisions, missing feedback, or meeting load. Not five.
- Book the slot. Ask for time in the 1:1 agenda or a separate 15 minutes so they are not blindsided mid-status.
- Open with intent (1 min). You want better outcomes together, not a scorecard on their soul.
- Share SBI + request (5–7 min). Situation, behavior, impact, ask.
- Listen (5 min). They may have constraints you do not see (executive pressure, headcount, risk).
- Agree a trial (2–3 min). One change, one check-in date.
- Follow up in writing. Short summary so memory does not rewrite the deal.
- Revisit once. If nothing changes and impact remains, escalate through the path your company defines.
Script (what to say / send)
Agenda line:
Upward feedback ask (10–15 min): one pattern affecting delivery, plus a proposed change.
Opening:
“I want to share something that would help me do better work with you. It’s about a pattern, not a verdict on you as a manager. Are you open to that now?”
Core:
“In the last three planning cycles, when priorities changed in Slack without an updated ranked list, I spent time on work we later dropped. Impact: slipped [project] and duplicate effort with Design. Request: when priorities change, can we update a single ranked list within a day and confirm in our 1:1? I can draft the list for your edit.”
If they get defensive:
“I’m not saying you’re failing. I’m saying this one workflow is costing us. What constraint am I missing, and what alternative would you try?”
If they agree:
“Great. Let’s trial it for two weeks and review on [date]. I’ll send a three-line summary after this meeting.”
Written follow-up:
Summary of today’s upward feedback: pattern [X], impact [Y], trial change [Z], check-in [date]. Thanks for hearing it.
If they refuse any change and work remains blocked:
“I hear that this won’t change right now. I’ll document priorities as I understand them after each shift and flag conflicts in writing so we have a shared record.”
Output artifact
Upward feedback one-pager (private):
| Field | Your notes |
|---|---|
| Pattern | |
| Examples (2–3) | |
| Impact | |
| Request | |
| Their response | |
| Trial + check-in date |
Store it where your 1:1 notes live. If you later need HR guidance, facts beat vibes.
Watch-outs
- Character attacks. “You’re disorganized” lands worse and teaches less than “decisions don’t get written down.”
- Pile-ons. “Everyone feels this” without permission to speak for others is risky. Speak for your experience; invite them to check the team.
- Feedback dumping during their worst week. Timing still matters; schedule it.
- Secret surveys as weapons. Engagement comments can help systems; they are not a substitute for a brave 1:1 when safety allows.
- Career retaliation anxiety. If you reasonably fear retaliation, use formal channels and HR guidance rather than a lone confrontation.
- Skipping the ask. Complaints without a proposed change are harder to use.
- Ignoring business context. Budget, board, or sales commitments may explain thrash; learn enough via finance for non-finance managers and how sales works to ask sharper questions.