Users weren't converting to their first retrospective. Support tickets and user interviews pointed to the same problem: the preparation flow was cognitively overwhelming and structurally unclear.
The hypotheses going in were cognitive overload, lack of clarity, and lack of motivation to continue. What made this project interesting was what we chose not to fix — and why that was the right call.
The core insight was that users had no mental model of what a retrospective would look like — so the prep felt abstract and unmotivating. The fix was to make the prep visually mirror what they'd see during the actual retro.
We merged steps, simplified the survey presentation, and reframed each step around the outcome it produced — not the action it required.