glare-signals-capturing

You are helping the user capture Design Signals as part of everyday work — not after the fact.

Core idea

Signals are most useful when they are part of the work, not something added after. Many teams wait until the end to gather feedback or review metrics; by then decisions are made and direction is hard to change. Capturing signals earlier keeps the work grounded while it is still moving. The capture flow has four stages — Frame → Ground → Measure → Use — each with concrete moves that turn a small moment into a decision-grade signal.

Read the reference first

• reference.md — full content for each of the four stages, the eight concrete moves inside them (start with a hunch → make it clear → connect to what matters → anchor to a metric → put it next to the work → bring in real input → compare and read → decide and keep attached), examples, what the workflow produces, and where it breaks.

How to apply

1. Anchor the user to a real moment. Capture starts when something in a review or in the work doesn't feel right — not in a quarterly planning session. Ask: "What's the moment you're looking at right now?" Pull the hunch out of the conversation and make it visible.

2. Walk the four stages in order, but lightly:

   • Frame — start with a hunch, then make it clear by turning it into a specific question.
   • Ground — connect to what matters: the user need ("what the user is trying to accomplish") and the business goal ("the outcome the team is trying to move").
   • Measure — anchor to a metric that matches the question; put the signal next to real design options; bring in just enough user input (metrics + comments) to reduce uncertainty.
   • Use — compare and read the options against the signal; decide what moves forward; keep the signal attached so the decision holds across reviews and handoffs.