Whole System Alignment

Align local parts and incentives with the behavior of the whole system so local optimization does not undermine global viability.

Version

v1 · 2026-08-24 · History

Solution archetype #

1128

Problem family

Scale, Hierarchy & Emergence Mismatch

Problem subfamily

Hierarchical Delegation & Multilevel Coordination

Essence

Whole-System Alignment is the intervention pattern for cases where parts of a system are doing locally sensible things that add up to a globally poor result. It does not merely ask people to “think systemically.” It changes the structure around local action: what actors see, what they are rewarded for, what feedback they receive, how tradeoffs are escalated, and which outcomes count as success.

The core question is: what must change so that each part can remain locally competent while also preserving the viability of the whole?

Compression statement

When locally rational actions produce globally poor outcomes, map part-whole interactions and realign metrics, incentives, feedback, constraints, interfaces, or coordination rules with shared whole-system outcomes so local action supports system-level viability rather than suboptimization.

Canonical formula: whole_system_alignment = whole_system_map + part_whole_interaction_map + shared_outcome_metric + local_metric_crosswalk + incentive_alignment_rule + feedback_path_adjustment + coordination_protocol + tradeoff_resolution_rule

When This Archetype Applies

Partial catalog groundingSome structural conditions are represented by existing abstractions, but no sufficient condition set is fully represented.

Diagnostic problem

Parts of a system optimize locally, act independently, or follow fragmented metrics in ways that degrade emergent whole-system behavior, shift costs across boundaries, or make the larger system less viable even though each part may appear successful on its own terms.

What this problem means

The structural problem is **suboptimization**: parts optimize for local goals that are not equivalent to the health of the whole. This can happen even when no actor is malicious. A team rewarded for speed may create operational fragility. A department rewarded for throughput may create downstream rework. A supplier rewarded for unit cost may weaken resilience. A school rewarded for one score may narrow learning.

The underlying tension is that local decision-making is necessary, but local signals are incomplete. The whole is produced by interactions among parts, yet responsibility, measurement, incentives, and authority are often partitioned.

Applicability expression6 distinct conditions

Local improvement harms wholeandHidden system interdependenciesandFragmented responsibility, joint outcomesandCost transfer across partsandPart metrics dominate viabilityandWeak tradeoff coordination

Algebraic1∧2∧3∧4∧5∧6

groundedpartly groundedopen

6 conditions, all required.

6Required in every casenumbered 1–6

These hold no matter which pattern applies.

1

Local improvement harms whole · grounded

Local units, teams, agencies, modules, species, markets, or subsystems can improve their own metrics while worsening end-to-end outcomes. more

primeGoal Congruence (Alignment)— Alignment of objectives.

and — also required

2

Hidden system interdependencies · open

The system has interdependencies, feedback loops, shared resources, cumulative effects, or delayed consequences that local actors do not fully see. more

and — also required

3

Fragmented responsibility, joint outcomes · grounded

Responsibility is fragmented across parts, but outcomes are produced by the interaction among those parts. more

primeGoal Congruence (Alignment)— Alignment of objectives.

and — also required

4

Cost transfer across parts · open

A local optimization transfers cost, risk, maintenance burden, delay, or harm to another part of the system. more

and — also required

5

Part metrics dominate viability · grounded

Metrics, incentives, budgets, or accountability rules reward part-level performance more strongly than whole-system viability. more

primeGoal Congruence (Alignment)— Alignment of objectives.

and — also required

6

Weak tradeoff coordination · open

Cross-boundary coordination is necessary, but existing interfaces, governance, or review rituals are too weak to reconcile tradeoffs. more

Other requirements and context (2)

Why these sit outside the expression

Supporting context — it may accompany or help interpret the situation, but it is not a load-bearing condition in a sufficient diagnostic set.

• Supporting contextA proposed improvement in one area threatens system resilience, equity, safety, long-term sustainability, user experience, or lifecycle value. more

• Supporting contextThe system boundary is sufficiently defined that alignment can be attempted, but still broad enough to include the consequences that matter. more

Coverage

3 of 6 conditions grounded · 3 open.

Read the methodology · Download the trigger-logic data

When to Use This Archetype

