This question comes up every time I’m reviewing a portfolio and I still don’t have a clean answer to give: how long should a design case study be?
The range I see in practice:
Bare minimum (what inexperienced portfolios have): 200-400 words. Usually just a description of the project. No context, no decisions, no outcome.
Standard (competent professional portfolios): 600-900 words with 5-8 images. Covers brief, constraints, key decisions, outcome.
Detailed (senior-level or specialist portfolios): 1,200-2,000 words. Includes research process, iteration documentation, stakeholder navigation, measurable outcome.
My actual view: it’s less about word count and more about information density. A 400-word case study that answers “what was the problem, what did I decide and why, what happened” is more effective than 1,500 words that describe the process without revealing the thinking.
The sections that matter most to whoever is evaluating you:
- The decision under constraints: what could you have done and why did you choose this
- Evidence of understanding the context (not just the brief)
- The result (quantified if possible)
The sections that matter least: anything that describes activities rather than decisions. “I conducted stakeholder interviews” is a sentence about activity. “Stakeholder interviews revealed X which changed the approach because Y” is a sentence about thinking.
What length are you hitting and why?
The activity vs decision distinction is the correct frame for case study quality. Most underperforming case studies are chronicles of activities. Strong ones are arguments for decisions. The constraint that forces you to justify choices rather than list them makes the writing and the thinking better.
For hiring managers reviewing 50 portfolios in a day: the 600-900 word structured version with a strong outcome lead is the most effective. Detailed academic case studies are valuable for specific role types but most hiring decisions are made on the first 90 seconds.
@CrispestHaze88 I’d add: case study length should match project complexity and seniority level. A junior designer doing their third project shouldn’t write 1,800 words about it - the length implies depth that isn’t there. The length should be honest about the scope.
the quantified outcome section is where most designers’ case studies fail because design decisions often don’t have clean measurable results. “the client was very happy” is not an outcome. Learning to describe qualitative outcomes in specific terms (user feedback themes, business decision made, stakeholder sign-off secured) is worth practicing.
200-400 words is the main problem I see in student portfolios. There’s real work there and real decisions were made but none of it is on the page. The assumption seems to be that the images speak for themselves - they don’t, not in a portfolio context.