Brag Doc Template
UX Designer Brag Doc
A brag doc for a UX Designer is the running record of research that changed a decision, prototypes that closed a debate, accessibility work that made a product usable for more people, and the design-system contributions that outlasted the project they were made for. Most UX work is invisible six months later, especially the studies that prevented bad decisions. The template below makes it durable.
Fill it in below. Saves to your browser automatically. Download when you're done.
UX Designer Brag Doc
What to include
UX review cases are built on four things: research that changed product direction, usability testing that quantified the user experience, accessibility work that opened the product to more users, and design-system contributions that compounded across the team. Quantify wherever possible (task completion rate, accessibility audit score, study sample sizes). When numbers are not available, name the decision the research moved and the artifact that resulted.
Personalize
Optional · Appears in downloadThe template
Research That Changed Direction
Studies, interviews, or analyses where the finding moved a real decision.
- ·What research did you run that caused the team to ship something different than the initial spec?
- ·Whose mind did you change with the data, and what was the original belief?
- ·What study findings have been cited by other teams or referenced months later?
- ·What did you decide NOT to study, and why was that the right call?
- (no entries)
Prototyping and Concept Testing
Prototypes that closed a debate or revealed a problem before code shipped.
- ·What prototype did you build that prevented a bad direction from getting built?
- ·What concept test exposed a usability gap that would have shipped otherwise?
- ·What fidelity level were you working at and why was that the right choice?
- ·Which prototype became the basis for the final shipped design?
- (no entries)
Accessibility and Inclusive Design
Work that made the product usable for more people.
- ·What accessibility audit or improvement did you lead this period?
- ·What WCAG criteria did the product newly meet because of your work?
- ·What assistive-technology user feedback did you act on?
- ·What pattern did you introduce that the design system now applies broadly?
- (no entries)
Design System and Cross-Team Influence
Patterns, components, or rituals that other designers now use.
- ·What component, pattern, or design token did you contribute that other designers picked up?
- ·What design review or critique did you give that changed someone else's direction?
- ·What documentation, Figma library, or template did you author that the team uses?
- ·What was a cross-team usability problem you helped solve outside your immediate product area?
- (no entries)
Your entries save automatically in your browser. Nothing is sent anywhere.
Opens your browser's print dialog · Choose "Save as PDF"
Generated via Bloom, a career journal for iPhone. Bloom writes this document for you from your daily entries; the template is the manual version. Bloomjournal.cc
Weak vs. Strong bullets
The format does the easy part. The bullets carry the weight. A few examples to set the bar.
Weak
Did user research.
Strong
Ran 12 moderated usability sessions on the onboarding flow over 3 weeks. Identified the password-rule confusion responsible for 18% of dropoff at step 3. Re-designed the affordance; D7 onboarding completion rose from 64% to 79%.
Weak
Improved accessibility.
Strong
Closed 23 of 27 outstanding WCAG 2.1 AA violations across the checkout flow in one quarter. Added focus-trap to the modal pattern (adopted by 4 other teams), screen-reader labels to icon-only buttons, and color-contrast fixes that brought the entire palette to AAA on body text.
Weak
Worked on the design system.
Strong
Designed and shipped the data-table component (sortable, filterable, paginated). Adopted by 6 product areas in 8 weeks. Replaced 4 ad-hoc table implementations and reduced new-table-build time from 2-3 days to under 4 hours by spec.
Weak
Ran concept tests.
Strong
Built 3 competing low-fidelity prototypes for the search experience and ran tree tests with 47 participants. The version 3 IA had a 91% first-click success rate vs 64% and 71% for v1 and v2; PM approved v3 the same week. Saved roughly 6 weeks of build-and-iterate time.
Manual template vs. Bloom generated report
Manual brag doc
- Works when you already remember the right examples.
- Requires manual sorting, rewriting, and evidence cleanup.
- Best for a one-time draft or printable structure.
Bloom generated report
- Starts from the work you captured when it happened.
- Organizes entries by goals, skills, impact, and review period.
- Turns daily evidence into shareable summaries and PDF reports.
You don't fill out a Bloom report. Bloom writes it.
The template above is the manual version. Bloom is the generated version. Thirty seconds when something good happens (speak it or type it) and at review time the entire document is in your share sheet. Same shape as the template. Your numbers, your names, your dates. Already written.
Get Bloom for iPhoneFree to start · iPhone · iOS 17+
Build the evidence before you need the template
Templates help with format. A career journal helps with memory. Use these pages together: learn the structure, generate a quick outline, then keep the source material current in Bloom.
Frequently asked questions
Can I use this as a UX Designer brag doc app replacement?▾
You can use the template manually, but it will only stay useful if you update it consistently. Bloom is the app version: capture wins daily, then generate reports when you need them.
What should a brag doc include?▾
A strong brag doc includes dated wins, measurable impact, collaborators, skills, feedback, decisions, evidence links, and review-category alignment.
Is Bloom a brag doc app?▾
Yes. Bloom is a brag doc app and career journal that keeps the source material current, then turns entries into performance reports, recaps, and reusable career stories.