Use this archetype when local optimization is visibly diverging from system-level health. The pattern is especially relevant when teams, modules, agencies, departments, suppliers, disciplines, or ecological actors each improve their own metrics while the end-to-end outcome worsens.

It is useful when the whole has real emergent properties: reliability, resilience, safety, ecosystem health, patient outcomes, learning, user experience, lifecycle value, or public trust. It is weak when the system boundary is still undefined, when a one-time impact map is enough, or when the only intended change is a conversation or diagram.

Structural Problem

The structural problem is suboptimization: parts optimize for local goals that are not equivalent to the health of the whole. This can happen even when no actor is malicious. A team rewarded for speed may create operational fragility. A department rewarded for throughput may create downstream rework. A supplier rewarded for unit cost may weaken resilience. A school rewarded for one score may narrow learning.

The underlying tension is that local decision-making is necessary, but local signals are incomplete. The whole is produced by interactions among parts, yet responsibility, measurement, incentives, and authority are often partitioned.

Intervention Logic

The intervention begins by naming the whole whose viability matters. Then it maps parts, dependencies, feedback paths, metrics, and local incentives. The draft then asks where local success creates system harm. Alignment is created by modifying the local environment of action: shared outcome metrics, local metric crosswalks, incentive rules, feedback paths, coordination protocols, and tradeoff resolution rules.

The goal is not total centralization. Good alignment preserves local autonomy inside guardrails and reserves system-level coordination for decisions that affect shared invariants.

Key Components

Whole-System Alignment intervenes when locally sensible action adds up to a globally poor result, and its components organize into two halves: representations that make the part-whole structure legible, and structural levers that change what local actors see, are rewarded for, and must coordinate on. The Whole-System Map names the relevant whole — its parts, boundaries, flows, dependencies, and emergent behaviors — so alignment is not based on one part's view. The Part-Whole Interaction Map narrows the picture to the causal channels through which local actions actually shape system-level outcomes, exposing where local wins become global losses. The Shared Outcome Metric names the system-level result that multiple parts must jointly preserve — reliability, patient outcome, ecological viability, equity, or lifecycle value — and the Local Metric Crosswalk ties existing local measures to that outcome so each part can see which of its current behaviors support or burden the whole.

Four further components turn that representation into ongoing structural change rather than a one-time diagram. The Incentive Alignment Rule adjusts rewards, budgets, approval criteria, or accountability paths so local actors are no longer rationally pushed to harm the whole — the metric crosswalk surfaces the conflict, but the incentive rule resolves it. Feedback Path Adjustment ensures that downstream, delayed, or cross-boundary consequences actually reach the actors who can change behavior, without which alignment decays into aspiration. The Coordination Protocol defines how parts share information, make joint decisions, and update plans, giving the alignment a repeatable operating structure rather than ad hoc meetings. Finally, the Tradeoff Resolution Rule specifies how conflicts among local efficiency, safety, equity, resilience, cost, and long-term viability are judged when they cannot all be satisfied at once — Whole-System Alignment exposes tradeoffs but does not magically remove them, and without an explicit resolution rule the surfaced tensions either freeze coordination or get decided by power rather than legitimacy.

Component	Description
Whole-System Map ↗	A whole-system map shows the relevant whole, its parts, boundaries, flows, dependencies, feedback paths, and emergent behaviors. It prevents alignment from being based on one part’s view of the system.
Part-Whole Interaction Map ↗	A part-whole interaction map focuses on the causal channels through which local actions shape system-level outcomes. It shows where local wins become global losses.
Shared Outcome Metric ↗	A shared outcome metric names the system-level result that multiple parts must jointly preserve. It might be reliability, patient outcome, ecological viability, safety, resilience, equity, or lifecycle value.
Local Metric Crosswalk ↗	A local metric crosswalk connects local measures to system outcomes. It helps each part see which local behaviors support the whole and which create hidden burden elsewhere.
Incentive Alignment Rule ↗	An incentive alignment rule adjusts rewards, penalties, budgets, approval criteria, or accountability paths so local actors are not rationally pushed to harm the whole.
Feedback Path Adjustment ↗	Feedback path adjustment ensures that downstream, delayed, or cross-boundary consequences reach the actors who can change behavior. Without feedback, alignment decays into aspiration.
Coordination Protocol ↗	A coordination protocol defines how parts share information, make joint decisions, resolve tensions, and update plans. It gives alignment a repeatable operating structure.
Tradeoff Resolution Rule ↗	A tradeoff resolution rule specifies how conflicts among local efficiency, safety, equity, resilience, cost, speed, and long-term viability should be judged. Whole-system alignment exposes tradeoffs; it does not magically remove them.

