What the approved design hasn’t resolved
Content variation and publishing rules become delivery work when approval leaves them undecided.
Illustrative scenario. The situation and arithmetic below explain a delivery pattern. They are not a reported interview or a client result.
The title wraps onto another line.
The approved card contains a short sample title, while the staging version carries a longer customer record that pushes the price below the adjacent card and leaves the editor choosing between changing the words and raising a ticket.
Both versions follow their inputs.
Design approval made the work visible.
A detailed design gives the client and delivery team something concrete to review before implementation, helping them agree hierarchy, interaction and visual consistency while changes are still easier to discuss than they will be inside a release.
That review serves a purpose.
The team reduced one uncertainty.
Designers use representative content to make a review manageable, and developers rely on approved layouts to understand the intended behaviour; neither team can resolve every publishing exception before somebody identifies which records the finished system must accommodate.
The samples set the boundary.
The exception becomes repeat work.
In an illustrative review, 12 components each need two additional content states, and each state takes 30 minutes to implement and check; that adds 12 hours before wider regression testing or further client approval is considered.
The states accumulate across components.
Content continues to change.
A translated title, a missing image or a newly introduced product can reveal a state absent from the original sample, even when the design review was thorough and everyone delivered the work described in the agreed brief.
Variation belongs in a publishing system.
Approval needs a content boundary.
When sample content stands in for an agreed range of records and behaviours, design approval leaves part of the component specification open, and production becomes the place where those remaining decisions are discovered and negotiated.
The approved design needs agreed content states before its implementation can be priced reliably.