Emanuele Ceccherini
Project Name
A clear, three-line description of what this project is about.
The context, the challenge, and the users you were designing for.
The kind of stakes and timeline involved.
The challenge
Describe the original brief in plain terms. What was the business problem? What were the constraints? Who were the stakeholders? What were the success criteria? Give enough context that a reader outside the company understands why this mattered.
A second paragraph if needed — perhaps covering user research findings, existing pain points discovered through interviews or data analysis, or the key insight that shaped the direction.
Design explorations
How did you approach the solution space? Describe the different directions explored, the trade-offs considered, and how you narrowed down to the chosen path.
Direction A
First exploration direction. What was the hypothesis, what did it look like, and why it was eventually refined or set aside.
Direction B
Second direction. What was different about this approach, what it solved better, and the key insight that made it a stronger candidate.
Testing results
How did you test the designs? Usability sessions, prototype testing, moderated or unmoderated? What were the key findings and how did they change the design?
Key finding
The most important insight from testing. What users struggled with, what worked well, and the specific change that followed from this observation.
The final design
Walk through the shipped solution. What does it look like, how does it work, and how does it map to the original brief? This is the "hero" part of the case study — give it space.
Detail spotlight
Highlight a specific interaction, micro-animation, or design decision that had outsized impact on the experience. Show the craft.
What we validated
Describe the experiment. What hypothesis were you testing, what were the variants, and what metric were you optimising for?
Control — existing design. Conversion rate: 4.2%.
Challenger — new design. Conversion rate: 6.1% (+45%).
Results
What the data showed, how long the test ran, the confidence level, and what was rolled out to production as a result.
What I took away
-
01
Validate assumptions early
Spending the first week on research and a few quick interviews saved weeks of rework. Getting the brief right is half the design work.
-
02
Shipping beats perfecting
The first version was 80% of the vision. Shipping it, measuring real behaviour, and iterating in cycles produced better outcomes than waiting for perfect.
-
03
Align the team, not just the spec
The best design decisions happened in early conversations with PM and engineers — not in Figma alone.