Scoring Model

The scoring model helps teams see how well a design review worked. It looks at each part of the conversation and measures two things:

  • How clearly the step showed up

  • How much it shaped the direction of the call

This moves the team past "that felt like a good call." It shows where the conversation really gained or lost strength. Use the scoring model after a design review, or when you run a transcript through the SIGNAL Call Rubric.

Start with a real design review conversation. This can be:

  • A call transcript

  • A meeting recording turned into text

  • Notes from a review, if there is no transcript

A transcript works best because it shows what really happened in the conversation. It gives the team something real to score instead of memory.


How scoring works

Each step of the SIGNAL flow is scored from 1 to 5.

Surface → Identify → Ground → Navigate → Align → Lock

Each step is scored on its own, based on what happened in the conversation. The goal is not a perfect score. The goal is to see how the conversation held together and where the team can improve the next review.

After scoring, look for:

  • Where scores are low

  • Where clarity first dropped

  • Where the conversation lost strength

  • What to improve next time

You do not need to fix everything at once. Improving one or two weak steps can change how the next review goes.

The step scale

The scale shows how much each step shaped the call.

<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 75px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p><strong>Score</strong></p></th><th colspan="1" rowspan="1"><p><strong>Level</strong></p></th><th colspan="1" rowspan="1"><p><strong>Summary</strong></p></th></tr><tr><td colspan="1" rowspan="1"><p>1</p></td><td colspan="1" rowspan="1"><p>Reactive</p></td><td colspan="1" rowspan="1"><p>The step is mostly absent. The conversation moves forward without it.</p></td></tr><tr><td colspan="1" rowspan="1"><p>2</p></td><td colspan="1" rowspan="1"><p>Emerging</p></td><td colspan="1" rowspan="1"><p>The step shows up briefly but does not change the direction.</p></td></tr><tr><td colspan="1" rowspan="1"><p>3</p></td><td colspan="1" rowspan="1"><p>Functional</p></td><td colspan="1" rowspan="1"><p>The step is present and working, but it does not shape the conversation in a meaningful way.</p></td></tr><tr><td colspan="1" rowspan="1"><p>4</p></td><td colspan="1" rowspan="1"><p>Strong</p></td><td colspan="1" rowspan="1"><p>The step is clear and shapes the direction, with minor gaps.</p></td></tr><tr><td colspan="1" rowspan="1"><p>5</p></td><td colspan="1" rowspan="1"><p>Leading</p></td><td colspan="1" rowspan="1"><p>The step is clear, consistent, and actively shapes how the group thinks and decides.</p></td></tr></tbody></table>

Reading the total

Each of the six steps is scored out of 5, for a total out of 30. The lowest possible total is 6. The total shows how strong the conversation was from start to finish.

<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 75px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p><strong>Score</strong></p></th><th colspan="1" rowspan="1"><p><strong>Band</strong></p></th><th colspan="1" rowspan="1"><p><strong>Summary</strong></p></th></tr><tr><td colspan="1" rowspan="1"><p>25–30</p></td><td colspan="1" rowspan="1"><p>Leading</p></td><td colspan="1" rowspan="1"><p>The conversation created strong clarity across the full decision flow. The group moved from problem to action with confidence.</p></td></tr><tr><td colspan="1" rowspan="1"><p>19–24</p></td><td colspan="1" rowspan="1"><p>Advancing</p></td><td colspan="1" rowspan="1"><p>The conversation worked well overall, with a few gaps that softened clarity or momentum.</p></td></tr><tr><td colspan="1" rowspan="1"><p>13–18</p></td><td colspan="1" rowspan="1"><p>Functional</p></td><td colspan="1" rowspan="1"><p>The conversation had useful moments, but several steps were weak or underdeveloped.</p></td></tr><tr><td colspan="1" rowspan="1"><p>6–12</p></td><td colspan="1" rowspan="1"><p>Reactive</p></td><td colspan="1" rowspan="1"><p>The conversation lacked structure. Decisions were unclear, weak, or not fully secured.</p></td></tr></tbody></table>

The step levels and the total bands share some names, but they measure different things. A level describes one step. A band describes the whole call. A call in the Functional band can still have one step at Leading and another at Reactive.

Patterns across the six steps matter more than the total. A call can have a decent total and still break down in one important step. Look for the step where clarity first dropped. That is usually the best place to improve.

