Example Achievement Log for a Product Designer

This example log tracks a Product Designer's year working on a mobile banking app and internal design systems. The entries capture shipped features, design critiques that stung and stuck, and the unglamorous work of unblocking engineers mid-sprint.

A year in the life of a Product Designer's log

Feb - achievement: Shipped the Scheduled Transfers feature end-to-end. Ran 6 user interviews on the original flow, found 4 people confused by the repeat-on dropdown; redesigned as a checklist. Launched to 15% of users on Feb 18. No support escalations in first week.
Feb - task: Took over Card Settings specs from departing designer. Handed over 23 unreviewed frames to Eng. Spent two days in Figma archaeology to understand what was locked, what was old, what was actually in the backlog.
Apr - feedback: Marcus (Eng lead) in standup: 'This spec is so clear I literally just built it.' That stuck with me. Means fewer Slack clarifications, fewer rework days.
May - achievement: Completed the color token refactor for the design system. Moved 47 hardcoded colors in Figma to a shared library. Reduced design file size by 12MB. Eng now uses same naming convention in code, no more hex-to-design translation.
Jun - task: Redesigned the Payment History table three times. First version had too many columns, users scrolled sideways. Second had collapsible rows, but QA found a bug with sort after collapse. Third version shipped in June with fixed-width columns and a detail drawer.
Jul - achievement: Ran an accessibility audit on the Dashboard. Found 8 WCAG AA violations: contrast on secondary buttons, missing alt text on SVG icons, no focus indicator on the send money button. All fixed by end of July. Passed external audit in August.
Sep - feedback: Product lead Sarah in review: 'You ship with confidence, but you also ship measurable.' She meant the research and the rollout data. I like that framing.
Oct - task: Onboarded new UX researcher, Priya. Spent 4 hours walking her through our Figma, Miro, and user session library. She's running interviews in November now, so I got ahead of it.
Oct - achievement: Designed and shipped the bill split feature. Validated concept with 8 users in Figma prototypes first. Launched Oct 28. Hit 2000 uses in first 10 days, 78% repeat usage rate by week two.
Nov - task: Started the mobile web redesign work. Built a component inventory across both platforms; found 15 inconsistent button states between native and web. Documented a plan to converge them by Q1.
Dec - achievement: Launched the redesigned onboarding flow. User drop-off on step three fell from 34% to 19%. Completion time increased from 3.2 minutes to 4.1 minutes (good: users read the terms now). Net new account opens up 8% in first two weeks.

What makes a strong entry

What most people write: Shipped the Scheduled Transfers feature with a redesigned flow based on user feedback.

What went in the log: Shipped the Scheduled Transfers feature end-to-end. Ran 6 user interviews on the original flow, found 4 people confused by the repeat-on dropdown; redesigned as a checklist. Launched to 15% of users on Feb 18. No support escalations in first week.

The strong version names the research method, the specific problem found, the number of users affected, the launch date and rollout strategy, and a measurable outcome that proves it worked. Without this, the reviewer has no way to know if the feature mattered or if it even got finished.

What most people write: Completed the color token refactor and improved the design system workflow.

What went in the log: Completed the color token refactor for the design system. Moved 47 hardcoded colors in Figma to a shared library. Reduced design file size by 12MB. Eng now uses same naming convention in code, no more hex-to-design translation.

The strong version quantifies the scope (47 colors), the technical benefit (file size cut by 12MB), and the downstream impact (engineers use the same names, reducing translation work). This shows scope and cross-team value, not just effort.

How this becomes your review in November

This year I shipped four major features and completed two system-wide improvements that reduced friction across the team. The bill split feature reached 2000 uses and 78% repeat usage in its first two weeks, and the Scheduled Transfers flow cut support escalations to zero through early user research. I also refactored the color tokens in our design system, reducing Figma file size by 12MB and aligning engineering naming conventions with design, which eliminated an entire category of Slack clarification work. One gap I hit was the Payment History table, which needed three designs before we got the interaction right, that taught me to prototype interactions earlier, not just layouts. Looking ahead, I'm deep in the mobile web redesign and have already mapped 15 component inconsistencies across platforms, so we're ready to converge them by Q1.

Starting your own log

Don't try to reconstruct a year you have already had. Start from today, one line whenever something happens, and let it build. The Perform Review Achievement Log does this for you and can capture wins straight from Slack, and how to start an achievement log covers the wider playbook.

Example Logs for Related Roles

Ready to start your own? Start your Achievement Log free, see how the Perform Review Achievement Log works, or browse performance review phrases for Product Designer.