We used to hand over beautifully organised files and watch them drift. The files were never the problem.
## Document intent, not just appearance
For each component, state what it is for, when not to use it, and which decisions are fixed against which are contextual. Developers make dozens of small judgements a day; intent is what makes those judgements consistent without a review meeting.
## Agree how the system grows
Name who may add a component, what evidence is needed, and where it gets recorded. Systems do not decay because people ignore them; they decay because there is no legitimate route to extend them under deadline.
Where this applies
- Graphic Design
- Web Design
Work with Atlas Fieldwork
This documentation comes from the work Atlas Fieldwork does. See what they offer, the results they can evidence, and how to start a conversation.
More from Atlas Fieldwork
- PlaybookPlanning a shoot day in a working facilityFilming in an operating plant is a logistics problem with a camera attached. Access, safety, noise and the production schedule decide what you get, long before anyone frames a shot.
- GuideInterviewing a customer so the story is usableA customer interview fails when it collects praise instead of specifics. The questions that produce usable footage are about the situation before, the decision, and what changed operationally.
- GuideBriefing creators for usable product footageMost creator footage is unusable in paid because the brief asked for a review instead of a demonstration. Here is the brief we send, and the shot list we ask for.
- GuideDesigning a report people actually finishIndustry reports are commissioned as marketing and designed as documents. The ones that get read are structured around findings, with charts that make a single point each.