Process Book: Documenting Design Thinking

The Process Book Habit

I started keeping process books — visual documents of the design development on a project — after a difficult client experience where the approved direction was questioned after delivery. The client didn't remember approving it. They didn't understand how we got from brief to final. In the absence of a shared record, the conversation got unpleasant.

The process book solves this problem and several others.

What Goes in a Process Book

A process book documents the development of a project from brief to delivery. It's not a portfolio piece — it's a working record. It includes:

The brief summary: the strategic foundation, the client's stated needs, the competitive context.

Exploratory sketches and early concepts: rough work, discarded directions, the range of territory explored.

Concept presentation materials: the three options (or however many) presented at first review.

Feedback and rationale: what feedback was received, what was incorporated, why certain directions were eliminated.

Refinement stages: the evolution from initial concept through revisions to final.

Final deliverables: the approved work in context.

The process book is a narrative of design decisions, not just a collection of outputs.

Why It Improves the Work

Documenting process makes you more conscious of the decisions you're making. When I know I'll be explaining why I made a choice, I make that choice more deliberately. The process book creates accountability to my own reasoning.

It also forces reflection at each stage. When I write up what I did and why before moving to the next phase, I often catch weak reasoning or unexplored alternatives that I would have missed in the flow of making.

Why It Improves Client Relationships

When a client questions a final direction, the process book provides a shared record. "We reviewed this option on March 12th, and the feedback was X, which led us to develop in direction Y" is a statement that can be verified rather than disputed.

More positively: clients who see the process book often develop more confidence in the work and deeper understanding of the decisions. They understand that the final result is the product of considered choices, not arbitrary preferences. That understanding builds trust.

The Format

I maintain process books as PDF documents organized chronologically. For major projects they can run 30–50 pages. For smaller projects, 10–15 pages is sufficient.

I deliver the process book to the client at the end of the project, alongside the final deliverables. Most clients genuinely value having it — it's documentation of their brand investment.

The Portfolio Benefit

Process books are also exceptional portfolio material. Showing the development of a project — the thinking, the alternatives, the refinements — demonstrates far more about how I work than a gallery of final outputs. For new client pitches, sharing process work from past projects is more persuasive than showing finished results.

Outcomes can come from anywhere. Process reveals the designer.