M
Implementation Architecture™
Guidance Series · 2026
Evidence · Adaptation · Learning
Measurement& Learning
Designing the evidence loops that help strategy improve while it moves — not merely report what happened after the work is over.
Hall Strategic PartnersStrategy that powers impact.
A starting point

Measurement is not the end of implementation. It is part of the architecture.

Measurement & LearningThe implementation problem
The problem
Organizations often measure what is easiest to count — not what is most useful to learn.

Dashboards fill. Reports circulate. Meetings review red, yellow, and green.

Yet implementation can still drift because the organization has not designed the connection between evidence and action.

A metric that never changes a decision is reporting. It is not yet a learning system.

Measurement becomes part of Implementation Architecture™ when leaders know what evidence matters, when it should be reviewed, what it means, and what happens when the signal changes.

The point is not to create more measures. The point is to create enough visibility to make better decisions while implementation is still underway.

That requires more than data collection. It requires a designed loop between evidence, interpretation, decision, adaptation, and action.

Measurement & LearningVocabulary
Implementation Architecture™ vocabulary

Learning Loop

noun · Implementation Architecture™

A recurring structure that turns evidence from implementation into interpretation, decision, adaptation, and renewed action.

Signal 01

Leading Indicator

An early measure that helps show whether implementation is moving in the intended direction before final outcomes are visible.

Signal 02

Lagging Indicator

A measure that confirms what ultimately happened, often after the opportunity for early correction has passed.

Signal 03

Decision Signal

Evidence explicitly tied to a choice: continue, adjust, stop, escalate, resource differently, or investigate further.

Signal 04

Adaptation Threshold

A predefined point at which evidence is strong enough to trigger review or a change in implementation.

Practice 05

Measurement Cadence

The recurring rhythm for collecting, reviewing, interpreting, and acting on evidence.

Practice 06

Learning Review

A structured conversation focused not only on performance, but on what the evidence suggests should change next.

ML
Measurement & LearningThe learning loop
The architecture
Evidence only creates value when it re-enters the work.

A functioning measurement system does not end with a dashboard. It carries evidence back into implementation through a recurring decision loop.

Outcome
→
Signal
→
Review
→
Interpret
→
Decide
→
Adapt
→
Act
The loop closes only when evidence changes what the organization does next.
Measurement & LearningSix conditions
Designed for use
Six conditions make measurement useful for implementation.

These conditions move measurement from a reporting function to an operating capability.

01

Measure what matters

Connect measures to the strategic outcome, implementation assumptions, and decisions leaders actually need to make.

02

Distinguish activity from progress

Separate inputs, activities, outputs, implementation signals, and outcomes so motion is not confused with movement.

03

Build evidence into the workflow

Collect evidence close enough to the work that teams can use it before problems become retrospective explanations.

04

Define decision thresholds

Agree on what evidence should trigger continuation, adjustment, escalation, deeper review, or stopping.

05

Create a learning cadence

Establish recurring forums where evidence is interpreted, not merely presented.

06

Close the loop

Document what changed because of the evidence and carry the learning into the next cycle of implementation.

Measurement & LearningSignal vs. noise
Not every metric deserves a meeting
The question is not, “What can we measure?” It is, “What do we need to know?”
TypeWhat it tells youTypical risk
ActivityWhether work happened: meetings held, people trained, outreach completed.Can create the appearance of progress without showing whether implementation is working.
OutputWhat the work produced: plans, referrals, services, deliverables, completed actions.May show volume without showing quality, use, or effect.
Implementation signalWhether the conditions required for execution are strengthening or weakening.Often overlooked because it sits between activity and final outcomes.
OutcomeWhether the intended change occurred for the organization, customer, community, or system.May arrive too late to guide mid-course correction if used alone.
Learning signalWhat the organization now understands that should influence the next decision.Gets lost when meetings focus only on status rather than interpretation.
A smaller set of decision-relevant measures is often more useful than a larger set of reportable measures.
Measurement & LearningDecision use
A practical rule
A good measure changes a decision.

Before adding a metric, ask what someone will do differently when it changes.

