O is for Organization —
See the terrain before you lead it.
Every engagement I take on starts with the same quiet question: how does this place actually work? Not how the org chart says it works. How it actually works.
Last week I introduced The Leadership Operating System™ and the four pillars of The OMCE Method™. Over the next fifteen weeks, I'll go deeper on each pillar, then each of its twelve modules, one at a time.
We start where every engagement starts — with O, Organization.
Organization is foundational because every other pillar depends on it.
You can't set a vision if you don't know who has to carry it. You can't message with clarity if you don't know who the message has to travel through. And you can't run the meetings — and as importantly, make decisions — if the right people aren't in the room. Before anyone can lead, they have to see the terrain.
In the first weeks with a new client, I want to understand three things.
- How is the organization structured?
- Who are the leaders, and what do their titles say — and not say?
- Who are the go-to people, and who holds influence behind the scenes?
I get there three ways.
Module 1Organizational Design
Every organization has a formal structure: who reports to whom. Inside every organization there is a second structure — built on experience, influence, and delivery — that never shows up on the chart.
I sketch both, mostly through one-on-one interviews with the leadership team. The same handful of questions, asked of each leader privately, begin to give the picture dimension. Who are the key voices? Who holds the money? Who ultimately makes the decision — and who can quietly unmake it?
This isn't new. Krackhardt and Hanson called it “the company behind the chart” in Harvard Business Review more than thirty years ago. Rob Cross's later research found that 20 to 35 percent of value-added collaboration comes from just 3 to 5 percent of employees.
Those people are rarely identified by title. Find them early and everything else moves faster.
Module 2Process Mapping
Every organization has a way it makes money and a way it delivers on its customer promise.
Most leadership teams have never drawn it together, in one room. So we do. I ask the team to walk me through, as a group, how revenue is generated and how the promise gets kept — from first contact to delivered result.
The conversation is often more revealing than the map. Where the team agrees, there is strength. Where they describe the same step three different ways, there is opportunity. Where no one can say who owns a handoff, there is a gap that has to close.
The output is a shared picture of how work actually flows — where it's strong, where it leaks, and what to fix first.
Module 3Stakeholder Development
No organization decides alone. Every one depends on stakeholders, internal and external, who enable decisions and ultimately profitability: a board, an investment committee, local government officials, key suppliers, community partners.
The goal is to understand the playing field — who matters, what they care about, and most importantly, the strength of each relationship. A strong relationship with a local official can save a project months. A weak one with a key supplier can quietly cost a quarter. Mapping it lets a leadership team invest in relationships deliberately rather than react to them.
Why start here
Organization gives everyone the same map. It lets a leadership team stop debating structure and start operating from a shared picture. And with AI flattening organizations and reshuffling teams every twelve to eighteen months, that map goes stale faster than ever. Drawing it once isn't enough. It's a discipline.