Example Achievement Log for a UX Designer

This UX Designer's log tracks a year of design work across product iterations, user research cycles, and cross-functional collaboration. You'll see concrete deliverables, moments when things didn't work out as planned, and specific feedback from teammates and stakeholders that shaped the work.

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

Jan - task: Started audit of checkout flow for mobile app. Ran first usability session with 6 users on iOS 15; watched them hit the same error state twice before abandoning. Documented all the pain points.
Jan - feedback: Marcus from Product said in standup: 'Your session notes are way clearer than what we usually get from research vendors.' Felt good to have that noticed.
Mar - achievement: Redesigned checkout error states after the January findings. Cart abandonment dropped from 18% to 14% at the error page in the first two weeks. Shipped with confidence intervals logged.
Apr - task: Built component library documentation for 47 UI elements across spacing, colour, and type. Added code examples and Figma links. Took longer than estimated because accessibility labels kept changing mid-sprint.
May - achievement: Led design system adoption review. Twelve product teams now referencing the library; reduced their design-to-handoff time by averaging 30% across three tracked projects. Three teams caught misalignment issues before dev.
Jun - task: Assigned to redesign legacy admin dashboard. Started with stakeholder interviews. Discovered the actual daily users were customer support staff, not internal ops. Had to pivot the whole scope mid-planning.
Jul - feedback: Showed dashboard wireframes to Priya, our lead Support Specialist. She said: 'Finally someone asked us what we actually do here.' Spent two hours with her team instead of going to lunch.
Sep - achievement: Launched new admin dashboard. Support team ticket resolution time improved from 8 min to 5 min average on their most common workflows. Shipped version 1.0 with four requested features disabled for future release.
Oct - task: Ran seven unmoderated remote tests on new onboarding flow. Participants from US, UK, Germany. Ran into platform lag issues with Maze on day two; manually transcribed video notes for the third session to stay on schedule.
Nov - achievement: Onboarding completion rate increased from 62% to 71% after October test insights. Changed the form from nine fields to three, moved verification to a separate step. Account creation time dropped 2 minutes median.
Nov - feedback: Fran, VP Product, in review call: 'Your work keeps showing up in the data.' Acknowledged that the research upfront saves revisions later.

What makes a strong entry

What most people write: Improved checkout flow based on user research.

What went in the log: Redesigned checkout error states after the January findings. Cart abandonment dropped from 18% to 14% at the error page in the first two weeks. Shipped with confidence intervals logged.

The strong version specifies the exact metric (abandonment rate and the two-week window), the before/after numbers, and the fact that rigour was applied (confidence intervals). Six months later, your manager knows what you moved and by how much, not just that you 'improved' something.

What most people write: Worked on admin dashboard redesign project.

What went in the log: Assigned to redesign legacy admin dashboard. Started with stakeholder interviews. Discovered the actual daily users were customer support staff, not internal ops. Had to pivot the whole scope mid-planning.

The strong version includes a real discovery and a real course correction, which proves you know how to listen and adapt. Vague versions hide the fact that you caught an assumption mistake early; specific ones make that judgement visible to the reviewer.

How this becomes your review in November

This year I focused on grounding design decisions in direct user insight and cross-functional collaboration. The checkout error state redesign brought abandonment down from 18% to 14% in the first two weeks because I ran usability sessions early and had the research to back the changes. When I took on the admin dashboard project, I discovered through talking to the support team that the actual users were different from what was planned, and I pivoted scope before we built the wrong thing. That kind of discovery work seems to be valued here: Fran mentioned in my review that my work keeps showing up in the data, which I think reflects the habit of running tests, shipping with measurement, and letting evidence lead the next iteration.

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 UX Designer.