Example Achievement Log for a UX Researcher
This UX Researcher spent the year shifting from foundational discovery work into strategic influence on product priorities, with a visible thread of moving teams from assumption-driven to evidence-based decisions. The log captures both the unglamorous reality of recruiting hard-to-reach users and the momentum that builds when research findings actually change what gets built.
A year in the life of a UX Researcher's log
- Jan - task: Took over moderation of the accessibility audit sessions after Sarah left. Four interviews booked with screen reader users, two showed up; learned recruitment for disabled participants needs 3-week lead time and clear payment terms upfront.
- Mar - achievement: Completed diary study tracking checkout flow for mobile commerce users across 14 days. Found 73% abandoned carts when users hit unexpected payment verification step; flagged to Dan in Payments, who deprioritized that flow.
- Mar - feedback: In the search retro, Chen said the research on query intent 'saved us building the wrong thing'. Specific quotes from users in that report made it land where abstract metrics wouldn't have.
- Apr - task: Set up Userlytics panel for continuous monitoring of key user journeys; configured 12 monthly unmoderated tests with rotating participant pools to catch regressions before QA did.
- Jun - achievement: Moderated usability test of dashboard redesign with 8 power users and 7 occasional users split by segment. Heatmaps showed left-sidebar navigation was invisible to 64% of occasional users; design moved to top nav.
- Jun - achievement: Published findings from six-week study of onboarding flows. Compared three variants across 42 new users; variant B showed 34% faster first value, was shipped to 100% of new signups in July.
- Aug - feedback: Product review feedback from Marcus: 'You brought actual human problems into a room full of people defending their roadmap. That's rare.' Said it in the Slack thread on the retention findings.
- Sep - task: Recruited and ran four co-design sessions with enterprise customers to define design system component library. Two sessions didn't yield usable feedback; switched to structured annotation of Figma mockups for sessions three and four.
- Sep - achievement: Completed comparative analysis of competitor platforms for the design system audit. Documented component patterns across Zendesk, Intercom, and HubSpot; contributed accessibility checklist to the DS guidelines.
- Nov - task: Managed recruitment crisis for the B2B buyer research. Original vendor fell through; found and onboarded alternative vendor with 48 hours' notice, delivered 12 qualified interviews on schedule.
- Dec - achievement: Analysed full-year search data from usage analytics and moderated interviews. Identified three intent patterns that didn't match our IA; recommended taxonomy restructure that UX team is testing in Q1.
What makes a strong entry
What most people write: Completed usability test of dashboard redesign.
What went in the log: Moderated usability test of dashboard redesign with 8 power users and 7 occasional users split by segment. Heatmaps showed left-sidebar navigation was invisible to 64% of occasional users; design moved to top nav.
The strong version includes the segmentation strategy, the actual heatmap finding (64% invisibility, not 'low usage'), and the concrete outcome (navigation redesigned). A reviewer can verify this happened and see the impact; the weak version could be invented.
What most people write: Improved recruitment for accessibility studies.
What went in the log: Took over moderation of the accessibility audit sessions after Sarah left. Four interviews booked with screen reader users, two showed up; learned recruitment for disabled participants needs 3-week lead time and clear payment terms upfront.
The strong version names the predecessor, shows the real show rate (50%), and documents a specific operational lesson (3-week lead, payment clarity). It's credible because it admits a stumble and explains what was learned, not because it claims perfection.
How this becomes your review in November
This year I shifted into a more strategic research role, moving teams from assumption-based decisions toward evidence-based ones. The dashboard navigation work and the onboarding variants study both resulted in shipped changes, and feedback from product peers suggests the research is landing because I'm grounding findings in specific user behavior rather than abstract patterns. I also built new operational capacity: the Userlytics continuous monitoring setup and the design system research pipeline will scale how we catch usability issues before they reach QA.
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 Researcher.