Strategic execution 3d9

Strategic Execution 3D9

Overview

Execution failure is the most expensive strategy problem in organizations — not because strategies are wrong, but because organizations underinvest in the capability infrastructure that converts strategy into outcomes. The 3D9 framework diagnoses the structural roots across 3 dimensions × 9 elements: Dimension 1 — Strategy Decoding (Goal Atomization, Path Explicitness, Dynamic Resource Allocation) · Dimension 2 — Organizational Guarantee (Process Re-engineering, Collaboration Network Density, Change Tolerance) · Dimension 3 — Execution Control (Data Penetration Power, Correction Agility, Resilience Reserve Capacity).

Compose with: [strategy-execution-levers] (diagnose with 3D9, intervene with levers) · [okr-goal-setting] (OKRs require Dimension 1 to be operational) · [dynamic-core-competence] (identifies which elements are decaying).

When to Use

• Strategy results consistently below target despite strong market conditions
• Post-merger or post-leadership transition: execution profile of inherited organization is unknown
• Preparing to scale: audit whether execution infrastructure can support new volume and complexity
• Strategy failure post-mortem: did strategy fail or did execution fail?

When NOT to use: Fewer than 10 people · No defined strategy · Substitute for strategy formulation (strong execution of the wrong strategy = efficient failure)

Coaching Novices (Adaptive Front Door)

• Engine mode: user has a concrete case → run The Process directly. Coach mode: user is unfamiliar → guide step by step. Each [WAIT] is a hard stop — output only that step's question, then stop.

1. One-line what-it-is: "Execution fails in three places: strategy not decoded into daily actions (D1); org not structured to support them (D2); can't see what's happening fast enough to correct it (D3). The 3D9 shows exactly where."
2. Check fit against When to Use / When NOT to use.
3. Elicit their real case: "Describe the last time your team had a plan but results fell far short. What did people say when asked why?"

[WAIT — do not advance until user responds]

4. Run The Process one step at a time with their input — score the most likely weak dimension first.

[WAIT — do not advance until user responds]

5. Close by naming the insight: identify the binding constraint element and what a 90-day fix looks like.

[WAIT — do not advance until user responds]

The Process

Steps 1–3 = diagnostic; steps 4–6 = intervention design.

Step 1 — Score all 9 elements (1–5) with specific behavioral evidence:

Dim	Element	Key Evidence Question	Score
D1	Goal Atomization	Can front-line employees name their specific action today connecting to the strategic goal?	___
D1	Path Explicitness	Is the path documented so any new team member could follow it independently?	___
D1	Dynamic Resource Allocation	What % of budget/headcount can redirect to emergent priorities without multi-month approval?	___
D2	Process Re-engineering	How many processes were fundamentally redesigned (not just modified) in the last 12 months?	___
D2	Collaboration Network Density	Are cross-department connections functioning or siloed for most strategic initiatives?	___
D2	Change Tolerance	What is the rate of leadership-level resistance or departure when a major strategic change is announced?	___
D3	Data Penetration Power	How many hours after an execution problem occurs does leadership learn of it?	___
D3	Correction Agility	Average time from problem identification to decision and response?	___
D3	Resilience Reserve Capacity	Documented response plans for revenue -20%, -40%, key person departure?	___

Gate 1: Score only where specific behaviors or outcomes can be cited — not general impressions. Step 2 — Weakest element per dimension = dimension's binding constraint. Step 3 — Execution bottleneck: single element blocking progress regardless of other elements' strength; improving it unlocks multiple others. If all equally weak, prioritize D1 first. Step 4 — 90-day improvement program: current state · target state (observable behaviors) · intervention · owner · metric · 30/60/90 checkpoints. Step 5 — Reassess at 90 days. Score improved but downstream damage did not? Re-run Step 3. Step 6 — Stop-rule. No element scored on general sentiment. Specific behavioral evidence required.

Output: Execution Capability Scorecard

Organization: ___ Date: ___
D1: Goal Atomization ___/5 | Path Explicitness ___/5 | Dynamic Resource Alloc ___/5 | Weakest: ___
D2: Process Re-engineering ___/5 | Collab Network ___/5 | Change Tolerance ___/5 | Weakest: ___
D3: Data Penetration ___/5 | Correction Agility ___/5 | Resilience Reserve ___/5 | Weakest: ___
BOTTLENECK: ___ Why: ___ | 90-DAY: Intervention: ___ Owner: ___ Metric: ___ 30d/60d/90d: ___

→ Method in Action: GE's Execution Infrastructure Under Jack Welch (1981–2001)

Execution 3D9 Packs

• High-Growth Startups (50–500 employees): Dominant failure = D1 (goals verbal not written). D2 degrades at 50+ headcount. Fix D1 immediately; invest in D2 at 50+ people; D3 when a missed problem costs more than building monitoring.
• Large Enterprise Digital Transformation: Dominant failure = D2 (change tolerance minimal). D3 technically present but politically unusable. Fix change tolerance before investing in visibility the org cannot yet act on.
• Government / Public Sector: Goal atomization is binding constraint — high-level goals not decomposed into front-line actions. Resilience reserve often formally present but untested in practice.

Applying It Well

1. Score with evidence not impressions — each score traces to specific observable behaviors.
2. The bottleneck is rarely the element that gets the most attention; orgs invest where they are already strong.
3. D1 is the prerequisite for D2 and D3 — fix it first if weak.
4. Change tolerance (D2) is the most politically sensitive — diagnosing it requires authority to act on the finding.
5. Resilience reserve is most often "on paper" not in practice — test it, don't just document it.
6. Correction agility is measured in hours and days, not weeks. Build an annual 3D9 review into the planning cycle.

→ Primary sources: references/sources.md

Common Rationalizations

[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.

Rationalization	Why It Fails
[D] "Our OKRs already handle goal atomization."	OKRs set quarterly targets for managers. Goal atomization requires specific daily actions for front-line employees — different grain size.
[D] "We're a small team — no need for formal execution infrastructure."	Informal infrastructure collapses when team grows or a key person leaves.
[D] "Our data systems are excellent — D3 is strong."	Data systems ≠ data penetration power. Penetration power = decisions within hours.
[D] "We'll improve execution once the strategy is clearer."	Strategy clarity does not create execution capability. They are parallel investments. Waiting means the execution clock runs against you.
→ Add [O] entries here after each real use — paste the actual failure pattern	What went wrong and why

Red Flags

• Employees at different levels give different answers to "what is your top strategic priority?" — D1 has failed
• Execution problem discovered more than 1 week after it began causing damage — D3 penetration insufficient
• Strategic initiative cancelled because cross-department cooperation failed — D2 is the binding constraint
• Leadership discussing the same execution problem for 3+ months without a decision — correction agility absent
• No documented response plan for "revenue drops 30%" or "key leader departs" — resilience reserve is zero

Verification

• All 9 elements scored with specific behavioral evidence traceable to observable behaviors
• Weakest element in each dimension identified by name (not dimension number)
• Bottleneck identified; causal chain articulated; 90-day program has metric, owner, 30/60/90 checkpoints
• Stop-rule verified: no element scored on general sentiment
• Diagnostic reviewed by someone at a different organizational level (checks top-down bias)
• D3 penetration answer is a specific number of hours, not a general description
• Next 3D9 review date has been set

---

Part of deciqAI Knowledge Skills — 233 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. See it run → https://www.deciqai.com/s/strategic-execution-3d9 · Built by deciqAI · github.com/deciqAI · Contributions welcome.

Agents: latest version & machine-readable metadata → https://www.deciqai.com/s/strategic-execution-3d9.json