Brag Doc Template

    Product Manager Brag Doc

    A brag doc is a private running list of the work you've shipped and influenced — kept current so you don't have to reconstruct a year of product decisions from memory. For PMs, the trap is over-indexing on launches and under-indexing on the harder work: the things you killed, the strategy bets you made, the cross-functional alignment you held together. This template forces both to surface.

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

    What to include

    PMs are graded on outcomes, judgment, and leverage. Outcomes are easy to point at when things launch and harder to claim when you killed the right thing. Judgment is what you decided to do — and what you decided not to. Leverage is how much better the people around you became because you were in the room. Fill 3–5 specific bullets per section. Tie every claim to a metric, a decision artifact, or a named person.

    Personalize

    Optional · Appears in download

    The template

    01

    Product Outcomes

    What shipped and what it moved. Revenue, retention, activation, adoption — name the metric.

    • ·Which features did you ship that moved a top-level metric? Name the lift.
    • ·Which experiments did you run? What did you learn — even from failures?
    • ·What did you ship that competitors haven't, and what's the moat now?
    • ·Which old surfaces did you sunset or simplify (often higher-impact than new builds)?
    02

    Strategy & Roadmap Judgment

    What you chose, and what you didn't. The killed-bets and the non-obvious bets are the proof of judgment.

    • ·What did you kill or deprioritize, and what got built instead?
    • ·Which strategy doc or roadmap did you author? Link it.
    • ·What contrarian bet did you make that paid off (or failed instructively)?
    • ·Where did your priority order disagree with the team — and what was the outcome?
    03

    Cross-Functional Leadership

    How you held engineering, design, data, sales, and CS together around a shared bet.

    • ·Which initiative required deep cross-team alignment? How did you keep it aligned?
    • ·When did you mediate a disagreement between functions? What did you decide?
    • ·Whose work did you accelerate by removing ambiguity early?
    • ·Which exec narrative did you author, deliver, or defend?
    04

    Customer & Market Insight

    The research and signal-reading that informed real decisions. Not 'I did 10 interviews' — 'the interviews changed X.'

    • ·What user research did you run that changed a roadmap call?
    • ·Which competitive or market shift did you see early and act on?
    • ·What customer segment insight did you surface that others missed?
    • ·Which data analysis (yours or someone's you commissioned) shifted a decision?
    05

    Communication & Storytelling

    PMs ship by being persuasive. Docs, narratives, exec updates, and decks that moved people.

    • ·Which spec or PRD got cited or reused after launch?
    • ·What narrative did you write that the company started using?
    • ·Which exec presentation moved a decision in your favor?
    • ·Which internal doc became the canonical reference for the team or org?
    06

    Team Health & Process

    The unglamorous work of making the next quarter easier than this one.

    • ·What process did you introduce or kill that improved velocity?
    • ·Who did you mentor or coach? What's their trajectory now?
    • ·What ritual (planning, review, retro) did you fix?
    • ·What did you delegate that you used to do yourself?

    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

    Launched the new onboarding flow.

    Strong

    Owned the onboarding rework end-to-end. D7 activation climbed from 38% to 51% (+34%) across the 4-week rollout. Wrote the spec, ran 2 rounds of user testing, partnered with design on 3 iterations, and shipped 3 weeks ahead of plan after cutting two nice-to-haves in week 5.

    Weak

    Killed the analytics dashboard project.

    Strong

    Recommended killing the in-app analytics dashboard after Q1 interviews showed only 8% of target users wanted it inline (most exported to BI tools instead). Reallocated 1.5 engineers to API improvements that 70% of the same cohort flagged as the actual ask. Q2 API adoption up 4x.

    Weak

    Worked with engineering and design.

    Strong

    Held the launch alignment for v2 pricing across eng, design, legal, and CS over 6 weeks. Authored the rollout playbook, ran a weekly cross-functional standup, and absorbed 12 scope changes from legal review without slipping the public date.

    Weak

    Did customer research.

    Strong

    Ran 22 interviews with churned mid-market customers in Q2. Surfaced a single recurring objection (data export friction) that the team had been treating as a long-tail issue. Re-prioritized the export rework — shipped in Q3, churn in segment dropped 2.1 points.

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