Free template · Marketing / Design
Performance review template for a product / ux designer
A ready-to-use, section-by-section template with the competencies that matter for a product / ux designer, role-specific example phrases, and a guard against the stock filler that makes most reviews read as generic. Copy the structure, fill in your evidence, or skip the writing entirely with Crestento.
The template
Four sections, in this order. Length should match the evidence you have — a thin section is honest; an invented paragraph is not.
Summary
One or two paragraphs setting the context: what was expected of product / ux designer this period, and your overall verdict. Lead with the headline.
Example phrasing
“Owned the onboarding redesign from problem reframing through ship (activation lifted from 41% to 58% on the new-user cohort), contributed eight components to the design system (now used across four product surfaces), and ran one-week diagnostic research rounds that changed the framing on the notifications redesign.”
Strengths
The behaviours and outcomes that made the work happen. Anchor in evidence: shipped features and downstream metric movement, design-system component contributions, research rounds run or synthesised.
- Evidence for: problem framing and design judgement.
- Evidence for: visual craft (typography, hierarchy, motion).
- Evidence for: interaction design and prototyping.
- Evidence for: research engagement and synthesis.
Areas for Growth
Forward-looking development edges. Frame as opportunities, not deficiencies. Specific behaviours to develop, not generic product / ux designer criticism.
- One pattern observed across the period.
- One specific behaviour to develop.
- One concrete next step.
Goals for the Next Period
Two or three concrete goals. Each should name a specific behaviour change, a measurable target, and a deadline. Avoid vague aspirations.
Competencies to evaluate
The 7 competencies a strong product / ux designer review structures around, in priority order. Use these as the spine of the Strengths and Areas for Growth sections.
- problem framing and design judgement
- visual craft (typography, hierarchy, motion)
- interaction design and prototyping
- research engagement and synthesis
- design-system contribution and stewardship
- cross-functional partnership (engineering, PM, research)
- design-critique participation (giving and receiving)
Before you write
Strong product designers reframe the problem, not just iterate the visuals. The work that matters is mostly invisible to non-designers: research synthesis, problem-framing decisions, design-system contribution, the trade-offs negotiated with engineering. Pretty figma files are the floor; reframing the actual problem is the ceiling. A review that only celebrates the visual craft misses the design judgement underneath.
Evidence to gather
Strong reviews for a product / ux designer cite evidence of these shapes. Only use a specific value (a percentage, a count, a dollar amount) if you actually have it — don’t invent a number to sound concrete.
- shipped features and downstream metric movement
- design-system component contributions
- research rounds run or synthesised
- PRs reviewed (especially design QA on engineering builds)
- design-doc contributions
- stakeholder satisfaction (designer NPS)
- mentorship of earlier-career designers
Where to find the evidence
Work products a product / ux designer produces. Reference these by name in the review when they’re relevant — it signals you know the work.
- Figma files (exploration + final)
- design rationale documents
- interaction prototypes
- design-system component contributions
- research synthesis docs
- design critiques attended / given
- PR comments on implementation builds
Phrasing that lands vs phrasing that doesn’t
Strong — specific, evidenced, role-appropriate
“Owned the onboarding redesign from problem reframing through ship (activation lifted from 41% to 58% on the new-user cohort), contributed eight components to the design system (now used across four product surfaces), and ran one-week diagnostic research rounds that changed the framing on the notifications redesign.”
Weak — vague, unevidenced, generic
“Strong designer with great taste.”
Phrases to never use
Stock filler that AI-written product / ux designer reviews slip into. Managers spot it instantly. Rewrite to name a specific behaviour instead.
- “talented designer”
- “great taste”
- “creative thinker”
- “user-obsessed”
- “passionate about UX”
- “crafts thoughtful user experiences”
- “raises the design bar”
- “natural designer”
- “consistent creative voice”
Don’t invent these specifics
The details an AI tends to fabricate for product / ux designerreviews. If you don’t have the specific number, name, or date in your notes, leave it out — generic-but-honest beats specific-but- invented every time.
- specific activation / conversion lifts not in input
- named features or projects when only general work was mentioned
- specific design-system component counts not provided
- named research rounds when only general research work was mentioned
- specific stakeholder satisfaction scores not in input
- named designers mentored when not in input
Skip the template, generate the review
Drop your bullet points into Crestento and it produces the polished draft using this exact template structure, tuned for a product / ux designer. Two reviews free, no card.
Try Crestento free