3:14 - some sort of rendering mess up. The actual storytelling arc framework should look like this: blog.vaexperience.com/create-a-ux-portfolio-how-detailed-should-your-ux-case-study-be/
"It is that simple - you just need to start doing it". That's the most important sentence for me. I spent so much time thinking about HOW I could write my case study, instead of just start to write it.
Ha！You beat me to it again, VAX. The classic 3 act story arc. I was going to mention that in one of your previous vid "best portfolio tool PDF". One of the non-design related creative books I've read was Robert McKee's "Story". It's a book really for filmmakers/screenwriters. I spent about 10 years working on indie films during my 30's. So that book really taught me the way to tell a good story. My approach is very much similar to VAX. Start with a story outline, what’s the main theme of this case study. In McKee’s book, it’s called “Controlling Idea” of a film. Then, I draw out a storyboard based on the 3 act arc. They’re just boxes with some doodling of what goes in there, classic pencil and paper style. They could be just boxes with words if you can’t doodle. The storyboards break down your story into “shots(the screens)”. Once you have a 20-30 boards depend on the length of your story, you can have a bird eye view of this presentation(cast study). You might need to reshuffle the slides to make sure this is the right narrative and it follows the outline you established. At this point, you would cherry pick those shots/screens, some of the screens may need to go because they don’t fit that narrative very well, no matter how fancy or pretty they are. You might have to add a few missing one like VAX pointed out. The flow of the narrative is important here. Once you’re happy with this storyboard, you can now start to make a content inventory(in film it’s called shot list): do I have all the assets needed to tell this story? Make an existing list and make a missing list. Are there some existing assets still need polishing? How long it will take me to produce new assets given the time I have? Assess the maturity of those slides. From this point on, it’s all about production of those shots/screens and putting it all together. You’re half way there. The other thing I want to point out is that to keep the length of the case study presentation in check. You usually have about 30-45 min to do your presentation, then open for Q&As from the panel. So if one slide is 1 min, but usually more than that because people might interrupt you for questions. So I usually keep my case study under 30 slides. You might ask: what about all those details I want to pack into? You would prepare those in separate smaller and more focused presentations. For instance, I only show 2-3 slides in my case study to talk about the usability and insights. Now if the interview panel want to learn more on how I ran the usability. I’ll would open up that supporting deck to show 10 more slides talks just about all the details in the usability, screener questions, mod guides, quotes/video recordings and whatnot. I usually keep those supporting decks open at the same time just in case they want to “probe” me with in depth questions so I know I got that covered. If you realize you have a lot of material to cover during the storyboarding stage, you would create the “sub plot” storyboard of the main story. Think about where the interview panel will likely to grill you with those tough questions and you need more material to support your case study. Those sub plot is the your supporting material. Do the same thing with the sub plots: sub plot outline, storyboard, content inventory list… Last but not least, just don't wait the day before your onsite/onzoom interview to do all this work. This cast study archiving work should be an ongoing effort for every designer. You're constantly putting together different case studies/stories. Once you have a few different ones, you should feel pretty confident about going into a panel interview. You might still need to make a few tweaks here and there, but it's not like trying to build Rome in a day.
Great points as usual, Shaun. If you haven't already, you should start sharing them somewhere be it blogs, videos etc. - will help your thought leadership and act as an extension to your portfolio. But most importantly, will give back to the design community
Of course! Thank you for your other videos as well! They are all helpful!😀 I have a question. I got some feedback for my ux case study. Some people told me that the solution part should be as concise as possible like the other parts, while other people told me that it should be detailed. What do you think? Do hiring managers want to see how I solve a problem or just the final designs with features I ideated?
If it's proper UX then how you arrive at the solution matters more than the actual solution itself; you probably have noticed in my reviews that I don't dwell on the end result or UI as much as the process, decisions made and the whys - these are the key factors I'd look for in any candidate. Unless of course it's a UI focused role, like UI designer, product designer with no real research etc. But for both mature enough design teams will want process and dealing with real challenges.
@@vaexperience Thank you! I do agree with you! But I’m confused because I’ve got some negative feedback on my UX case study and they said “I only care a problem, solution and result! Are you looking for a UX researcher position?” They didn’t really seem to care about my process. Do you have any idea about why they said something like that? I don’t know how to improve mine because I’m really confused.
In theory it could, but in practice I'd recommend to have at least a couple to display more versatility in challenges, processes and outcomes. Basically the more GOOD QUALITY evidence you've got the better the chances to get in
Thank you always for helpful videos! I have a question! I'm applying to a university and they don't require an interview. In this case, should I explain all the thoughts behind the process? I feel pressure to explain as much as possible because they only get my portfolio, and can't ask me in person.
Hi! Just ran into your channel, watched couple of videos and subscribed. Definetly a good watch! I am looking for some sort of portofolio template that includes proces steps and object spacing (Letter font/size) etc, where I can focus much more on a storytelling rather then visualization, otherwise my attention will flow away in UI direction. Any recommendation?
How come no one in their case studies(or at least the case studies that I've seen) talks about monetization and how is the product going to be generating revenue ? I'm creating my first case study right now and I don't see anyone talking about monetization. I'm afraid myself if I don't talk about monetization in my UI/UX case study that I will be asked about it when I actually do the interview and how do I GO ABOUT ANSWERING THAT QUESTION ? Can anyone shed some light on this please and help me understand this part please.
Thanks for the great info! If you don't mind, I sent you an e-mail requesting for a review of the UX analysis tool(Beusable). Thanks in advance for considering my request :)
3:14 - some sort of rendering mess up. The actual storytelling arc framework should look like this: blog.vaexperience.com/create-a-ux-portfolio-how-detailed-should-your-ux-case-study-be/
You blog link not working
Hello
@@emaduddin5374 Hello
"It is that simple - you just need to start doing it". That's the most important sentence for me. I spent so much time thinking about HOW I could write my case study, instead of just start to write it.
Awesome! glad you took it away. Like with most things at one point we just need to take the first step
Exactly😁Just the same with me
Same thing with me :)
Everyone single one of your videos has been nothing short of valuable and practical advice. Thank you!
Ha！You beat me to it again, VAX. The classic 3 act story arc. I was going to mention that in one of your previous vid "best portfolio tool PDF". One of the non-design related creative books I've read was Robert McKee's "Story". It's a book really for filmmakers/screenwriters. I spent about 10 years working on indie films during my 30's. So that book really taught me the way to tell a good story. My approach is very much similar to VAX. Start with a story outline, what’s the main theme of this case study. In McKee’s book, it’s called “Controlling Idea” of a film. Then, I draw out a storyboard based on the 3 act arc. They’re just boxes with some doodling of what goes in there, classic pencil and paper style. They could be just boxes with words if you can’t doodle. The storyboards break down your story into “shots(the screens)”. Once you have a 20-30 boards depend on the length of your story, you can have a bird eye view of this presentation(cast study). You might need to reshuffle the slides to make sure this is the right narrative and it follows the outline you established. At this point, you would cherry pick those shots/screens, some of the screens may need to go because they don’t fit that narrative very well, no matter how fancy or pretty they are. You might have to add a few missing one like VAX pointed out. The flow of the narrative is important here. Once you’re happy with this storyboard, you can now start to make a content inventory(in film it’s called shot list): do I have all the assets needed to tell this story? Make an existing list and make a missing list. Are there some existing assets still need polishing? How long it will take me to produce new assets given the time I have? Assess the maturity of those slides. From this point on, it’s all about production of those shots/screens and putting it all together. You’re half way there.
The other thing I want to point out is that to keep the length of the case study presentation in check. You usually have about 30-45 min to do your presentation, then open for Q&As from the panel. So if one slide is 1 min, but usually more than that because people might interrupt you for questions. So I usually keep my case study under 30 slides. You might ask: what about all those details I want to pack into? You would prepare those in separate smaller and more focused presentations. For instance, I only show 2-3 slides in my case study to talk about the usability and insights. Now if the interview panel want to learn more on how I ran the usability. I’ll would open up that supporting deck to show 10 more slides talks just about all the details in the usability, screener questions, mod guides, quotes/video recordings and whatnot. I usually keep those supporting decks open at the same time just in case they want to “probe” me with in depth questions so I know I got that covered. If you realize you have a lot of material to cover during the storyboarding stage, you would create the “sub plot” storyboard of the main story. Think about where the interview panel will likely to grill you with those tough questions and you need more material to support your case study. Those sub plot is the your supporting material. Do the same thing with the sub plots: sub plot outline, storyboard, content inventory list…
Last but not least, just don't wait the day before your onsite/onzoom interview to do all this work. This cast study archiving work should be an ongoing effort for every designer. You're constantly putting together different case studies/stories. Once you have a few different ones, you should feel pretty confident about going into a panel interview. You might still need to make a few tweaks here and there, but it's not like trying to build Rome in a day.
Great points as usual, Shaun. If you haven't already, you should start sharing them somewhere be it blogs, videos etc. - will help your thought leadership and act as an extension to your portfolio. But most importantly, will give back to the design community
This was as helpful as the video, thank you for sharing your ideas!
@@vaexperience Hello
Thanks mate!! this is VERY useful!
This is what I really needed! Thank you!
Glad it was helpful!
Of course! Thank you for your other videos as well! They are all helpful!😀 I have a question. I got some feedback for my ux case study. Some people told me that the solution part should be as concise as possible like the other parts, while other people told me that it should be detailed. What do you think?
Do hiring managers want to see how I solve a problem or just the final designs with features I ideated?
If it's proper UX then how you arrive at the solution matters more than the actual solution itself; you probably have noticed in my reviews that I don't dwell on the end result or UI as much as the process, decisions made and the whys - these are the key factors I'd look for in any candidate. Unless of course it's a UI focused role, like UI designer, product designer with no real research etc. But for both mature enough design teams will want process and dealing with real challenges.
@@vaexperience Thank you! I do agree with you! But I’m confused because I’ve got some negative feedback on my UX case study and they said “I only care a problem, solution and result! Are you looking for a UX researcher position?” They didn’t really seem to care about my process. Do you have any idea about why they said something like that? I don’t know how to improve mine because I’m really confused.
Awesome video! I also love the quality or filming! What camera+lens are you using?
Can it be enough to have only one but very well done case study to get an internship or junior position? Love your channel!
In theory it could, but in practice I'd recommend to have at least a couple to display more versatility in challenges, processes and outcomes. Basically the more GOOD QUALITY evidence you've got the better the chances to get in
Thank you always for helpful videos! I have a question! I'm applying to a university and they don't require an interview. In this case, should I explain all the thoughts behind the process? I feel pressure to explain as much as possible because they only get my portfolio, and can't ask me in person.
Hi! Just ran into your channel, watched couple of videos and subscribed. Definetly a good watch! I am looking for some sort of portofolio template that includes proces steps and object spacing (Letter font/size) etc, where I can focus much more on a storytelling rather then visualization, otherwise my attention will flow away in UI direction. Any recommendation?
I want your book! When and How can I buy it?
Still in progress, stay tuned!
How come no one in their case studies(or at least the case studies that I've seen) talks about monetization and how is the product going to be generating revenue ?
I'm creating my first case study right now and I don't see anyone talking about monetization.
I'm afraid myself if I don't talk about monetization in my UI/UX case study that I will be asked about it when I actually do the interview and how do I GO ABOUT ANSWERING THAT QUESTION ?
Can anyone shed some light on this please and help me understand this part please.
Thanks for the great info! If you don't mind, I sent you an e-mail requesting for a review of the UX analysis tool(Beusable). Thanks in advance for considering my request :)
is your book out yet?
Soon