Revising Case Study Drafts

Here’s why your case study is getting skipped: → It shows what you did. → But not why it mattered. → And definitely not how you decided. Most designers think a case study is a timeline. “Here’s my research → here’s my wireframes → here’s the final UI.” But that’s not a case study. That’s a to-do list. Hiring managers aren’t looking for your steps. They’re looking for your thinking. Here’s the 6-part structure I use with my clients — the same one that got me a 50% salary bump: → Context: Frame the project with stakes and story. → Problem: Define what was broken — and how it hurt users/business. → Objectives: Be clear on the impact you were chasing. → Research: Highlight insights that shifted your direction. → Design: Narrate decisions, not just deliverables. → Results: End with proof, not polish. Bonus tip? Start your case study like a Netflix cold open: “High bounce rates. Angry users. 3 weeks to fix it.” Now you’ve got attention. So ask yourself: Are you telling a story… or just listing tasks? List or narrative — which one builds trust?

🔥 During design interviews, presenting your case study can feel like a make-or-break moment. However, many designers can benefit from strengthening one essential skill: clearly communicating the impact of their work. In my latest video, I worked with Joshua McKenzie, a Senior Product Designer, to critique his case study presentation and help him elevate it to interview-ready status. The goal? Craft a compelling story that showcases his skills, approach, and outcomes 🏆. In this critique, we cover: - How to structure your case study for clarity and engagement. - The importance of pairing visuals with a strong narrative. - Why you need two versions of your case study: one to send, one to present. - How to effectively integrate data and metrics into your story. - Common presentation pitfalls (and how to avoid them). 👀 Watch the full critique and take your portfolio to the next level: https://lnkd.in/gcjxD7VJ Some key takeaways: - Structure matters: Start with a clear business problem and user challenge, then walk through your process step by step, ending with measurable outcomes. - Visuals over words: Avoid text-heavy slides—let your work speak for itself while you guide the story. - Tailor for the audience: Use a concise, visual version of your case study for live presentations and a more detailed, written version if sending out. - Leverage data: Metrics and insights show your impact and differentiate your thinking and work from others. - Practice storytelling: Your ability to communicate your work is just as important as the work itself. ✨ If you're preparing for design interviews or looking to refine your case study game, this video is packed with actionable advice to help you stand out! 💥

A designer I was mentoring had an Apple interview coming up. She asked me to review her portfolio. Her work was strong. Good product thinking, solid research, clean execution. But her portfolio wasn't telling that story. The problem was her headlines. "E-Commerce Redesign." "Mobile App Design." Generic. Her project summaries read like job descriptions — "conducted user research, created wireframes, iterated on prototypes." I told her: imagine a hiring manager reads nothing but your headlines and your first sentence. That's it. Because that's the reality. I've reviewed thousands of portfolios. I spend maybe 60 seconds on a first pass. Probably less. We didn't rewrite her case studies. Didn't touch her process docs or visuals. We just rewrote the headlines and opening lines. "E-Commerce Redesign" became "Reducing cart abandonment by 30% by rethinking the checkout mental model." The first sentence stopped describing her process and started describing her impact. Took about an hour. She got the callback. Here's what I keep seeing: designers bury their best work under process. They lead with what they did instead of what it achieved. It's the same mistake I see in stakeholder presentations — the story is there, it's just hiding behind the methodology. Your case study headline is a hook. Treat it like one. If it could describe anyone's project, it's not specific enough. If it leads with the process instead of the outcome, flip it. Your best work deserves a better headline than "Mobile App Redesign."

If you want founding designer energy, don’t add more screens. Power-up the narration. Because your case study isn’t a diary. It’s a business story. Here's how to narrate like a founder (simple swaps) 👇 ↳ Say: “Our north star was retention; everything else was optional.” Why: Anchors the work to a business goal, especially if you have the metrics. Use instead of: “We improved the UX.” → Better: “Goal: raise D30 retention. Every decision served that.” ↳ Say: “We sized the bet: small scope, high signal, 2-week readout.” Why: Shows you de-risk with fast, measurable tests (and don't forget to get technical with the data here) Use instead of: “We ran some tests.” → Better: “2-week A/B on step-2 change; success = +3 pts activation.” ↳ Say: “Great idea, wrong metric, so we killed it.” Why: Signals ownership and courage to stop low-impact work. Shows certainty. Use instead of: “We might revisit later.” → Better: “No lift on retention after 7 days, ended the experiment.” ________________________________________________________ 🔥 Founder-level storytelling = goal → bet → evidence → impact → next. ________________________________________________________ Copy-paste case-study skeleton👇 Headline: metric, timeline, scope e.g., “–38% time-to-value, +4.2pts activation in 6 weeks (onboarding revamp)” Context: problem, constraints, risks “Activation stuck at 21%; legacy auth; must avoid support spikes.” Bet: hypothesis + success metric “If we fix step-2 friction, activation +3pts; success = +3 in 14 days.” Work: 3 decisions + tradeoffs “Auto-capture addresses (–23% time) / deferred animations (+400ms latency) / stricter validation (–errors, +1 extra field).” Evidence: chart + customer quote Graph: before/after activation; Quote: “Finished setup without pinging support.” Impact: business outcome + money math “–12% tickets (~–2 FTE/qtr ≈ $280k/yr); payback <90 days.” Distribution: loop/SEO/pricing/onboarding lever “90-sec first win + ‘Invite a teammate’ moment → +18% WAU.” Ops: tokens/patterns/checklists created “Input validation pattern removed 3 bug classes; delivery +25%.” AI/Ethics (if relevant): failure modes + guardrails “Human-in-the-loop for edge cases; model card sets expectations.” Next: what you cut + what 2 more weeks would do “Deferred perf uplift; next: reduce latency 300→180ms.” Adopt the language above, drop it into the skeleton, and your case study reads like ownership, not ornament. (also makes it easier for you to present in an interview) #ux #design #johnisaac #tech #ai #productdesign #careers #startups P.S. Ok so this one takes a little practice, or does it? Refining your storytelling technique and keeping it concise is key.

