Brag document for designers
Capture the outcomes your work created — adoption, conversion, drop-off reduced, a roadmap changed by your research — not a folder of Figma files.
A designer's brag document records the outcomes your work created — adoption, conversion, drop-off reduced, a roadmap changed by your research — not a folder of Figma files. I'm a designer, and I built Workfied because careful designers get overlooked when their real impact stays invisible.
The designer's specific trap
Design impact is diffuse and usually second-hand. You make four teams faster with a component library, and nobody attributes the speed to you. You run the research that kills a costly feature, and the win is invisible because the feature never shipped to be celebrated. If you describe your year as "designed these screens," you've buried exactly the work that proves your seniority.
What to include — and what to cut
- User outcomes you moved — task success up, drop-off down, conversion lifted
- Design-system work — components adopted across teams, and the time it saved them
- Research influence — the specific decisions and roadmaps you changed
- The costly thing you prevented — the feature your research killed before launch
- Your specific contribution to shared work, named plainly
- A tour of Figma files and screens shipped
- "Made it look better" with no outcome
- Output counts — number of mockups, number of flows
- Credit so spread across "the team" that you disappear
- Process for its own sake, detached from any result
How to prioritize
- Business and user outcomes first — the metric your design moved.
- System leverage second — adoption across teams and the time it saved.
- Research influence third — the decisions and directions you changed.
- Craft and process last — supporting evidence, not the headline.
Name the influence, or lose it
Because design impact travels through other people, it has to be named to exist. "Standardized the review criteria now used by the whole design org" is a senior-level claim. "Did design reviews" is not. For shared wins, state your part: "I led the research and defined the direction" is something a committee can weigh.
How Workfied helps here
Workfied captures your design outcomes in your own words the day they land, and keeps them as a private, dated record — so your review and promotion case read as influence, not a portfolio tour. Built for you, never visible to your manager or your company. Encrypted in transit and at rest.
Evidence
Include vs cut
Cut the Figma-file tour. Keep adoption, drop-off, conversion — the outcomes your design produced.
Workfied house view
The trap
You speed up four teams and nobody attributes it to you. Named, it's seniority; unnamed, it's invisible.
Workfied house view
What to capture
The roadmap your research redirected and the costly feature you killed are your strongest, least-visible wins.
Design practice