Managing Up & Workplace Communication
Build trust with your manager, communicate early and clearly, package decisions so they're easy to say yes to, give and receive feedback, handle difficult conversations, and escalate carefully — with a free difficult-conversation planner.
Understand your manager's style
Managing up starts with studying your manager's working style — how they like information, how fast they decide, how they handle risk. Match their channel where you can; it's not about mimicking them, it's about reducing friction so your good work gets noticed.
- Does your manager prefer email, call, or chat? Match their default.
- Do they want detail or one-line summaries? Lead with their preferred length.
- Do they want options or a recommendation? Adjust your pitch accordingly.
- Do they decide fast or slowly? Align your timing to their cadence.
- Note what they worry about — headcount, budget, visibility — and address it.
Over-communicate early, not late
Bad news late is a problem; bad news early is information. Regular, short, predictable updates — good or bad — are how you build trust. No surprises is the goal; a manager who hears about risk from you first rarely blames you for it.
- Give a short, regular status update — even if there's no change.
- Flag risks early with a proposed fix, not a bare problem.
- Never let a deadline pass without a heads-up beforehand.
- Share wins promptly too — managers can't champion what they don't see.
- Confirm key decisions back in writing so you both have a record.
Make it easy to say yes
The best way to get a decision is to package one — bring your recommendation first, the options next, the reasoning last. Most managers will happily approve a well-prepared proposal; few enjoy being presented an open question that's really yours to answer.
- Lead with your recommendation, not the full background.
- Give 2-3 options, with pros/cons and your pick.
- Pre-empt the obvious objections before they're asked.
- Include the ask: approval, budget, time, headcount — make it explicit.
- Make approving the default: 'I'll proceed on Friday unless you object.'
Give and receive feedback well
Feedback is a skill, not a personality. Give it specifically, close to the event, and with the other person's goals in mind. Receive it without defending — hear it, take what's useful, say what you'll change, and park the rest. The receiver sets the value of feedback, not the giver.
- Be specific — names, actions, impact — not vague labels like 'good' or 'poor'.
- Give feedback close to the event, not in a stored-up performance review.
- Ask before giving; invite before receiving.
- When you receive, don't defend — say 'what I hear is...' and what you'll change.
- Follow up to show the feedback landed; it makes the next one easier.
Handle difficult conversations
Difficult conversations get harder the longer they wait. Prepare — know the facts, separate the person from the problem, own your part, and be clear about what you want. Most are far less painful than you expect once you start them well, with a clear opening line.
- Prepare the facts; strip interpretation.
- Separate the person from the problem — no labels.
- Own your part of what happened, however small.
- Open with the outcome you want, not the grievance.
- Practise your first line out loud; the rest gets easier.
Escalate carefully
Escalation isn't failure — done well it's how blockers get moved. Escalate to get help, not to punish; tell your manager first, frame the problem, name what you've tried, and propose what you need. Done badly — late, vague, or as a weapon — it damages trust.
- Escalate the problem, not the person — no blame framing.
- Name what you've already tried and what happened.
- Be specific about the help you need: a decision, a contact, a budget.
- Warn your manager before escalating above them.
- Combine follow-up in writing so the ask is on the record.
Difficult conversation planner
Prepare a tricky conversation in advance — saved to this device — then copy the plan into your notes before you speak.
DIFFICULT CONVERSATION PLAN With: [name] 1. What happened (facts only, no labels): [describe the event objectively — what was said, when, what was the impact] 2. My part in it (small or large): [what you contributed to the situation] 3. What I want from this conversation: [the outcome, not the punishment] 4. My opening line: "[your first sentence — outcome-led, calm, specific]" 5. Follow-up: [what you'll do after — in writing, to confirm what was agreed]
Do
- ✓ Match your manager's preferred channel and length
- ✓ Send short, regular status updates — good or bad
- ✓ Bring a recommendation, not just options
- ✓ Give specific feedback close to the event
- ✓ Escalate to get help, not to punish
- ✓ Confirm important decisions back in writing
Don't
- ✕ Surprise a manager with bad news on the deadline
- ✕ Bring an open question you should answer
- ✕ Store up feedback for a performance review
- ✕ Label people, not behaviours, in difficult chats
- ✕ Escalate above your manager without warning them
- ✕ Defend on autopilot when you receive feedback
Frequently asked questions
How do I give negative feedback without damaging the relationship?
Be specific about behaviour, not personality — 'you interrupted three times in that meeting' rather than 'you're rude'. Give it close to the event, in private, and frame it around shared goals. Own any part that's yours. Most people accept specific, well-timed feedback readily; they reject vague or public criticism. A short follow-up later reinforces that the relationship is intact.
What if my manager never gives me feedback?
Ask for it specifically and regularly. 'What's one thing I could do differently?' is a low-friction opener. Then act on what you hear and mention it back, so the loop closes. If you still get little, build your own feedback from peers and stakeholders — a fuller picture than one manager anyway. The career quiz and a trusted colleague can surface blind spots a quiet manager won't.
When is it appropriate to escalate?
Escalate when you've genuinely tried to resolve something and hit a blocker you can't move alone — typically a decision, a budget, or another team's cooperation. Tell your manager first, frame the problem, name what you've tried, and be specific about the help you need. Don't escalate to punish, and don't escalate above your manager without warning them — it damages trust and usually the result.
How often should I update my manager?
It depends on your role, but a short regular update — weekly for most office roles, daily for fast-moving or remote work — beats ad-hoc bursts. The goal is predictability: your manager should never wonder whether a thing is moving. Include status, risks with your proposed fix, and any decision you need. A weekly pattern also makes performance reviews much easier to write.