The Commercial Operating System.
What I’ve learned, across more than 150 organizations, about how companies actually become more capable over time.
For most of my career, I believed I was helping organizations improve sales.
Eventually I realized I wasn’t.
The organizations that consistently outperformed weren’t simply better at selling. They were better at making decisions. Better at learning from what they made. Better at preserving what they learned. Better, over enough quarters to be sure, at becoming more capable than they had been the quarter before.
That realization changed how I thought about the work. Sales, leadership, recruiting, customer success, operations, forecasting, AI — the deeper I looked, the more they resolved into a single question hiding underneath. Not whether the departments were strong. Whether the organization was thinking.
That question became the beginning of the Commercial Operating System. It isn’t a methodology. It’s a body of work on how organizations become more capable when they improve how they think, decide, learn, and adapt together.
How a thinking organization actually moves.
What the organization is actually able to notice.
Every organization I’ve worked inside produced more information than it could act on. That was never the problem. The problem was that most of it never made it to the moment of decision.
Over time I began to notice a pattern. The intelligence that would have prevented a bad quarter almost always existed somewhere inside the company. It just didn’t exist at the seat where the choice was made. A customer success manager had seen the churn signal in July. A field seller had heard the objection three deals in a row. A finance lead had flagged the concentration risk. None of it reached the room.
Organizations can’t store judgment. They can, however, preserve the things that produce better judgment.
This is the part of the operating system that AI is most often expected to replace, and least equipped to. Judgment lives in context — the history of a relationship, the reasoning behind an earlier call, the read on a team member that took years to earn. None of that transfers cleanly to a model.
What can transfer is the material that produced the judgment in the first place. The reasoning behind past decisions. The pattern of trade-offs the organization has actually made. The context surrounding calls that worked and calls that didn’t. Preserve those things, and executive judgment strengthens across the entire company — not because a machine is deciding, but because the humans deciding are inheriting a smarter starting point every time. Technology informs judgment. It never replaces it.
Perspective is designed. Perception is automatic.
Most executives I’ve worked with are excellent at perception. They walk into a room and read it inside a minute. Perception is fast, individual, and often correct. It is also, on its own, insufficient.
Perspective is what an organization sees when it deliberately puts more than one lens on an important question. Who provides input. Who owns the call. Who is required to dissent. Whose experience the room is missing before the choice gets made. In the strongest organizations, this is designed on purpose. In most, it isn’t.
Without designed perspective, decisions default to the strongest individual in the room. That works for a while. It stops working the moment the strongest individual is wrong — and no one in the architecture was structured to say so.
Not what the company knows. What it hasn’t had to relearn.
Visible in behavior, not on the org chart.
The intelligence of an organization isn’t a function of how much it knows. It’s a function of how it behaves. How quickly it revises an assumption in the face of new information. How consistently it applies a lesson across teams that don’t normally talk. How reliably the next decision is measurably better than the last.
After working with more than 150 companies, I stopped believing the gap was about talent.
The most talented rooms I ever sat in were also, occasionally, the least capable of learning. The system around them wasn’t organized to convert what they saw into what the company did.
Organizations become more capable when they improve how they think, decide, learn, and adapt together.
The system exists to make great people greater.
The framing that AI will replace exceptional people has never matched what I’ve actually seen inside companies. The best commercial leaders I know are more valuable, not less, when the infrastructure around them is stronger. They make better calls, faster, across more surface area. Their judgment compounds instead of getting spent on friction.
The point of the operating system isn’t to reduce the need for judgment. It’s to make sure the people with the best judgment are operating at the top of their capacity across an organization that’s finally big enough to matter.
Learning isn’t complete until it changes future behavior.
Nearly every organization I’ve worked with had a retrospective process of some kind. Most produced observations that were factually correct and behaviorally inert — the same lesson re-learned across three consecutive quarters, filed away each time, and applied by no one.
The test isn’t whether the review happened. It’s whether the next decision was measurably different because of it. Every important decision should leave the organization more capable than it was before the decision was made. If it doesn’t, the learning hasn’t actually happened yet — no matter how thorough the meeting felt.
The reasoning is the asset.
Most organizations track what they decided. Very few track why. Circumstances change — they always change — and the organization can no longer tell the difference between a decision that has become wrong and one that was wrong from the beginning.
Preserving the rationale is what allows an organization to evolve its judgment instead of accumulating its conclusions. It is also, quietly, one of the highest-leverage things AI can do inside a company. Not making the decision. Holding onto the reasoning that produced it, so the next executive making the next version of that decision inherits a smarter starting point than the last one did.
The tendencies the organization can’t see about itself.
Not a feature.
A layer of the architecture.
The organizations that will compound advantage over the next decade won’t be the ones that adopted the most AI tools. They’ll be the ones that treated AI as infrastructure — a layer of the operating system, integrated with judgment, memory, and learning.
AI as feature accelerates isolated tasks. AI as infrastructure changes the shape of the organization itself — what it’s able to notice, remember, and consistently do. The distinction sounds small on a slide. Inside a real company, it’s the difference between marginal speed and structural capability.
I don’t believe extraordinary organizations are built by discovering perfect answers. I believe they’re built by creating systems that continually improve the quality of their thinking, their decisions, and their ability to learn together.
That’s the work I’m pursuing. Longer essays, white papers, and keynote material will extend each of these ideas in turn — tested against the reality of running commercial organizations, refined the way any body of work worth its readers has to be.
This is only the beginning.