Bonus: Tell the Story Behind Your Project
Nobody gets excited about a feature list. Learn the five-beat story shape — funny hook, who feels it, your AI solution, why it's better, and a UI that shows it — that makes someone else actually care.
🎁 This One’s Optional
The workshop is done — you built, you tested, you shipped a demo. This lesson is for afterward, for anyone who wants to turn this week’s favorite project into a story worth telling — in an interview, on a resume, in a portfolio, or from an actual stage. No pressure to do this today; read it whenever you’re ready.
🤔 Start With the Why, Not the Feature
Nobody leans in for “I built an app that recommends outfits.” That’s a feature. What makes someone actually care is the moment that made you build it — a specific, true, slightly ridiculous thing that happened to a real person.
Here’s the whole shape of a story that sells an idea, in five beats:
- A funny, relatable hook — a specific true moment, not a general statement
- Who feels this — the exact demographic that recognizes themselves in it
- Your AI solution — what you built, introduced as the answer to that moment
- Why it’s better — the honest before/after, not a list of features
- A UI that shows it — the interface itself reflects the story, instead of just narrating it
Let’s walk through all five with one running example.
😅 The Hook: A Story, Not a Statement
Compare these two openers:
“Choosing an outfit can be a difficult and time-consuming decision for many people.”
“Did you ever have a time your girlfriend — or wife — said ‘give me 5 minutes’… and 20 minutes later she’s still standing in front of a closet full of clothes, insisting she has nothing to wear?”
The first is a fact nobody reacts to. The second is a story — specific, a little funny, and instantly recognizable to anyone who’s ever waited by the door for someone else to get ready. That recognition is the entire point of the hook: it makes a stranger think “oh, I know exactly that feeling” before you’ve said one word about your app.
Don’t reach for a dramatic, invented crisis when a small, true, funny moment works better. “5 minutes turned into 20, and she still had nothing to wear” is memorable because it’s small and real — everyone’s lived some version of it. Exaggerating the stakes makes a story feel like marketing copy instead of something that actually happened — and people can tell the difference.
🎯 Who Feels This: Name the Demographic
A hook only lands if it’s aimed at someone specific. “Everyone struggles with decisions sometimes” is too broad to feel like it’s about anyone. Narrow it down until it names a real group of people:
- Not: people who find choices hard
- Yes: someone running late who has ten minutes to leave the house and a closet full of options
That’s the compelling issue — not indecision in the abstract, but indecision at the exact moment it costs you something. You can find the same shape inside your own world: a flight crew member packing an overnight bag with a strict weight limit, or a first-time flyer who overpacked and can’t decide what to wear through security. Same beat, aviation flavor.
✈️ Then: The AI Solution
Once the story has made someone feel the problem, introduce what you built as the direct answer to that exact moment:
“Enter OOTD — type in the event and the weather, and it hands you back one complete outfit pulled from the closet you already own. No standing in front of the closet, no ‘I have nothing to wear’ when there’s clearly something to wear.”
Notice the solution is described in terms of the story that came before it — it resolves the specific moment you just told, not a generic capability.
📈 Why Is It Better?
“It’s an app” isn’t a reason to care. A real before/after is:
Before: [the old way — how long it takes, how it feels, what goes wrong]
After: [your way — how long it takes now, what changed]Example:
Before: “5 minutes” that turns into 20, a closet full of clothes, and still “nothing to wear.” After: two taps, ten seconds, one outfit pulled from that same closet, out the door.
That contrast — not a feature list — is “why it’s better.” It’s the same instinct as the rose and thorn from your Day 3 feedback test: a concrete before-and-after is proof, and proof is what makes a claim believable instead of just optimistic.
🖥️ Let the UI Tell the Story
This is the beat first-time builders skip: the interface itself should reflect the story, not just sit underneath it. If your story is about decision fatigue, an app that shows a scrollable grid of twenty outfit options has quietly rebuilt the exact problem it claims to solve — just moved it onto a screen.
OOTD’s UI, done right, is one card with one outfit on it, and a single “Try Again” button. No grid, no filters, no browsing. The design choice is the punchline of the story: one clear answer, same as the story promised.
This is the same clarity-feedback-hierarchy lens from Day 2 — here, pointed specifically at your pitch. Before you demo, ask: does my screen visibly do the thing my story promised, or does it just technically contain the feature somewhere?
✍️ Try It
Pick your favorite project from the week and draft your own version of the five beats:
1. Hook: [A specific, true, slightly funny moment — not a general statement]
2. Who feels it: [The exact person/situation, not "everyone"]
3. Solution: [What you built, described as the answer to that moment]
4. Why better: [Before/after — time, effort, or feeling, not features]
5. UI: [One sentence on how your screen visibly shows the "after"] Then scale it to fit the room: compress all five into one sentence for a resume line, or stretch each beat out with a live demo if you’re ever on an actual stage. Same shape, different length.
One student pitches: 'My app helps with time management.' Another tells the outfit story above, then shows a one-card UI with a single outfit and a 'Try Again' button. What's the actual difference between these two pitches?
Reveal Answer & Explanation
The second pitch has all five beats — a specific real moment, a named audience, a solution introduced as the answer to that moment, a concrete before/after, and a UI that visibly delivers on the promise. The first has none of them.
“Helps with time management” is a category, not a story — it could describe a thousand different apps and doesn’t make anyone picture a real moment. The outfit story works because it’s specific and true, names exactly who feels it, and then proves the “why it’s better” claim by showing a UI that visibly does the one thing the story promised, instead of just claiming to.
👋 That’s the Whole Workshop
The loop, the PM lens, debugging, real feedback, a permanent home for what you built, and now — the story that makes someone else care. The tool you use next will change. The way you find the true, specific moment behind what you build, and let your UI prove it, won’t. Keep building, and keep telling the story.