Scoring calibration

Use the full scale, but score carefully. The step scale above says what each number means.

Score each step on its own. Don't let one strong part of the call lift every score. Don't let one weak part pull everything down. The score should reflect what actually happened in the conversation.

Back each score with evidence from the transcript. The behavioral metrics below show what to look for.


Step scoring guide

Use the guide below to score each step of the SIGNAL flow.

Surface Challenges

A strong score means the real problem is clear, specific, and tied to a consequence. The group understands what is breaking down and why it matters.

<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p><strong>Score</strong></p></th><th colspan="1" rowspan="1"><p><strong>Description</strong></p></th></tr><tr><td colspan="1" rowspan="1"><p>5</p></td><td colspan="1" rowspan="1"><p>Clear pain and consequence surfaced</p></td></tr><tr><td colspan="1" rowspan="1"><p>4</p></td><td colspan="1" rowspan="1"><p>Tension identified, consequence partly quantified</p></td></tr><tr><td colspan="1" rowspan="1"><p>3</p></td><td colspan="1" rowspan="1"><p>Friction is visible and discussed, but not pushed far enough to shape the call</p></td></tr><tr><td colspan="1" rowspan="1"><p>2</p></td><td colspan="1" rowspan="1"><p>Surface-level acknowledgment, no depth</p></td></tr><tr><td colspan="1" rowspan="1"><p>1</p></td><td colspan="1" rowspan="1"><p>Feature-level conversation only</p></td></tr></tbody></table>

Identify Outcomes

A strong score means the group agrees on what success looks like. There is a clear sense of what should change and how the team will recognize improvement.

<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p><strong>Score</strong></p></th><th colspan="1" rowspan="1"><p><strong>Description</strong></p></th></tr><tr><td colspan="1" rowspan="1"><p>5</p></td><td colspan="1" rowspan="1"><p>Clear, measurable outcome agreed</p></td></tr><tr><td colspan="1" rowspan="1"><p>4</p></td><td colspan="1" rowspan="1"><p>Outcomes stated and mostly measurable, agreement implied</p></td></tr><tr><td colspan="1" rowspan="1"><p>3</p></td><td colspan="1" rowspan="1"><p>Goals stated but vague</p></td></tr><tr><td colspan="1" rowspan="1"><p>2</p></td><td colspan="1" rowspan="1"><p>Outcomes mentioned but not defined</p></td></tr><tr><td colspan="1" rowspan="1"><p>1</p></td><td colspan="1" rowspan="1"><p>Deliverables dominate the discussion</p></td></tr></tbody></table>

Ground in Signals

A strong score means real signals guide the conversation. Evidence shapes how people think and changes the direction of the discussion.

<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p><strong>Score</strong></p></th><th colspan="1" rowspan="1"><p><strong>Description</strong></p></th></tr><tr><td colspan="1" rowspan="1"><p>5</p></td><td colspan="1" rowspan="1"><p>Signals drove the conversation</p></td></tr><tr><td colspan="1" rowspan="1"><p>4</p></td><td colspan="1" rowspan="1"><p>Signals referenced and shaped key decisions</p></td></tr><tr><td colspan="1" rowspan="1"><p>3</p></td><td colspan="1" rowspan="1"><p>Some signal grounding</p></td></tr><tr><td colspan="1" rowspan="1"><p>2</p></td><td colspan="1" rowspan="1"><p>Signals mentioned but not used for decisions</p></td></tr><tr><td colspan="1" rowspan="1"><p>1</p></td><td colspan="1" rowspan="1"><p>Opinion-driven review</p></td></tr></tbody></table>

Navigate Decisions

A strong score means a clear direction forms. The group moves from discussion to a recommendation that people understand and support.

<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p><strong>Score</strong></p></th><th colspan="1" rowspan="1"><p><strong>Description</strong></p></th></tr><tr><td colspan="1" rowspan="1"><p>5</p></td><td colspan="1" rowspan="1"><p>Clear recommendation and explicit agreement</p></td></tr><tr><td colspan="1" rowspan="1"><p>4</p></td><td colspan="1" rowspan="1"><p>Recommendation given, agreement mostly clear</p></td></tr><tr><td colspan="1" rowspan="1"><p>3</p></td><td colspan="1" rowspan="1"><p>Direction given but commitment soft</p></td></tr><tr><td colspan="1" rowspan="1"><p>2</p></td><td colspan="1" rowspan="1"><p>Options presented without a recommendation</p></td></tr><tr><td colspan="1" rowspan="1"><p>1</p></td><td colspan="1" rowspan="1"><p>Discussion without a decision</p></td></tr></tbody></table>

