Gumshoe · Method reference

Design annotations

Add notes to designs that explain behavior, logic, and intent for accurate implementation.

Conceptual illustration of design annotations.
Effort
Low
Participants
Not required
Remote friendly
Yes
Evidence / output
Inference

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

  1. Identify what the visuals do not explain.
  2. Annotate behavior, logic, and states.
  3. Note content rules and edge cases.
  4. Reference standards where relevant.
  5. 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.

Need help choosing and applying a method?

Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.

Discuss your project with Gumshoe Explore Gumshoe services

Sources and further reading

Explore related methods

A general practice reference. This page does not establish that a method was used on a particular client project or that an outcome was measured.