Make sources and rules findable in a design handoff

Screenshots help teams discuss spacing, content and visual priorities. Their number alone is not an adequate measure of a development handoff, however. What matters is whether the team can identify the valid version and the rule that leads from one view to another.

Two views leave decisions open

In a fictional portal project, development receives wide and narrow exports of a project list. Filters sit side by side in the wide image; the narrow one shows only a filter icon. Both images can be correct without answering the following questions.

The table identifies missing information in the example, rather than defects in a project actually reviewed. Anyone who guesses these rules while building the interface is also making decisions about product behaviour.

Existing rules can support a concise handoff

Carbon separates content rules, behaviour and interaction in its button documentation. This shows why a visual reference can point to further information.

If a suitable component is already clearly documented and both teams use the same version, a screenshot with a precise reference may be enough. Describing every unchanged detail again would create unnecessary maintenance work. Product-specific deviations, new wrapping rules and undecided content remain open, however.

Assess the handoff by its outstanding decisions

Before implementation, check that the source file, valid version and agreed rules are accessible. Identify remaining questions and how decisions will be made. This allows the handoff to be assessed by its information content, while screenshots retain their useful place as visual references.

Sources

• Carbon: Button Guidelines