Latest / 5 Minute UX / Case Studies: Telling the Story of Your Work
Transcript
- 0:07This lesson is Case Studies: Telling the Story of Your Work.
- 0:10Let's get started.
- 0:18Ask a UX team how they handle case studies, and the answers
- 0:20cluster into a few approaches. [pause:1s] Most start with a
- 0:23feature tour, listing every button and screen without
- 0:25explaining the why. This is the most common pitfall, hiding your
- 0:28actual role and skipping reflection. [pause:1s] The core
- 0:30issue is that these tours lack a story and fail to demonstrate
- 0:33critical thinking. Recruiters and peers look for decision-
- 0:35making, not just visual output or a pretty interface.
- 0:38[pause:1s] When you list features without context, you
- 0:40hide your contribution and miss the chance to show impact. The
- 0:43goal is to turn a finished project into a credible,
- 0:45compelling story for portfolios or talks. [pause:1s] You need to
- 0:48identify the five components of the UX narrative arc to avoid
- 0:51this trap. By applying the narrative framework, you
- 0:53distinguish between essential story elements and irrelevant
- 0:55feature details. [pause:1s] That sets the stage for building the
- 0:58five-part structure that actually showcases your work.
- 1:07The sequence begins by establishing the context and the
- 1:09problem, which means you have to define the user need and the
- 1:11business challenge with absolute clarity right from the start.
- 1:13You are not just listing features here, because a feature
- 1:16tour with no story fails to demonstrate critical thinking,
- 1:18so you must anchor the listener in the specific pain point that
- 1:20demanded a solution. When you skip this foundational step, the
- 1:22rest of your case study floats without gravity, and the
- 1:25audience struggles to care about the screens you designed later.
- 1:27The reason is simple: people connect with struggles, not just
- 1:29solutions, so you need to articulate the 'why' before you
- 1:31ever show the 'what'. This first step sets the stage for
- 1:34everything that follows, ensuring your work feels
- 1:36necessary rather than just decorative. The second step
- 1:38requires you to explicitly state your role versus what the team
- 1:40did, because hiding your actual contribution is a common pitfall
- 1:42that undermines your credibility. You might feel
- 1:44modest about claiming credit, but the field treats vague
- 1:47language as a red flag, so you must distinguish your specific
- 1:49inputs from the collective effort. Instead of saying the
- 1:51team built the app, you need to say you led the user research or
- 1:53defined the information architecture, which clarifies
- 1:55exactly where your expertise lies. This transparency allows
- 1:58hiring managers to assess your individual capabilities, rather
- 2:00than guessing what you might have done behind the scenes.
- 2:02When you are clear about your role, you avoid the trap of
- 2:04diluting your impact with passive voice or ambiguous group
- 2:07statements. The third step highlights the process and the
- 2:09key decisions you made, which means you should focus on the
- 2:11specific choices and the reasoning behind them. You are
- 2:13not documenting every single task, but rather explaining why
- 2:15you chose one path over another, because that reasoning reveals
- 2:18your strategic thinking. For instance, you might explain why
- 2:20you simplified a login flow to reduce drop-offs, rather than
- 2:22just stating that you designed the screen. This distinction
- 2:25separates a mechanic who follows instructions from a designer who
- 2:27solves problems, and it shows how you navigate trade-offs in
- 2:29real time. Experienced practitioners look for these
- 2:31decision points, because they indicate how you will handle
- 2:34complex challenges in future projects. The fourth step
- 2:36presents the outcome and its impact, requiring you to share
- 2:38measurable results or qualitative feedback rather than
- 2:40just claiming completion. A project is not a success story
- 2:42if it lacks evidence, so you must avoid the pitfall of having
- 2:44no measurable outcome by citing specific metrics or user quotes.
- 2:47Whether it is a fifteen percent increase in engagement or a
- 2:49reduction in support tickets, these data points validate the
- 2:51work you described in the previous steps. Without this
- 2:53evidence, your case study remains an opinion, but with it,
- 2:56you transform your narrative into a credible account of value
- 2:58creation. The field respects data, so let the numbers or the
- 3:00user voices speak for the effectiveness of your design.
- 3:02The final step involves honest reflection, where you discuss
- 3:05what you learned, what failed, and what you would do
- 3:07differently if you started over. Skipping reflection is a missed
- 3:09opportunity to show growth, because perfection is not the
- 3:11goal, but continuous improvement is. You might admit that a
- 3:13certain assumption was wrong or that a timeline was unrealistic,
- 3:16which demonstrates self- awareness and maturity. This
- 3:18vulnerability makes you more relatable and trustworthy,
- 3:20because it shows you are capable of learning from mistakes. By
- 3:22including this final piece, you complete the five-part narrative
- 3:25arc, turning a static project description into a dynamic story
- 3:27of professional development. That's the structure of the
- 3:29work; the specific decisions practitioners face inside it
- 3:31come next.
- 3:43Consider your last project and ask yourself which part of the
- 3:45five-part arc feels weakest in your current portfolio. You
- 3:48might find that you hid your role or skipped reflection
- 3:50entirely, which means the story lacks the critical thinking that
- 3:53hiring managers look for. The reason this matters is that a
- 3:56feature tour without a narrative fails to demonstrate your
- 3:58specific contributions to the team’s success. Pause and think
- 4:01about one case study where you can identify a project where you
- 4:04hid your role or skipped reflection. Experienced
- 4:06practitioners notice that rewriting the role section to
- 4:08explicitly name your contributions transforms a
- 4:10generic description into a compelling professional
- 4:12narrative. When you apply this arc to your next portfolio
- 4:15update or conference talk outline, you’ll see how much
- 4:17stronger the story becomes. The signal of strong work here is a
- 4:20clear distinction between what the team did and what you
- 4:22specifically led. So when you rewrite that section, focus on
- 4:25the decisions you made and the impact those choices had on the
- 4:28final product. That brings the lesson full circle, back to the
- 4:30listener and the moment they’ll first put the protocol into
- 4:33practice.
- 4:36Welcome to The Take. I'm joined by a fellow practitioner and
- 4:39together we're going to dig into Case Studies: Telling the Story
- 4:42of Your Work — what it means in practice and what's worth
- 4:44remembering.
- 4:46[HOST] That shift from listing features to explaining the "why"
- 4:49behind decisions feels like a necessary correction. It forces
- 4:52us to stop treating our portfolios as digital
- 4:54scrapbooks. [LEARNER] Absolutely. I find the hardest
- 4:57part is actually admitting what I didn't do. The instinct is to
- 5:00inflate the team's work to make the project look bigger. [HOST]
- 5:03But vagueness reads as incompetence to hiring managers.
- 5:06They need to know exactly where your expertise lies so they can
- 5:09assess risk and fit. [LEARNER] That’s true, though it’s tricky
- 5:12when you were just one voice in a loud room. How do you
- 5:15highlight your specific contribution without sounding
- 5:18arrogant? [HOST] You anchor it in the decision points. If you
- 5:21argued for a specific information architecture because
- 5:24of user data, that's your contribution. [LEARNER] I like
- 5:27that. It moves the focus from output to outcome. But what
- 5:30about the reflection section? It feels vulnerable to admit
- 5:33failure. [HOST] Vulnerability builds trust. If you never show
- 5:36what went wrong, you look like you haven't learned anything
- 5:39from complex projects. [LEARNER] I worry it highlights weaknesses
- 5:42rather than growth. Maybe I’m just too used to selling
- 5:45perfection. [HOST] Perfection is boring. Recruiters wanna see how
- 5:48you navigate trade-offs and recover from bad assumptions.
- 5:51[LEARNER] That makes sense. It shows resilience. I wonder if AI
- 5:54tools will change how we write these narratives though. [HOST]
- 5:57They might help generate the structure, but they can't
- 6:00fabricate the genuine insight behind your decisions. [LEARNER]
- 6:03Right. An AI could write a perfect five-part arc, but it
- 6:06wouldn't have lived the pain of the project. [HOST] Exactly. The
- 6:09story needs your specific scars to feel authentic. Keep the
- 6:12framework, but keep the humanity.