Methodologies / Signature Methodology 01

Integrated Enterprise Systems Thinking

The Dependency Web is the organizing concept. The methodology is used in Advisory Practices.

KATHLEEN REYNOLDSEXECUTIVE GOVERNANCE | INCIDENT COMMANDWritten By Kathleen Reynolds Advisory
Read This Methodology As Text

An executive problem is a change in a network of dependencies, not merely a defect in the department that first reports it.

The Stages

  1. Frame The Decision. Specify the decision, time horizon, value sought, constraints and accountable sponsor. Here, a business wants to double demand through marketing.
  2. Map The System. Model the resources, obligations, information paths and control points around the decision, and mark the relationships that are uncertain.
  3. Locate Leverage & Bottlenecks. Separate root constraints from symptoms. Scheduling, workforce certification, service capacity and cash collection are already constrained, and new demand will travel straight into them.
  4. Generate Strategic Options. Build at least three options, including a pilot and a structural redesign, and compare their cost, speed, downside and reversibility.
  5. Stress Test Interactions. Push each option through operations, finance and customer outcomes. Added sales can surface as backlogs, refunds or liquidity stress.
  6. Assign Authority & Execution. Name the owner and decision rights, and set the gates a staged rollout has to pass: capacity first, then working capital.
  7. Observe & Adapt. Track leading indicators, realized effects and unintended consequences, with explicit triggers to revisit the decision.

What It Does Not Claim

  • A complete enterprise map can become too slow or speculative. The method keeps scope proportional and stops mapping once more detail no longer changes the decision.
  • For a bounded, low-consequence issue, a single-function fix can be faster and is the better choice.