A company exists because people can make commitments together that none of them could make alone.
Not accomplish more — commitments specifically. An individual can produce work, generate ideas, deliver a service. An organization makes promises that bind future action, allocate shared resources, create obligations between people, and persist over time regardless of which individuals remain. That binding quality — the ability to make commitments that outlast any single person's presence or intention — is what organizations do that collections of individuals cannot.
Everything that happens inside an organization is ultimately in service of making, keeping, or renegotiating commitments.
What a Commitment Is
A commitment is not a legal contract, though some commitments take legal form. A commitment is any act that binds future action and creates obligations that extend beyond the person who initiated it.
- A customer order: we commit to delivering by a date, at a quality, for a price
- A hiring decision: we commit to this person's role, development, and compensation
- A budget approval: we commit to allocating resources this way and not another
- A product roadmap: we commit to solving these problems in this order
- A strategy: we commit to competing here rather than there
- A board resolution: we commit to this capital structure, this governance model, this direction
Commitments are different from intentions. An intention is private and revocable — it lives inside one person's mind and can be changed without consequence. A commitment binds others. It creates expectations, dependencies, and obligations that propagate through the organization and beyond it. When a commitment is broken, someone is surprised, harmed, or let down — not just the person who made it, but the people who were counting on it.
This is why organizations exist. Not to aggregate productive capacity — markets do that more efficiently, as Coase observed. But to enable a form of commitment that no individual can make alone: commitments that bind the collective, that allocate shared resources, that persist over time, and that can be kept even as individuals join, leave, and change roles.
Customers Buy Commitments
Look at any commercial relationship from this angle and it becomes clarifying.
Customers do not buy products or services. They buy commitments — the promise that a product will perform as described, that a service will be delivered as agreed, that a company will still exist to honor the warranty, that the software will be maintained and improved, that support will be available when something goes wrong.
The product is the evidence that the commitment can be kept. The brand is the track record of commitment-keeping over time. The contract is the formal record of what was committed.
Employees join commitments — to a role, to a team, to a culture, to a future that the organization is promising to build. Investors fund commitments — to a strategy, to a management team, to a plan for generating returns. Boards govern commitments — ensuring that the commitments made to shareholders, regulators, and other stakeholders are honored, and that the commitments the organization makes to the future are coherent with its current capabilities.
Software executes commitments — automating the delivery of what was promised. AI helps form commitments — reducing the uncertainty and coordination cost that make commitment formation expensive and error-prone. Governance structures protect commitments — ensuring that authority is clear, that deviations are visible, and that the organization can be held accountable.
Everything inside an organization exists because commitments have to be made, and they are hard to make well.
Every Organizational Friction Is a Commitment Problem
Uncertainty is not knowing whether a commitment can be kept, or whether the assumptions behind an existing commitment still hold. The organization made a promise under conditions it believed to be true — but conditions change, and the organization does not always know when they have changed enough to matter.
Coordination Cost is the work of aligning the organization around a commitment. A commitment made at the top must propagate through the organization with consistent meaning — every function must understand what the commitment implies for their work, and act accordingly. The cost of that propagation is coordination cost.
Latency is the time between when a commitment becomes incoherent — when reality has drifted far enough from the conditions that justified it — and when the organization learns this and can revise the commitment. The longer the latency, the more damage accumulates before the commitment is updated.
Local Optimization is different parts of the organization making commitments that are locally rational but collectively incoherent. Sales commits to a delivery date that operations cannot keep. Marketing commits to a feature that engineering has not scoped. Finance commits to a cost structure that the business model cannot sustain.
Capability is the organization's ability to make larger, more ambitious, more reliable commitments in the future. This depends entirely on whether the organization learns from the commitments it has made in the past — which commitments it kept, which it failed, what it learned about its own capabilities, and what that implies for the commitments it can credibly make next.
What Makes a Commitment Well-Governed
A well-governed commitment has five properties. Most organizational commitments have none of them in practice.
Traceable. You can retrieve what was committed, when, by whose authority, and on what evidence. The commitment is not reconstructed from memory and email — it is a first-class artifact, accessible to anyone who needs to understand it or act on it.
Reasoned. The assumptions behind the commitment are explicit. When a commitment needs to be revisited, you know what would justify revising it — because the reasoning that justified making it was preserved alongside the commitment itself.
Aligned. The commitment was understood consistently across the parts of the organization that need to act on it. The engineering team, the sales team, and the finance team are all operating from the same understanding of what was committed and what it implies for their work.
Monitored. Someone or something is watching whether the conditions that made the commitment sensible still hold. Drift is visible — not reconstructed after the fact from its consequences, but detected while there is still time to act.
Revisable. There is a governed process for updating the commitment when it needs to change. Revision is explicit, authorized, and recorded — not ad hoc, not informal, not the quiet death of a decision nobody will admit was wrong.
The Missing Abstraction
The history of enterprise software is a history of successive abstractions. Each abstraction reduced the cost of something that previously required significant organizational capacity.
Databases abstracted storage — organizations no longer had to manage where data lives physically or build custom filing systems for every domain.
ERP abstracted operations — organizations no longer had to build the integrated infrastructure for running finance, procurement, inventory, and manufacturing from scratch.
Workflow engines abstracted process — organizations no longer had to code the movement of work through an approval chain or cross-functional handoff for each new business requirement.
AI assistants abstract individual cognition — an individual no longer has to do all information synthesis, drafting, and analysis alone.
The missing abstraction is the governance of organizational commitment — the infrastructure that makes commitment formation, tracking, and revision something the organization does not have to rebuild from scratch in every domain, for every decision, every time.
That infrastructure does not exist as a mature category today. Organizations assemble partial solutions: documents record some commitments, CRMs track some customer-facing commitments, project tools track some delivery commitments, boards approve some strategic commitments. None of these systems are connected. None of them preserve reasoning. None of them monitor drift. None of them support revision with a clear record of what changed and why.
The result is that the most consequential thing organizations do — make and keep commitments — is the thing for which they have the least adequate infrastructure.
The Implication
If organizations are commitment-making machines, then the relevant questions about organizational health change.
The question is not "are we productive?" — productivity is in service of commitments. The question is: are the commitments we make well-formed? Are they based on adequate evidence? Are they understood consistently across the organization? Are they monitored? When they need to change, do they change explicitly and with a record?
The question is not "are we innovative?" — innovation produces new commitments. The question is: do we have the organizational capacity to make commitments we have not made before? To enter a new market, to launch a new product, to acquire a new company? Capability — the fifth friction — is specifically this: the organization's ability to expand the space of commitments it can credibly make.
The question is not "is our AI useful?" — AI is in service of commitments. The question is: does it reduce the uncertainty and coordination cost that make commitment formation expensive? Does it help the organization identify when commitments have drifted from reality? Does it preserve the reasoning behind commitments in a way that improves future decisions?
Organizations have always been commitment-making machines. What changes, in each technological era, is the cost of making commitments well.
Core thesis: A company exists because people can make commitments together that none of them could make alone. Every organizational friction is, at its root, a commitment problem. The idea you can't unsee: Customers don't buy products. They buy commitments. Vocabulary shift: "are we productive?" → "are our commitments well-formed?" Connects to: Article 1 (The Organization as an Adaptive System), Article 2 (The Physics of Organizations), Article 3 (The Adaptive Cycle) Version: 1.0 / 2026-07-06