Twice a year, everyone at every company sits down to write the same document: a case for why they deserve the next title. We have reviewed hundreds of these, mostly our own, and noticed that the promo packet is not so much a summary of your work as a translation of it — from what actually happened into a dialect specifically evolved to survive a calibration meeting you will not be in. Here is the dictionary.
"I fixed a bug" becomes "Drove a cross-functional reliability initiative"
The bug was in your own code. You fixed it alone, on a Tuesday, in forty minutes, while listening to a podcast. "Cross-functional" refers to the fact that you also pinged someone on the infra team to confirm it was safe to deploy, and they replied "lol yeah go for it." That single Slack message is the entire cross-functional component of a reliability initiative that appears, in the final packet, as a bullet point with its own sub-bullets.
"I was in the meeting" becomes "Partnered closely with stakeholders to align on strategy"
You said one sentence in that meeting. The sentence was "makes sense to me." This has been promoted, in the retelling, from a sentence to a partnership, and from a meeting to an alignment process, neither of which existed at the time but both of which are now permanently true in the document that determines your salary.
"Nothing broke" becomes "Maintained 99.9% uptime through proactive monitoring"
Nothing broke because nothing was going to break. You did not do anything proactive. You looked at a dashboard that was already green, the way you look at a smoke detector that isn't beeping, and the absence of catastrophe has been reframed as an achievement with a percentage attached, because a percentage is the only number calibration committees are structurally able to read as a fact rather than a feeling.
"I asked a good question in standup" becomes "Identified a critical gap in the team's technical strategy"
The question was "wait, are we sure this handles the empty-state case?" It was a good question. It took four seconds to ask. In the packet, four seconds becomes a gap, the gap becomes critical, and the whole sentence now implies a strategic audit that resembles, in no way, the actual experience of mumbling a concern into a Zoom call while muted on your first attempt.
"I onboarded the new hire" becomes "Built scalable systems for team enablement and knowledge transfer"
You sat with someone for ninety minutes and showed them where the staging environment was. "Scalable" is doing enormous work in that sentence, implying a system that could onboard a thousand people, built instead for an audience of one, over coffee, partly off-topic, including eleven minutes about a show neither of you finished.
Why the translation happens
Because the native language of work — forty minutes, one Slack message, four seconds, ninety minutes — does not survive contact with a calibration spreadsheet, where every row is compared against every other row and the rows that win are the ones written in the register of inevitability. Nobody has ever been promoted on the strength of "it was pretty easy, honestly." The document rewards a specific confidence of phrasing that has only the loosest relationship to the actual difficulty, duration, or import of what you did, and everyone in the room reviewing packets knows this, and writes theirs the same way anyway, because the alternative is losing to someone who didn't.
Our recommendation
Write the inflated version — the system selects for it, and refusing on principle mostly means losing to people with fewer principles and better adjectives. Just keep a private, honest copy somewhere for yourself, in the original dialect: forty minutes, one message, four seconds. It's a useful document. It's just not the one that gets you promoted.
If your packet currently describes a Tuesday afternoon as a "strategic cross-functional initiative" and you're wondering if that's too far, it isn't — email us at contact@b2bsaas.guru and we'll help you go further. We've never met an achievement we couldn't scale.