Design work gets weaker when teams lose the memory of the work.
Organizing Work looks at how well your team captures, shares, and reuses what it learns. Strong design teams do not restart from scratch every time. They build on what came before. This dimension shows whether design knowledge compounds across projects or disappears between meetings, files, and teams.
Why Organizing Work Matters
Most teams create plenty of work. They have research notes, design files, test results, meeting takeaways, stakeholder feedback, and launch learnings. The problem is not that evidence does not exist. The problem is that evidence often gets scattered.
When that happens:
-
Teams repeat the same debates
-
Decisions lose context
-
New work starts without past learning
-
Findings stay trapped in old decks
-
Strong signals do not shape future direction
-
Leaders cannot see how design thinking has developed
The work may be good, but the learning does not carry forward. Organizing Work helps teams make design evidence easier to find, explain, and reuse. It turns scattered learning into a shared system.
What this dimension shows
Organizing Work shows how well your team keeps design learning connected as work moves forward.
It looks at whether your team can clearly answer:
-
What were we trying to achieve?
-
What did we believe going in?
-
What did we learn?
-
What changed because of that learning?
-
Where can this evidence be reused?
-
How does this work help the next decision?
When this dimension is strong, design work becomes easier to trust because the reasoning is visible. When it is weak, teams rely on memory, meetings, and scattered artifacts to explain why decisions were made.
Where momentum breaks
Momentum breaks when the team cannot easily trace the work.
A project may start with a clear goal, but the reasoning gets lost as more people get involved. A test may produce strong findings, but no one knows where to find them three months later. A design decision may be smart, but the next team cannot see what evidence supported it.
This creates drag. Teams spend more time explaining the past than improving the future. You see it when:
-
Research findings are hard to find later
-
Teams rerun similar studies without knowing it
-
Design decisions are explained differently by different people
-
Stakeholders ask the same questions again
-
New team members lack context
-
Evidence does not connect across projects
-
Past learning does not influence new work
The issue is not effort. It is the lack of a clear memory system for design.
<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><td colspan="1" rowspan="1"><h3><strong>What strong looks like</strong></h3><p>Strong Organizing Work makes design learning easier to carry forward.</p><p>The team captures the purpose of the work, the reasoning behind decisions, the signals collected, and the outputs others can use. Evidence does not sit in one person’s head or one project folder. It becomes part of how the organization learns.</p><p>Strong teams:</p><ul><li><p>Define the goal before the work begins</p></li><li><p>Document the hunches and assumptions behind the work</p></li><li><p>Capture signals as the work progresses</p></li><li><p>Connect findings to decisions</p></li><li><p>Turn learning into simple, reusable outputs</p></li><li><p>Make evidence easy for other teams to understand</p></li><li><p>Build a stronger foundation for future work</p></li></ul><p>This does not mean creating a heavy documentation process.</p><p>It means making the important parts of the work easier to see.</p></td><td colspan="1" rowspan="1"><h3><strong>What weak looks like</strong></h3><p>Weak Organizing Work creates repeated friction.</p><p>The team may be moving fast, but the learning does not stick. Each project feels separate. Decisions depend on whoever was in the room. Evidence exists, but it is not easy to use.</p><p>Weak teams often:</p><ul><li><p>Start projects without clear goals</p></li><li><p>Lose track of why decisions were made</p></li><li><p>Capture findings without turning them into action</p></li><li><p>Store research in places others do not use</p></li><li><p>Create decks that are read once and forgotten</p></li><li><p>Struggle to connect past learning to new work</p></li><li><p>Depend on individual memory instead of shared evidence</p></li></ul><p>This makes design feel less mature, even when the work itself is strong.</p></td></tr></tbody></table>
How Organizing Work is evaluated
Organizing Work is evaluated through the Decision Map.
The Decision Map gives the team a shared way to track how design knowledge moves through the work. It looks across the Glare blocks and shows whether the team is connecting the right inputs, decisions, evidence, and results.
For Organizing Work, the assessment focuses on four layers:
-
Objectives
-
Drivers
-
Learning
-
Outputs
These layers show how well the team is using the Decision Map to carry design knowledge from the start of the work into something others can understand, trust, and reuse.
[Image]
The four layers of Organizing Work
Organizing Work is not just about storing files or documenting research. It is about how well the team uses the blocks in the Decision Map to keep the work connected.
A strong team can show:
-
What the work was trying to achieve
-
What needs, constraints, and goals shaped it
-
What hunches or methods drove the direction
-
What questions and comparisons created learning
-
What findings, decisions, and results came from the work
-
How that evidence can be reused later
When these blocks are connected, design knowledge compounds.
When they are scattered, teams lose the thread. Decisions become harder to explain. Findings get buried. The next project starts without the benefit of what the team already learned.
Objectives
Objectives show how well the team uses the Decision Map to define what the work is trying to achieve.
This includes blocks like user needs, concepts, initiatives, and business goals. Together, they help the team explain why the work exists and what success should look like.
When objectives are strong, the team can clearly show the connection between the user problem, the design direction, and the business goal. When objectives are weak, work starts broadly. Teams may create ideas, tests, or deliverables without a clear way to explain what the work is meant to change.
Drivers
Drivers show how well the team captures what is pushing the work forward.
This includes blocks like audience, hunches, methods, and workflows. These blocks explain who the work is for, what the team believes, how they plan to learn, and how the work fits into the way the team operates.
When drivers are strong, the team can explain why it chose a direction, method, or audience. When drivers are weak, decisions feel disconnected. The team may know what it did, but not why that path made sense.
Learning
Learning shows how well the team captures what it discovers as the work moves.
This includes blocks like collecting, questioning, comparing, and mapping. These blocks help the team gather signals, ask sharper questions, compare options, and connect evidence across the system.
When learning is strong, the team can see how evidence changed the work. When learning is weak, signals stay scattered across notes, tests, conversations, and dashboards. The team has information, but the learning does not become easy to use.
Outputs
Outputs show how well the team turns learning into something others can act on.
This includes blocks like UX metrics, findings, decisions, and results. These blocks help the team show what was measured, what was learned, what choice was made, and what changed because of it.
When outputs are strong, evidence becomes clear, reusable, and leadership-ready. When outputs are weak, learning stays local. The team may have done valuable work, but it does not travel far enough to shape future decisions.
How to strengthen Organizing Work
Start by making the reasoning easier to follow. You do not need a massive repository or a new operating model. Use the Decision Map to trace one project from the first objective to the final output.
The goal is to create a clearer trail:
Objective → Driver → Learning → Output
That trail should show what the team was trying to achieve, what shaped the direction, what signals changed the work, and what others can reuse later.
Useful moves:
-
Define the goal before the work starts
-
Connect the user need to the business goal
-
Write down the hunches behind the direction
-
Clarify the audience, method, and workflow
-
Capture the signals that shaped the work
-
Summarize findings in plain language
-
Connect each finding to a decision
-
Create one reusable artifact others can reference
-
Store evidence where the next team can find it
The goal is not documentation for its own sake, but rather make design learning easier to understand, trust, and reuse.
Questions to ask
Use these questions to evaluate how well your team organizes design work:
-
Can someone quickly understand why this work started?
-
Are the user need and business goal clear?
-
Did we capture the hunches and assumptions behind the work?
-
Can we see what signals changed our thinking?
-
Are findings connected to decisions?
-
Is there a clear output others can reuse?
-
Can another team apply what we learned?
-
Will this work still make sense three months from now?
What improves when this is strong
When Organizing Work is strong, design becomes easier to scale.
Teams spend less time reconstructing context. Leaders see how decisions formed. New work builds on past learning. Research and design evidence become more valuable because it does not disappear after one project.
Strong Organizing Work helps teams:
-
Reduce repeated debates
-
Onboard people faster
-
Reuse evidence across projects
-
Make decisions easier to explain
-
Build stronger proof over time
-
Create a shared language for design impact
This is where design maturity starts to compound.
How this connects to results
Organizing Work is one dimension in the Design Assessment. This page explains what the dimension means and what strong or weak behavior looks like. The Results Guide explains how to interpret your score after you complete the assessment survey.
Use the Organizing Work Results page to review:
-
Your overall dimension score
-
Your layer scores across Objectives, Drivers, Learning, and Outputs
-
Where the pattern is strong or uneven
-
What strengths and gaps show up in the results
-
What action to take next
The goal is to move from understanding the dimension to improving it in real work.
Go deeper:
Related dimensions
Organizing Work supports the other four dimensions in the Design Assessment. When design knowledge is easier to trace, teams can:
-
Manage complexity with more context
-
Build proof from stronger evidence
-
Guide decisions with less debate
-
Scale influence because the story is easier to share
Use the other dimension pages to see where design impact may be breaking beyond how the work is organized
Next step
Review one recent project and trace it through the Decision Map:
Objective → Driver → Learning → Output
Look for the weakest link. Can someone see why the work started, what shaped the direction, what the team learned, and what changed because of it?
That is where Organizing Work should improve first. Then use the scoring section to evaluate the pattern more clearly and decide what to strengthen next.
