{"id":15623,"date":"2021-08-02T04:00:00","date_gmt":"2021-08-02T09:00:00","guid":{"rendered":"https:\/\/aquent.com\/?p=15623"},"modified":"2021-08-02T04:00:00","modified_gmt":"2021-08-02T09:00:00","slug":"how-to-make-your-ux-case-study-stand-out","status":"publish","type":"post","link":"https:\/\/aquent.com\/en-au\/blog\/how-to-make-your-ux-case-study-stand-out","title":{"rendered":"How To Make Your UX Case Study Stand Out"},"content":{"rendered":"\n

Recently, <\/span>I presented<\/span><\/a> at a <\/span>Women in UX Meetup<\/span><\/a>, organised by <\/span>UX Australia<\/span><\/a> and UX Career Mentor <\/span>Mags Hanley<\/span><\/a> where I shared advice on how <\/span>to showcase your work and capabilities through the creation of <\/span>a UX case study.<\/span>.<\/span><\/p>\n<\/body><\/html>\n\n\n\n

I’d like to share this advice with you now, so let’s take a deep dive…<\/span><\/p>\n<\/body><\/html>\n\n\n\n

Who are you designing your case studies \/ portfolio for?<\/span><\/h1>\n\n\n\n

To start with, I want you to think about WHO you are designing your portfolio for? Is it for yourself or other designers, or are you taking a user-focused approach and thinking about viewers who are involved in potentially employing you?<\/span><\/p>\n<\/body><\/html>\n\n\n\n

Try and <\/span>think about your profile<\/span><\/a> (resume, portfolio, case studies, LinkedIn) from the viewpoint of these employers — be they hiring managers, <\/span>recruiters<\/span><\/a>, Human Resources (HR) or Talent Acquisition (TA). I’m going to delve into some insights as to what each of these viewers tend to look for further along in this post, but I want to plant this seed early.<\/span><\/p>\n<\/body><\/html>\n\n\n\n

Where to start?<\/span><\/h1>\n\n\n\n

I recommend starting with just one project — approach it as a <\/span>Project Overview<\/b> first, then expand it out to a case study. <\/span><\/p>\n<\/body><\/html>\n\n\n\n

Pick the project you’re most proud of and ideally also aligns best to the type of work you want to get, or the <\/span>role you are applying for<\/span><\/a>. Start with the basic overview, bullet point the key details that give context to the project and your work on it. Think of this as a process overview, rather than the project insights. T<\/span>he aim is for a viewer to understand the type of project and what you did in a 3 second scan. These project overviews <\/span>are to gain interest, get you shortlisted or land an interview.<\/span><\/p>\n<\/body><\/html>\n\n\n\n

TIP > If you've come from a design background, avoid getting distracted with formatting by using a Word doc or email to layout content.<\/span><\/h3>\n\n\n\n

Key <\/span>information needed on these project overviews are:<\/span><\/h4>\n\n\n\n