Align Ownership

A strong score means responsibility is clear. The group knows who is taking the next step and how the work will move forward.

<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p><strong>Score</strong></p></th><th colspan="1" rowspan="1"><p><strong>Description</strong></p></th></tr><tr><td colspan="1" rowspan="1"><p>5</p></td><td colspan="1" rowspan="1"><p>Clear ownership and clean boundaries</p></td></tr><tr><td colspan="1" rowspan="1"><p>4</p></td><td colspan="1" rowspan="1"><p>Most ownership explicit, minor gaps</p></td></tr><tr><td colspan="1" rowspan="1"><p>3</p></td><td colspan="1" rowspan="1"><p>Partial clarity</p></td></tr><tr><td colspan="1" rowspan="1"><p>2</p></td><td colspan="1" rowspan="1"><p>Some ownership discussed, not confirmed</p></td></tr><tr><td colspan="1" rowspan="1"><p>1</p></td><td colspan="1" rowspan="1"><p>Ambiguity persists</p></td></tr></tbody></table>

Lock Momentum

A strong score means the conversation leads straight to action. Next steps are clear, timing is understood, and the team agrees on what happens next.

<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p><strong>Score</strong></p></th><th colspan="1" rowspan="1"><p><strong>Description</strong></p></th></tr><tr><td colspan="1" rowspan="1"><p>5</p></td><td colspan="1" rowspan="1"><p>Impact and next steps locked</p></td></tr><tr><td colspan="1" rowspan="1"><p>4</p></td><td colspan="1" rowspan="1"><p>Next steps defined with owners, timeline soft</p></td></tr><tr><td colspan="1" rowspan="1"><p>3</p></td><td colspan="1" rowspan="1"><p>Next steps soft</p></td></tr><tr><td colspan="1" rowspan="1"><p>2</p></td><td colspan="1" rowspan="1"><p>Vague follow-up mentioned</p></td></tr><tr><td colspan="1" rowspan="1"><p>1</p></td><td colspan="1" rowspan="1"><p>Call ended without commitment</p></td></tr></tbody></table>

What the score should produce

A scored review should give the team more than a number. It should produce:

  • The total score

  • The score band

  • Step scores from Surface to Lock

  • A short summary of the call pattern

  • Where clarity first dropped

  • Strengths to keep using

  • Weak points to improve

  • The primary improvement for the next call

This helps the team turn the score into action.

How to use the results

After the review is scored, look for the first weak point in the flow. That is usually where the next improvement should happen.

  • If Surface is weak, clarify the real problem earlier.

  • If Identify is weak, define success before debating options.

  • If Ground is weak, bring stronger signals into the review.

  • If Navigate is weak, make recommendations and tradeoffs more explicit.

  • If Align is weak, make clear who owns the next move.

  • If Lock is weak, close with clear actions, owners, and timing.

The scoring model shows how well a conversation turned into a decision. Over time, this creates more consistent reviews, clearer decisions, and stronger outcomes.


Additional scoring areas

The score tells the team how the conversation performed. These areas explain why it performed that way and what to do next. They turn the rubric from a rating into an improvement plan.

Behavioral metrics

Behavioral metrics help explain why the call scored the way it did.

The SIGNAL score shows how well each step worked. Behavioral metrics show what was happening underneath the score. They are not separate scores. They are supporting evidence from the transcript.

These metrics describe how people talked in the call. They are not the Behavioral UX metrics that Helio tests measure.

Use them to understand:

  • Who carried the conversation

  • Whether the client or the team owned the problem

  • Whether decision language showed up

  • Whether signals changed the discussion

  • Whether a clearer frame was adopted

  • Whether the call ended with confirmed action

Talk time

Talk time shows who carried the conversation. It looks at how much of the call was led by the team running the review and how much came from the other participants.

Talk time does not need to be perfectly balanced. Some calls need more explanation. But a big imbalance can show that the conversation was not building enough shared ownership.

