Working method ·
Design Docs
A working format for keeping exploration, decisions, and developer requirements together.
Starting in 2018, I developed a regular practice of creating a Design Doc for each design task at Juice Analytics. It gave exploration, decisions, and implementation requirements a shared home instead of leaving that context scattered across tickets, sketches, messages, and design files.
A flexible working format
The document has three main sections: a ticket summary and design brief to establish scope; progress notes for questions, sketches, and evolving ideas; and a Design Solution section for the final requirements, prototypes, assets, components, and success or error states.

From exploration to handoff
For Juicebox work, I used the Design Solution section to walk stakeholders and developers through a proposed experience, then added questions and notes during the discussion. Developers could turn those requirements into implementation tickets, with a link back to the document for context.

The format supports the design files and prototypes rather than replacing them. Its value is keeping the reasoning and requirements readable as the work evolves.