The Commercial Operating System.
Twenty years of observation about how organizations actually think — and why the strongest ones improve at that faster than they improve at anything else.
Most organizations don’t fail because they lack talented people. They fail because good people make isolated decisions inside systems that were never designed to think collectively.
For most of my career I thought I was helping organizations improve sales. Over time I realized I wasn’t really helping them improve sales. I was helping them improve how they made decisions. That observation changed everything.
The deeper I looked, the more I saw that sales, leadership, recruiting, customer success, operations, forecasting, and AI were not separate problems. They were expressions of something larger — reflections of how an organization thinks. Once that becomes visible, it’s hard to unsee.
That observation is the beginning of the Commercial Operating System. Not a methodology. A body of work on how organizations become more capable when they improve how they think, decide, learn, and adapt together. Revenue is an outcome, not the objective. The goal isn’t better departments. The goal is a better operating system.
How a thinking organization actually moves.
What the organization is actually able to notice.
Every organization I’ve worked inside had more information than it could act on. Customer conversations, market signals, deal patterns, financial data — the volume was never the problem.
The problem was that most of it never made it to the moment of decision. Commercial Intelligence isn’t about generating more signal. It’s about designing the system so the signal that matters reliably reaches the people responsible for choosing what to do about it. Organizations optimize locally and fail systemically — usually because the intelligence that would have prevented the failure existed somewhere in the company, but not at the seat where the decision was made.
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 customer relationship, the reason a prior decision was made under conditions that no longer apply, 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. When those things are preserved, executive judgment strengthens across the entire company. Technology informs judgment. It never replaces it.
Perspective is designed. Perception is automatic.
Most executives are excellent at perception. They walk into a room and read it inside a minute. But perception is what a single person sees. Perspective is what the organization sees when it deliberately puts more than one lens on an important question.
The best organizations I’ve worked inside had this designed on purpose. Who inputs on a decision. Who owns it. Who is required to dissent. Whose experience the room is missing before the choice gets made. It looks like structure. What it really is, is discipline about how the organization thinks together.
Without that discipline, decisions default to the strongest individual in the room. That works for a while. It stops working the moment the strongest individual is wrong.
Not what the company knows. What it hasn’t had to relearn.
Every high-performing company I’ve seen loses meaningful people. What separates the ones that keep compounding from the ones that stall isn’t retention. It’s what happens to the context when someone leaves.
In most organizations, that context walks out the door — customer history, deal reasoning, the read on a partner relationship. In the strongest ones, the operating system holds it. That’s Institutional Memory. Not a knowledge base. A discipline about what deserves to be preserved.
The most important thing to preserve isn’t the record of what was done. It’s the record of why it was done — the reasoning behind decisions that later proved right, and the ones that didn’t. Decisions without their rationale age badly. Decisions with their rationale become the organization’s next round of judgment.
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 lessons across teams that don’t normally talk. How reliably it improves the quality of its next decision after the last one.
You can see this from the outside. Some organizations feel — to customers, to boards, to the people inside them — noticeably smarter this quarter than they were last quarter. Others don’t. The gap isn’t talent. Organizations become more capable when they improve how they think, decide, learn, and adapt together. Everything else is downstream of that.
The system exists to make great people greater.
The framing that AI will replace exceptional people has never matched what I’ve seen inside actual organizations. 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.
Great organizations don’t replace exceptional people with AI. They multiply exceptional people through better systems. 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.
Every organization I’ve worked with had a retrospective process of some kind. Most of them produced observations that were factually correct and behaviorally inert — the same lessons re-learned across three consecutive quarters, and never applied.
Learning systems are the deliberate mechanisms by which experience actually changes what the organization does next. That’s the test. Not whether the review happened. 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.
The reasoning is the asset.
Most organizations track what they decided. Very few track why. When circumstances change — and they always change — the organization can no longer tell the difference between a decision that’s become wrong and a decision that was wrong from the start.
Preserving the rationale is what allows an organization to evolve its judgment instead of accumulating its conclusions. It’s 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.
The tendencies the organization can’t see about itself.
Over enough decisions, every organization develops tendencies. Which trade-offs it consistently makes. Which risks it consistently avoids. Which timescales it consistently underweights. These patterns are usually invisible to the people inside them — the same way a person can’t hear their own accent.
Naming those patterns out loud is often the difference between an organization that improves its judgment and one that repeats it. Most of the strongest improvements I’ve seen inside companies started with someone saying, quietly, in a room: we do this every time.
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 organizations become extraordinary because they discover the right answers. They become extraordinary because they build systems that continually improve the quality of the questions they ask, the decisions they make, and the way they learn together.
This work is my attempt to describe how that actually happens — and to keep testing the description against the reality of running commercial organizations. It is designed to survive challenge rather than chase trends. Longer essays, white papers, and keynote material will extend each of these ideas in turn.
The intent, from the beginning, has been the same: to understand the operating system that lets an organization become more capable over time — and to build the version of it that I would want to work inside.