The problem in most design reviews isn't the quality of the thinking. It's that the thinking never reaches the room.
I've sat in hundreds of design reviews over seven years. I've watched talented designers present work that was genuinely good — well-researched, carefully considered, the right answer for the right reason — and watched the room not receive it. The stakeholders looked unconvinced. The questions were defensive. The decisions went sideways.
The design didn't fail. The story did.
Presenting design decisions is not a soft skill or a personality trait. It is a craft — and like any craft, it can be taught, practised, and systematically improved. That was what the third session in this workshop series set out to do.
The Method: S3
The framework I use is called S3: Scenario, Science, Solution.
Scenario: set the stage. Who is the user, where are they, and what are the stakes if this problem goes unsolved? Make the listener feel the context before you explain the decision.
Science: provide evidence. What data, research, behavioural insight, or technical constraint supports your approach? One well-chosen piece of evidence lands harder than five. The goal isn't to overwhelm — it's to show that your decision is grounded in something beyond preference.
Solution: present the outcome. How does your design directly address the scenario using the evidence you've just provided? End with impact, not features.
The structure sounds simple. In practice, it's harder than it looks — because it requires you to resist the pull toward the solution before the room understands the problem. And that pull, it turns out, is very strong.
The First Attempt: What Went Wrong
I gave my team problem statements — randomly assigned topics from an interactive tool I'd built using AI — and asked them to apply S3.
What came back was technically structured but emotionally flat. They all understood the three parts intellectually. Scenario, Science, Solution — the labels were clear. But in practice, every single person jumped to the solution within the first thirty seconds.
The scenario was thin. A sentence, maybe two. The science was thinner. And the solution was fully formed, confidently presented, and completely unearned.
What was missing wasn't knowledge — it was patience. The willingness to sit in the problem before reaching for the answer. To brew in the scenario, to really explain what's going wrong and why, to let the evidence build before the solution arrives.
Designers are trained to solve. Years of briefs, reviews, and client expectations have optimised them for the moment of resolution. S3 asks them to slow down the arrival of that moment — to spend more time in the discomfort of the problem than feels natural. The first exercise showed me exactly how unnatural that felt.
The Fix: Brands They Already Knew
I iterated. The second version used brands — real, familiar ones the team used themselves. Spotify. YouTube. Nike. Myntra. Each person was assigned a brand and given one instruction: tell its story using S3 without naming it. Build a scenario from a real user's life. Bring the science. Then reveal what the brand created and why it worked. The others had to guess the brand from the story alone.
The room transformed completely.
The Spotify story was the one that landed hardest. The person started with a very specific scenario: you're on a long commute, your phone is locked, you want to keep listening — but you're on a data plan and YouTube ads are burning through it. You can't afford to lose the song. You can't afford the interruption. The science followed naturally: how much cognitive disruption a single ad creates mid-listening, how playlist sharing changes the way people discover music, how genre exploration maps to personality in ways that feel personal rather than algorithmic.
Nobody named Spotify. Nobody needed to. The room knew exactly what brand had solved that problem — because they'd lived inside that scenario themselves.
The reaction was immediate. People nodded, smiled, added their own versions of the same experience. The story had found the room because it was true — drawn from a real moment the presenter had personally felt, shaped into a structure that made the design logic visible.
The Story That Struggled
The Myntra story was the hardest to land. The person tried an emotionally ambitious angle — fashion reaching smaller cities and towns through an online platform, people in places that previously had no access to certain styles suddenly able to participate in something they'd been excluded from. It was a genuine insight. It had real human weight.
But it struggled to connect.
The reason, when we discussed it, was that fashion is deeply personal. What frustrates one person about shopping — the return process, the sizing inconsistency, the gap between the photo and the product — is irrelevant to another. The scenario didn't have a specific enough user in a specific enough moment. It was true in a general way, but not true in the way that makes a room lean in.
The lesson wasn't that Myntra is a harder brand to story-tell. It was that the scenario has to be narrow enough to be felt. A universal story is often no one's story. A specific story — one person, one moment, one problem — is the story that travels.
Why Corporate Kills the Baton Pass
The final exercise was a baton pass presentation. Each person owns one section of S3. You begin exactly where the previous person stopped. No recap, no safety net, and — crucially — no option to carry the whole story yourself.
This is where something unexpected surfaced.
In college, group presentations are standard. Everyone gets a section. You learn to hand over, to trust that the next person will pick up the thread, to be satisfied with your part of the story rather than needing to own the whole thing.
Corporate undoes that.
In most professional environments, presentations are solo performances. You prepare the deck. You present the deck. You own the room for the duration. The expectation is that you can carry the full argument from context to conclusion without passing anything to anyone. That expectation, repeated across years of reviews and client meetings, quietly kills the instinct for collective storytelling.
The baton pass broke at the Scenario section. The person assigned to it — someone with a genuinely strong storytelling instinct — couldn't stop at the end of their section. They kept going. Into the science. Toward the solution. Circling back. They weren't being difficult. They were doing exactly what years of corporate presenting had trained them to do: prove that they could carry it.
Being satisfied with less than a minute of talking time in a group presentation — trusting that your contribution has value even when it's deliberately incomplete — is a skill most designers have been quietly unlearning since they entered the workforce.
The baton dropped. We debriefed it openly. Not as a failure but as a pattern worth naming: the instinct to prove yourself in a room is often the instinct that makes the collective story fall apart.
The Change That Happened Quietly
After the session, I didn't see anyone stand up in a meeting and deliver a textbook S3 presentation. That's not how learning transfers.
What I noticed instead was smaller and more durable. The questions my team started asking changed. In product discussions, I began hearing things like: what scenario is this being used in, and by which user? What's failing right now and what's the science behind it? These are S3 questions. They weren't labelling them as such. They were just asking them.
And one or two people developed a specific habit in presentations: before jumping to the solution, they'd take thirty seconds to quickly frame the scenario and touch on the evidence. Not a full S3 structure — just enough to gather the room, orient everyone to the problem, and create the conditions for the solution to land.
That's what good facilitation looks like after the workshop ends. Not a performance of the framework. A quiet absorption of the thinking behind it.
For the Designer Reading This
If you have good ideas but struggle to make them land in a room, the problem is not your ideas. It is the distance between what you know and what the room experiences when you speak.
Close that distance with a scenario. Put a real person in a real moment before you say anything about the solution. Let the room feel the problem before you offer the answer.
And the next time you're in a group presentation — resist the pull to carry the whole story. Your section is enough. Trust the baton. The story belongs to everyone in the room, not just to the person who most wants to tell it.