There is a particular sadness in finding a folder of half-finished photographs from a project you loved. You remember the six weeks of sketching, the failed colour tests, the night you rebuilt the whole thing from scratch, and all you have to show for it is three blurry phone snaps and a scrap of paper reading “fix the back”. Documenting work as you go is not busywork. It is the difference between a portfolio entry that shows what you made and one that shows how you think.
Begin at the messy beginning
Most case studies start too late. They open on a clean desk and a clear brief, when the real interest — the searching, the wrong turns, the second thoughts — has already been tidied away.
The research phase is where your project earns its keep in a portfolio. Save the references you actually used, not the ones that sound impressive. When you screenshot an image, add a line explaining why it caught your eye. Links rot, so download or photograph anything you want to keep. A bookbinder researching exposed spines might photograph a shelf of library books and note the two bindings that came closest to what she had in mind. Six months later, that note explains an entire design decision.
Keep a single running document for the project — one file, dated entries, no tidying. Everything goes there: sketches, rejected directions, a photograph of a colour swatch held against a wall.
Build a capture routine that fits real life
Projects go undocumented for one reason: capture depends on remembering, and nobody remembers when they are deep in the work. Attach the habit to something you already do — the moment you stop for the day.
Before you tidy up, run through this short list:
- One wide shot of the workspace exactly as it stands, mess included.
- One close-up of whatever is on the bench or the screen right now.
- Three lines in the log: what you did, what went wrong, what comes next.
- One image of anything you printed, cut, folded, glued or drew that day.
Two minutes. That is the whole commitment. Work near a window where you can, and shoot in daylight when it is available, but do not let imperfect lighting stop you. A slightly grainy photograph of a real process is worth more than a perfect photograph you never took.
Photograph the moments that carry the story
You do not need hundreds of process shots. You need the right five or six, and they tend to fall into predictable places:
- The first rough. The ugliest version, made before you knew what you were doing.
- The pivot. The day you abandoned an idea and started again.
- Hands at work. Scale, material and effort read better with a person in the frame.
- A detail that shows a decision. A joint, a stitch, a colour test, a set of wireframes side by side.
- The finished piece in its setting. On a wall, in a room, in someone's hand.
Keep the framing roughly consistent so the images sit together later. A marked spot on the floor, a piece of tape on the wall, the same camera height — small habits that save hours of cropping.
Notes that will still make sense in two years
Future-you is not present-you. “Changed the blue” means nothing six months on. Write the decision and the reason: “changed the blue because it read as cold against the oak”.
Date every entry. Note numbers where they matter — hours spent, versions made, materials used, how many times you reprinted something. Record anything a client or collaborator said that shaped the work, while you still remember the tone it was said in. And keep a line for what you would do differently. That line is often the most useful thing in the whole folder, and it is the first thing people ask about in an interview.
Document the finished thing properly
When the project is done, give it a proper session rather than grabbing shots in the last ten minutes. Photograph the piece in even light against a plain background, then again in context. Turn it over. Shoot the underside, the back, the edge — the places where craft is decided and where most portfolios fall silent.
For digital work, capture full-page screenshots alongside detail crops, and remember the states people forget: empty screens, error messages, the mobile view, the awkward long title. Name files sensibly so you can find them later, and back everything up in two places, one of them off-site.
Turn the archive into a case study
Now the easy part, because the work is already done. Open the folder and read it through before you write anything.
Start with the problem, not the brief. What was actually difficult about this? Then move through four beats: the question you were answering, the constraint you were working within, the turning point, and the outcome. Keep them short. A case study is not a diary.
Edit the images hard. For each one, ask whether it moves the story forward; if it is there because you like it, cut it. Ten considered images beat forty loose ones. Write captions as if the reader will never scroll back up — captions do more work in most portfolio pages than the body text does.
Include the failure if it taught you something. A project that went smoothly is pleasant to read about. A project where you took the wrong route and found a better one is memorable.
Start the next project with a folder and a line
Before you begin anything new, create the folder and the log. Name them with the date. Paste in the brief, however vague it is. Put your phone somewhere within reach and take one photograph of the blank page, the clean bench, the empty canvas.
That is the system. Two minutes a day, one document, one folder, a handful of deliberate photographs. Do it once and you will have a case study. Do it for a year and you will have a body of work that explains itself.
Photo: ready made / Pexels
