Brag Doc Template

    Product Designer Brag Doc

    A brag doc for a Product Designer is the proof that the work shipped and worked — not the Dribbble shots. The hard part is showing the *judgment* behind the pixels: the alternatives you killed, the research you ran, the tradeoffs you made explicit. This template surfaces that side, not just the screens.

    Fill it in below. Saves to your browser automatically. Download when you're done.

    What to include

    Designers are graded on shipped impact, design quality, and the multiplier effect — how much better the team is because you were in the room. Each section maps to one of those. Bullets should reference specific projects, metrics, or design artifacts (RFCs, system contributions, research findings).

    Personalize

    Optional · Appears in download

    The template

    01

    Shipped Work & Outcomes

    Features and flows that shipped under your design lead, with measurable outcomes. Not 'I designed X' — 'X shipped and moved Y.'

    • ·Which projects did you design lead, end-to-end? What was the outcome metric?
    • ·What did you ship that improved activation, retention, or conversion?
    • ·Which design did you push for that got pushback initially, and shipped anyway?
    • ·What did you sunset or simplify that was higher-impact than building new?
    02

    Design Quality & Judgment

    The craft side and the judgment side. Polish, accessibility, and the alternatives you didn't ship.

    • ·Which alternatives did you explore but kill? Why?
    • ·What accessibility or inclusion improvement did you ship?
    • ·Where did you push back on a PM's framing of the problem — and what changed?
    • ·Which interaction or detail did you obsess over that shipped because of you?
    03

    Research & User Insight

    The research you ran, commissioned, or referenced — and how it actually changed a decision.

    • ·Which research did you run that changed a roadmap call?
    • ·What user pattern did you surface that the team had been guessing about?
    • ·Which usability finding did you act on (not just file)?
    • ·What did you learn from a launched feature that informed the next?
    04

    Design System Contribution

    Components, patterns, tokens, and docs that other designers and engineers now reuse.

    • ·Which component, pattern, or token did you contribute to the system?
    • ·What did you deprecate or simplify in the existing system?
    • ·Which design-system doc or guideline did you author?
    • ·Whose work got faster because of a system contribution you made?
    05

    Cross-Functional Collaboration

    How you partnered with engineering, product, research, content. The unglamorous alignment work.

    • ·Which engineer's implementation did you pair on that landed cleaner because of it?
    • ·What spec or design doc did you author that prevented a rebuild?
    • ·Which content/copy partnership shaped a flow's voice?
    • ·Where did you escalate a quality bar productively?
    06

    Mentorship & Critique

    The multiplier effect — design reviews, mentorship, and the way you raise the room.

    • ·Which designer did you mentor or coach? What's their trajectory?
    • ·What critique did you give that visibly changed someone's work?
    • ·Which design review did you run or restructure that the team uses now?
    • ·What internal talk, doc, or session did you produce?

    Your entries save automatically in your browser. Nothing is sent anywhere.

    Opens your browser's print dialog · Choose "Save as PDF"

    Weak vs. strong bullets

    The format does the easy part. The bullets carry the weight. A few examples to set the bar.

    Weak

    Redesigned the onboarding flow.

    Strong

    Led the onboarding redesign across 4 surfaces. Shipped after 3 rounds of usability testing on 14 users. D7 activation moved from 38% to 52% (+37%) in the 4 weeks post-launch. Killed 2 earlier alternatives that tested worse — wrote the decision memo.

    Weak

    Worked on the design system.

    Strong

    Owned the Form pattern audit: catalogued 23 variant uses across 8 surfaces, consolidated to 3 canonical patterns, wrote migration guide. 4 product teams adopted; cut new-flow design time by ~40% for any feature involving forms.

    Weak

    Did user research.

    Strong

    Ran 12 interviews with churned mid-market users in Q2. Surfaced one recurring objection (data export friction) the team had been treating as a long-tail issue. Pushed for the rework — shipped Q3 — segment churn dropped 2.1 points.

    Weak

    Helped designers on the team.

    Strong

    Ran weekly design critique for the team's 6 designers. Restructured it from 'show work' to 'present 1 specific decision'; review attendance went from 60% to 95%. Two designers cited the critique in their own promo packets.

    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 iPhone

    Free 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.

    Brag document guide

    What to include and how to write stronger bullets.

    Brag doc generator

    Turn role, goals, and wins into an outline.

    Bloom career journal

    Capture the evidence that feeds your brag doc.

    Frequently asked questions

    Can I use this as a Product 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.