The pattern matters more than any single score.
The Design Assessment gives each dimension a score, but the real value comes from seeing how those scores work together. A number can show where something is strong or weak. A pattern shows how design impact moves, slows, or breaks across the organization. Reading Patterns helps teams understand what the scores mean as a system.
Why patterns matter
Most teams want to know their score first. That is natural. A score gives the assessment a clear starting point. But the score is only useful if it leads to a better conversation.
A team might score high in one dimension and low in another. That does not automatically mean the low score is the first thing to fix. The real question is how that low score affects the rest of the system.
For example:
-
Strong Organizing Work with weak Scaling Influence means knowledge may be captured, but proof is not traveling far enough
-
Strong Building Proof with weak Guiding Decisions means evidence exists, but it may not be shaping choices
-
Strong Guiding Decisions with weak Building Proof means teams may move fast, but proof may not be strong enough to defend the direction
-
Strong Managing Complexity with weak Organizing Work means teams may handle large work well, but learning may still get lost afterward
The score shows the parts. The pattern shows the flow.
What patterns reveal
Patterns reveal where design impact is getting blocked. They help teams see whether the issue is happening early, in the middle, or late in the work.
A pattern can show:
-
Where work starts clearly
-
Where learning gets lost
-
Where complexity slows progress
-
Where proof breaks down
-
Where decisions lose momentum
-
Where influence stops moving
-
Where one strong dimension is carrying the others
-
Where one weak dimension is creating drag
This helps teams avoid surface fixes. Instead of saying, “Our score is low, so we need more process,” the team can ask, “Where is the system actually breaking?”
Common pattern types
The assessment usually reveals one of a few common patterns.
These patterns are not labels for the team. They are ways to understand where improvement should start.
Balanced and strong
A balanced and strong pattern means the team scores well across all five dimensions. Design knowledge is organized. Complexity is handled. Proof is built. Decisions are guided by signals. Evidence travels beyond the immediate team.
This usually means the team has a repeatable design impact system.
What this suggests:
-
Keep the system consistent
-
Share the model with other teams
-
Look for places to scale what works
-
Use the assessment as a benchmark over time
The risk is complacency. Strong systems still need maintenance as teams, tools, products, and leadership priorities change.
Balanced but low
A balanced but low pattern means no single dimension is carrying the system.
The team may be working hard, but the design impact system is underdeveloped across the board. Work may rely heavily on individual effort, informal conversations, and inconsistent practices.
This usually means the team needs a stronger foundation.
What this suggests:
-
Start with one clear operating habit
-
Fefine how work begins
-
Capture signals in a simple, repeatable way
-
Connect findings to decisions
-
Avoid trying to improve every dimension at once
The risk is spreading effort too thin. Pick one area where improvement will create visible movement.
Strong start, weak finish
A strong start, weak finish pattern means early work is clear, but impact fades later. The team may define needs, goals, and learning well, but struggles to turn that work into proof, decisions, or influence.
This can show up as strong Organizing Work or Managing Complexity with weaker Building Proof, Guiding Decisions, or Scaling Influence.
What this suggests:
-
Connect early goals to measurable outcomes
-
Define what proof should look like before work begins
-
Turn findings into explicit decisions
-
Package results so leaders can use them
The risk is that good work keeps happening without creating enough visible impact.
Weak start, strong finish
A weak start, strong finish pattern means the team can create outcomes, but the early reasoning is unclear.
The team may make decisions, ship work, or show results, but the trail behind the work is hard to follow. This can happen when strong individuals push work forward without enough shared structure. This can show up as weaker Organizing Work or Managing Complexity with stronger Building Proof, Guiding Decisions, or Scaling Influence.
What this suggests:
-
Clarify the objective before work begins
-
Document hunches and assumptions
-
Make dependencies visible sooner
-
Capture why decisions were made
-
Connect outcomes back to the original intent
The risk is that success becomes hard to repeat because the system depends too much on people remembering how it happened.
Strong proof, weak influence
A strong proof, weak influence pattern means the team has evidence, but it does not travel far enough.
The team may run useful tests, collect strong signals, and connect work to outcomes. But leadership, adjacent teams, or strategic forums may not use that proof to guide larger decisions. This often shows up as stronger Building Proof with weaker Scaling Influence.
What this suggests:
-
Translate proof into leadership language
-
Create reusable proof stories
-
Connect results to business goals
-
Share signals earlier in planning conversations
-
Build a simple format for design impact
The risk is that design stays respected locally but does not shape broader priorities.
Strong decisions, weak proof
A strong decisions, weak proof pattern means the team moves, but the evidence behind the movement is not strong enough. The team may make choices quickly, align well in reviews, and avoid endless debate. But decisions may rely too much on intuition, stakeholder confidence, or thin evidence.
This often shows up as stronger Guiding Decisions with weaker Building Proof.
What this suggests:
-
Define what proof is needed before deciding
-
Connect decisions to UX metrics
-
Capture baselines or comparisons
-
Show what changed for users
-
Make the evidence behind decisions easier to see
The risk is that fast decisions become hard to defend later.
Strong organization, weak complexity
A strong organization, weak complexity pattern means the team captures knowledge well, but larger work still gets tangled.
The team may document goals, signals, findings, and decisions clearly. But as projects grow across systems, teams, and dependencies, the work slows down.
This often shows up as stronger Organizing Work with weaker Managing Complexity.
What this suggests:
-
Name the type of complexity earlier
-
Separate simple, complicated, and complex work
-
Clarify dependencies before they block progress
-
Define ownership across teams
-
Decide what needs process and what needs learning
The risk is that documentation improves, but the work still feels heavy.
High activity, low impact
A high activity, low impact pattern means the team is producing a lot, but the work is not clearly changing outcomes. There may be many projects, tests, meetings, artifacts, and reviews. But the connection between activity and impact is weak.
This can show up when several dimensions are mid-range, but Building Proof or Scaling Influence stays low.
What this suggests:
-
Reduce the number of things being tracked
-
Focus on fewer, clearer outcomes
-
Connect design work to user and business goals
-
Turn results into decision-ready proof
-
Stop measuring activity as a proxy for impact
The risk is that the team looks busy while momentum quietly fades.
Local strength, limited scale
A local strength, limited scale pattern means one team or group is working well, but the maturity does not spread. The organization may have strong design practices in one product area, team, or leadership group. But other teams do not share the same methods, language, or evidence.
This often shows up as uneven scores across dimensions or inconsistent survey responses.
What this suggests:
-
Identify where the strongest behavior already exists
-
Turn that behavior into a reusable practice
-
Create shared formats for evidence and decisions
-
Help experts connect patterns across teams
-
Bring leaders into the proof earlier
The risk is that design maturity stays dependent on isolated champions.
How to read your pattern
Start with the full score set.
Look across all five dimensions:
Then ask:
-
Which score is strongest?
-
Which score is weakest?
-
Which gap is largest?
-
Which dimension creates the most drag?
-
Which strength can support the next improvement?
-
Is the issue early, middle, or late in the system?
-
What would create the most visible movement in the next 30 days?
Do not look only for the lowest number. Look for the break that affects the whole system.
How patterns guide action
Patterns help teams choose where to focus. A weak dimension may need attention, but the best first move is usually the one that unlocks movement across several dimensions.
For example:
-
If proof is strong but influence is weak, focus on Scaling Influence.
-
If decisions are slow because evidence is unclear, focus on Building Proof.
-
If work gets tangled before decisions happen, focus on Managing Complexity.
-
If learning keeps disappearing, focus on Organizing Work.
-
If evidence exists but choices keep circling, focus on Guiding Decisions.
The goal is not to improve every score at once, but to make the next improvement obvious.
What this does not mean
A pattern is not a permanent label.
It is a current read on how design impact is moving through the organization. Patterns can change as teams improve how they capture evidence, guide decisions, build proof, manage complexity, and scale influence.
Do not use patterns to blame teams. Use them to understand where the system needs support.
Next step
Once you understand the pattern, move to Using Results.
Reading Patterns helps you see what is happening. Using Results helps you decide what to do next.
