# Organizing Work Turn clarity into shared systems that last. Many teams can show results. Fewer can keep that proof alive once the project ends. Organizing Work measures how effectively your team captures, connects, and reuses what it learns, how knowledge turns into a living system of evidence that compounds over time. When this score is strong, design knowledge flows naturally. Objectives, decisions, learning, and outcomes stay visible, forming a shared foundation for future work. When it’s lower, proof fades into archives or slides, and every new project starts from scratch. The strongest design teams don’t just deliver outcomes,  they build memory. ### **Where this fits** Organizing Work is one of five dimensions in the Design Assessment. Each dimension shows a different place where design impact can strengthen or break down: 1. [Organizing Work](https://glare.helio.app/document-overview/design-assessment/results-guide/organizing-work): how well design knowledge is captured, connected, and reused. 2. [Managing Complexity:](https://glare.helio.app/document-overview/design-assessment/results-guide/managing-complexity) how well teams handle work as systems, teams, dependencies, and uncertainty grow. 3. [Building Proof:](https://glare.helio.app/document-overview/design-assessment/results-guide/building-proof) how well design work connects to user outcomes and business results. 4. [Guiding Decisions:](https://glare.helio.app/document-overview/design-assessment/results-guide/guiding-decisions) how well signals turn into clear choices. 5. [Scaling Influence:](https://glare.helio.app/document-overview/design-assessment/results-guide/scaling-influence) how well design proof travels beyond the immediate team. Use this Results page to understand your Organizing Work score, review the layer pattern, and choose what to improve next. ### **Why Organizing Work Matters** Design maturity depends on what an organization remembers. When documentation is consistent and accessible: - Teams stop re-solving old problems. - Leaders see a clear record of progress and proof. - Each new initiative begins with more clarity than the last. Organized knowledge keeps momentum alive. It makes clarity tangible,  something everyone can see, trust, and build on. **In short:** organizing proof turns isolated wins into a shared foundation for clarity, trust, and continuous improvement. ## **How to Use This Page** This page helps your team interpret your Organizing Work results and apply them to daily practice. You can move through it section by section, or jump directly to what you need most. Use this page to: 1. **Overview & Score**: See how your score reflects how well your team captures, connects, and reuses design knowledge. 2. **How It’s Measured**: Understand how the four-layer model (Objectives → Drivers → Learning → Outputs) captures knowledge flow. 3. **Rubric Breakdown**: Compare your layer scores to examples of maturity and see where visibility or linkage breaks down. 4. **Strengths and Gaps**: Spot where documentation flows smoothly and where clarity fades between layers. 5. **Next Actions**: Turn insights into steps that build lasting, reusable systems of proof. The goal isn’t perfect documentation,  it’s connected documentation. When proof is easy to find and reuse, design maturity grows faster than it forgets. **💡 First Step:** Review your results together. Highlight where documentation already builds clarity,  and where knowledge disappears. Those gaps mark your best opportunities to strengthen visibility. * * * ## **1\. OVERVIEW & SCORE** ### **Understanding Your Organizing Work Score** Your **Organizing Work** score reflects how effectively your team captures, connects, and reuses design knowledge. It measures how well clarity flows across your documentation system, from setting objectives to recording outcomes. High scores mean your team has consistent, visible systems that link goals, learning, rationale, and results. Low scores suggest knowledge fades between projects, leaving teams to rebuild context or repeat research. This score shows how well your organization: - Documents goals and decisions before work begins. - Engages in continuous learning by collecting, questioning, benchmarking, and mapping insights - Links those findings to outputs that demonstrate measurable results. When these elements stay connected, design proof compounds. Each project starts with a stronger foundation of clarity and evidence. ### **Score Interpretation**

Score Range

Label

What It Means

90–100

Systemic Learning

Documentation and learning are connected and reusable. Knowledge flows across projects and teams.

70–89

Consistent Documentation

Processes are in place, but the connection between goals, reasoning, and learning is uneven.

60–69

Developing Practices

Documentation exists, but learning is inconsistent and outcomes are disconnected.

Below 60

Isolated Knowledge

Work is recorded, but little active learning takes place. Findings are not connected to outcomes.

