🔥 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! 💥
Effective Ways To Present Your Design Process
Explore top LinkedIn content from expert professionals.
Summary
Presenting your design process is more than showing polished designs; it's about effectively communicating the story behind your work, the challenges you faced, and the impact of your solutions. A strong presentation can help you stand out in a competitive field by highlighting both your technical skills and critical thinking abilities.
- Craft a clear narrative: Structure your presentation to include the problem, your approach, and the outcomes, ensuring you connect your design decisions to user and business needs.
- Visuals over text: Use high-quality, impactful visuals paired with concise explanations to keep your audience engaged and make your story easy to follow.
- Show your thought process: Go beyond showcasing the final product—explain the "why" behind your decisions, demonstrate how you addressed challenges, and include measurable results to highlight your impact.
-
-
We all know we're supposed to "show instead of tell." But most design portfolios fail to do this and here's why. 👇 Designers love showcasing their raw work in their portfolios including outputs or deliverables such as: → Sketches → Diagrams → User flows → Wireframes → Sticky notes → Journey maps But to be honest, 90% of the time, I have absolutely no idea what is going on in those images. For example, I'll often come across a screenshot or picture of 25+ sticky notes, but: → They are too zoomed out. → If I zoom in, they're too blurry. → Even if I can seem them, they're too overwhelming. Then I start asking myself questions such as: → Am I supposed to read every sticky note? → What's important about these sticky notes? → Is this worth my time and attention to decipher? This is where storytelling comes in. What if instead of showing a raw zoomed out screenshot of sticky notes, we instead pulled out the key highlights and takeaways? Then we can guide the reader's attention to what's actually important, and optionally include a link to the original raw image afterwards. This creates a far more compelling narrative for our audience (hiring managers and recruiters), and ensures we're showing the right level of detail that is necessary to understand the story. Now to be clear, I'm not saying you should entirely avoid raw images or assets (or even raw Figma files). For example, these can be effective during the interview process because the designer can use their voice to guide their audience through the image. But when it's an online written case study submitted with an application, then you won't be in the room when a hiring manager first sees it. In that moment, your story will need to stand on it's own. It will need to communicate the right level of clarity and detail to compel the hiring manager to offer you an interview. In summary, when we want to "show instead of tell", that doesn't mean slapping a raw screenshot or image in our portfolio. It means reflecting on how we're using our words and images to give context, clarity, and tell an impactful story. Use it effectively to your advantage. What are your thoughts? #ux #design #portfolio #casestudy #storytelling
-
Not getting another interview after your portfolio presentation? Maybe this is why 👇 I've sat in many portfolio presentations. I also work with numerous mentees, helping shape their stories. The biggest mistake I always see is not showcasing the why behind your work. Context. So many presentations go like this: - Hi, it me 👋 - Here's my first case - Here is a persona I made - Here is another persona I made - Here is an arbitrary user flow - Here is a sketch I made - Here is a wireframe I made - Here is the final solution - I learned a couple of things Your presentation should be a story, not a simple show and tell. Don't just tell your audience WHAT you did. Tell them WHY you did it. The why connects your thought process to your design. We want to hear what drove your decisions. Paint a vivid picture of the challenges you faced, the insights you stumbled upon, and the brainstorms that led to breakthroughs. What separates you from other designers is how you think and your design decisions. ✅ Frame your failures ✅ Dissect your decisions ✅ Incorporate your successes ✅ Create a beginning, middle, and end ✅ Show the path from initial idea to final Each slide and each statement should reveal a bit more about your thinking process. Details matter. Subtleties matter. They all add up to a powerful narrative. When your presentation is infused with purpose and passion, your work shines. It demonstrates your technical skills and your capacity for critical thinking, problem-solving, and empathetic understanding. And that's what sets you apart. Not just the sheer quality of your work but also the depth of thought put into it. Make them remember what you did and why you did it. Because, in the end, it's the why that truly matters. ------------------------------------- 🔔 Follow: Mollie Cox ♻ Repost to help others 💾 Save it for future use
-
Confession: While I've reviewed thousands of portfolios, I've never read a case study all the way through. I ALWAYS scan them. I just don't have the time to look through every detail. And I know that most other folks who are reviewing portfolios are doing the exact same thing for the same reasons. This means that your portfolio should: 1. Make it easy to scan 2. Use big, high quality visuals 3. Tell quick, concise stories 4. Most importantly, make that story easy to consume in two minutes or less If I were to build my portfolio today, here's how I would do it using these principles: 1️⃣ I'd have a top overview section that has a short blurb of what to expect/what I accomplished AND the final mockups/prototype of what I created. 2️⃣ I'd write out each case study using a word document first to make sure that my headlines told the entire story quickly and concisely. I'd use a classic story arc 1. Context/background 2. Conflict 3. Rising action 4. Climax 5. Falling action 6. Resolution The simpler version of this is the 3 Cs of storytelling: 1. Context 2. Conflict 3. Change (AKA what improved as a result of your work) 3️⃣ I'd optimize my headlines below the overview to tell the story of what I learned. Once everything was written out in a Google doc, I'd edit everything down to the essentials. I'd make sure to pull out the important learnings/quotes and make them big so reviewers could easily scan them. 4️⃣ I'd break up sections with large images to make it feel more interesting and less fatiguing. 5️⃣ I'd ask friends and family to read it and provide feedback about clarity and how much time it took them. If they can easily understand it, see my impact, and quickly go through it, then I'm on the right track. 6️⃣ I'd use LinkedIn and adplist.org to find more folks to provide feedback. Again, I'd focus their feedback on clarity and the amount of time it took for them to go through it.
-
In the past few months, I’ve reviewed over 400 design portfolios while seeking to fill a mid-level design position (2-3 years of experience). More than 90% of these portfolios didn’t pass the screening process. One striking observation was that around 75% of all portfolios looked the same. If your portfolio resembles a basic template, you’re doing something wrong. Don’t get me wrong, perfect portfolios don’t exist, and I’m definitely not saying you should go overboard. However, hiring managers are reviewing many portfolios at once, and standing out with a well-designed portfolio that balances UX with a beautiful and aesthetically pleasing UI will definitely grab the hiring manager’s attention and win you more time. Top Mistakes: 1. Using the Same Design Process for All Projects: • If you have a one-size-fits-all design process, it indicates inexperience. Every project has different needs, requirements, constraints, and challenges. I want to see the challenges you’ve faced in the design process, what methods you chose to overcome a particular challenge, and why you chose that method. 2. Not Connecting Business Goals/Needs to Your Solutions: • Once I open one of your case studies, I want to see what problem you are solving and how it will help the business. Clearly linking your design solutions to business objectives demonstrates a deeper understanding of the impact of your work. 3. Not Enough Exploration: • Most portfolios I reviewed didn’t show enough solution exploration. They usually display only the chosen solution. I want to know which other solutions you considered, why you chose a particular solution over the others, and how you determined this was the best solution. 4. Too Much Clutter in Case Studies: • One of the greatest challenges in designing your portfolio is deciding how much detail to include in your case studies. Too much detail can overwhelm users (hiring managers), causing them to not finish reading your case study, which lowers your chances of getting an interview. Too little detail results in incomplete stories, which also lowers your chances. Focusing on the bigger picture and ensuring your case study is easily scannable is crucial. Make sure a user can scan and understand your case study within 30 seconds. Final Advice: There’s so much advice out there about this subject. If I have to leave you with one thing from this post, it would be to treat your portfolio as a real product design project and understand your audience really well. A well-crafted portfolio that effectively communicates your design process, challenges, and solutions can significantly enhance your chances of standing out to hiring managers.”
-
93% of Junior UX portfolios I see don't do this. 😔 👇 ↳ Reflect Real-World Problem Solving: → Many portfolios show beautiful interfaces but fail to show the designer's process of solving problems that matter. 💡 Pro tip: If you're new to UX, don't use bootcamp or school projects only. Get freelance or hackathon work as case studies. ↳ Have Personal Branding: → Many UXers don't give enough background on themselves. Companies hire you, not your 𝐩𝐨𝐫𝐭𝐟𝐨𝐥𝐢𝐨. ↳ Showcase Collaboration and Feedback: → It's rare to see a designer's ability to: ✅ Work on a team ✅ Articulate their working process ✅ Show their design changes based on feedback ↳ Show the Research Process: → The best case studies tend to: ✅ Showcase qualitative and quantitative data to back their designs ✅ Incorporate their insights into their solutions ↳ Show Empathy and Understanding: → I've noticed many junior designers have zero context to their users and the business in their case studies. 𝘛𝘩𝘦𝘺 𝘰𝘧𝘵𝘦𝘯: → Don't demonstrate their problem-solving process → Don't tell me why they did what they did and why it matters → Don't explain why their solutions help users and the business 🥇 𝗬𝗼𝘂𝗿 𝗮𝗰𝘁𝗶𝗼𝗻 𝗽𝗹𝗮𝗻: ☑ Craft a compelling story for your case studies that don't bore your reader to death ☠️. ☑ Show the results: what went wrong, what went right and what did you learn? ☑ Show how you've worked with others and leveraged feedback in your designs. ☑ Show your research process, how you gathered and interpreted data, and why it informed your design decisions. ☑ Articulate what problems you tackled and why. Show your thought process and how your design solves these issues effectively. ☑ Please for heaven's sake, get a real portfolio website. In this competitive market Dribbble sites, Behance sites, PDFs, and Figma files are not enough. ✨ Portfolios are hard to maintain and even harder to grow, but if you care about your UX career they are worth it. --- PS: What's stopping you from finishing your portfolio? Follow me, John Balboa. I swear I'm friendly and I won't detach your components.
-
Your portfolio is not about your work. Your portfolio is an opportunity to showcase your ability to do the work, but it's not about your work. Your portfolio is a story, and you should be the hero of your story. The work is just a supporting character. Too often I've seen portfolios that just list out the activities that were done. Telling me that you did surveys, interviews, created personas, wireframed a design solution and then prototyped it for testing doesn't tell me anything about you or your process. I want to know what decisions or tradeoffs you made along the way. What challenges did you face, and how did you overcome them? What was the impact to the business, to the user, to your team? What reflections did you take away after the work was complete, and what would you do differently next time? Don't get me wrong, I'm still expecting to see great work outcomes in your portfolio, but your portfolio is not about your work. I'm not hiring the work, I'm hiring the person behind it.
-
I've reviewed thousands of UX portfolios since 2017, and here's one of the biggest mistakes I see: Your portfolio feels like it's selling the product you worked on. But in reality, your portfolio should be selling the product of YOU. Too many portfolios focus on the end features and shiny design, but they miss the mark by not highlighting the process and decisions that got them there. Here are a few things recruiters and hiring managers really want to see in your UX portfolio ... and hear in interviews 😉 - How you arrived at a decision or solution - How you iterated based on user feedback - What trade-offs you had to make and why - How you navigated challenges or constraints - How you collaborated with cross-functional teams - What you learned and how it informs your future work - Why you chose a specific type of research, method, etc - And honestly, so much more ... but I'll leave it here for now Your portfolio isn’t just a showcase of what you made; it’s a showcase of how you think. Helping UX and Product people create stronger portfolios that equip them to talk about their work in interviews effectively is just one of the "5 Sprints" we do inside Career Strategy Lab's 3-month UX and Product Job Search Accelerator. You can learn more here: https://lnkd.in/gjeyFT8P Feel free to DM me here on LinkedIn if you have questions or use the chat widget on our website. Hope this re-frame about UX portfolios helps you see how you might improve your own portfolio so it meets the needs of your users (aka recruiters and hiring managers) 💜 #ux #uxdesign #productdesign