Project Name Goes Here

A single-sentence framing question or opening statement that hooks the reader. Why does this problem matter? What did we set out to solve?

Overview
Two to three sentences describing what this project was, the context in which it shipped, and the scope of work involved.
My role
Lead Product Designer
Team
PMEMFEBEURMe
Timeline
2025 Q2–Q3
Metric 1
+37%
Context sentence explaining what this number means and why it mattered to the business.
Metric 2
3→ 12.7%
Context sentence for the second metric. Can also be a qualitative outcome if no metric exists.
Metric 3
200%
Third metric or outcome. Keep all three consistent in tone and specificity.

Why this problem mattered, and what was getting in the way

Context paragraph explaining the business or user situation. Include any relevant background data, growth numbers, or market dynamics that made this problem worth solving.

Friction 01
First identified friction point
Short description of this friction, ideally backed by a quote or data point.
Friction 02
Second identified friction point
Short description of this friction, ideally backed by a quote or data point.
Friction 03
Third identified friction point
Short description of this friction, ideally backed by a quote or data point.

How I investigated the problem

One or two sentences framing the research approach. Multi-method research combining qualitative and quantitative signals gives the team a more complete picture than any single method alone.

1

Research method one

Description of the method, sample size, and what it uncovered. For example: dogfooding with the team, customer interviews, analytics funnel analysis.

Supporting image or artifact
2

Research method two

Description of the second method and the specific insight it produced. Name the sample size or data source where possible.

Supporting image or artifact
3

Research method three

Description of the third method. The combination of methods should show triangulation, not repetition.

Supporting image or artifact

What we designed, feature by feature

One or two sentences tying the solutions back to the frictions identified earlier. Each feature below addresses a specific friction and includes the design challenge that shaped the decisions.

Feature 1 — Name of the first feature

Design challenge: the specific tradeoff or constraint we were navigating with this feature.

Screen 1
Caption describing what this screen shows and why.
Screen 2
Caption describing what this screen shows and why.
Screen 3
Caption describing what this screen shows and why.

Feature 2 — Name of the second feature

Design challenge: the specific tradeoff or constraint we were navigating with this feature.

Screen 1
Caption describing what this screen shows and why.
Screen 2
Caption describing what this screen shows and why.
Screen 3
Caption describing what this screen shows and why.

What happened after we shipped

Summary sentence of what the work achieved. If hard metrics exist, lead with them. If not, qualitative outcomes like reduced support tickets, compliance approval, or stakeholder feedback are equally valid.

First outcome bullet with a specific number or qualitative signal
Second outcome bullet grounded in what the business or user actually experienced
Third outcome bullet, ideally naming the source (analytics dashboard, support ticket volume, user interview)

A user or stakeholder quote that validates the outcome in their own voice. Even one strong quote is more credible than three generic claims.

— Source attribution (role, company, context)

What I'd take into the next project

Honest retrospection on what worked, what didn't, and what I'd do differently. This section signals senior-level maturity and is the clearest differentiator between a case study that reads like a report and one that reads like a peer conversation.

What worked
  • First thing that worked well and why
  • Second thing that worked well
  • Third thing worth calling out
What I'd do differently
  • First thing I'd change if doing this again
  • Second honest admission about a tradeoff or blind spot
  • Third learning that applies to future projects

Templates and articles from this project

Optional section for any articles, frameworks, or templates that came out of this work. Signals thought leadership and generosity.