Project title placeholder one

Short two-to-three sentence summary: the problem we set out to solve, who it was for, and the outcome we shipped. Keep it tight — a reviewer should grasp the project in under fifteen seconds.

Plain-language statement of the real problem and why it mattered. One sentence on business stakes, one on user stakes — no jargon, no setup, no marketing.

What I did to understand the problem: interviews, diary studies, analytics review, competitive teardown. Two or three insights are what mattered.

1. 01

   Insight one

   The headline insight in a sentence, then a beat of evidence that grounds it.

2. 02

   Insight two

   Second insight that reframed the problem and shaped the direction we ultimately took.

3. 03

   Insight three

   Third insight — often the uncomfortable one that killed an obvious solution.

How I moved from insight to solution. The explorations that mattered, the decisions I made, and the tradeoffs I weighed out loud with the team.

• Decision one

  What was on the table, what I picked, and the tradeoff I accepted.

• Decision two

  The second key call — usually where craft and constraint collided.

• Decision three

  A decision I'd defend in a Staff review — the reasoning, not the artifact.

The final design, walked through by the flows that carry the most weight. Not a screenshot dump — a guided read.

Flow 01

Primary flow

How a user accomplishes the core job, and why each step earns its place.

Flow 02

Edge flow

The edge case that proves the system holds up under real conditions.

What shipped and what it moved.

Where numbers don't tell the whole story: the qualitative shifts in team confidence, customer trust, or the way the product is talked about.

One short paragraph on what I learned, what I'd revisit, and the muscle this project built. Honest, specific, and short.