High-stakes industries like aviation and healthcare have long relied on three-way communication to prevent catastrophic errors: a sender transmits information, the receiver repeats it back, and the sender verifies understanding. According to the American Academy of Family Physicians, this “check-back” technique has dramatically reduced medical errors, particularly when critical instructions are at stake. Yet in software development, we rarely apply this proven pattern to one of our most error-prone handoffs—the translation of UX designs into working code. The solution lies in flipping a common assumption: engineers, not designers or product managers, should write user stories based on annotated designs.

Here’s how the three-way pattern transforms design handoffs.

1. First, the designer creates thoroughly annotated mockups that document not just what components look like, but how they behave across edge cases, interactions, and responsive states.
2. Second, the engineer “repeats back” their understanding by drafting user stories that describe the implementation in their own words—breaking down the design into specific, actionable work items with acceptance criteria.
3. Third, the designer reviews and comments on those stories, catching misunderstandings before code is written.

This closed-loop communication ensures mutual understanding and surfaces disconnects early, when they’re cheapest to fix.

This approach aligns with core agile principles. Mike Cohn, the definitive authority on user stories, explicitly states that “anyone can write user stories” and that who writes them matters far less than who discusses them.

When engineers translate designs into stories themselves, they engage more deeply with design intent, catch technical constraints early, ask better questions, and take ownership of the work. Product owners still prioritize and manage the backlog, but they’re freed from the impossible task of being expert in both product strategy and technical implementation.

For consultancies especially, where team compositions shift and client handoffs are more frequent, this pattern creates a verifiable paper trail of shared understanding. The annotated design becomes the sender’s message, the user story becomes the receiver’s confirmation, and the designer’s review becomes the final verification—a safety technique borrowed from industries where miscommunication costs lives, now applied to ensure we build the right thing, right.

It’s not about shifting responsibility; it’s about creating a collaborative verification loop that catches errors before they cascade into expensive rework.