What it is
Notes layered onto designs that specify behavior, interaction logic, content rules, states, and intent that visuals alone cannot convey, ensuring engineering builds what was designed.
When to use it
During Prototype and at Implement handoff.
Why (value)
Prevents misinterpretation at build time by documenting the behavior and rules behind the pixels.
How to run it
- Identify what the visuals do not explain.
- Annotate behavior, logic, and states.
- Note content rules and edge cases.
- Reference standards where relevant.
- Review with engineering.
Inputs and outputs
- Inputs: Designs and knowledge of intended behavior.
- Outputs: Annotated designs ready for accurate handoff.
Time and effort
Low. Incremental with handoff.
Evidence and limitations
A communication artifact, not evidence. See Evidence and limitations.
Tips and pitfalls
- Annotate what pixels cannot show: logic and states.
- Keep annotations close to what they describe.
- Include accessibility annotations.
Variations
Redlines, interaction specs, accessibility annotations.
Related methods
Need help choosing and applying a method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- UX Tigers, “100 UX methods.”
Explore related methods
- Accessibility annotations — Specify accessibility intent, headings, focus order, labels, so it is built in, not bolted on.
- Design handoff and specification — Give engineering everything it needs to build the design correctly, including the edge cases.
- UI state mapping — Design every state a screen can be in, not just the ideal one.
