{"id":7556,"date":"2026-11-12T12:23:07","date_gmt":"2026-11-12T12:23:07","guid":{"rendered":"https:\/\/www.originux.com\/resources\/?p=7556"},"modified":"2026-11-12T12:29:54","modified_gmt":"2026-11-12T12:29:54","slug":"how-to-write-a-ux-case-study-that-recruiters-actually-read","status":"publish","type":"post","link":"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/","title":{"rendered":"How to Write a UX Case Study That Recruiters Actually Read"},"content":{"rendered":"<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_81 counter-hierarchy ez-toc-counter ez-toc-grey ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/#What_Is_a_UX_Case_Study\" >What Is a UX Case Study?<\/a><ul class='ez-toc-list-level-4' ><li class='ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/#What_a_good_case_study_shows\" >What a good case study shows<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/#Who_Reads_Case_Studies_and_How\" >Who Reads Case Studies and How<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/#Step_1_Pick_the_Right_Project\" >Step 1: Pick the Right Project<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/#Step_2_Choose_a_Structure\" >Step 2: Choose a Structure<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/#Step_3_Write_a_Strong_Summary\" >Step 3: Write a Strong Summary<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/#Step_4_Explain_the_Problem_and_Context\" >Step 4: Explain the Problem and Context<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/#Step_5_Show_Your_Research\" >Step 5: Show Your Research<\/a><ul class='ez-toc-list-level-4' ><li class='ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/#What_to_include\" >What to include<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/#Tips\" >Tips<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-11\" href=\"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/#Step_6_Define_the_Problem_and_Priorities\" >Step 6: Define the Problem and Priorities<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-12\" href=\"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/#Step_7_Show_Ideation_and_Design_Decisions\" >Step 7: Show Ideation and Design Decisions<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-13\" href=\"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/#Step_8_Show_Testing_and_Iteration\" >Step 8: Show Testing and Iteration<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-14\" href=\"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/#Step_9_Present_Outcomes_and_Reflection\" >Step 9: Present Outcomes and Reflection<\/a><ul class='ez-toc-list-level-4' ><li class='ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-15\" href=\"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/#Outcomes\" >Outcomes<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-16\" href=\"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/#Reflection\" >Reflection<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-17\" href=\"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/#Writing_Style_Tips\" >Writing Style Tips<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-18\" href=\"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/#Visual_Tips\" >Visual Tips<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-19\" href=\"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/#Case_Study_Length_and_Formats\" >Case Study Length and Formats<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-20\" href=\"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/#Common_UX_Case_Study_Mistakes\" >Common UX Case Study Mistakes<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-21\" href=\"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/#UX_Case_Study_Checklist\" >UX Case Study Checklist<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-22\" href=\"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/#Getting_Started\" >Getting Started<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-23\" href=\"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/#Final_Thoughts\" >Final Thoughts<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-24\" href=\"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/#FAQs\" >FAQs<\/a><ul class='ez-toc-list-level-4' ><li class='ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-25\" href=\"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/#How_long_should_a_UX_case_study_be\" >How long should a UX case study be?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-26\" href=\"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/#What_should_I_include_in_a_UX_case_study\" >What should I include in a UX case study?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-27\" href=\"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/#How_do_I_write_a_UX_case_study_with_no_real_results\" >How do I write a UX case study with no real results?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-28\" href=\"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/#Can_I_include_team_projects_in_my_case_study\" >Can I include team projects in my case study?<\/a><\/li><\/ul><\/li><\/ul><\/nav><\/div>\n\n<p class=\"wp-block-paragraph\">A designer spends three months on a project, runs interviews, tests prototypes and ships a redesign that improves task completion. Then she posts it in her portfolio as six screenshots with a one-line caption. Recruiters scroll past in seconds, because nothing shows what the problem was, what she did or why it mattered.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A UX case study turns your work into a story that proves how you think. It is the most important piece of any UX portfolio, and it is also the piece many designers find hardest to write. This guide explains what a case study is, how to structure it, how to write each section, what to avoid and how to review it before you publish.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"What_Is_a_UX_Case_Study\"><\/span><strong>What Is a UX Case Study?<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A UX case study is a written and visual account of a design project. It explains the problem, your process, the decisions you made and the results. Unlike a gallery of final screens, it shows reasoning, collaboration and impact.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"What_a_good_case_study_shows\"><\/span><strong>What a good case study shows<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem-solving ability:<\/strong> you can frame and tackle real challenges.<\/li>\n\n\n\n<li><strong>User understanding:<\/strong> your decisions are grounded in research.<\/li>\n\n\n\n<li><strong>Process:<\/strong> you work in a structured, repeatable way.<\/li>\n\n\n\n<li><strong>Communication:<\/strong> you can explain complex work clearly.<\/li>\n\n\n\n<li><strong>Impact:<\/strong> you care about outcomes, not only visuals.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Who_Reads_Case_Studies_and_How\"><\/span><strong>Who Reads Case Studies and How<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Understanding your readers shapes how you write.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Reader<\/th><th>What they want<\/th><th>How they read<\/th><\/tr><\/thead><tbody><tr><td>Recruiters<\/td><td>Quick proof of fit and level<\/td><td>Skim headings, images and summaries<\/td><\/tr><tr><td>Design leads<\/td><td>Depth of thinking and craft<\/td><td>Read selected sections closely<\/td><\/tr><tr><td>Hiring managers<\/td><td>Evidence of impact and collaboration<\/td><td>Look for results and role clarity<\/td><\/tr><tr><td>Peers and mentors<\/td><td>Process details and learnings<\/td><td>Read the full story<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Write so a reader can grasp the project in 30 seconds, then dive deeper if they choose.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Step_1_Pick_the_Right_Project\"><\/span><strong>Step 1: Pick the Right Project<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Not every project deserves a case study. Choose work that shows your abilities.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>A real, meaningful problem:<\/strong> users or a business genuinely needed a solution.<\/li>\n\n\n\n<li><strong>Visible process:<\/strong> you have artifacts such as research notes, sketches and test results.<\/li>\n\n\n\n<li><strong>Clear personal contribution:<\/strong> you can explain your role precisely.<\/li>\n\n\n\n<li><strong>Relevance to your goals:<\/strong> it fits the roles you want.<\/li>\n\n\n\n<li><strong>Some outcome or learning:<\/strong> results, metrics or honest reflections.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">If you lack client work, use self-initiated projects built on real problems, interviews and testing rather than a visual redesign of a popular app.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Step_2_Choose_a_Structure\"><\/span><strong>Step 2: Choose a Structure<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A clear structure makes your story easy to follow. Here is a flexible template.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Section<\/th><th>Purpose<\/th><th>Typical length<\/th><\/tr><\/thead><tbody><tr><td>Summary<\/td><td>Give the headline: problem, your role and outcome<\/td><td>3 to 5 lines<\/td><\/tr><tr><td>Context and problem<\/td><td>Explain the situation and who it affects<\/td><td>A short paragraph<\/td><\/tr><tr><td>Goals and constraints<\/td><td>Define success and limits<\/td><td>A few bullets<\/td><\/tr><tr><td>Research<\/td><td>Show how you learned about users<\/td><td>A few paragraphs plus visuals<\/td><\/tr><tr><td>Insights and definition<\/td><td>Turn findings into a clear problem statement<\/td><td>A short section<\/td><\/tr><tr><td>Ideation<\/td><td>Show options you explored<\/td><td>Sketches and brief notes<\/td><\/tr><tr><td>Design<\/td><td>Present key solutions and decisions<\/td><td>Annotated screens<\/td><\/tr><tr><td>Testing and iteration<\/td><td>Show how feedback changed the design<\/td><td>Findings and revisions<\/td><\/tr><tr><td>Outcome<\/td><td>Share results or learnings<\/td><td>Metrics or reflections<\/td><\/tr><tr><td>Reflection<\/td><td>Explain what you would do differently<\/td><td>A short paragraph<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Adapt the structure to the project. A research-heavy project may expand the research section, while a design system project may focus on components and adoption.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Step_3_Write_a_Strong_Summary\"><\/span><strong>Step 3: Write a Strong Summary<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Most readers decide in seconds whether to continue. Start with a summary box that answers:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What was the project?<\/strong><\/li>\n\n\n\n<li><strong>Who were the users?<\/strong><\/li>\n\n\n\n<li><strong>What was your role and the team?<\/strong><\/li>\n\n\n\n<li><strong>How long did it take, and which tools did you use?<\/strong><\/li>\n\n\n\n<li><strong>What changed as a result?<\/strong><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">A sample summary: \u201cRedesigned the onboarding flow for a savings app used by first-time investors. I led research and design with one PM and two engineers over eight weeks. Usability testing showed task completion rising from 58 percent to 86 percent.\u201d<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Only claim numbers you can honestly support, and explain how you measured them.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Step_4_Explain_the_Problem_and_Context\"><\/span><strong>Step 4: Explain the Problem and Context<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Help readers understand why the project mattered.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Describe the users:<\/strong> who they are and what they need.<\/li>\n\n\n\n<li><strong>Describe the business context:<\/strong> goals, market and constraints.<\/li>\n\n\n\n<li><strong>State the problem clearly:<\/strong> use simple language and avoid jargon.<\/li>\n\n\n\n<li><strong>Include evidence:<\/strong> analytics, support tickets or user quotes that show the problem.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Good problem framing shows that you do not jump straight to solutions. Teams often use a <strong><a href=\"https:\/\/www.originux.com\/design-thinking-workshops\">design thinking workshop<\/a><\/strong> to align on problems before designing, and describing a similar alignment step in your case study can show strong facilitation skills.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Step_5_Show_Your_Research\"><\/span><strong>Step 5: Show Your Research<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Research is where many case studies become convincing.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"What_to_include\"><\/span><strong>What to include<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Methods:<\/strong> interviews, surveys, usability tests, competitive analysis or analytics review.<\/li>\n\n\n\n<li><strong>Participants:<\/strong> how many and who, without revealing private details.<\/li>\n\n\n\n<li><strong>Key findings:<\/strong> the most important insights, not every note.<\/li>\n\n\n\n<li><strong>Synthesis:<\/strong> an affinity map, journey map or persona, explained in a sentence or two.<\/li>\n\n\n\n<li><strong>How findings shaped direction:<\/strong> link research to decisions explicitly.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Tips\"><\/span><strong>Tips<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Be selective:<\/strong> show the artifacts that best explain your thinking.<\/li>\n\n\n\n<li><strong>Explain visuals:<\/strong> never post a diagram without a caption that says what to notice.<\/li>\n\n\n\n<li><strong>Be honest about limits:<\/strong> small samples or time constraints are fine if you acknowledge them.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Strong <strong><a href=\"https:\/\/www.originux.com\/services\/ux-research\">UX research<\/a><\/strong> habits make this section far more persuasive, because decisions backed by evidence read as professional and credible.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Step_6_Define_the_Problem_and_Priorities\"><\/span><strong>Step 6: Define the Problem and Priorities<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Show how you moved from insights to a clear direction.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem statement:<\/strong> a concise sentence describing what you will solve.<\/li>\n\n\n\n<li><strong>Design principles or goals:<\/strong> a few guiding ideas for the solution.<\/li>\n\n\n\n<li><strong>Priorities:<\/strong> what you decided to focus on and what you left out.<\/li>\n\n\n\n<li><strong>Trade-offs:<\/strong> constraints such as time, budget and technology.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Explaining what you chose not to do often impresses reviewers, because it shows judgment.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Step_7_Show_Ideation_and_Design_Decisions\"><\/span><strong>Step 7: Show Ideation and Design Decisions<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">This is the heart of the story.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Explore options:<\/strong> show sketches, flows or alternatives you considered.<\/li>\n\n\n\n<li><strong>Explain choices:<\/strong> say why you selected one direction over others.<\/li>\n\n\n\n<li><strong>Annotate screens:<\/strong> point out key decisions and the reasoning behind them.<\/li>\n\n\n\n<li><strong>Show system thinking:<\/strong> mention components, patterns and consistency where relevant.<\/li>\n\n\n\n<li><strong>Address accessibility:<\/strong> note contrast, readability and inclusive choices.<\/li>\n\n\n\n<li><strong>Collaborate visibly:<\/strong> mention input from engineers, product managers and stakeholders.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Avoid dumping dozens of screens. Pick the few that best demonstrate your decisions.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Step_8_Show_Testing_and_Iteration\"><\/span><strong>Step 8: Show Testing and Iteration<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Testing proves that your design works, or reveals what did not.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Describe the method:<\/strong> moderated or unmoderated testing, prototype fidelity and tasks.<\/li>\n\n\n\n<li><strong>Share findings:<\/strong> what worked, what confused people and what surprised you.<\/li>\n\n\n\n<li><strong>Show what changed:<\/strong> before and after versions with explanations.<\/li>\n\n\n\n<li><strong>Admit mistakes:<\/strong> learning from a failed idea shows maturity.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">A structured <strong><a href=\"https:\/\/www.originux.com\/services\/ux-audit\">UX audit<\/a><\/strong> mindset can help here: review your own design like an evaluator, and explain the issues you found and fixed.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Step_9_Present_Outcomes_and_Reflection\"><\/span><strong>Step 9: Present Outcomes and Reflection<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">End with results and learning.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Outcomes\"><\/span><strong>Outcomes<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Metrics:<\/strong> task success rates, conversion, time on task, satisfaction scores or error rates, if you have reliable data.<\/li>\n\n\n\n<li><strong>Qualitative feedback:<\/strong> user quotes or stakeholder comments.<\/li>\n\n\n\n<li><strong>Business impact:<\/strong> efficiency gains, reduced support requests or increased adoption.<\/li>\n\n\n\n<li><strong>If you lack data:<\/strong> explain what you learned and how you would measure success next time.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Reflection\"><\/span><strong>Reflection<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What went well:<\/strong> strengths in process or collaboration.<\/li>\n\n\n\n<li><strong>What was hard:<\/strong> constraints, disagreements or surprises.<\/li>\n\n\n\n<li><strong>What you would change:<\/strong> concrete improvements for next time.<\/li>\n\n\n\n<li><strong>What you learned:<\/strong> skills or insights you carry forward.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Honest reflection builds trust more than perfect-sounding success stories.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Writing_Style_Tips\"><\/span><strong>Writing Style Tips<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Lead with the point:<\/strong> start sections with the main takeaway.<\/li>\n\n\n\n<li><strong>Use short paragraphs and clear headings:<\/strong> make it skimmable.<\/li>\n\n\n\n<li><strong>Prefer plain language:<\/strong> avoid buzzwords and unexplained acronyms.<\/li>\n\n\n\n<li><strong>Use \u201cI\u201d for your work and \u201cwe\u201d for the team:<\/strong> clarify your contribution.<\/li>\n\n\n\n<li><strong>Show, do not only tell:<\/strong> support claims with visuals and evidence.<\/li>\n\n\n\n<li><strong>Keep length reasonable:<\/strong> aim for a story that can be skimmed in a couple of minutes and read deeply in ten.<\/li>\n\n\n\n<li><strong>Edit ruthlessly:<\/strong> remove details that do not support the story.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Visual_Tips\"><\/span><strong>Visual Tips<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Visual<\/th><th>How to use it<\/th><\/tr><\/thead><tbody><tr><td>Annotated screens<\/td><td>Highlight decisions and rationale<\/td><\/tr><tr><td>Before and after comparisons<\/td><td>Make improvement obvious<\/td><\/tr><tr><td>Process diagrams<\/td><td>Explain complex workflows simply<\/td><\/tr><tr><td>Prototype links or short videos<\/td><td>Let readers experience the solution<\/td><\/tr><tr><td>Research artifacts<\/td><td>Show synthesis, curated and captioned<\/td><\/tr><tr><td>Consistent layout<\/td><td>Keep alignment, spacing and typography clean<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Make images accessible with alt text, good contrast and readable sizes, and check how everything looks on mobile.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Case_Study_Length_and_Formats\"><\/span><strong>Case Study Length and Formats<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Format<\/th><th>Best for<\/th><th>Notes<\/th><\/tr><\/thead><tbody><tr><td>Short case study (one page)<\/td><td>Quick portfolio scanning<\/td><td>Focus on summary, key decisions and outcome<\/td><\/tr><tr><td>Detailed case study<\/td><td>Depth for interviews and senior roles<\/td><td>Include research, iteration and reflection<\/td><\/tr><tr><td>Slide deck or PDF<\/td><td>Applications that need attachments<\/td><td>Keep it concise and visual<\/td><\/tr><tr><td>Presentation or video walkthrough<\/td><td>Interviews and talks<\/td><td>Practice telling the story aloud<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Having both a short and a detailed version of your best projects gives recruiters flexibility.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Common_UX_Case_Study_Mistakes\"><\/span><strong>Common UX Case Study Mistakes<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Mistake<\/th><th>Why it hurts<\/th><th>Better approach<\/th><\/tr><\/thead><tbody><tr><td>Showing only final screens<\/td><td>Hides your thinking<\/td><td>Explain process and decisions<\/td><\/tr><tr><td>Describing everything chronologically without focus<\/td><td>Loses the reader<\/td><td>Lead with the problem and key insights<\/td><\/tr><tr><td>Vague role descriptions<\/td><td>Unclear contribution<\/td><td>State exactly what you did<\/td><\/tr><tr><td>Overloading with process artifacts<\/td><td>Overwhelms readers<\/td><td>Curate and caption the best ones<\/td><\/tr><tr><td>Using unexplained jargon<\/td><td>Alienates non-designers<\/td><td>Write in plain language<\/td><\/tr><tr><td>Claiming results without evidence<\/td><td>Damages credibility<\/td><td>Share honest, supported outcomes<\/td><\/tr><tr><td>Hiding failures<\/td><td>Misses a chance to show growth<\/td><td>Include lessons learned<\/td><\/tr><tr><td>Sharing confidential material<\/td><td>Breaks trust or contracts<\/td><td>Anonymize or get permission<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"UX_Case_Study_Checklist\"><\/span><strong>UX Case Study Checklist<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Does the summary explain the problem, your role and the outcome?<\/li>\n\n\n\n<li>Is the user and business context clear?<\/li>\n\n\n\n<li>Does the research show methods, findings and how they shaped decisions?<\/li>\n\n\n\n<li>Are design decisions explained, not just displayed?<\/li>\n\n\n\n<li>Did you show testing and what changed afterward?<\/li>\n\n\n\n<li>Are outcomes honest, specific and supported?<\/li>\n\n\n\n<li>Is your personal contribution unmistakable?<\/li>\n\n\n\n<li>Is the writing skimmable, clear and free of jargon?<\/li>\n\n\n\n<li>Are visuals annotated, accessible and mobile-friendly?<\/li>\n\n\n\n<li>Have you checked confidentiality and permissions?<\/li>\n\n\n\n<li>Has someone else read it and given feedback?<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Getting_Started\"><\/span><strong>Getting Started<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">You do not need to rewrite your whole portfolio at once. Pick your strongest project, write a short summary, add the problem, process and results, then ask someone to read it and tell you what they understood. Revise and repeat. If you want to see how professional teams organize real projects from discovery through delivery, exploring <strong><a href=\"https:\/\/www.originux.com\/services\/ui-ux-design-services\">UI\/UX design services<\/a><\/strong> can offer useful context for how engagements are structured and communicated.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Final_Thoughts\"><\/span><strong>Final Thoughts<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A great UX case study tells a clear, honest story about a real problem and how you solved it. Start with a strong summary, show your research and reasoning, explain trade-offs and decisions, and end with results and reflection. Write for skimmers first and deep readers second, and keep editing until every section earns its place. When someone finishes your case study, they should understand not only what you designed but how you think.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"FAQs\"><\/span><strong>FAQs<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<h4 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"How_long_should_a_UX_case_study_be\"><\/span><strong>How long should a UX case study be?<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">Long enough to show your process and short enough to stay engaging. Many strong case studies can be skimmed in a couple of minutes and read in depth in around ten, with a summary at the top.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"What_should_I_include_in_a_UX_case_study\"><\/span><strong>What should I include in a UX case study?<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">A summary, the problem and context, your role, research, insights, design decisions, testing and iteration, outcomes and a reflection on what you learned.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"How_do_I_write_a_UX_case_study_with_no_real_results\"><\/span><strong>How do I write a UX case study with no real results?<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">Focus on process, insights and what you learned. Share evidence from usability tests, explain how you would measure success and be honest about the project\u2019s context.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Can_I_include_team_projects_in_my_case_study\"><\/span><strong>Can I include team projects in my case study?<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">Yes, but be very clear about your contribution. Explain your role, the decisions you made and how you worked with others.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A designer spends three months on a project, runs interviews, tests prototypes and ships a redesign that improves task completion. Then she posts it in her portfolio as six screenshots with a one-line caption. Recruiters scroll past in seconds, because nothing shows what the problem was, what she did or why it mattered. A UX&hellip; <a class=\"more-link\" href=\"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/\">Continue reading <span class=\"screen-reader-text\">How to Write a UX Case Study That Recruiters Actually Read<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-7556","post","type-post","status-publish","format-standard","hentry","category-blog","entry"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.2 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>How to Write a UX Case Study: Step-by-Step Guide<\/title>\n<meta name=\"description\" content=\"Learn how to write a UX case study that impresses recruiters, with a clear structure, storytelling tips, templates, examples, common mistakes and a practical checklist for designers.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"How to Write a UX Case Study: Step-by-Step Guide\" \/>\n<meta property=\"og:description\" content=\"Learn how to write a UX case study that impresses recruiters, with a clear structure, storytelling tips, templates, examples, common mistakes and a practical checklist for designers.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/\" \/>\n<meta property=\"og:site_name\" content=\"OriginUX Studio\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-12T12:23:07+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-11-12T12:29:54+00:00\" \/>\n<meta name=\"author\" content=\"master.origin\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"master.origin\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"9 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/\"},\"author\":{\"name\":\"master.origin\",\"@id\":\"https:\/\/www.originux.com\/resources\/#\/schema\/person\/735b211d8a21c6181bb758144923ef3c\"},\"headline\":\"How to Write a UX Case Study That Recruiters Actually Read\",\"datePublished\":\"2026-11-12T12:23:07+00:00\",\"dateModified\":\"2026-11-12T12:29:54+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/\"},\"wordCount\":1928,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/www.originux.com\/resources\/#organization\"},\"articleSection\":[\"Blog\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/\",\"url\":\"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/\",\"name\":\"How to Write a UX Case Study: Step-by-Step Guide\",\"isPartOf\":{\"@id\":\"https:\/\/www.originux.com\/resources\/#website\"},\"datePublished\":\"2026-11-12T12:23:07+00:00\",\"dateModified\":\"2026-11-12T12:29:54+00:00\",\"description\":\"Learn how to write a UX case study that impresses recruiters, with a clear structure, storytelling tips, templates, examples, common mistakes and a practical checklist for designers.\",\"breadcrumb\":{\"@id\":\"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.originux.com\/resources\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to Write a UX Case Study That Recruiters Actually Read\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.originux.com\/resources\/#website\",\"url\":\"https:\/\/www.originux.com\/resources\/\",\"name\":\"OriginUX Studio\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/www.originux.com\/resources\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.originux.com\/resources\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.originux.com\/resources\/#organization\",\"name\":\"OriginUX Studio\",\"url\":\"https:\/\/www.originux.com\/resources\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.originux.com\/resources\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/www.originux.com\/resources\/wp-content\/uploads\/2022\/05\/origin-logo.png\",\"contentUrl\":\"https:\/\/www.originux.com\/resources\/wp-content\/uploads\/2022\/05\/origin-logo.png\",\"width\":120,\"height\":120,\"caption\":\"OriginUX Studio\"},\"image\":{\"@id\":\"https:\/\/www.originux.com\/resources\/#\/schema\/logo\/image\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.originux.com\/resources\/#\/schema\/person\/735b211d8a21c6181bb758144923ef3c\",\"name\":\"master.origin\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/356acc98edd1351e180a192318e3335999f553b20c01c8a00391239e394d4727?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/356acc98edd1351e180a192318e3335999f553b20c01c8a00391239e394d4727?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/356acc98edd1351e180a192318e3335999f553b20c01c8a00391239e394d4727?s=96&d=mm&r=g\",\"caption\":\"master.origin\"},\"sameAs\":[\"https:\/\/www.originux.com\"],\"url\":\"https:\/\/www.originux.com\/resources\/author\/master-origin\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"How to Write a UX Case Study: Step-by-Step Guide","description":"Learn how to write a UX case study that impresses recruiters, with a clear structure, storytelling tips, templates, examples, common mistakes and a practical checklist for designers.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/","og_locale":"en_US","og_type":"article","og_title":"How to Write a UX Case Study: Step-by-Step Guide","og_description":"Learn how to write a UX case study that impresses recruiters, with a clear structure, storytelling tips, templates, examples, common mistakes and a practical checklist for designers.","og_url":"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/","og_site_name":"OriginUX Studio","article_published_time":"2026-11-12T12:23:07+00:00","article_modified_time":"2026-11-12T12:29:54+00:00","author":"master.origin","twitter_card":"summary_large_image","twitter_misc":{"Written by":"master.origin","Est. reading time":"9 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/#article","isPartOf":{"@id":"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/"},"author":{"name":"master.origin","@id":"https:\/\/www.originux.com\/resources\/#\/schema\/person\/735b211d8a21c6181bb758144923ef3c"},"headline":"How to Write a UX Case Study That Recruiters Actually Read","datePublished":"2026-11-12T12:23:07+00:00","dateModified":"2026-11-12T12:29:54+00:00","mainEntityOfPage":{"@id":"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/"},"wordCount":1928,"commentCount":0,"publisher":{"@id":"https:\/\/www.originux.com\/resources\/#organization"},"articleSection":["Blog"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/","url":"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/","name":"How to Write a UX Case Study: Step-by-Step Guide","isPartOf":{"@id":"https:\/\/www.originux.com\/resources\/#website"},"datePublished":"2026-11-12T12:23:07+00:00","dateModified":"2026-11-12T12:29:54+00:00","description":"Learn how to write a UX case study that impresses recruiters, with a clear structure, storytelling tips, templates, examples, common mistakes and a practical checklist for designers.","breadcrumb":{"@id":"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.originux.com\/resources\/blog\/how-to-write-a-ux-case-study-that-recruiters-actually-read\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.originux.com\/resources\/"},{"@type":"ListItem","position":2,"name":"How to Write a UX Case Study That Recruiters Actually Read"}]},{"@type":"WebSite","@id":"https:\/\/www.originux.com\/resources\/#website","url":"https:\/\/www.originux.com\/resources\/","name":"OriginUX Studio","description":"","publisher":{"@id":"https:\/\/www.originux.com\/resources\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.originux.com\/resources\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.originux.com\/resources\/#organization","name":"OriginUX Studio","url":"https:\/\/www.originux.com\/resources\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.originux.com\/resources\/#\/schema\/logo\/image\/","url":"https:\/\/www.originux.com\/resources\/wp-content\/uploads\/2022\/05\/origin-logo.png","contentUrl":"https:\/\/www.originux.com\/resources\/wp-content\/uploads\/2022\/05\/origin-logo.png","width":120,"height":120,"caption":"OriginUX Studio"},"image":{"@id":"https:\/\/www.originux.com\/resources\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/www.originux.com\/resources\/#\/schema\/person\/735b211d8a21c6181bb758144923ef3c","name":"master.origin","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/356acc98edd1351e180a192318e3335999f553b20c01c8a00391239e394d4727?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/356acc98edd1351e180a192318e3335999f553b20c01c8a00391239e394d4727?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/356acc98edd1351e180a192318e3335999f553b20c01c8a00391239e394d4727?s=96&d=mm&r=g","caption":"master.origin"},"sameAs":["https:\/\/www.originux.com"],"url":"https:\/\/www.originux.com\/resources\/author\/master-origin\/"}]}},"_links":{"self":[{"href":"https:\/\/www.originux.com\/resources\/wp-json\/wp\/v2\/posts\/7556","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.originux.com\/resources\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.originux.com\/resources\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.originux.com\/resources\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.originux.com\/resources\/wp-json\/wp\/v2\/comments?post=7556"}],"version-history":[{"count":2,"href":"https:\/\/www.originux.com\/resources\/wp-json\/wp\/v2\/posts\/7556\/revisions"}],"predecessor-version":[{"id":7566,"href":"https:\/\/www.originux.com\/resources\/wp-json\/wp\/v2\/posts\/7556\/revisions\/7566"}],"wp:attachment":[{"href":"https:\/\/www.originux.com\/resources\/wp-json\/wp\/v2\/media?parent=7556"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.originux.com\/resources\/wp-json\/wp\/v2\/categories?post=7556"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.originux.com\/resources\/wp-json\/wp\/v2\/tags?post=7556"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}