The Over-Explained Case Study
I’ve noticed something about my portfolio recently.
Every new project makes the case study longer than the last.
When I open a file to edit, I rarely remove anything. I add more context. More process slides. More annotations explaining why a button is blue or why a layout is structured a certain way. I expand paragraphs so nothing feels misunderstood.
It looks thorough.
And on the surface, it feels responsible. We’re told to show our thinking. Recruiters want clarity. Faculty want structure. Every decision should sound intentional. So I document user pain points, research insights, iterations, feedback loops. I make sure the story flows cleanly from problem to solution.
The case study becomes detailed. Structured. Safe.
But recently I’ve started asking myself a different question:
Am I explaining because the work needs it, or because I’m afraid of being misread?
There’s a subtle difference.
Sometimes the process was messy. Decisions were influenced by time pressure, instinct, incomplete information. In reality, design rarely unfolds in neat chapters. But in the case study, uncertainty becomes insight. Confusion becomes exploration. The narrative sounds confident.
Get Looks Right’s stories in your inbox
Join Medium for free to get updates from this writer.
The writing becomes stronger than the memory.
And while clarity is important, over-clarity can quietly turn into protection. When every decision is defended before it’s questioned, the explanation starts carrying the project. The reader understands the thinking, but the work itself feels secondary.
That’s when I realized something:
Over-explaining often isn’t about depth. It’s about safety.
It feels safer to justify everything than to risk being seen as unclear. Safer to sound intentional than to admit parts were intuitive. Safer to add more slides than to trust that the work can stand on its own.
But strong work doesn’t need a courtroom defense.
It needs just enough context to be understood and enough restraint to let the design breathe.
So here’s the shift I’m experimenting with:
Instead of asking, “Have I explained this enough?”
I’m asking, “If I removed half of this, would the core still hold?”
If the answer is yes, I cut.
Because a good case study isn’t long.
It’s clear.
And clarity doesn’t come from saying everything.
It comes from saying what matters.
Takeaway:
If your case study feels heavy, it might not need more explanation. It might need more trust in your work, and in the reader.
