Insights
Perspectives from the field on what makes organizations work, why change initiatives succeed or fail, and how leaders can build systems that hold.
These articles draw on direct experience leading transformation programs, advising executive teams, and building organizations through complexity. The goal is not theory, it is practical thinking that executives can apply.
Many organizations begin transformation with an answer already in mind. The most important work happens before a solution is selected: understanding how the business actually works today, where performance is breaking down, and what is creating the friction.
Change resistance gets blamed for a lot of failed transformations. But often, by the time resistance becomes visible, the transformation has already been in trouble for months. The earlier problem is usually a definition issue.
A company does not need a fractional COO simply because it cannot justify hiring a full-time COO. It needs one when operating complexity is becoming a constraint and experienced operating leadership can materially change the outcome.
Most organizations can show you their operating model. But the way the business actually operates is different. The two are not always the same, and the gap shows up in cycle time, rework, and missed commitments.
Technology projects force unresolved business decisions into the open. The problem is having those conversations after the technology decision has already started driving the transformation.
An AI strategy built primarily around the technology can miss the bigger opportunity. Before deciding where AI belongs in the organization, it helps to understand how the organization actually works.
A deal can make complete sense on paper and still be extraordinarily difficult to integrate. Operational compatibility is harder to see during due diligence — and it has enormous implications for integration.
Great people can make almost any process work for a while. That doesn't mean the process works, and it definitely doesn't mean it will scale. On the difference between processes that get bigger and systems that actually scale, and what leaders need to build before growth exposes the gap.
Complexity is not something that happens to a company. It accumulates — one shortcut and one workaround at a time. On why the best leaders default to subtraction when something breaks, and the three questions worth asking before any technology decision.
If something here resonated with a challenge your organization is facing, a conversation is the right next step.