Look for:

  • Who spoke the most

  • Whether one side carried the call

  • Whether the group had enough space to respond

  • Whether important decisions were discussed by the people who need to own them

Use this to see whether the review was collaborative or mostly one-sided.

Problem ownership

Problem ownership shows whether the people in the room acknowledged the real issue. This matters most in Surface. A problem is stronger when the team or client names the tension themselves, instead of only agreeing with someone else's framing.

Look for language like:

  • "We're struggling with…"

  • "The issue is…"

  • "This keeps coming up…"

  • "We need to fix…"

  • "That's where people are getting stuck…"

Strong problem ownership means the group sees the problem clearly and feels some responsibility for solving it. Weak problem ownership means the problem may still feel outside the group, vague, or easy to avoid.

Decision language

Decision language shows whether the conversation moved toward commitment. This matters most in Navigate and Lock. A review may sound aligned, but if no one uses decision language, the direction may still be soft.

Look for words and phrases like:

  • "Let's move forward"

  • "We should choose…"

  • "I'm comfortable with…"

  • "Let's commit to…"

  • "That's the direction"

  • "Next step is…"

Strong decision language means the group is moving from discussion into action. Weak decision language means the call may still be exploring, even if people sound positive.

Reframe adoption

Reframe adoption shows whether the group picked up a clearer way of seeing the problem. This matters most in Ground and Navigate. Sometimes the strongest moment in a call is when someone reframes the issue and the group starts using the new frame.

Look for:

  • A clearer way of describing the problem

  • A shift from opinion to signal

  • A shift from feature talk to outcome talk

  • Participants repeating or building on the new frame

  • The conversation changing direction after the reframe

Strong reframe adoption means the group did more than hear the idea. They used it. Weak reframe adoption means a better frame was offered but did not shape the conversation.

Closing clarity

Closing clarity shows whether the call ended with enough structure to keep the work moving. This matters most in Align and Lock. A call can score well early and still lose momentum if the ending is vague.

Look for:

  • Named owners

  • Specific actions

  • Timing or checkpoints

  • Confirmed agreement

  • A clear next review point

  • A shared understanding of what happens next

Strong closing clarity means the decision can continue after the call. Weak closing clarity means the same conversation may need to happen again.

Strengths

Strengths show what the team should keep doing. After scoring the call, name the parts of the conversation that helped create clarity. These are behaviors worth repeating.

Strengths may include:

  • The real problem was surfaced clearly

  • Outcomes were made specific

  • Signals shaped the conversation

  • The team made a clear recommendation

  • Ownership was confirmed

  • Next steps were locked

The goal is not only to fix weak points. The team should also know what worked, so those behaviors become repeatable.

Improvement areas

Improvement areas show where the conversation needs more support. They should come straight from the scores and the transcript evidence. Focus on the moments that weakened clarity, slowed the decision, or made action less certain.

Improvement areas may include:

  • The problem stayed too general

  • Success was not defined

  • Signals were mentioned but not used

  • Options were discussed without a recommendation

  • Ownership stayed vague

  • Next steps were too soft

Keep this section focused. A call may have many weak spots, but the team should only work on the ones that would most improve the next review.

Primary improvement

The primary improvement is the one change that would most improve the next call. It should come from the first big point where clarity dropped in the SIGNAL flow, because that is usually the best place to improve.

Use this format:

Primary improvement: [specific behavior to change]

Why it matters: [how this weakened the call]

Next time: [what to do differently]

Example:

Primary improvement: Make a clear recommendation.

Why it matters: The group had enough signal to choose a direction, but the conversation stayed open.

Next time: State the recommended direction, explain the tradeoff, and ask for agreement before moving on.

Related links

Anum Hassan

Anum Hassan on iterative product design steps for continuous improvement. Useful when teams want practical iteration steps to copy.

Jun Loayza

Walks through how to uncover real user needs through conversations, behavior, and pattern-spotting. Useful when planning user research to back a new product or feature.

Airfocus

Airfocus video explaining the RICE scoring framework with examples. Useful for teams that learn faster from video walkthroughs.

Identify where decision quality breaks down

The Glare Design Assessment helps teams spot weak validation, stakeholder friction, alignment gaps, and assumptions that scale without measurable learning—so you have a clearer starting point for improvement.

About 5 minutes · Team-based · Diagnostic snapshot you can act on

Take the Design Assessment