Use title for 'Why', primary metric to be solved/reached. Very good but minimal & realistic hero image. Use impactful callouts, starting from Overview. Take a big problem statement, and then break it down into small different problems.(Problems need to be crisp & very clear). Explain/justify your judgement of identifying problems in the first place.: How do you identify this problems? Also show, who you are solving for. Who are facing these problems? Metrics(Measurement of progress)-*Correlate problem with the Metric, to maintain the storytelling coherence. Make the metrics simple to understand(set relative context)- Answer 2 questions: Why did you choose this metrics? How are you measuring that? Research-Do research to understand the problem's depth(first principles & reverse contemplation), instead of using it as a way to validate the existence of the problems you identified. Validating the problem statement is a part of a Product Manager's job. User stories-Who they are? What they do? Why they do it? vs User Personas(to be related to the problem statement) User Flows-Consider edge cases Solutions- Problems you are solving Explain the solution(UI Screens as a flow) Metric improvement(Impact) Show worthy Iterations/edge cases Usability testing Insights Explain the adapted solution(UI Screens as a flow) Layout: Title Hero Problem Context Product Overview Problem statement/list of problems Defined Metrics Defining the Core Users Primary Research Understanding current flow/behaviour(surveys, interviews) Competitive analysis(secondary research) List of problems at each step of current user flow(which steps) Metrics
Rather than watching random videos on RU-vid or Netflix, I enjoyed watching this and learned more about making good case studies❤, a great way to spend the weekend! Highly Recommended🔥
Your creation of valuable content, especially in the field of product design, provides an incredibly inspiring and in-depth learning experience, packed with knowledge. Your assistance in molding diverse individuals is greatly valued.
Good one. There were multiiple places felt like you (from and HR Manager POV) jumping into conclusions, i can say/blame it may be due how the case study by the fellow gentleman wriitien or framed it. But there were many sitivation as such :) But a good way to look at what an HR might feel or think. And derail this gentleman's orginal intend of the case study. Very informative
@@anishamalhotra6195 i think it's because of the storytelling, it's like there were no emotions telling the whole story. it was like i'm just reading a abstract document explaining some problem and then fixing it on its own. a straight way process which isn't usual in real life projects.
@@DesignPilot It was a take-home assignment to design an android app to track groceries, vegetables and fridge items used in the kitchen to reduce food wastage and to efficiently manage kitchen stock. Users were not defined in the PS. However, the brief did have the sentence "Many of us started cooking since covid". Now, I don't know what "us" means here. I included two groups initially - 1. Cooking enthusiasts 2. Bachelors living by themselves (not sure) But, I think anyone who cooks on a regular basis is my potential user. What do you think?
Hello Chethan, I have a question regarding case studies in today's context. Assuming that 50-60% of case studies currently feature a solid UI design, and I believe this trend will continue to grow over time. In your opinion, what do you think will set apart or differentiate case studies in the future?
Hi chetham, Thank you for the Amazing contents also wanted to ask If you'd still be creating a case study as one of the chapters on the learnproduct platform. I noticed the chapter had been removed .
You said not to validate the problem statement as it is PMs job. What if i want to make the project more research emphasised? To become a UX researcher. Is UX research job to validate the chosen problem statement before going ahead to define users? Kindly reply chetan ❤ looking forward.
Quick Question, Since the designer here tackled both the front end (Applicant) and the back end (HR) of the identified problem, at least that was what he was hoping for, doesn't this become a Service Design approach (minus the service blueprint) to solve a product problem. I'd like to know what you think about this. Thank you, wonderful video, helped a lot
@@DesignPilot Since the case study was about solving for both the applicant and well as the recruiter, can this be considered and service design approach rather than a product design one? Thank you
@aditya9226 Well every company has its own ways of working. And that’s not a designers job to decide. But the tool should help both parties irrespective of the process the company follows. So the problem statement is how to make it scalable for any sort of process
hey chethan, I am new to product design I have a question, the way people show the processes in case study do they solve the problem like this in a sequential manner I have seen in a lot of case studies where people put the problem statement before user research but when I read the design process problem statement came in the define stage so I am getting confused on the internet there's so much material to learn from but more I read the more I get confused so yeah like why people put it before is it a storytelling technique? or they do they solve it in this way?
1. I'm confused in choosing screens for creating hero images or mockups. The problem is, I was confused about the places of putting final images after testing. 2. Do I add the final prototype(for the 2nd phase test) link before the test section?
@@DesignPilot I meant, not for who your user is, but what do they want and why do they want it ( like you mentioned in the video), the needs,wants frustration etc.. this is done after the user research... this is what i thought
I genuenly have only one question suppose a person who is following your method for how to validate problem statement like a pro you didn t do any user survey or user primary research how will you identify your workflow in a case study like this I mean can we just follow that order? i am super confused
@@DesignPilot Question is do we really have to do user surveys or user interviews to get insight or to understand the problem statement ? Or should just go with the approach is to just to define user persona or user stories on our own but valid using that method ? And if we use your method how will we show a that into a case study?
@@DesignPilot it is not making sense tbh i found your approach much much more suitable and ideal to approach the problem it actually makes sense and i can understand the actual user problem instead of focusing on what to ask and whom to ask your approach is much more suitable this is why i am saying i want to incorporate your approach in my case study
really liked your video , don't you think that you should do this live with that person if he/she is comfortable and time also agrees with both of you who submits its case study , and one more mistakes that you are doing is at the start of the video u said that please like and subscribe , if i liked ur video then i will do that i won't wait 4 u, because no like to miss valuable content , saying that in the beginning just does not make sense and this must be said at the end, hahahaah just kidding loved ur video