If the answer is “nothing,” the measure may belong in a report — but not in the operating system.

Some evidence exists to establish context, detect a trend, or deepen interpretation. But critical measures should have a clear reason for being visible.

Five questions

1. What question is this measure answering?

2. Who needs to see it?

3. When do they need to see it?

4. What change would be meaningful enough to discuss?

5. What decision could follow from that discussion?

HSP principle

Design the decision before you design the dashboard.

The purpose of visibility is not to display the work. It is to support the next move.

Measurement & LearningLearning cadence
Different questions require different rhythms
Learning should happen at the speed of the decision.

A single quarterly dashboard cannot serve every implementation need. Different layers of the work require different review rhythms.

Weekly / biweekly

Operational coordination

What is moving? What is blocked? Which handoffs or dependencies need attention now?

Monthly

Implementation review

Are the implementation signals moving in the intended direction? What requires adjustment?

Quarterly

Strategic learning

What patterns are emerging? Are assumptions still valid? Do priorities or resources need to change?

Annual / cycle end

Outcome learning

What changed? What held? What should be retained, redesigned, stopped, or carried forward?

Cadence is not calendar discipline. It is the timing architecture that keeps evidence close enough to action to matter.
Measurement & LearningQuick diagnostic
Conversation guide
Can your organization learn while the work is still moving?

Use these questions with one strategic priority at a time. Uncertainty is useful information.

Can we name the outcome this work is intended to change?

Do we distinguish activity, output, implementation signals, and outcomes?

Do we know which measures are leading indicators and which are lagging?

Is each critical measure tied to a decision or learning question?

Have we defined what level of change should trigger review or adaptation?

Is evidence reviewed often enough to influence implementation?

Do the right people participate in interpreting the evidence?

Can we point to decisions that changed because of what we learned?

Diagnostic signal

If the organization can collect data but cannot explain how that data changes the work, the learning loop is incomplete.

HSP perspective
Evidence without ownership is reporting.
Ownership without evidence is guessing.

Measurement & Learning is one element of Implementation Architecture™. Evidence only becomes useful when ownership, decision rights, cadence, resources, and coordination allow the organization to respond to what the evidence reveals.

The objective is not a perfect measurement system. It is an organization that can see, learn, decide, and adapt before momentum is lost.
Measurement & LearningWorking principles
Keep the system useful
What a stronger measurement architecture should make possible.
01

See earlier

Detect implementation risk before it becomes an outcome failure.

02

Interpret together

Bring the people who understand the work into the meaning-making process.

03

Decide faster

Use thresholds and decision rights to reduce avoidable delay.

04

Adapt deliberately

Change implementation because of evidence, not because of noise or anxiety.

05

Retain learning

Capture what the organization learned so the next cycle does not start from zero.

06

Make progress visible

Show leaders, teams, boards, partners, and communities what is changing and why.

The best measurement system is not the one with the most data. It is the one that improves the quality of implementation.
Measurement & LearningEvidence base
Sources to anchor the guidance
Measurement for improvement, learning, and adaptation is established across implementation disciplines.

Institute for Healthcare Improvement. Model for Improvement. The framework emphasizes using measures to determine whether a change is an improvement and testing change through iterative cycles.

Agency for Healthcare Research and Quality. Learning Health System resources. AHRQ describes learning systems as environments where data and experience are converted into knowledge and knowledge is applied back into practice.

Centers for Disease Control and Prevention. Program evaluation guidance. CDC evaluation practice emphasizes useful, credible evidence and applying findings to decision-making and program improvement.

Project Management Institute. Benefits realization guidance connects performance information, ownership, and ongoing review to the realization and sustainment of intended benefits.

Publication note

This guidance is diagnostic, not a substitute for measurement-system design.

HSP's deeper work can include measure architecture, implementation indicators, learning cadence, executive reporting, adaptation thresholds, and facilitated evidence reviews.

L
Implementation Architecture™ Guidance Series
Closing thought
What you measure should help you learn.
What you learn should change what you do.

That is the difference between performance reporting and a living implementation architecture.

Hall Strategic PartnersStrategy that powers impact.