Strategic choices keep returning to the same forum.
Decision drag
Slow decisions
Diagnose delayed, reversed, or repeatedly escalated decisions by connecting authority, evidence, ownership, platforms, and governance.
Leader question
Which decisions are slowing the company, and who has the right to resolve them?
Use the specific metric to find aging decisions and establish a 30-day baseline.
Problem Signature
Recognize slow decisions in the work.
These are observable signals—not the diagnosis. Together, they show where to begin inspecting the system.
Visible pattern
Decision paths keep stalling
Teams wait for alignment before making commitments.
Roadmaps slip because dependency decisions are unresolved.
Architecture, platform, and product decisions move on different clocks.
Executives keep adjudicating decisions that should have clear owners.
First 30 Days
Move from diagnosis to operating proof.
Keep the intervention bounded. Each move should make ownership, decisions, evidence, or control easier to inspect.
The intervention rule
Fix one consequential workflow before starting a broad transformation.
01Observe
List the 10 decisions currently slowing the highest-value work.
Visible operating move
02Clarify
Assign an accountable decision owner and target date to each one.
Visible operating move
03Intervene
Map the evidence source, approval path, and escalation rule for each decision.
Visible operating move
04Review
Review decision latency weekly until aging decisions have an owner or escalation.
Visible operating move
Worked Example
See the diagnosis become a decision.
Illustrative example — not customer evidence.
The example keeps the situation, intervention, and observable result connected so the operating change is easy to follow.
01 · Situation
A product launch is two weeks late because pricing, security, and platform decisions keep returning to the same steering committee.
02 · Intervention
- 01
The team lists the three unresolved decisions and names one decider for each.
- 02
Each decider receives the evidence required, a target date, and one escalation condition.
- 03
The steering committee stops reopening decisions unless the recorded escalation condition occurs.
03 · Observable result
Within 30 days, the launch has a stable decision path and leaders can inspect decision latency instead of counting meetings.
Proof, not activity
LPM Diagnosis
The visible problem is not the whole problem.
LPM traces the symptom into the operating conditions underneath it, then identifies the layers leaders should inspect first.
Operating causes
- 01Decision rights are implied instead of designed.
- 02Ownership and authority are split across different roles or forums.
- 03Evidence is fragmented, so leaders debate facts before they can debate tradeoffs.
- 04Governance reviews work but does not clarify who can decide, approve, pause, or redirect.
Layer 02 · inspect first
Decision Architecture
Identify the critical decisions, owners, evidence, timelines, and escalation paths.
Layer 01 · contributing condition
Identity & Incentives
Clarify who owns the outcome and who is accountable for the decision.
Layer 04 · contributing condition
Information Ecology
Confirm that decisions are based on trusted, current, and shared facts.
Layer 06 · contributing condition
Governance Architecture
Separate risk review from decision ownership so governance removes friction.
Metrics and Artifacts
Metrics to inspect and artifacts to build
Each use case becomes practical when the diagnosis connects measurable signals to concrete operating artifacts.
Metrics to Inspect
Recommended Operating Artifacts
Slow decisions
Diagnose the symptom before prescribing the solution.
Use the specific metric to find aging decisions and establish a 30-day baseline.