⏱️ It takes about five seconds for a hiring manager to think: “Oh…nice. I’d love to talk to this designer.” ___ Most case studies blend in: long intros, unclear challenges, too many screens, not enough thinking. When a case study feels clear, intentional, and crafted from the first glance, it stands out. Those first 5 seconds aren’t about impressing anyone. They’re about giving the reviewer’s brain a tiny moment of relief: “This designer thinks differently.” ___ 👇 If you are not sure how to achieve it, here are 5 ways to create that feeling: 1️⃣ Start with context, challenge, and stakes (not process) Design managers need orientation before detail. 💡 Use this structure: 1 title sentence → lead with what you learned, not what you did. That's your hook.  3 bullets or lines of text → if the title is exciting, they would like to understand a bit more depth by reading a few lines of text. But make it 5 lines of text, and nobody will read it. 1 infographic → Make it easy to connect the dots at a glance.  Clear framing is a highly underrated skill. Your goal is to curate their attention. ___ 2️⃣ State the type of work upfront (signaling maturity) Was it a redesign, rebuild, rescue, or zero-to-one? Don’t make them guess. 💡 Examples: “Zero-to-one feature for a scaling marketplace.” “Full redesign on legacy architecture.” “Rebuild of onboarding to reduce support load.” It shows you understand the shape of your challenge and can intentionally go about it. ___ 3️⃣ Give the layout air. Calm structure = confident thinking Clutter hides your message. A clean layout reveals it. 💡 What helps: More white space Clear section breaks Larger thumbnails and infographics  Strong typography A clean preview sets the tone for your entire story. ___ 4️⃣ Show intentionality behind outcomes It’s okay if you don’t have metric numbers. What matters is whether you understand how your design connects to behavior and business impact. 💡 Ways to show this: A quick note on why the change reduces friction, increases adoption, etc. Before/after visuals Slack screenshots or teammate comments An “expected business impact” line Intentionality is the differentiator. Evidence is a bonus. ___ 5️⃣ Add an honest moment of reflection Design managers want to work with people who think and grow. 💡 Try sharing: “What you'd do differently next time.” “The toughest constraint and how you handled it.” “One decision that changed everything.” Reflection turns your case study into a window into your mind — not just your output. ___ 🎩 Want to see how your case study lands in those first seconds? I built the 20-Second Portfolio Test, so you can finally get the unfiltered first impressions reviewers never share. It’s quick, fun, and may or may not make you want to redesign everything again 😄 👇🔗 Link in the comments. #portofliochallenge #UXportfolio #portofliotips #productdesigner

No success metrics? No problem. Your case study can still reflect strong business and product thinking. Outside of showing how you landed on your 'final' solution, you can highlight how you think BEYOND THE HANDOFF ❌ "Here are my final designs" = I'm done thinking ✅ "Here's what I'd do next" = I'm always thinking ahead Add a "Next Steps" section to your case study (even if the project didn't ship or you no longer work there, speak to what you would do). Consider talking about: • Metrics you'd track: "Measure task completion time and conversion to learn if the solution is driving expected results and what to explore next" • Research you'd prioritize: "Interview users who dropped off at step 3 to better understand the friction" • Design improvements: "Polish design components and update color palette for accessibility" (especially helpful if you had to use an outdated design system or know that the visual design could improve). • Ideas for tests you'd run: "A/B test the CTA copy to optimize conversion" • Features you'd like to add: "V2 I'll explore adding advanced filtering we learned users wanted, but couldn't fit into scope for V1" You don't need perfect designs or data. You just need to show you understand that good design never stops evolving. Designs aren't ever really final. Your thinking shouldn't be either. Agree? Disagree? Like or comment below 💬 #uxdesign #productdesign #portfolio #casestudies #designthinking #uxcareertips