| Timeline | e.g. 8 weeks, Apr–Jun 2024 |
| My role | e.g. Lead Product Designer |
| Team | e.g. 1 PM, 2 Engineers, 1 Researcher |
| Tools | e.g. Figma, Maze, Hotjar |
| Platform | e.g. iOS & Android native app |
<aside> <img src="/icons/info-alternate_blue.svg" alt="/icons/info-alternate_blue.svg" width="40px" />
Lead with impact. Hiring managers skim — if they see strong results first, they'll read the rest. Include 2–3 headline metrics (e.g. "Reduced task completion time by 68%" or "Increased conversion by 23%"). If the project hasn't launched or you don't have hard data, state qualitative outcomes: stakeholder buy-in achieved, usability test scores, or design system contributions. Frame outcomes in terms of both user value and business value.
</aside>
<aside> <img src="/icons/info-alternate_blue.svg" alt="/icons/info-alternate_blue.svg" width="40px" />
Write a 2–3 sentence elevator pitch of the project. What was built, for whom, and why it mattered. This is your reader's first impression — make it crisp. Think of it as the subtitle that hooks a hiring manager into reading further.
</aside>
<aside> <img src="/icons/info-alternate_blue.svg" alt="/icons/info-alternate_blue.svg" width="40px" />
Go beyond listing names. Describe your scope of ownership — which parts of the design process were solely yours vs. collaborative? How did you work with PMs, engineers, and researchers day-to-day? If you led anything (design reviews, workshops, mentoring), explain how that came about and what you learned from it. If you needed sign-off from stakeholders, describe how you presented work and navigated feedback.
</aside>
<aside> <img src="/icons/info-alternate_blue.svg" alt="/icons/info-alternate_blue.svg" width="40px" />
Frame the problem as a story, not a statement. What was happening for users? What pain or friction existed? What was the business feeling — lost revenue, support tickets, churn? Use a concrete scenario or quote to make it tangible. Then explain why now was the right time to solve it. A strong problem frame makes the rest of your case study feel inevitable.
</aside>
<aside> <img src="/icons/cursor-click_green.svg" alt="/icons/cursor-click_green.svg" width="40px" />
📸 Visual storytelling tip: Include a screenshot, heatmap, support ticket excerpt, or analytics dashboard that makes the problem visible. Show, don't just tell.
</aside>