UX/UI Design: Foundations to Practice · Design Handoff and Working with Developers
Reviewing an Implementation Against the Original Design
A design's genuine work does not end once a specification is handed off; reviewing the actual, real implementation against that original intent is where a genuine discrepancy, whether from a missed detail or a misunderstood specification, actually gets caught before it reaches real users.
An engineer implementing a design, however carefully and thoroughly that design was actually specified, will inevitably introduce some genuine discrepancy from the original intended design, whether from a specific missed detail, a specific technical constraint that required a small adjustment along the way, or a simple, honest misunderstanding of a particular specification, which is exactly why a genuine review comparing the real, actual implementation directly against the original intended design remains a necessary step, not an optional, dispensable extra given how carefully the specification was originally written.
- An engineer implementing even a carefully specified design will inevitably introduce some genuine discrepancy, making a real implementation review a necessary step, not optional.
- A meaningful review happens on the actual target device or browser, not only a design file comparison, since some discrepancies only become visible in true, final real-world context.
- Not every difference from the original design is a mistake; some reflect a legitimate technical constraint, requiring a reviewer to distinguish this from a genuinely correctable error.
- Implementation feedback benefits from the same specific, factual discipline as design feedback generally, rather than a vague complaint with no actionable detail.