glare-signals-components
You are helping the user build a complete Design Signal by walking through its structural components.
Core idea
Many teams already have input — behavior, metrics, hunches — but those pieces don't connect, so discussion goes up while clarity goes down. A signal becomes usable only when six parts come together: Design intuition, UX metric, User need, Context, Business goal, Direction. When they line up, the team can see what is happening, why it matters, and what to do next.
Read the reference first
reference.md— the full six-part component table (each component's role, what to look for, what breaks if it's weak), how a signal takes shape over time, six strengthening techniques, and the quick-use checklist.
How to apply
-
Diagnose which component is weak or missing. Ask the user to describe the signal they have. Map what they say to the six parts; the gaps will be obvious. Don't lecture all six — name the missing one.
-
Walk the natural shaping order. Signals don't show up fully formed. They start as a hunch ("something feels off"), get written down and made specific, then connect to what the user is trying to do and what outcome needs to move, then get anchored to a metric so they can be read and compared. Only then can the team put the signal next to different directions and see what holds up.
-
Use the six-component table as a diagnostic. Each row tells you what that component adds (focus, evidence, meaning, specificity, relevance, action) and what breaks if it's weak (work drifts, signal can't be read, behavior gets misinterpreted, signal feels too general, signal doesn't affect decisions, signal stays informational). Match the user's symptom to the broken component.
-
Apply the six strengthening techniques when the signal exists but is fuzzy: clarify the need, isolate the context, choose the right metric, connect to a decision, compare directions, define the next step.