Journal · Web & Tech
A design handoff nobody has to ask questions about
[Placeholder copy] If a developer has to guess, the design was not finished. Guessing is a specification failure.
[Placeholder] Every question a developer has to ask is a decision the design left open. Some of those decisions will be made without you.
[Placeholder] Specify the states nobody enjoys drawing: empty, loading, error, too-long, too-short, offline. That is where handoffs actually break.
[Placeholder] Name things once and use the name everywhere. A token that is called three things becomes three values in the codebase.
[Placeholder] The handoff is a document, not a meeting. If the knowledge only exists in someone's head, it leaves when they do.
More from the journal
Want this done rather than described?
The Studio runs it as a project, with a scope and a signature.
Start a project