Common Mechanisms

8 documented mechanisms across 7 implementation forms.

The grouping reflects forms represented among the mechanisms currently documented for this archetype; an absent form is not necessarily an impossible implementation.

Assessment, Review & Assurance · 2 mechanisms

• System Health Review — Puts local scorecards next to whole-system outcomes on a cadence to catch local wins that quietly harm the whole.
• Systems Engineering Review — Checks at design gates that component and interface choices add up to the performance the whole system must deliver.

Communication, Facilitation & Learning · 1 mechanism

• Patient Care Team Conference — Convenes a patient's specialists to re-plan care around the whole-person outcome no single discipline owns.

Monitoring, Sensing & Alerting · 1 mechanism

• Balanced Scorecard — Tracks multiple performance dimensions to reduce single-metric tunnel vision in organizations.

Organization, Role & Governance · 1 mechanism

• Cross-Silo Governance Forum — Gives interdependent units a standing body with authority to adjudicate cross-boundary tradeoffs and rewrite shared rules.

Protocol, Workflow & Routine · 1 mechanism

• Integrated Planning Process — Reconciles separate budgets, schedules, and dependencies into one end-to-end plan owned across the parts.

Representation, Specification & Plan · 1 mechanism

• Ecological Management Plan — Aligns land uses and stakeholders around ecosystem viability across long horizons and cross-boundary effects.

Rule, Policy & Commitment · 1 mechanism

• Shared OKRs or Cross-Functional Goals — Binds interdependent teams to one common objective while each keeps ownership of how it hits its own key results.

Parameter / Tuning Dimensions

Important tuning dimensions include the scale of the whole, the time horizon, the number of outcome dimensions, the degree of local autonomy, the strength of shared incentives, feedback latency, escalation thresholds, governance cadence, metric granularity, and the acceptable cost of coordination.

A narrow whole is easier to govern but may exclude externalities. A broad whole is more realistic but harder to measure and coordinate. Stronger central governance may improve coherence but can suppress local knowledge. Looser governance preserves autonomy but may let suboptimization persist.

Invariants to Preserve

The archetype should preserve whole-system viability, legitimate local autonomy, transparent tradeoffs, timely feedback, plural outcome representation, stakeholder legitimacy, and proportional coordination cost. It should also preserve the boundary discipline that keeps “the whole” from being defined in a way that exports harm.

Target Outcomes

Successful Whole-System Alignment reduces suboptimization, connects local action to global consequences, improves end-to-end outcomes, clarifies tradeoffs, strengthens coordination, and makes shared system health visible. It helps parts stop winning locally by shifting burden elsewhere.

Tradeoffs

The main tradeoff is between local autonomy and system coherence. Alignment also trades speed for coordination, simplicity for plural metrics, and local accountability for shared responsibility. The pattern can improve viability, but it adds governance overhead and can be misused as a rationale for excessive central control.

Failure Modes

Common failure modes include aligning the wrong whole, reducing system health to one simplistic metric, centralizing too much, creating alignment theater, encouraging metric gaming, receiving feedback too late, overloading coordination forums, and allowing powerful actors to define “the whole” in self-serving ways.

The most important mitigation is to tie every alignment artifact to action: a decision rule, an owner, a cadence, a feedback path, or a tradeoff procedure.

Neighbor Distinctions

Whole-System Alignment is distinct from System Scope Definition, which defines the system boundary. It is distinct from Boundary Reframing, which redraws the boundary to reveal different causes or responsibilities. It is distinct from Whole-System Impact Mapping, which maps possible consequences before action. It is distinct from Feedback Loop Redirection, which changes a feedback loop itself. It is broader than Incentive Alignment, because incentives are only one lever among metrics, feedback, coordination, constraints, and governance.

It is also distinct from generic systems thinking. Systems thinking may motivate the intervention, but this archetype requires enacted structural changes.

Cross-Domain Examples

