The problem beneath the framework
Large-scale Agile environments can become internally consistent and still struggle operationally. The framework may define roles, events, and planning structures, while leaders still face unclear ownership, dependency friction, inconsistent priorities, and difficulty connecting enterprise strategy to accountable product work.
The work at Edward Jones increasingly focused on those enterprise conditions rather than treating methodology as the goal.
The work
- Established and facilitated senior General Partner governance to clarify executive ownership, decision rights, dependencies, escalation paths, and portfolio accountability.
- Guided product and value-stream identification and clarified ownership around shared business outcomes.
- Partnered with Market Management to shape and launch Fast Smooth Flow, connecting strategic priorities to accountable work, performance visibility, and corrective action.
- Established and used KPIs, OKRs, Client Satisfaction, Mean Time to Respond/Restore, and flow measures to improve prioritization and decision quality.
- Coached executives, General Partners, product leaders, RTEs, Scrum Masters, and delivery teams while simplifying excessive framework complexity.
The design tension
Simplify the framework without weakening the operating discipline.
Removing unnecessary process can improve flow and decision clarity. Removing the mechanisms that connect strategy, ownership, dependencies, measures, and correction can simply create fragmentation. The work therefore focused on preserving the management system while reducing complexity that no longer served the outcome.
What changed
The transformation conversation shifted toward a more useful set of questions: Who owns the outcome? What is blocking flow? Which priorities matter most? What evidence tells us the system is improving? What decision is required from leadership?
That shift matters because enterprise agility is not created by adding more process. It is created when the operating model makes strategic choices, ownership, dependencies, flow, and corrective action easier to see and act on.
The larger the transformation, the more important it becomes to simplify. Complexity should earn its place by improving a decision or an outcome.
Field lesson
More process is not the cure for weak accountability.
When ownership, decision rights, or priorities are unclear, organizations often add coordination. That can make the system look more managed while leaving the underlying ambiguity intact. Senior governance becomes valuable when it clarifies who owns the outcome and who can make the tradeoff.
Why this case matters
Transformations often accumulate mechanics faster than they accumulate clarity. Once the organization has learned the basic practices, the next improvement may come from removing unnecessary structure, strengthening product and value-stream accountability, and making governance more consequential.
Leadership question
Which parts of your delivery framework create necessary enterprise discipline, and which survive mainly because removing them feels risky?