Consider an experienced individual contributor heading into a promotion cycle after a heavy half year of visible work. They had delivered difficult projects, helped steady cross-functional work, and earned trust from peers. What was at stake was not effort recognition in the abstract, but whether a written case could persuade other people who were not in the room for the work itself. That is where common mistakes in a promotion case showed up.
Their manager was supportive, but support alone was not enough. The packet had to travel beyond direct observation and hold up under comparison with peers pursuing the same level.
The situation that looked stronger than the packet
On paper, the work should have been competitive. The candidate had taken on ambiguous projects, handled partner coordination, and cleaned up problems that had real downstream impact. In conversation, their manager could explain why they were valuable.
But the written case leaned on broad claims. It said they were reliable, proactive, collaborative, and increasingly strategic. Those are helpful signals, but they are not promotion evidence by themselves. A review group needs enough detail to understand scope, decisions, and outcomes without filling in the blanks from goodwill.
Mistake one was listing work instead of proving level
The first weakness was volume without translation. The packet named many projects, meetings, and responsibilities, but it did not make clear why those examples demonstrated performance at the next level.
A weak version sounded like this:
- Led an important cross-functional initiative
- Supported a critical rollout
- Helped multiple teams align
- Improved team processes
A stronger version would have tied each item to level-relevant proof:
- Clarified ownership across three teams when delivery risk was rising, reset the decision sequence, and got the work moving again
- Identified a dependency gap before launch preparation hardened around the wrong plan, which avoided rework and gave partner teams a cleaner path forward
- Introduced a lighter operating rhythm that reduced repeated clarification requests and made handoffs more reliable
The work did not need to change. The explanation did. Promotion discussions are rarely about whether you were busy.
Mistake two was describing effort more clearly than impact
The candidate had plenty to say about what they did week to week. They had far less written about what changed because of those actions. That made the packet read like a strong self-review draft instead of a persuasive promotion argument.
This is one of the most common mistakes in a promotion case. Effort is visible to you because you lived it. Impact is what other people need because they did not.
The stronger rewrite focused on questions such as:
- What moved faster, cleaner, or with less risk because of your work?
- What decision became possible because you did the prep or created clarity?
- What recurring problem happened less after your change?
- What did partner teams start relying on you for?
Where exact metrics were unavailable or too sensitive to carry into a personal note, the candidate could still state directional outcomes clearly. Better alignment, reduced rework, cleaner ownership, and improved decision quality are all meaningful when attached to a concrete example.
Mistake three was hiding the hardest part of the work
A surprising amount of senior-level work looks ordinary after it succeeds. The packet mentioned outcomes, but it did not surface the judgment required to get there. That made hard work look routine.
For example, one project summary said the candidate coordinated stakeholders and kept work on track. That phrasing concealed the actual contribution. What mattered was that they noticed the team was solving the wrong problem, reframed the decision, and redirected effort before more time was lost.
That is the kind of detail reviewers use to infer level. They are not only asking what got done. They are asking how much ambiguity, judgment, and influence the candidate handled.
A promotion packet gets stronger when another reviewer can explain your case without having watched the work happen.
Mistake four was relying on the manager to connect the dots live
The manager knew the story, but the packet assumed the manager would fill gaps in discussion. That is risky. Review conversations are constrained by time, and your case may be compared against better-documented packets in the same meeting.
The improved version made the manager's job easier. Each example answered four questions in a tight format:
- What was the situation?
- What was this person's ownership?
- What changed because of their decisions or execution?
- What proof supports that claim?
That last part matters more than people expect. A short reference to a shipped artifact, stakeholder note, planning document, or before-and-after process state gives the case something sturdier than assertion. ImpactLogr is useful here because the same work note you capture when the project is fresh can later become packet material instead of forcing you to reconstruct proof months later.
What changed when the case was rebuilt
The candidate did not invent new accomplishments. They narrowed the packet to fewer examples and made each one carry more weight. Instead of ten thin bullets, they built a smaller set of stronger stories.
Each story showed:
- the problem or risk
- the decision or ownership they took on
- the outcome that followed
- the evidence another person could repeat
That rewrite did not guarantee a promotion. Promotion decisions depend on timing, comparison sets, and review standards beyond one packet. But it gave the candidate a clearer case that was easier for others to understand and defend.
What you should take from this example
The lesson is straightforward. Strong work can still lose if the packet stays at the level of tasks, traits, and busyness. Common mistakes in a promotion case usually come from weak translation, not weak contribution.
Before you submit your next case, review each example and ask:
- Does this show next-level scope or only activity?
- Did I name the decision that mattered?
- Did I explain what changed because of my work?
- Could another reviewer repeat this example clearly?
- Did I include proof without copying sensitive internal material?
If too many answers are no, the fix is usually better evidence capture, not more last-minute writing. You can start building that evidence earlier by saving your work examples in ImpactLogr as they happen.