Skip to content

Manage Up - Mistake

When to use it

  • Use the full loop when you want to grow into a larger role, lead work across teams, or prepare for a review cycle. It turns a vague hope for promotion into visible evidence and feedback.
  • Use a lighter update for ordinary work. Share the outcome, current state, risk, and needed decision; a promotion packet for every small fix wastes attention.
  • The benefit is clearer support and fairer recognition. Your manager can remove obstacles, give timely feedback, and explain your impact to people outside the project.
  • The cost is focused reflection and concise communication. Keep the record factual and short; this should not become personal marketing that hides team work.

Common mistakes

  • Waiting until performance review to discuss promotion. The manager has little time to help you close a real gap, and examples have faded. Fix: agree on the next-level bar and a small growth plan early; revisit it in regular one-on-ones. Atlassian notes that regular one-on-ones create room for career goals and action plans.
  • Showing activity instead of impact. “Closed 40 tickets” does not tell a reviewer which problem changed. Fix: connect the work to a baseline, user or business result, risk reduced, decision made, or team capability created.
  • Treating visibility as self-promotion. Broadcasting every task consumes attention and can make collaboration look like solo work. Fix: share a useful decision, result, lesson, or risk; name partners and their contributions. Visibility should make work easier to understand, not make you louder.
  • Assuming your manager knows your work. A manager sees many projects and may not know the before-and-after result or the hard trade-off. Fix: send a short context-action-result update while the work is current. Staff Engineer recommends using clear promotion evidence and becoming known for useful work, not merely becoming more visible.
  • Picking work for title value instead of the team's need. A grand “staff project” can fail or crowd out important work if it solves no real problem. Fix: start with a meaningful team or customer problem, then find the scope in which you can lead it.
  • Claiming the team's work as your own. Reviewers lose trust when the story erases design, product, support, or peer contributions. Fix: say what you owned, what others owned, and how you enabled them; influence is evidence, not a reason to take credit.
  • Asking for vague feedback. “Any feedback?” often earns praise that cannot change your next move. Fix: ask a specific question: “For the next level, was my cross-team leadership clear? What would you need to see again or at a larger scale?”
  • Collecting evidence only from your manager. A manager may not observe how you unblock another team or improve support work. Fix: ask a few close partners for concrete feedback near the work, then use it to correct your own story.
  • Chasing a sponsor before building the work. A sponsor can help an accurate case travel, but cannot replace demonstrated next-level impact. Fix: first operate at the needed scope and make the evidence clear; then ask your manager how the promotion process and advocates work. Staff Engineer describes promotion as a team process and distinguishes missing impact from missing recognition.

Continue to Best Practise.