Most teams score between 75 and 85, strong at documenting outputs but still maturing in how they connect results back to objectives and business value. ### **Example: How a Team’s Score Reveals Strength and Gaps** A team scoring **84** demonstrates strong clarity in recording objectives and processes, but weaker consistency in capturing and codifying results. - **Objectives (93):** Goals are clearly defined and visible. - **Drivers (85):** Design decisions are documented, but not always tied to results. - **Learning (83):** Teams collect and question insights, but activities are inconsistent or unstructured. - **Outputs (83):** Findings from learning are recorded, but not always linked to the original goals. This pattern shows a team that records effectively but struggles to turn documentation into an active knowledge system. [Image] **💡 Focus:** Strengthen how documentation transitions from process archives to reusable evidence. When documentation connects intent to outcomes, design proof compounds rather than resets each project. ### **Understanding the Model** The **Organizing Work** model measures how documentation flows across four connected layers of knowledge: 1. **Objectives** define what success looks like. 2. **Drivers** explain why design choices were made. 3. **Learning** captures how teams collect, question, and map understanding during projects. 4. **Outputs** record the findings and results that come from that learning. When these layers work together, documentation becomes a living system of proof. Clarity flows from intent to outcome, while trust flows back from results to strategy. When one layer weakens, knowledge gets lost in handoffs. Objectives lose traceability, decisions lose context, and proof fades into archives. Strong documentation doesn’t slow work. It accelerates it by making what was learned easier to find, understand, and apply. ### **How It Works**

Layer

Primary Function

What It Does

When It Works

Objectives

Capture intent

Define goals, metrics, and hypotheses that guide design direction.

Everyone can see what success means before work begins.

Drivers

Record rationale

Document the factors and decisions that shape design choices.

Design reasoning stays transparent and traceable.

Learning

Codify insights

Turn discoveries, user feedback, and test results into reusable knowledge.

Teams can learn from past work instead of starting from scratch.

Outputs

Archive proof

Capture final artifacts, visuals, and evidence that demonstrate results.

Outcomes are visible, measurable, and easy to reference.

When all four layers connect, documentation compounds. Clarity flows downward from objectives to outputs, while trust flows upward from results back to strategy, creating a continuous learning loop across projects. * * * ## **2\. HOW IT’S MEASURED** ### **See how your team’s documentation connects** Your Organizing Work score is built from four connected layers that show how knowledge flows through your process. Each layer reveals a different aspect of how clarity is created, recorded, and shared across projects. [Image] When all four layers are balanced, documentation supports learning and continuity. Teams move faster because they build on existing proof. When one layer lags, knowledge gets trapped in slides or archives, and valuable lessons fade before they are recorded in outputs. ### **How to Read Your Four-Layer Scores**

Layer

What It Represents

Knowledge Strength

Objectives

Defines success and aligns goals before execution.

Sets direction and creates measurable clarity.

Objectives

Explains why specific design choices were made.

Builds reasoning and connects intent to action.

Objectives

The act of collecting, questioning, benchmarking, and mapping discoveries during work.

Builds shared understanding and reveals where to focus next.

Objectives

Captures findings and results from the learning process.

Records measurable outcomes and connects them back to objectives.

When your layer scores are within 5 to 10 points of each other, knowledge flows smoothly from start to finish. A gap of 15 to 20 points suggests friction, often where documentation stops at intent or where learnings are not connected to results. ### **Start with the Shape, Not the Score** Your total score is important, but the *shape* of your four layers tells a more useful story. It shows how your documentation structure supports momentum and memory.

Pattern

What It Means

Focus Area

Balanced Flow (even layers)

Documentation and learning move consistently from goal to result.

Maintain visibility and consistent documentation habits.

Strong Start, Weak Finish (high Objectives, low Outputs)

Teams define goals but do not record what was learned or achieved.

Strengthen post-project reviews and link outcomes back to objectives.

Weak Middle (Drivers or Learnings low)

Decisions and learning are not connected, creating gaps in understanding.

Capture decisions and discoveries as you go, not after delivery.

Strong Finish, Weak Start (high Outputs, low Objectives)

Results are recorded, but their purpose is unclear.

Clarify goals and success measures before execution begins.

