Honestly.. Don’t do them. By that I mean don’t do them like everyone else does. TLDR; we know you polished things up to tell a story of success, team work, and demonstrate THE UX process. You’ll earn more points for demonstrating YOUR process when faced with actual constraints. I’ve been in UI/UX for almost 20 years and when hiring I just skim through them. They’re almost always the same cookie cutter polished finely tuned gift wrapped process you will never have the time to actually produce on the job, but good on you for dusting off those notebook sketches and filling in all the blanks. Somewhat surprised nobody asks “How long after this project did you begin building the case study?” Or “how much time did you spend putting this case study together?” Case studies are, in my opinion, a false narrative. “Hey look at the obligatory UX tools and techniques I used to demonstrate what I can do” - Most, if not all of the projects I’ve worked on had some sort of “oh lord, you’re kidding, right?” dimension to them. Working backwards, banging out UI improvements while requirements docs are written. You have 2 sprints to identify needs, validate assumptions, wireframe, collect feedback, and mock those up for handoff to engineering. You sit in sprint plannings listening to the list of features/functionality that needs to be introduced by the end of sprint ahead of the engineering hand off. I want to see how you handle THAT project.. you know? That one where you’re tasked with reimagining a product that has little/no documentation, the current version is riddled with UX, UI, IxD, and IA issues making it next to worthless as a guide/reference, and you’re job is to identify undefined workflows across multiple personas, solve for the multitude of disjointed manual processes, their pain points, and so on. The hurricane project. The project you were forced to cut corners on. The real project; Not the school project, boot camp capstone, or vaguely familiar mobile app project (e.g. Dog walking app, food delivery app, exercise tracking app). Edit: first line More on reddit.com

As in depth as they need to be. I’ve read case studies that are long but are just filled with nonsense and filler. They should include everything that is relevant to what you are presenting. People should be able to read it and not get bored. If you’re trying to brand yourself as a researcher you may want to include a sidebar in your case study for your general process for different parts of projects. Like how you approach determining your research methods, how you explain concepts you’ll need to dive into to stakeholders, etc. If you ran into an issue in the middle that delayed or required a deliverable stage to pivot, how did you handle it? It can be helpful to see a list of steps the case study will go through (mirroring project deliverables) at the beginning, like a table of contents. At the end of the stage you can have a recap of what deliverables were checked off and how you began the next stage. That’s what really sells you because if people like your process they’ll be more likely to hire you. If you give vague explanations from how to got from A to B and fluff it up with some diagrams and boilerplate copy it will be easy to gloss over. More on reddit.com

Hey I have a master degree in sociology and social research and am currently doing a PhD in data science so I hope I can help! :) methodology refers exclusively to the techniques you will be using in your analysis i.e. ethnomethodolgy, text mining etc. Case study is a type of study and not a technique :) I think you could proceed as follow 1.address the general topic like the market you are interested in 2. Define a clear research question 3. Define what techniques you will use 4. Collect data accordingly. To find a suitable technique and method you should ask yourself what the scope of your paper is, what you want to achieve, how can you treat the data structures you will create. Maybe if you give more details I can give my humble suggestion to help you find a good method. More on reddit.com

Case studies can be instrumental or intrinsic and there is no control condition. A case can be a single subject or something more complex, or even a multiple case study. An experiment would have a control. For an education example: you could do an experiment where you design a learning experience and then test it through pre and post tests (don't do this), or compare two groups who learn different materials or use different pedagogical approaches. Or, you could study an existing learning experience that you feel is a good example of some education theory (this would be an instrumental case study). With the experimental approach your data would likely be largely quantitative. With the case study you could have a mix and would benefit from multiple data sources (triangulation). Hope this is helpful! More on reddit.com