How a Lifetime of Learning Shaped
Fix • Prevent • Improve
If you look at my career on paper, it can read like eight different lives:
.png)
To most people, those worlds appear unrelated.
To me, they form a straight line.
That clarity, however, only exists in hindsight.
Living it was nonlinear - filled with false starts, conflicting guidance, constraints, and trial-and-error.
Fix • Prevent • Improve did not arrive fully formed:
-
It emerged gradually,
-
Problem by problem,
-
System by system,
Until the underlying pattern became impossible to ignore.
This is not a résumé.
It is the origin story of an operating model.
Early Lessons That Changed Everything
Quality Comes from Reducing Variation
Through mentorship and exposure to statistical thinking, I learned a simple truth: variation is the enemy. Defects, delays, cost overruns, and dissatisfaction are not random — they are symptoms of unmanaged variation.
Value Drives Loyalty and Profitability
Customers do not reward effort. They reward value. High value creates loyalty. Low value creates churn.
Processes Create Outcomes
Every result — good or bad — is produced by a process. If you want predictable outcomes, you need predictable processes.
Signal-Based Thinking Enables Improvement
Averages hide the truth. Systems reveal it. Process Behavior Charts distinguish real signals from normal noise and make intelligent decision-making possible.
These ideas planted the seeds of something larger.
Across industries that claimed uniqueness, the same structural truths repeated.
Organizations would improve performance for a period of time — sometimes dramatically — only to see results drift backward. The gains were real, but they did not hold.
Every problem is a process problem.
Every process has a signature of variation.
Every outcome reflects system design.
Every improvement requires structure.
Learning Across Domains — The Pattern That Became Impossible to Ignore
Across industries that looked radically different on the surface,
I kept encountering the same structural problem.
Organizations would improve performance for a period of time — sometimes dramatically — only to see results drift backward. The gains were real,
but they did not hold.
It wasn’t a lack of effort.
It wasn’t intelligence.
It wasn’t tools
It was structure.
There was no disciplined, repeatable way to stabilize performance, prevent recurrence, and raise capability under real-world pressure.
Improvement was episodic.
Learning was fragile.
Variation was misunderstood.
The industries changed. The pattern did not.
Once I saw that clearly, I could no longer unsee it.
The Spark — Designing an Intelligent Business System (2003)
In 2003, during a DARPA-funded research effort conducted in collaboration with the Air Force Research Laboratory, the question became explicit:
Why do organizations achieve short-term improvement, only to see performance decay?
The answer was not tools.
It was system design.
That work framed performance as a closed-loop architecture involving:
-
Sensing
-
Decision-making
-
Execution
-
Feedback
-
Learning
-
Governance
Variation was identified as the primary enemy of predictability.
Learning was embedded into daily operations.
An early form of an Intelligent Business System was designed — not as theory, but as architecture.
What was missing was a simple, repeatable execution rhythm.
From Theory to Practice
Years later, that gap became unavoidable.
Systems thinking alone was not enough. Organizations needed structure that worked under real-world variation.
The solution was not more abstraction.
It was sequencing.
Statistical Process Control, operational datasets, and daily routines were integrated into a practical framework.
What emerged was a disciplined rhythm that could scale under pressure.
The Birth of Fix • Prevent • Improve
Across decades of experience, a consistent execution pattern surfaced:
-
Fix — stop the bleeding; restore safety and stability.
-
Prevent — remove causes and lock in learning.
-
Improve — raise capability, flow, and value.
It mirrored clinical medicine:
-
Stabilize,
-
Prevent recurrence,
-
Restore function.
Fix • Prevent • Improve became the execution engine,
the Intelligent Business System had been missing.
FPI as an Operating System
High-performing organizations — regardless of industry — behave like intelligent systems.
They:
-
Respond quickly to signals
-
Standardize work
-
Manage flow
-
Reduce variation
-
Learn continuously