Show the Tension
A longer note on why tension, uncertainty, and tradeoffs are what make process writing credible, especially on personal and studio sites
Finished work has a habit of looking inevitable after the fact. Once the layout is refined and the color system is resolved, it becomes easy to tell the story as though the project had always been headed exactly here. But inevitability is rarely where the craft lives.
The craft is in the unstable middle: when the first concept is compelling but wrong, when the audience is fuzzier than the team wants to admit, when the clever direction has to be replaced by the clearer one.
Why tension matters
Tension lets the reader understand that the work was not merely assembled. It was chosen. And being able to choose well under pressure is far more impressive than being able to present a polished outcome after all the complexity has been stripped away from the story.
What I wish more case studies showed
- the brief that initially created the wrong incentives
- the version that looked better in isolation than it worked in context
- the tradeoff the team accepted and why it was worth it
- the moment where simplification made the work stronger, not safer
Tension is not a flaw in the narrative. It is what gives the narrative stakes.
Personal sites are read as character studies
That is especially true when the case study lives on a personal site. Readers are judging the output, yes, but they are also judging temperament. Do you sound reflective or defensive? Precise or inflated? Honest about uncertainty or eager to erase it?
Case studies become more persuasive when they trust the reader enough to show the unstable parts. Not all of them. Just the ones that reveal judgment.
Comments