September 23, 2026 · Julian Castellanos · 6 min read
Write decisions, not deliverables
A case study is a record of choices and their reasons. Here is a simple structure that makes them visible.
"I created wireframes, then high-fidelity mockups, then a prototype." Every designer has written this sentence, and it tells the reader nothing. Everyone makes wireframes. What the reader wants to know is what you decided, and why.
The decision and the reason
For each step worth mentioning, write two sentences. The first says what you decided, in plain words: "We grouped the list by store aisle." The second says why, ideally pointing back to something you observed: "People shopped aisle by aisle, but the list was sorted by recipe."
That pairing is the core of the structure Casepanorama drafts: every process step has a decision and a why. If it cannot find a reason in your notes, it leaves the why empty and asks you, rather than inventing a plausible one.
Three or four, not twelve
Pick the three or four decisions that changed the outcome. Readers remember a few sharp choices; they skim a list of activities. If a step was routine, leave it out or fold it into a sentence about constraints.
Let the images carry the evidence
Place each decision next to the image that shows it. A decision about grouping belongs beside the grouped list, not three scrolls away. In a horizontal story this is natural: the reader walks from the claim straight into the evidence.