In software reliability, feature teams can be aligned around user-visible reliability so feature velocity does not degrade the platform. In healthcare, specialists can coordinate around whole-patient outcomes rather than departmental throughput. In supply chains, procurement, production, logistics, and service can align around lifecycle value and resilience instead of unit cost alone. In watershed management, municipalities, farms, industry, and conservation actors can align around water quality and flood resilience. In education, accountability can balance test performance with attendance, wellbeing, equity, and long-term learning.

Non-Examples

A dashboard that nobody uses for decisions is not Whole-System Alignment. A holistic workshop without changed incentives or feedback is not this archetype. A centralized mandate that suppresses local knowledge is not automatically alignment. A clean modular architecture is not this archetype unless local behavior is being realigned with whole-system outcomes. A one-time impact map is a neighbor method unless it leads to ongoing alignment controls.

Related Abstractions

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (3)

• Composition: Arranges components into a cohesive whole.
• Feedback: Outputs influence inputs.
• Holism: Whole exceeds sum of parts.

Also references 4 related abstractions

• Boundary: Defines system limits.
• Boundary Critique: Examines inclusion/exclusion assumptions.
• Constraint: Limits possibilities to guide outcomes.
• Representation: Model complex ideas.

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Metric and Incentive Alignment · governance variant · recognized

Realigns local performance measures and incentives with shared whole-system outcomes.

• Distinct from parent: The parent includes mapping, coordination, feedback, and governance; this variant emphasizes measurement and reward structure.
• Use when: Local units meet their own targets while damaging system-level outcomes; Fragmented metrics reward speed, cost reduction, throughput, or utilization in ways that shift harm elsewhere; The system needs a practical bridge from whole-system goals to local decision criteria.
• Typical domains: organizations, platform engineering, healthcare, public administration
• Common mechanisms: Balanced Scorecard, Shared OKRs or Cross-Functional Goals, System Health Dashboard

Cross-Silo Whole-System Coordination · governance variant · recognized

Aligns units separated by organizational, jurisdictional, disciplinary, or functional boundaries around shared system outcomes.

• Distinct from parent: The parent can apply to any part-whole relation; this variant specifically addresses siloed or cross-boundary coordination.
• Use when: Separate units optimize handoffs, budgets, priorities, or accountability in incompatible ways; No single unit owns the end-to-end outcome even though each unit affects it; Local autonomy is valuable but uncoordinated choices create fragmentation.
• Typical domains: enterprise governance, public services, healthcare, infrastructure delivery
• Common mechanisms: Cross-Silo Governance Forum, Integrated Planning Process, Patient Care Team Conference

Whole-Part Reintegration · subtype · collapsed into parent

Reconnects specialized or decomposed parts to whole-system purpose after fragmentation or siloing weakens coherence.

• Distinct from parent: This name emphasizes repair after fragmentation; the parent also covers initial alignment and ongoing alignment maintenance.
• Use when: Parts have lost sight of the whole after decomposition, specialization, outsourcing, or silo formation; Local units maintain their own operations but no longer understand their role in system viability.
• Typical domains: organizations, systems engineering, integrated care, whole-of-government work
• Common mechanisms: Cross-Silo Governance Forum, Integrated Planning Process

Near names: Holistic Alignment, Local-Global Alignment, Suboptimization Correction, Balanced Scorecard, Cross-Functional Goals, Systems Thinking.

Editorial Notes

Problem Classification

Classification: Scale, Hierarchy & Emergence Mismatch → Hierarchical Delegation & Multilevel Coordination

Problem kernel: locally successful parts degrade whole-system viability across levels

Rationale: Locally autonomous parts optimize fragmented metrics and appear successful while shifting costs, degrading emergent whole-system behavior, and weakening system viability because consequences and authority are partitioned across levels. Mission drift captures narrow objectives displacing purpose, and multiscale feedback captures signals behaving differently by level; the earliest organizing defect is failure to align local decision rights with higher-level coherence.

Boundary considered: Goal, Value & Purpose Misalignment → Optimization Target & Mission-Scope Drift

Why this classification prevailed: Hierarchical coordination governs alignment of local autonomy and whole-system consequences across levels; mission drift governs displacement of intended outcomes by proxies or expanding subobjectives.

Review outcome: Adjudicated after independent review; high confidence.