Use short STAR stories with numbers, proof, and impact to show what you delivered across the review period.
You’re staring at a blank self-review box and a year’s worth of work. The way out is a simple, repeatable method that turns busy weeks into clear wins. Below you’ll find a fast method, concrete phrasing, and rewrites you can copy.
Writing Accomplishments For Your Review: Quick Method
Think in moments, not months. Pick 6–10 high-value items that map to goals or competencies. For each one, write a tight STAR note: the situation, your task or goal, the actions you took, and the result. Keep each story to 3–5 lines, and lead with the outcome.
What To Gather Before You Draft
Pull calendar notes, shipped tickets, dashboards, customer quotes, kudos, and any launch docs. Skim the year by quarter, then pick strong items that ladder to team goals. Aim for a mix: revenue, savings, risk reduction, time saved, quality raised, and teammate enablement.
Accomplishment Types And Proof You Can Use
| Category | What To Collect | Sample Metric |
|---|---|---|
| Revenue/Adoption | Sales data, MAU, trial starts, win-loss notes | +12% upsell rate |
| Efficiency | Cycle time, throughput, SLA hits, backlog trend | 42 hours saved/quarter |
| Quality | Bug counts, defect escape rate, NPS/CSAT, refunds | Defects down 38% |
| Cost/Risk | Vendor quotes, cloud bills, incident logs | $96k annualized savings |
| People | Hiring stats, ramp time, retention, peer kudos | Ramp cut from 8 to 5 weeks |
| Customer | Case studies, tickets, quote snippets | Time to first value from 10 to 4 days |
Pick The Right Wins
Balance breadth and punch. One large outcome beats a list of chores. If two items overlap, combine them under the bigger result and name the shared theme. Keep niche work only if it changed a target, removed a blocker, or shaped a team decision.
Turn Tasks Into Outcomes
Swap “what I did” for “what changed.” Start each bullet with the measurable shift, then backfill main moves. This puts the reader in the result fast and sets a strong tone for the rest of the review.
Use STAR To Keep It Tight
Structure beats memory. The STAR pattern (Situation, Task, Action, Result) keeps each note crisp and comparable. It also aids recall during the live meeting and prep. Many HR teams teach this format because it yields clear, specific evidence the reviewer can verify.
Write Clear, Modest, And Confident Bullets
Aim for clean, proud language without hype. Use action verbs and plain numbers. Name partners and teams when credit is shared. Where the metric lags, state the proxy you used. If a win was team-led, write “co-led” or “paired with X team.”
Formula You Can Reuse
Outcome — Action — Proof — Why it matters. One line per item is ideal; two lines max. This layout works across roles and levels, and it reads fast on mobile.
Sample Bullets Across Roles
Product: Raised feature adoption to 31% in 90 days by shipping a two-step setup, adding in-app cues, and partnering with Sales on a short demo clip.
Engineering: Cut build time from 24 to 11 minutes by caching dependencies and pruning test shards, unblocking daily deploys.
Marketing: Lifted trial-to-paid from 7.8% to 10.6% through a three-email onboarding flow and a pricing page tweak based on heatmap data.
Sales: Beat quota 4 quarters running; added $1.2M ARR with a multi-thread playbook and a new mutual plan template used by 8 reps.
Customer Success: Brought churn to 2.1% by launching a risk dashboard and a 30-day salvage motion; 19 saves in Q3.
People Ops: Shortened hiring cycle to 28 days by pre-booked panels and a structured debrief, raising offer-accept to 81%.
Calibrate Scope, Scale, And Stakeholders
Scope tells how wide the work ran, scale shows the size of the move, and stakeholders show who cared. Tie each item to a goal or KPI when you can. If you manage others, include one line on team outcomes and one on org enablement.
Numbers That Land Fast
Pick clear, hard-to-argue figures. Use ranges if needed, and label units. Percentages are great; time saved, dollars, cycle time, NPS, and defect rates also read well. Round when the exact figure adds no value.
Tone That Helps Your Case
Write in first person. Keep verbs strong. Trim adverbs. Avoid hedging words that shrink the win. Where you had help, name it. Where the result fell short, state what changed next and what you’ll try in the coming cycle.
Own Misses Without Dragging The Piece Down
One candid paragraph can raise trust. Pick one setback that taught you something, show the fix you applied, and share early signs that the fix is working. Keep it brief and concrete.
Where To Place Links And Proof
Drop short links to dashboards, shipped PRs, or launch docs after a bullet, not mid-sentence. Use a consistent label like “link.” Put screenshots only when the image carries data a reader needs. Keep alt text descriptive for accessibility.
Phrases That Make Results Pop
Swap passive lines for crisp ones. Lead with the shift, not the effort. The table below shows quick rewrites you can mirror in your draft.
| Weak Line | Stronger Rewrite | Why It Works |
|---|---|---|
| Worked on the new dashboard with the team | Launched a new dashboard used by 54 sellers within 2 weeks | Names adoption and timeline |
| Helped fix bugs in release 4.2 | Cut P1 bugs from 17 to 5 in release 4.2 | Shows scale of the change |
| Assisted with the Q2 launch plan | Co-led the Q2 launch plan that drove 3.4k trials | Shares credit and result |
| Improved page performance | Brought p95 load from 3.1s to 1.8s on the pricing page | Names the exact metric |
| Handled renewals | Renewed 26 of 28 accounts; $740k retained | Clear count and dollar impact |
Make Your Draft Skimmable
Reviewers skim first, then read. Use short headers for each area (Goals, Delivery, Quality, People, Growth). Under each, include 2–3 bullets. Keep the same tense and voice across the page.
One-Minute Outline
- Top outcomes (4–6 bullets)
- How you delivered (tools, methods, cross-team work)
- Growth items you drove
- One setback and what you changed
- Goals for the next cycle
Proof Points Reviewers Trust
Peer quotes, ticket links, and product analytics back up claims. HR teams also like clear ties to company values and goals. Many managers will nudge writers toward short STAR notes because that format reads clean and cuts vague claims.
When You Lack A Direct Metric
Use a proxy. If you can’t name revenue, point to demo-to-close rate, cycle time, adoption, or defect trends. If the figure is sensitive, show a percent shift and keep raw numbers in a private note.
Style, Voice, And Formatting
Drop long intros. Use bullets. Keep line length short so mobile readers don’t get lost. Bold the number in each line if your editor allows it. Keep punctuation light and consistent. Read your draft aloud; stumble points usually need a trim.
Examples You Can Adapt
Individual Contributor (IC)
Raised inbound lead volume 23% by shipping a content refresh and a landing page test. Built a simple brief template so design and copy moved in step.
Moved a stalled partner rollout over the line by drafting a joint success plan and weekly milestone check-ins; signed 3 logos.
Manager
Hired 4 engineers, cut ramp to first merged PR from 30 to 18 days using a buddy plan and a sandbox repo.
Lifted team predictability from 62% to 85% by setting weekly scope reviews and limiting WIP to 2 per dev.
Raised eNPS by 12 points by setting clear norms for code reviews and meeting load; held to a no-meeting block 3 days a week.
Senior Leader
Reset product plan to 3 north-star goals, retired 7 low-yield projects, and raised ARR per dev by 9%.
Launched a quarterly customer council; gathered input from 18 accounts and shipped two roadmap changes based on those sessions.
Template You Can Paste
Results • [Outcome with number] — [Action you took] — [Proof link] • [Outcome with number] — [Action you took] — [Proof link] • [Outcome with number] — [Action you took] — [Proof link] How I Delivered • Tools/skills used, cross-team partners, repeatable method Growth • Skill sharpened, course or project, how it changed your output Setback And Fix • Short line on what missed, the fix you tried, early signal it helped Next Cycle • 2–3 goals with a metric and a date
Timing And Process Tips
Block 90 minutes. Draft without editing, then cut. Read once with your manager’s lens: what do they track, and what would make their review easy to write? Read again with a peer’s lens for clarity and tone.
Two Smart References
You can scan the HBR self-assessment guide for a short set of steps on framing your wins, and check MIT HR’s review pages for forms and process cues used by many orgs.
Final Checks Before You Submit
- Six to ten items, each tied to a goal or KPI
- Outcome first, then the action and proof
- Numbers vetted; units labeled
- Names of partners where shared work applies
- One short note on a miss and the fix
- Plain links to dashboards or PRs
- A short goals list for the next cycle
Make It Easy For Your Manager
Hand them clean material. Send the document and a one-page summary of outcomes. Add links to proof and call out where you want coaching. The aim is a fair rating, a clear raise case, and agreement on next steps.