The engine you’ll wish you had built sooner.
SPADE OS is how a company turns continuous improvement into inevitable results. It works with how the brain is wired, the instincts and shortcuts it already runs on, so the right behavior becomes intuitive and instinctive.
Working session · in progressSpending rises while outcomes stay flat.
AI is the clearest example right now. Global corporate AI investment more than tripled between 2019 and 2024, from roughly $70 billion to $252 billion.1 Over the same period only 16 percent of transformations improved performance and sustained it,2 and 95 percent of enterprise generative-AI pilots have shown no measurable impact on the P&L.3 The pattern is older than AI. The distance between what goes in and what reaches the business is the execution gap, and it compounds every quarter it goes unaddressed.
A diagnostic that finds where strategy leaks before it reaches execution.
Engineered like a control system, with feedback built into the loop. It combines systems engineering, behavioral science, and product strategy, three disciplines most transformations apply in isolation.
I use product thinking to transform systems, and systems thinking to build products. Every intervention targets the same thing: the behavior that, once changed, moves the metric that matters.
Seven disciplines, one system.
SPADE OS reads two ways. It is an operating system for the business, and the name is a map of the work. SPADE is the method. OS is Operations and Systemic thinking, the ground the method runs on.
A big change, reached without a big step.
A real shift sounds like a leap, and leaps are costly, so most of them never happen. SPADE OS reaches the same destination the way Kaizen does, one deliberate change at a time. You are not asked to bet the company or to brace for a transformation. You make one change, let the new behavior settle, then make the next.
Significant change does not arrive fast, and it does not arrive in a single move. It compounds. Because each step works on behavior rather than on a mandate, the new way takes hold instead of sliding back. By the time people look back, the old way of working is the part that looks strange.
Why this one holds.
Plenty of people and firms name the strategy problem or the execution problem. Naming it is the easy part. Most methods differ more in name than in substance, so SPADE OS is built on the principles underneath them, together with one idea from control engineering: a system that measures its own outcomes and corrects them. That is what lets it hold inside real, complex organizations.
It runs as a closed loop
It borrows closed-loop feedback control from control engineering. It assumes outcomes will drift, measures the distance between the expected result and the real one, and corrects on every cycle.
Proven principles, applied by judgment
It works as a set of proven, immutable principles rather than a fixed recipe. The principles hold. How and when you apply them is judgment, and that takes an experienced leader.
Knowing when not to apply them
Knowing when a principle fits matters as much as knowing when it does not. Most of the skill lives in that restraint.
Fitted to each system
Every company is its own system. SPADE OS reads the one in front of it and adjusts, so the work fits the organization it is meant to change.
As simple as possible, and no simpler
Complex systems need real structure, and too much of it fails under its own weight. SPADE OS holds the balance, as simple as possible, but no simpler.
Multivariable by design
Complex systems move on many connected variables, and the result you want is the balance among them. SPADE OS optimizes for the whole system, not one local metric.
Drawn from many fields
It combines principles from mathematics, finance, leadership, product, systems and control engineering, economics, behavioral economics, psychology, social psychology, anthropology, history, physics, biology, agile, six sigma, project management, software engineering, and storytelling. The same principles keep reappearing across fields, and that convergence is the point.4
The biggest opportunities live between the departments.
Most improvement effort goes inside a single team, where the metrics already live. The largest gains usually sit between teams, in the interactions no one owns. When each department optimizes its own metric without seeing the others, individually rational choices add up to a worse result for the whole, a corporate version of the Prisoner’s Dilemma. The fix is structural: redesign the system so that optimizing for the department and optimizing for the company point in the same direction. Two rules run through the work. Clients describe solutions before they describe the problem, so every request gets traced back to the question underneath it. And no metric is neutral, because any metric a team is measured on will be optimized, whether or not it produces the behavior the business wants.
Context and hypothesis
Form a structural hypothesis about the business before going deep on any one team, and read past the stated request to the real question.
Department mapping
Map each unit on its own terms: its goal, the questions it must answer, the actions it takes, the data it trusts, and what it hands to and takes from its neighbors.
Gap and conflict analysis
Find where metrics pull against each other, where information one team generates never reaches the team that needs it, and where the feedback loop is broken.
Recommendation and roadmap
A three-horizon plan run in parallel, argued so each team sees its own case made first, before any joint decision.
Four AI projects were each delivering value on their own. The diagnosis found the real prize between them: promotions and yield were pulling against each other with neither team aware, and in an open brainstorm about 70 percent of the value ideas crossed team boundaries. The parts of a closed-loop, self-correcting system were already there. What was missing was the connective architecture that makes them run as one.
Why it takes an experienced leader.
Operations run badly even when the metrics look good, and it fails for reasons that repeat across companies. Metrics get defined badly, or defined first, as if having metrics were the answer. Then people look at the dashboard and do not know what to do with it, or there are too many ideas and too many opinions, and the room defaults to the highest-paid opinion, or to politics. Actions do not get taken. When they do, no one follows through, no one is accountable, and nothing ties the metric back to the action and to the operation it was meant to change.
SPADE OS starts with the question the metric is meant to answer, and that question comes from two sides at once: the problem to solve and the goal it serves. Defining the problem is the hard part. People confuse the problem with its cause and with its consequence, and no formula separates them cleanly, because everything is connected, the variables are many, and each person reads the situation through their own perspective and their own bias. Show ten capable people the same operation and, like a Rorschach card, they will describe ten different things.
We are not thinking machines that feel; we are feeling machines that think.António Damásio5
This is where an experienced leader earns their place. They read the room and find the people who carry real substance, and give them the voice they need over the loudest or the most senior. They separate things, so one thing stays one thing and another stays another, while holding the relationships between them. They distinguish each problem, and then, for each one, separate the problem from its cause and its consequence. Then they make a call on what is worth fixing: the root cause, the problem itself, or, when a strategic reason calls for it, the symptom for now, with that decision logged so the root cause comes back to be solved rather than quietly forgotten.
When the issue lives in people and behavior, which is most of the time, the leader identifies which behavioral principles to work on. People do not act as the rational actors most organizations are built for. Behavior is not deterministic, so this part runs as hypotheses, experiments, and iteration, with the judgment to read the results and adjust.
None of this follows a script. It takes someone deep in systems and operations, and just as deep in leadership: able to work across levels of hierarchy and interest, keep people engaged and contributing, hold the grit to keep going, and feel when to push, when to change focus, and when to give a team a win to keep them in it. That judgment is the method, and it is why SPADE OS holds up in the room rather than on a slide.
The results are measurable.
Across different organizations and systems, the same approach applied to the behavior that moves the metric.
// figures drawn from live engagements across manufacturing, banking, biotech and logistics
Talent hits a target no one else can hit. Genius hits a target no one else can see.Arthur Schopenhauer6
Seeing the target is the rare part. SPADE OS is the system for reaching it, one deliberate change at a time.
A working session on your actual problem.
You leave with a map of where your strategy is leaking to execution, yours to keep whether or not we work together. I take on a small number of engagements at a time.
Book a working session →The thinking, in the open.
Get your diagnosis first.
Five minutes. See where your organization is losing strategy to execution, and what it costs you.