Healthy systems build understanding as they go. Teams that make time to question, compare, and map discoveries create stronger results and more reusable knowledge. ### **Score Patterns to Watch** - **Balanced (within 10 points) **Documentation is connected and visible. Insights and outcomes are traceable across projects. - **Wide Spread (15–20+ points) **Gaps between Drivers or Learning indicate that reasoning and discovery are not being transferred to documentation. - **Top-Heavy (Objectives or Drivers higher) **Planning is strong, but learning activities are weak. Focus on collecting and mapping insights throughout the project. - **Bottom-Heavy (Outputs higher) **Teams deliver but skip key learning steps. Strengthen feedback loops and create space to question and benchmark during the process. **💡 Healthy Flow** means that learning feeds outputs, and outputs feed future objectives. * * * ## **3\. RUBRIC BREAKDOWN** ### **See how documentation maturity takes shape across your four layers** Design maturity becomes sustainable when teams can find, understand, and reuse what has already been learned. Each layer in the Organizing Work model represents a specific type of clarity that supports continuity. Together, these layers show how design proof moves from project intent to reusable knowledge. When these layers stay connected, documentation becomes a system of progress and understanding. When one weakens, clarity fades,  learning happens, but the insights never make it into the shared record. ### **How Design Maturity Takes Shape** The *Organizing Work* model tracks how teams move from planning to reasoning to active learning and, finally, to recording outcomes. Strong systems connect all four stages so learning informs results and results inform the next set of objectives. Weak systems break that loop. Teams end up discovering the same things repeatedly instead of building on past insight. [Image] Use this section to understand how maturity grows as teams shift from collecting information to managing clarity as a shared asset. ### **Example Layer Scores**

Layer

Score

Interpretation

Objectives

93

Goals are clearly defined and measurable before work begins.

Drivers

85

Reasoning is recorded but not consistently connected to what is learned during the project.

Learning

83

Teams explore, collect, and compare insights, but activities are inconsistent or unstructured.

Outputs

83

Findings from learning are recorded, but often lack links back to objectives or reasoning.

This pattern shows a team that plans and delivers well but lacks rhythm in how learning is practiced and captured. Learning happens, but without structure it does not translate into reusable proof. **💡  Focus:** Build consistency in learning activities. Create simple habits for collecting, mapping, and questioning throughout projects, and record validated findings in outputs. ### **Summary of the Four Layers**

Layer

What It Represents

When It’s Strong

When It’s Weak

How to Strengthen

Objectives

Defines purpose and success before execution.

Teams have clear direction and shared outcomes.

Projects start without clarity or alignment.

Create a short checklist to define goals before design begins.

Drivers

Records the reasoning behind design choices.

Decisions are traceable and supported by research.

Choices are made without visible rationale.

Capture short summaries of why each choice was made.

Learning

The act of collecting, questioning, benchmarking, and mapping discoveries during work.

Teams explore with structure and curiosity, building confidence through discovery.

Learning is inconsistent or informal, creating gaps in understanding.

Integrate lightweight methods like mapping or benchmarking into active design cycles.

Outputs

Captures findings and results from learning.

Results are documented and linked to goals and reasoning.

Findings exist but are disconnected or incomplete.

Record outcomes from learning sessions and connect them back to the original objectives.

When each layer strengthens the next, documentation becomes more than storage, it becomes a feedback system that fuels smarter, faster work. ### **How to Read the Layers** Each layer describes how design teams build and preserve clarity. As maturity increases, documentation shifts from static records to living systems that guide future work. **Objectives → Where clarity begins **Teams define goals and success measures before design starts. - When strong: Projects stay aligned and results are measurable. - When weak: Teams move fast but lose focus on outcomes. **Focus:** Define objectives together and record them where everyone can find them. **Drivers → Where intent is documented **Teams record the reasoning behind choices. - When strong: Decisions can be revisited and explained later. - When weak: Work looks logical but lacks visible context. **Focus:** Document the “why” behind major design moves as they happen. ** Learnings → Where insight becomes memory **Teams actively collect, question, benchmark, and map discoveries as they work. - When strong: Teams gain clarity fast and discover insights that guide better outcomes. - When weak: Learning happens informally and results get lost. **Focus:** Make learning visible. Use tools or short reviews to compare, question, and map insights as they emerge. **Outputs → Where proof is preserved **Teams store the final work and connect it to objectives. - When strong: Anyone can trace results back to goals. - When weak: Work is archived without clear outcomes. **Focus:** Link outputs to the problem they solved and record measurable results. When learning and outputs stay connected, documentation evolves into collective intelligence. It turns every project into both a result and a resource. * * * ## **4\. STRENGTHS AND GAPS** ### **See where clarity holds and where knowledge fades** Your Organizing Work results reveal how effectively your team turns work into memory.  Some layers already capture clear goals, rationale, and outcomes. Others may hold valuable information that never becomes reusable knowledge. - **Strengths** show where your process supports visibility and alignment. - **Gaps** show where documentation stops short, where decisions or discoveries are made but not stored, linked, or shared. The goal is not to produce more documentation. It is to connect what already exists, so your work tells a continuous story. ### **Example: Strengths and Gaps** For a team scoring 84 overall, strong planning and reasoning at the start of projects are clear strengths. Gaps appear in how active learning connects to outputs, leaving findings scattered or undocumented.

