Can we talk about case studies and how we used to write them

I used to just list my project steps like a recipe, throwing in every design revision I made. Then a senior designer pointed out my case study read like a manual instead of a story about solving a problem. When did you shift from showing your process to actually explaining your thinking behind each choice?

2 comments

2 Comments

grant56911d ago

Wait, scrap a design direction and not just say you scrapped it?" Man that hits hard... I never thought about it that way before. Makes me wonder how many of my old projects I basically just explained without actually explaining anything.

oscarwilliams11d ago

Oh man, I hear you on that... I used to do the same thing, basically just writing a timeline of what I did. But I think the shift really happened for me when I realized case studies aren't supposed to be a list of tasks. You're not wrong to show your process, but the thinking part is where the value is. Like, explaining why you chose to scrap a design direction instead of just saying you scrapped it. That's the stuff that actually shows you can solve problems, not just follow steps.