The SIGNAL Call Rubric shows how well a design review created clarity. It looks at the conversation itself. What problem came up? What outcome was defined? What signals shaped the direction? Did the call end with clear owners and next steps?
This makes the review easier to improve. The team can see where the conversation gained strength, where it lost momentum, and what to change next time.
Why this matters
In product and design work, decisions rarely fail all at once. They lose strength bit by bit. That usually shows up when:
-
The problem is loosely defined
-
Outcomes stay unclear
-
Evidence is mentioned but not used
-
A direction forms but does not stick
-
Ownership stays vague
-
Next steps are implied but not confirmed
From the outside, the call may look productive. Inside the work, momentum slows.
The rubric makes that visible. It shows where the conversation lost strength, so the team can keep the work moving.
Use this rubric with a transcript
The clearest way to check a design review is to run the rubric on a call transcript. A transcript shows what really happened. It gives the team something concrete to review, instead of memory or gut feel.
-
Input: a design review transcript
-
Process: check the call across Surface, Identify, Ground, Navigate, Align, and Lock
-
Output: a scored view of where the conversation created clarity and where it lost strength
Run a Transcript shows three ways to do this.
The decision flow
Every design review moves through a sequence, whether the team names it or not. SIGNAL makes that sequence clear:
Surface → Identify → Ground → Navigate → Align → Lock
Each step reduces uncertainty. By the end, the group has moved from an open problem to a committed next step.
-
Surface Challenges: the underlying challenge becomes clear
-
Identify Outcomes: the desired outcome is defined
-
Ground in Signals: evidence is brought in
-
Navigate Decisions: a direction forms
-
Align Ownership: responsibility is made clear
-
Lock Momentum: next steps are secured
The steps build on each other. When a meeting feels unfinished or stalls later, the cause is often an earlier step that did not fully develop.
The six SIGNAL steps
Each SIGNAL step is a moment in the conversation where something important needs to happen.
When these moments come together, the call moves forward with clarity and direction. When one is weak or skipped, the rest of the conversation has to work harder to make up for it.
S: Surface Challenges
Focus: clarifying the underlying problem
Most calls begin with something that sounds clear: a request, a goal, or a feature that needs attention.
What matters is whether the conversation stays at that level or gets to what is really driving it. As the discussion goes deeper, the problem gets more specific. Pressure or urgency starts to show, and people begin to describe what isn't working in real terms.
You can hear this shift in the language. People stop describing what they want and start describing what is happening.
This step sets the foundation for everything that follows.
It considers
-
Whether the root issue is explored
-
Whether consequences are made visible
-
Whether the challenge is clearly acknowledged
What to listen for
-
Language that describes friction or failure
-
Signs of urgency or pressure
-
A move from requests to real situations
What this unlocks
A clear challenge gives the conversation direction. It creates something real for the group to respond to.
What breaks if it's weak
The conversation stays general. Ideas are discussed without being tied to a real problem.
Connection to the next step
If the problem isn't clear, outcomes are harder to define.
I: Identify Outcomes
Focus: defining what "better" means
Once the problem is clear, the conversation moves toward outcomes. This is where the group defines what they are trying to change.
At first, this may stay broad. Stronger calls make outcomes more specific as they go. People describe what needs to improve, who it affects, and how success would show up.
When outcomes are clear, feedback gets more focused and easier to judge.
It considers
-
Whether business objectives are explicit
-
Whether user needs are clear
-
Whether success is shared and understood
What to listen for
-
Clear statements of what should improve
-
Links between user behavior and business impact
-
Agreement on what success looks like
What this unlocks
Clear outcomes give the conversation a target and help guide decisions.
What breaks if it's weak
The call drifts into opinions and preferences with no clear way to judge them.
Connection to the next step
Signals need a clear outcome to point toward.
Stella Parisi calls out:
I believe one of the hardest parts is to define clear Objectives and Key Results that can help us measure the design impact at different levels from the beginning of the project. The impact can be on the business, on the value for users or in the society in general.
When Objectives and Key results are well defined and track, it helps in communicating the progress to the various stakeholders during the design development and of course in the end.
G: Ground in Signals
Focus: bringing evidence into the conversation
As the conversation goes on, it needs to connect to something real. Signals can come from user feedback, data, testing, or patterns the team has seen.
In Glare, each Design Signal is one of four types: Need, Use, Prefer, or Adopt. Naming the type tells the group what the signal can settle. A Use signal shows whether a design worked. It does not show which option people would choose.
What matters is how signals are used. When they are used well, the conversation gets more grounded. People change their thinking based on something shared.
Signals do not need to be perfect. They need to be real enough to guide the discussion.
It considers
-
Whether real data or user feedback is referenced
-
Whether a baseline or change is understood
-
Whether signals influence decisions
What to listen for
-
References to user behavior
-
Data tied to a change or comparison
-
Moments where the direction shifts because of evidence
What this unlocks
Signals reduce ambiguity and help the group move forward with confidence.
What breaks if it's weak
The conversation loops. Opinions repeat without progress.
Connection to the next step
Signals make it easier to form a clear direction.
N: Navigate Decisions
Focus: shaping a clear direction
With context in place, the conversation moves toward a decision.
You can hear this when someone pulls the discussion together and points toward a path. A recommendation forms, tradeoffs are named, and priorities get clearer.
The conversation shifts from exploring ideas to shaping a direction. When the team is choosing between options it has already tested, this is where a Focus Bet gets pressure-tested.
It considers
-
Whether a recommendation is made
-
Whether tradeoffs are clear
-
Whether agreement begins to form
What to listen for
-
Clear recommendations
-
Tradeoffs said out loud
-
Movement toward a decision
What this unlocks
A clear direction gives the group something to align around.
What breaks if it's weak
Options are discussed but not resolved. Decisions are delayed.
Connection to the next step
Ownership depends on a clear direction.
A: Align Ownership
Focus: making responsibility visible
Once a direction is set, the conversation turns to responsibility.
This is where the group makes clear who will carry the work forward. Ownership becomes visible, and expectations get clearer.
This step connects the decision to the work.
It considers
-
Whether a clear owner is named
-
Whether decision authority is understood
-
Whether responsibilities are defined
What to listen for
-
Owners named out loud
-
Confirmation of responsibility
-
Clarity on who is driving the next step
What this unlocks
Ownership creates accountability and helps the work move forward.
What breaks if it's weak
Work slows down. Responsibility is assumed but not confirmed.
Connection to the next step
Momentum depends on ownership.
L: Lock Momentum
Focus: turning the conversation into action
The final step decides whether the conversation carries into the work or fades out.
Momentum shows up in how the call closes. Next steps are clear, timing is discussed, and alignment is confirmed.
The group leaves knowing what will happen next.
It considers
-
Whether actions are clearly defined
-
Whether timing is set
-
Whether alignment is confirmed
What to listen for
-
Specific next steps
-
Timing or checkpoints
-
Clear confirmation of alignment
What this unlocks
Momentum carries the decision forward and turns agreement into action.
What breaks if it's weak
The call ends without traction. The same topics come back later.
Connection to the system
This completes the cycle and sets up the next conversation.
How to use the results
After the transcript is reviewed, look for the step where clarity first dropped. That is usually where the next improvement should happen. The Scoring Model lists what to do when each step is weak.
The goal is not to perfect every review. The goal is to find the part of the conversation that needs the most help and improve it next time.
The SIGNAL Call Rubric helps teams see how decisions form inside a design review. It breaks the call into clear steps, shows where the conversation is strong, and shows where it loses strength.
Over time, this creates more consistent reviews, clearer decisions, and stronger outcomes.