Layer

Strengths

Gaps

Opportunity

Objectives

Goals are clear, measurable, and visible across the team.

Objectives are not always tied to the findings produced later.

Strengthen by linking each goal to specific learning outcomes and results.

Drivers

Decisions are thoughtful and supported by research.

Reasoning is not revisited during or after the learning process.

Capture short reflections on whether original reasoning held true as learning progressed.

Learning

Teams explore through questioning, benchmarking, and mapping.

Learning happens inconsistently or findings are not recorded.

Build short, structured learning reviews during each project phase.

Outputs

Findings and results are captured in some form.

Documentation lacks connection to goals and reasoning.

Link findings back to objectives and make them searchable for future reference.

Your team plans well and delivers clear outcomes, but valuable reasoning and insights fade once work is complete. Strengthening how information flows through the middle layers turns temporary clarity into long-term organizational memory. ### **Team Reflection** Use this section to guide a conversation about how your team creates and captures understanding. Discuss where learning happens naturally and where it tends to fade. 1. Where do we already explore, question, and benchmark effectively? 2. How often do our discoveries make it into shared documentation? 3. What learning behaviors create the most clarity for the team? 4. What small change could help us connect learning to outputs more consistently? **Tip:** The fastest way to build organizational memory is not to write more.  It is to *close the loop*, make learning visible as it happens, and record its results where everyone can find them. * * * ## **5\. NEXT ACTIONS** ### **Turn active learning into lasting clarity** Your Organizing Work results show how your team creates, connects, and keeps clarity. When goals, reasoning, and learning work together, outputs become more than records, they become living proof of how your organization grows. When learning happens but isn’t captured, momentum slows and teams lose visibility into how progress was made. ### **Implications and Recommendations** If your team scores high in Objectives and Outputs but lower in Drivers or Learnings, you likely plan and deliver well but lose visibility mid-process. Intent and results are solid, but reasoning and discoveries are not consistently recorded.  The learning is there,  it just isn’t structured or preserved. [Image] Focus on connecting active learning to shared outputs: - Build short, recurring learning checkpoints to reflect and question as work progresses. - Encourage teams to benchmark new insights against previous results. - Map what was learned during each phase and record final findings in outputs. - Create templates or cards that capture questions, patterns, and comparisons quickly. - Share these learning snapshots before project closeout to strengthen visibility. Good organization means learning and documentation move together. Proof is not just stored: it’s built, questioned, and connected as work unfolds. ### **30-Day Focus** Start small. Focus on creating one connected flow of information that builds confidence and reduces rework. 1. **Choose one project to document completely.** Capture goals, decisions, learnings, and results in one shared space. 2. **Add summaries at key checkpoints.** Include a short note for every major choice and discovery. 3. **Build one shared index or folder.** Centralize proof so teams can find examples or references quickly. 4. **Reflect at the end of 30 days.** Ask whether projects feel easier to start or hand off. Adjust the format before scaling. **Goal:** Create a single source of truth that saves time by making decisions, reasoning, and outcomes visible at a glance. * * * ## **Next Step: Managing Complexity** Once your team can capture and connect proof reliably, the next challenge is working through complexity. The Managing Complexity dimension examines how teams adapt structure and communication as systems grow. Where Organizing Work builds consistency, Managing Complexity builds adaptability—helping teams stay clear when conditions change. **Explore Next: \[**[**Managing Complexity →**](https://glare.helio.app/document-overview/design-assessment/results-guide/managing-complexity)**\]** See how to lead through growth with structure that keeps decisions clear and confidence steady as projects scale.