Where did this conviction begin?
I watched organizations invest enormous attention, energy and capital in transformation. They launched major programs, brought in strong people, introduced new technologies and created new governance. Many of those initiatives delivered something valuable. Yet the organization itself did not become better at transformation.
Once the program ended, the structures around it disappeared. External teams left, internal teams moved on and much of what had been learned simply disappeared. When the next challenge arrived, the organization assembled another program and began again.
The clearest version of this I remember was a CEO's own doubts about a major program never becoming visible. The program team's reality never reached the top in a form that could be honestly examined. Nobody had created the conditions for that conversation and, because the culture treated that kind of transparency as dangerous, nobody tried.
That is not primarily a consulting problem or a leadership failure. It is an organizational capability problem—and it is the problem MANREAU is built to address.
You have talked about the difference between an organization that will not move and one that cannot. Where did you learn that distinction?
From a reorganization that failed for two completely different reasons at once, although I only understood that in hindsight.
The first was political. A growth agenda—more headcount and international expansion—created competition for territory. Leaders pulled responsibilities toward their own units. Their choices were individually rational but collectively destructive to the design we had all agreed.
The second was a genuine capability gap. Some leaders did not know how to translate the strategy into concrete priorities for their own teams. They could endorse it at the level of the room. They could not operationalize it. So they improvised, each in their own direction.
We had gone straight from discussion to design without examining what people were seeing and believing. We assumed agreement on the words meant alignment on the meaning. That is the distinction I now call will and can. It matters because each condition requires a fundamentally different response. Push harder on someone who cannot, and you get more improvisation, not more capability.
How did that distinction change the way you looked at leadership and accountability?
I saw the same confusion, more starkly, with a CEO who kept returning to one conviction: his people were paid very well to cover their jobs. If the transformation stalled, the explanation was simple—leadership decides, everyone follows, and if they were not following, they were not doing what they were paid for.
He was not wrong that decisions had been made. He was wrong about where decision-making actually lived. Every line manager in that organization already held real decision-making power within their own scope, whether he had designed it that way or not. None had been asked whether they could carry what the transformation required, only told that they should.
I looked at his organigram with him. It was full of reporting lines—every manager connected upward, accountable and visible. I asked him: where are the supporting lines? Where, on this chart, does anyone show what a manager receives, not just what they owe?
There was no answer, because there was no line.
I ask that question with some authority. Early in my own career, I took a role reporting to two global sector leaders and a country manager at once—three reporting lines on paper, with no stated relationship to one another.
In the interview, before I accepted, I said the only thing that actually mattered to me: I hope these are not only reporting lines, but also supporting lines. Whether that turns out to be true is usually the difference between a structure someone can work inside and one they simply survive.
Was there a moment that shaped why you built this as its own category rather than a variant of strategy or change advisory?
I once worked with a genuinely excellent finance function: deep technical rigor, strong controls and capable people. When transformation initiatives started arriving faster than the organization could absorb them, their instinct was to bring in more finance advisers—more technical expertise. It made sense on paper.
It did not help. What they lacked was never technical knowledge. It was the capacity to move—to decide, commit and act together at the pace change was arriving. You cannot hire your way out of that gap with more specialists in the domain where you are already strong.
That is part of why MANREAU exists as its own category, not a variant of strategy, technology or change advisory. The problem was repeatedly treated as a knowledge gap. It was not one. It was the absence of a shared discipline for moving together.
You describe transformation as operating through a human and organizational system. What do you mean by that?
Every organization already has a Transformation Operating System: the wider system through which transformation is formed, interpreted, resourced, negotiated, executed and adapted. Much of it remains implicit—the habits that determine which signals reach leadership, whose perspectives are heard, how disagreements are worked through and whether decisions become credible commitments.
MANREAU does not install another system. We help leaders make the one already operating visible and manageable. Its human core is collective judgment: people seeing reality from different positions, interpreting what it means and deciding what they can credibly carry together.
SITT is the management discipline leaders exercise within that system: See reality, Interpret its meaning, Translate judgment into credible commitment and Transform through coherent action and learning. It does not replace leadership judgment. It gives leaders a disciplined way to form and exercise it under real uncertainty.
What stays with you most from the relational side of this work?
Something I noticed once and have now seen repeatedly across very different organizations: the loneliness of senior leadership as a structural condition. The work is highly ambiguous, politically complex and uncertain, yet leaders are expected to act as if the path is clear. The performance of certainty is part of the role, even when certainty is the one thing not available.
I think of one senior leader at a retail company, mid-transformation—the clearest example, not the only one. He was given something unusual: someone working closely alongside him, not to tell him the answer, but to help him see the full shape of what he was deciding, including what a rivalry with a peer was really costing him. Not a framework absorbed from a course. A different capacity, reached through his own experience, with someone beside him.
I do not think this is rare. I think it is simply rarely named.
What kind of client is ready for this approach?
Leaders who measure success by capacity that compounds, not programs that close—who want Booked and Sustained Value from this transformation and the next one, not a deliverable to sign off on and move past.
They are usually the ones who have already felt what repeated, disconnected programs cost an organization: the fatigue that sets in not because people stop believing in the direction, but because every initiative starts over instead of building on what the last one left behind. They are not looking for a program to be delivered to them. They are looking to stop paying that cost.
If you looked back in five years, what would tell you MANREAU had succeeded?
An organization that no longer depends on extraordinary interventions to transform, because the ability to see, judge, act and learn has become part of how it manages itself. Internal Transformation Champions carrying the discipline forward. The learning still available, still being used. And after MANREAU steps back, the rhythm continuing without us.
That is the organization MANREAU works with leaders to build.