How to Write a Client Case Study

Want to build a UX portfolio that actually gets you interviews? It starts with a strong case study. I created this simple outline for one of my mentorship clients, but it was too good not to share. If you’re a UX or product designer on the job hunt, this can help you tell your story clearly, show your impact, and stand out from the crowd. Here’s the case study formula I recommend (plus a few tips to make yours even stronger): 🔹 Background/Context: What was the project about? What was your role? Timeline? 👉 Tip: Keep this to 3–4 sentences. Add a visual of the final product. 🔹 The Problem: What problem were you solving, and why did it matter? 👉 Tip: 1–2 clear sentences. Bonus points for "before" screenshots or user quotes. 🔹 Discovery: How did you get up to speed? 👉 Tip: Share your research highlights and key findings. Show evidence of collaboration with your team and stakeholders. 🔹 Design & Iteration: How did you approach the design? 👉 Tip: Include early sketches, whiteboard sessions, and messy Figma explorations — it shows your thought process. 🔹 Testing (+ more iteration): Who did you share your designs with, and what did you learn? 👉 Tip: Summarize the feedback you got and how you incorporated it. 🔹 Impact/Outcomes: What happened because of your work? 👉 Tip: Even if the product didn’t ship, focus on what you learned, how you moved it forward, and what impact you had. A few key reminders: MAKE IT SCANNABLE. Use visuals, headings, and type hierarchy to guide people through. Tell a story. Move through your project step by step so it’s easy to follow. Be selective. You don’t need to show everything you did — just enough to show the problem, your thinking, and the outcome. Hope this helps someone out there polishing their portfolio! If you want the full template (including extra tips), feel free to DM me — happy to share. 🚀 [EDIT:] I'm so glad y'all are loving this! if we're not connected, please include a note in your connection request so I can send the full template your way. Cheers! #uxdesign #productdesign #portfolio #uxcareer

Hate how boring and time-consuming documentation feels? Yeah, same. But here’s the thing: the more you avoid it, the more you hurt your future self and miss opportunities to showcase your skills properly. So if you want to make documentation less painful (and actually useful), here are 6 tips I use with my clients to make it faster, clearer, and more impactful: 1. Start with an overview What’s the purpose of your project? What problem did it solve? Just 3–4 lines to set the stage. Make it easy for anyone to understand why it matters. 2. Walk through your process Break down the steps: How did you collect the data? How did you clean, analyze, or model it? What tools or methods did you use? This shows how you think and how you solve real-world problems. 3. Add visuals A clean chart > a wall of text. Use graphs, screenshots, and diagrams to bring your work to life. (And bonus: you’ll understand it faster when you come back later.) 4. Show your problem-solving What roadblocks did you hit? How did you fix them? Don’t hide your struggles, highlight them. This is where your value really shines. 5. Summarize your results What did you find? Why does it matter? What’s next? Answer these three questions clearly and your audience will instantly get the impact of your work. 6.  Use a structure that makes sense Try this flow: Introduction → Objectives → Methods → Results → Conclusion → Future Work Simple. Clean. Effective. P.S: After every milestone, take 5 minutes to update your notes, screenshots, or results. Turn it into a habit. ➕ Follow Jaret André for more data job search, and portfolio tips 🔔 Hit the bell icon to get strategies that actually move the needle.

Career advice I’d give my younger self: Keep a record of your wins Document your accomplishments as you go - not just what you did, but the real impact. (Keep this in a personal repository, not at work.) Most of us move from project to project, thinking we’ll remember the details when we need them. Then, when it’s time for a job search or a performance review, we struggle to articulate our impact. Instead, whenever you start a new project, ask yourself: “How will my future self talk about this?” Think in terms of a story - a problem worth solving, a difficult and challenging solution, and a meaningful transformation. You don’t have to wait until the project is finished to start writing it. Step 1: The problem What problem are you solving? A (business) problem worth solving has the problem itself, which lead to symptoms that, if they aren't addressed, can lead to disaster. For example, you might be replacing a legacy workflow. The old workflow is slow and includes manual steps. This results in errors and customer dissatisfaction, which leads to financial risk (due to errors) and churn, resulting in stagnant revenue and declining market share. You'll get more insight over time, but just start at the start. Write down what you know. Step 2: Document the outcomes you (or your leadership) are expecting or hoping for You may not know the final impact yet, but you have a hypothesis. What will change if your project succeeds? More revenue? Higher efficiency? Customer satisfaction improvements? Write that down. The transformation is often the opposite of the problem: if revenue is stagnant, the goal is growth. If churn is rising, the goal is retention. Define the ideal outcome early. Step 3: Capture the key components of the solution As technologists, we naturally document what we built. That’s fine, but remember—hiring managers and execs care less about features and more about impact. And how you collaborated and persuaded stakeholders to create and keep alignment. Step 4: Update your story as you go As your project progresses, go back and update: ✔ What you learned about the real problem ✔ Changes in your approach ✔ The actual results once customers started using your solution Often, the results blossom in unexpected ways - leading to social proof like customer stories, awards, or internal recognition. Capture those. These stories become the basis of a resume that gets interviews and they're great for performance reviews.

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.

***UX / UXR Job Seekers*** Having trouble with case studies and portfolios? I know it can be tough to create an artifact that respects confidentiality. I dug out an extended case study I did for a conference that I later wrote up as an article. You can see that client confidentiality is protected (even though for the conference itself I had permission to share it) and there are no user names or photos. And yet, I get into quite a bit of detail. More then you'll need for a portfolio. The basic format I used (then tweaked for presentation purposes) is as follows: 1. The Problem. What the client was asking for and what they believed was wrong with the product. 2. The Work. The methods used and how we structured the project. I interwove the findings into this section as well. 3. Recommendations and Implications. What this meant to the team and what it led to. Notice that, as a consultant, I was unable to see any tangible results but I was able to follow up and get an idea of how the work was moving forward and how their viewpoint had changed. A link to the full article is in the comments.

Junior designers can transform their UX portfolios. Using the 1/3/1 writing method can make their case studies stand out. One powerful opening sentence, three depth-providing sentences, and a memorable closing sentence. This method helps designers create engaging and memorable content. It goes beyond traditional portfolio presentation. It focuses on creating an emotional connection. It shows problem-solving skills and personal growth. This narrative rhythm captures attention. It provides meaningful insights. It leaves a lasting impression on potential employers or clients. The 1/3/1 method breaks free from generic, forgettable case studies. It helps designers showcase their unique stories. It makes their work more relatable and impactful. Designers can create a stronger emotional connection with their audience. They can demonstrate their problem-solving abilities effectively. They can highlight their personal growth and learning journey. This method is a game-changer for UX portfolios. It transforms how designers present their work. It makes their portfolios more engaging and memorable. It helps them stand out in a competitive field. The 1/3/1 writing method is a powerful tool for junior designers. It can elevate their portfolios and career prospects. Embrace this method and watch your UX portfolio shine.