Top Down Bottom Up Synthesis¶
Combine centralized direction with local knowledge so strategy is coherent and implementation is grounded.
The Diagnostic Story¶
Symptom: Plans look coherent in central documents but repeatedly fail during rollout. Frontline actors maintain shadow practices because the official process does not fit actual work. Local feedback is collected but not traceably connected to decision changes. Local teams request exceptions while central leaders read those requests as resistance rather than as evidence.
Pivot: Gather local signals, make central intent explicit, compare the two systematically, reconcile conflicts through a named rule or forum, translate the result into bounded local action, and feed implementation results back upward so synthesis is iterative rather than a one-time negotiation.
Resolution: Strategies become more implementable because local constraints shape them before rollout. Local adaptation becomes legitimate, bounded, and learnable rather than a hidden workaround. Central leaders gain earlier warning about plan-reality mismatch, and the system learns across local contexts rather than repeating the same implementation failure at every site.
Reach for this when you hear…¶
[field operations director] “Headquarters wrote the new workflow without asking any of the teams who do it, and now every site has a workaround for the three steps that do not match how the work actually flows.”
[urban planner] “The master plan looks great from above, but the residents near the transit corridor have been telling us for two years that the pedestrian connection does not work the way we drew it.”
[software product manager] “Engineering built exactly what the spec said, but the sales team knew from day one that customers would not use it that way — we just never had a channel to bring that knowledge in before launch.”
When This Archetype Applies¶
Partial catalog groundingSome structural conditions are represented by existing abstractions, but no sufficient condition set is fully represented.
Diagnostic problem
Central direction lacks local validity, while local input lacks system-wide coordination, prioritization, or authority to change the larger plan.
What this problem means
The structural problem is cross-level incompleteness. A top-down perspective sees scale, coherence, priorities, standards, and shared risk, but it abstracts away local detail. A bottom-up perspective sees lived constraints, tacit knowledge, specific failures, and practical opportunity, but it can be fragmented, parochial, and hard to prioritize across the whole system.
Failure appears when one level dominates. Pure top-down action produces brittle plans that look good on paper and fail in practice. Pure bottom-up action produces many local optimizations that may not add up to a coherent system. The problem is not that one side is “wrong.” The problem is that each side is structurally partial.
Show the applicability expression
Applicability expression4 distinct conditions
groundedpartly groundedopen
4 conditions, all required.
4Required in every casenumbered 1–4
These hold no matter which pattern applies.
Plan-disconfirming local signals · grounded
Local teams, sites, communities, users, or frontline workers are producing signals that the central plan does not explain.
It is appropriate only when local evidence can change the plan or when central intent can legitimately bound local variation. The narrower requirement in this condition set is: Local teams, sites, communities, users, or frontline workers are producing signals that the central plan does not explain.
Informal adaptation drift · open
Local units are adapting informally, creating drift, workarounds, inconsistent quality, or hidden noncompliance.
It is also useful when local actors have already begun creating informal adaptations. The narrower requirement in this condition set is: Local units are adapting informally, creating drift, workarounds, inconsistent quality, or hidden noncompliance.
Late implementation learning · grounded
Implementation learning arrives too late, after the central commitment has become politically, financially, or technically hard to revise.
It is especially useful during strategy rollout, policy implementation, organizational change, platform governance, service redesign, and community-facing programs where central plans often fail because they do not match how work or life actually happens. The narrower requirement in this condition set is: Implementation learning arrives too late, after the central commitment has become politically, financially, or technically hard to revise.
Multilevel partial truths · open
Multiple levels describe the problem differently, and each description contains partial truth.
The structural problem is cross-level incompleteness. The narrower requirement in this condition set is: Multiple levels describe the problem differently, and each description contains partial truth.
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 strategy, policy, standard, or program is being designed centrally but must work across varied local contexts.
It is especially useful during strategy rollout, policy implementation, organizational change, platform governance, service redesign, and community-facing programs where central plans often fail because they do not match how work or life actually happens. In this archetype, the relevant contextual consideration is: A strategy, policy, standard, or program is being designed centrally but must work across varied local contexts. It helps interpret the situation or strengthens the practical case for examining the archetype.
Supporting contextCentral leaders need coherence, comparability, risk control, or strategic prioritization, but purely local optimization would fragment the system.
A top-down perspective sees scale, coherence, priorities, standards, and shared risk, but it abstracts away local detail. In this archetype, the relevant contextual consideration is: Central leaders need coherence, comparability, risk control, or strategic prioritization, but purely local optimization would fragment the system. It helps interpret the situation or strengthens the practical case for examining the archetype.
Coverage
2 of 4 conditions grounded · 2 open.
Mechanisms / Implementations¶
- Participatory Strategy Process: Structures strategy formation so leadership intent is tested against knowledge from people who must implement, use, or live with the strategy.
- Executive-Guided Co-Design: Pairs a fixed executive direction with hands-on co-design sessions that shape a workable plan to local constraints without loosening its non-negotiable frame.
- Frontline Feedback System: Collects structured observations, exceptions, workarounds, bottlenecks, and early warnings from people closest to implementation.
- Federated Governance Cadence: Creates recurring cross-level decision forums where central owners and local representatives revise standards, exceptions, and shared priorities.
- Local-National Policy Synthesis: Reconciles broad policy goals with regional, municipal, community, or site-level implementation evidence.
- Agile Portfolio Governance: Uses periodic portfolio review to align central priorities with delivery-team evidence, capacity, dependencies, and learning.
- Community-Informed Implementation: Uses community knowledge to adapt central programs, services, or interventions to lived context while preserving program goals.
- Pilot-and-Scale Feedback Review: Runs limited local implementations, examines what they reveal, and revises the central plan before wider rollout.
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 (2)
- Perspective: Representation of depth.
- Sociotechnical Systems: Social + technical interaction.
Also references 8 related abstractions
- Accountability: Responsibility for actions.
- Collective Systemic Learning: Shared adaptation.
- Downward Causation: Higher-level influence.
- Feedback: Outputs influence inputs.
- Formal vs. Informal Structures: Official vs actual systems.
- Goal Congruence (Alignment): Alignment of objectives.
- Local Autonomy & Tiered Escalation: Escalate when needed.
- Stakeholder Analysis: Identify involved parties.
Variants¶
Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.
Frontline-Informed Strategy · governance variant · recognized
A variant in which strategic direction is revised using evidence from frontline workers, service providers, local operators, or users.
Federated Direction Setting · governance variant · recognized
A variant in which central and local units share direction-setting through a federated forum, standard, or cadence.
Policy Implementation Synthesis · domain variant · recognized
A policy-focused variant that adapts central rules to local implementation evidence while feeding local outcomes back into policy design.
Central-Local Portfolio Synthesis · implementation variant · candidate
A portfolio-planning variant that reconciles central priorities with delivery-team capacity, dependencies, risk, and learning.
Editorial Notes¶
Problem Classification¶
Classification: Scale, Hierarchy & Emergence Mismatch → Hierarchical Delegation & Multilevel Coordination
Problem kernel: central coherence and local validity are not synthesized across levels
Rationale: Earliest causal condition: Central direction lacks local validity, while local input lacks system-wide coordination, prioritization, or authority to change the larger plan.
Independent corroboration: The earliest necessary condition in the frozen evidence is: Central direction lacks local validity, while local input lacks system-wide coordination, prioritization, or authority to change the larger plan. That is a hierarchical delegation and multilevel coordination problem because Local autonomy and higher-level coherence are mismatched, producing central bottlenecks, vague mandates, shadow authority, and cross-tier accountability gaps.
Review outcome: Independent reviewer agreement; high confidence.