How to Brief Developers on Structural Intent
Short summary
Developers fill gaps in a design by interpreting intent, because the service has to do something in states the design did not specify. The quality of those interpretations depends almost entirely on what they were told about structure rather than about screens. A brief that specifies appearance and behaviour on the designed path leaves every undesigned state to guesswork. A brief that communicates structural intent, meaning what the service is trying to protect and why, lets a developer make sound decisions in situations neither of you anticipated.
Why screen specification is not enough
Most design handover documents communicate what the screens look like and what happens when a user does an expected thing. This is obviously necessary and it covers the designed path well.
However, it says nothing about the undesigned states, and undesigned states are where developers spend a meaningful share of their build time. Imagine that a condition fires that nobody mapped, two rules interact in a way the design did not anticipate, or a user arrives in a state the flow diagram does not contain. In each case the developer has to decide what happens, and the specification in front of them does not help, because it describes the path rather than the structure underneath it.
What they fall back on is inference. They look at the designed states, work out what the design seems to be trying to do, and extend that logic to the situation in front of them. Sometimes this produces exactly the right answer. Sometimes it produces something that looks reasonable and quietly undermines the thing the design was protecting.
What structural intent means
Structural intent is the reasoning underneath a design decision: what the service is trying to achieve or protect at that point, and what would constitute a failure.
A screen specification says that after submission the user sees a confirmation with a reference number. Structural intent says that after submission the user must be able to prove to themselves and to us that the submission happened, because this journey has a consequence for both the service and the user, and uncertainty about whether it completed generates both distress and support contact.
Structural intent tells a developer what to protect. If a constraint emerges that makes the specified confirmation impossible, the developer working from structural intent knows what the replacement has to achieve. The developer working from screen specification knows only what it used to look like.
What to include in a structural brief
What this part of the journey is protecting
State what could go wrong for the user at this point and what the design is doing about it. This is the single highest-value item, because it is the thing a developer cannot infer from a screen and the thing that determines whether their interpretation holds.
Which elements are load-bearing
Distinguish between decisions that exist for a specific reason and decisions that were the best available option at the time. A developer who knows which is which can adapt the flexible parts under constraint without touching the parts that would break something.
What the service should do in states you have not designed
Specify the fallback explicitly. Every service behaves somehow in unhandled states. Deciding that behaviour deliberately, and telling the developer what it is, converts an unpredictable failure into a predictable one.
Which combinations you have and have not checked
Where conditional logic is involved, say which states have been explicitly designed and which have not. A developer who knows that twelve of five hundred combinations were checked will treat the remainder differently from one who assumes the design covers everything.
What to come back to you about
Name the situations where you want to be consulted rather than have a decision made without you. This is more effective than a general request to be consulted about everything, which developers reasonably ignore under delivery pressure. A short, specific list is more likely to get used.
Where the brief should live
A structural brief communicated only in a conversation or a kickoff meeting has a short life. The decisions it needs to inform will be made weeks later, by someone who may not have been in the room, under pressure, at a moment when nobody thinks to go looking for it.
The brief needs to sit where the work sits. In the ticket, in the specification the developer opens when they start the piece, in annotations on the designs themselves. The test is whether a developer encountering an unanticipated state at four in the afternoon on a Thursday can find the reasoning without asking anyone.
This is the same principle that governs design rationale generally. Reasoning that lives in the designer's head, or in a conversation that happened once, is not available at the moment it is needed. Reasoning embedded in the artefacts the delivery team uses is already where it needs to be.
Instead of asking whether your specification is detailed enough, ask whether a developer hitting a state you did not design would know what the service is supposed to protect.
Frequently asked questions
What is structural intent in design handover?
Structural intent is the reasoning underneath a design decision: what the service is trying to achieve or protect at that point, and what would constitute a failure. A screen specification describes what the interface does on the designed path. Structural intent describes what the design is for, which is what allows a developer to make sound decisions in states the design did not anticipate.
Why do developers change design decisions during build?
Developers change design decisions during build because constraints emerge that the design did not anticipate, and someone has to decide what happens. Working from a screen specification, they can see what the design looked like but not which parts were load-bearing or why. They extend the apparent logic to the new situation, which sometimes produces the right answer and sometimes quietly undermines what the design was protecting.
What should a design brief include beyond screen specifications?
Include what each part of the journey is protecting and what could go wrong for the user there, which elements are load-bearing against which were the best available option, what the service should do in states you have not designed, which conditional combinations you have and have not checked, and a short specific list of situations where you want to be consulted rather than have a decision made without you.
Where should structural design intent be documented?
Where the work sits: in the ticket, in the specification the developer opens when starting the piece, and in annotations on the designs themselves. A brief that is communicated only in a kickoff conversation has a short life, because the decisions it needs to inform are made weeks later under pressure. The test is whether a developer hitting an unanticipated state can find the reasoning without having to ask anyone.