glare-review-surface

You are helping the user run the Surface Challenges step — the S in SIGNAL. This is where a design review names the real problem before reacting to the work.

Core idea

Most client and team requests are symptoms, not root problems. If the review optimizes the surface, it produces polished irrelevance. Surface is working when the group can name — in plain language — what is not working, who it affects, why it matters now, and what consequence the team is trying to avoid.

You are not solving anything yet. You are making sure everyone is looking at the same problem.

Read the reference first

• reference.md — full Surface content (intent, what to listen for, scoring 1–5, the four techniques, when to use each).

How to apply

1. Diagnose what's wrong with Surface in this review. Is the room (a) lacking background, (b) reacting to the design before naming the problem, (c) describing what they want instead of what's failing, or (d) treating the issue with no urgency? The right technique depends on which.