You shipped a feature, unblocked a teammate, or led a tough migration. But when performance review season arrives, can you actually remember what you did six months ago? Most people can’t. That’s exactly why brag items exist — they capture your wins as they happen so you never have to reconstruct your impact from memory.
The problem is that most people write brag items that are either too vague to be useful or so long that nobody reads them. This guide will show you how to write brag items that are concise, compelling, and directly tied to your career growth.
The Impact + How Format
Every brag item in LadderHub follows a simple two-part structure:
Accomplished [Impact / Result] by doing [How / Action]
Impact is the outcome — what changed because of your work. It answers: “So what?”
How is the action — the specific thing you did. It answers: “What did you actually do?”
This format forces you to connect your effort to a business or team outcome. It turns a generic task description into a story about value delivered.
Weak vs. Strong: Side by Side
Let’s look at some real-world examples to see the difference.
1. Shipping a feature
Weak
“Worked on the new search feature.”
Strong
“Reduced average search latency from 1.2s to 180ms by replacing the full-table scan with an Elasticsearch index and implementing query result caching.”
2. Mentoring
Weak
“Helped junior developers.”
Strong
“Enabled 3 junior engineers to deploy independently within their first month by creating a guided onboarding checklist and pairing with each of them on their first production release.”
3. Fixing a bug
Weak
“Fixed a production bug.”
Strong
“Restored checkout flow for 12,000 daily users within 45 minutes by identifying a race condition in the payment service and deploying a hotfix with proper mutex locking.”
4. Process improvement
Weak
“Improved the CI/CD pipeline.”
Strong
“Cut average build time from 22 minutes to 7 minutes by parallelizing test suites and introducing layer caching for Docker builds, saving the team ~2 hours of wait time per day.”
5. Cross-team collaboration
Weak
“Coordinated with the design team.”
Strong
“Shipped the redesigned onboarding flow 2 weeks ahead of schedule by facilitating daily syncs between engineering and design and breaking the project into shippable increments that allowed parallel work.”
Writing the Title
The title is the first thing your manager sees. It should be a short headline — ideally under 10 words — that captures the core achievement. Think of it like a newspaper headline: specific enough to stand on its own.
Link Every Brag to a Skill
A brag item is evidence. But evidence of what? LadderHub lets you link each brag item to one or more skills in your career ladder. This is what turns a list of accomplishments into a structured case for promotion.
When you link a brag item to a skill, you’re saying: “This work demonstrates my competency in this area.” Over time, your manager can see a pattern of evidence mapped to each skill on your ladder making assessments faster and more objective.
Example mapping:
- → “Reduced search latency by 85%” → Software Design, Code Fluency
- → “Onboarded 3 engineers” → Mentoring
- → “Shipped redesign ahead of schedule” → Delivery, Collaboration
When to Write a Brag Item
The best time to write a brag item is immediately after the work happens. Details fade fast. The numbers, the people involved, the specific approach you took — these are vivid today and forgotten next month.
Here are some natural triggers to build the habit:
- ✓ You merge a PR that you’re proud of
- ✓ Someone thanks you in Slack or a meeting
- ✓ You resolve an incident or unblock a teammate
- ✓ A project milestone is reached
- ✓ You present something to the team or stakeholders
- ✓ Friday afternoon — a weekly recap of wins
Common Mistakes to Avoid
Being too vague
“Improved performance” tells your manager nothing. What improved? By how much? Compared to what? Include numbers, percentages, or concrete before/after states whenever you can.
Writing a task list, not an achievement
“Attended 5 meetings, reviewed 12 PRs, updated documentation” is a list of activities, not evidence of impact. Instead, ask: what changed because you did these things?
Waiting too long
If you wait until review season to fill in your brag document, you’ll only remember the most recent work. Months of effort become invisible. Write brag items as they happen or at least once a week.
Underselling your contribution
You don’t have to be humble in a brag document — that’s the whole point. If you drove the decision, say so. If you owned the project end-to-end, say that. Use “I” statements when the contribution was yours.
Forgetting the “How”
“Improved page load time by 60%” is good, but it doesn’t tell your manager what you did. Including the how demonstrates your technical skill and decision-making ability. It’s the difference between showing impact and proving competency.
Quick Checklist
Before you save a brag item, run through this list:
- ☐ Title is specific and under 10 words
- ☐ Impact is stated with a measurable outcome or clear result
- ☐ How explains the specific action or approach you took
- ☐ Skill link connects the brag to at least one ladder skill
- ☐ Date is set to when the work actually happened
Start Building Your Brag Document
Your future self will thank you. Sign up for LadderHub and start capturing your wins today — one brag item at a time.