The Physics of Purpose
Why missions need metabolism, not monuments.
One of the patterns I’ve noticed over a career designing, operating, and renewing large IT managed services engagements is that they rarely end discussing the same questions they began with.
They begin with business outcomes, transformation, modernization, and a shared vision of the future. Five years later, at renewal, the conversation is often about service levels, pricing, benchmarks, governance models, and contractual obligations. None of those things are wrong. In a mature operating relationship, they matter enormously. The problem is what happens when they become the whole conversation.
Somewhere over the life of the contract, the relationship starts optimizing around the things that are easiest to measure. The original mission may still exist in a strategy deck. Everyone may still be able to recite the transformation ambition that justified the deal in the first place. But the day-to-day decisions are increasingly shaped by the dashboard, the SLA report, the benchmarking exercise, or the renewal model.
The market data backs up that lived experience. ISG recently described this as “the incumbents’ disadvantage”, noting that in Q1 2026, new-scope managed services annual contract value was up 20% year over year while renewal and extension ACV was down 24%. In a 2013 sourcing white paper, ISG reported that the non-incumbent win rate on competitive restructuring and renewal deals stood at 59%. Once the work goes competitive, the incumbent is not protected by familiarity. Incumbency becomes evidence to be overcome.
I’ve watched this happen enough times that I used to think of it as simply the lifecycle of outsourcing. Transformation becomes operation. Operation becomes governance. Governance becomes commercial negotiation. By the time renewal arrives, the incumbent may still be delivering the contract, but the conversation has drifted away from the business purpose the contract was created to serve.
For a long time, I treated that as a familiar pattern in large operating relationships. Recently, though, I’ve started to wonder if it is only one visible example of something more fundamental.
The catalyst was Gizmodo’s article, “The New Meta for Silicon Valley Startups Is Nihilism”.
The startup itself wasn’t really what interested me. What caught my attention was the philosophy the article described: the idea that growth, winning, and optimization are the only objectives that really matter. Mission, values, and purpose become little more than branding.
My reaction surprised me. I expected to disagree. I didn’t expect to feel genuine disgust. Whenever I have that kind of visceral response, I’ve learned not to trust the emotion. I trust the investigation instead.
The first place I landed was Goodhart’s Law, often summarized this way:
“When a measure becomes a target, it ceases to be a good measure.”
It is one of those deceptively simple observations that explains an enormous amount about organizational life. Companies begin with a purpose and create metrics to understand whether they are making progress. Over time, the metrics begin to replace the thing they were supposed to measure. Revenue replaces customer value. Engagement replaces meaningful interaction. Velocity replaces craftsmanship. Service levels replace business outcomes.
Metrics are not the enemy. Without metrics, organizations can’t learn. They can’t improve. They can’t tell whether effort is turning into progress. The danger begins when metrics stop serving judgment and start substituting for it.
Most organizations don’t consciously abandon their mission. They drift.
At first, I thought Goodhart’s Law explained everything that bothered me about the article. Then I realized the startup philosophy being described was not drifting toward Goodhart’s Law at all. It appeared to begin where Goodhart’s Law often ends, treating the metric not as a proxy for the mission but as the mission itself.
That is why the nihilism bothered me. It was not merely purpose drift. It was purpose drift declared as strategy.
That observation stayed with me because, around the same time, I had been wrestling with a very different version of the same problem.
Over the past year, I have been building what I call the Fellowship: a small team of AI agents that help with research, infrastructure, writing, operations, and continuous improvement. The challenge was not getting them to produce work. AI systems are increasingly good at producing work. The harder challenge was keeping that work coherent, useful, and connected to the purpose of the system as the loops got faster.
That takes attention.
The Fellowship does not stay aligned because I described its mission once. It stays aligned because I keep paying attention through standups, peer reviews, retrospectives, memory maintenance, goal reviews, prompt refinements, and the occasional uncomfortable intervention when an agent starts optimizing the wrong thing.
The interesting part is that I did not invent those practices for AI.
I borrowed them from human teams.
The Fellowship looks the way it does because it is modeled on the healthiest organizational practices I have seen over decades of leading teams, designing operating models, and helping large enterprises transform. Human teams need standups because work drifts. They need retrospectives because assumptions decay. They need memory and documentation because context disappears. They need peer review because individual judgment is fallible. They need goals because activity and progress are not the same thing.
I modeled the AI team that way because it is what I know from experience. At first, I thought I was simply applying familiar leadership practices to a new domain. Then it hit me that those practices were not just management techniques. They were mechanisms for continuously reconnecting a system to its purpose.
That is where the physics first clicked for me.
One common entropy formulation of the Second Law of Thermodynamics is that the total entropy of an isolated system never decreases over time. Organizations are not thermodynamic systems in the literal sense, and I am not suggesting they are. The point is not to force physics onto management theory.
The useful insight is simpler: order does not maintain itself.
Entropy gave me the first metaphor. But metabolism may be the better one.
Living systems are not isolated systems. They stay organized because they continuously do work. Cells repair themselves. Immune systems patrol. Forests regenerate. Bodies metabolize energy. Memory is consolidated and pruned. The work of staying alive is never finished.
Perhaps healthy organizations work the same way.
We write a mission statement, polish the language, put it in the strategy deck, and assume the act of declaration will somehow preserve the purpose. Then we are surprised when, five years later, no one can explain why the company exists beyond making this quarter’s numbers.
But maybe that should not surprise us at all. A mission statement is an artifact. It is not a metabolism.
Purpose does not persist because it has been declared. It persists because the organization keeps doing the work required to remain connected to it.
That is what I now see in the Fellowship. The daily standup is not overhead. The retrospective is not bureaucracy. The goal review is not ceremony. The memory pruning is not housekeeping. These are the system’s internal stewardship mechanisms. They are how the team resists drift.
The same is true for human organizations. Strategy reviews, customer listening, architectural governance, retrospectives, coaching, documentation, decision reviews, and cultural rituals are not distractions from the work. Done well, they are the work that keeps the work connected to purpose.
Once I started looking through that lens, I saw the pattern everywhere. Engineering teams accumulate technical debt. Knowledge bases accumulate stale information. Cultures accumulate compromises. Leadership teams accumulate blind spots. Managed services contracts accumulate operational habits that slowly detach from the original business case. Every optimization solves a local problem while potentially increasing the distance between what the organization does and why it exists.
We already have a name for one version of this pattern in software: technical debt.
There is also a related concept called organizational debt: the structural friction that accumulates when teams defer hard decisions about roles, processes, ownership, or operating models. That idea is useful, but I think what I am describing is narrower and sharper.
Purpose Debt is what accumulates every time an organization optimizes for a metric without reconnecting that optimization to its mission.
Like technical debt, purpose debt does not appear all at once. It accrues quietly through hundreds of locally rational decisions. A sprint ships. A quarterly target is met. A service level is achieved. A renewal strategy is optimized. A process becomes more efficient. An AI agent gets faster. Every decision makes sense in isolation. Collectively, they can create distance between what the organization does and why it exists.
The encouraging part is that purpose debt can be repaid. Not through another mission statement. Not through an annual off-site. Not through a consultant arriving from outside with a new framework and a better slide deck.
Purpose debt is repaid through stewardship.
Through the continuous practices that reconnect people, teams, contracts, systems, and increasingly AI agents to the reason they exist in the first place.
That is what Silicon Valley nihilism gets wrong. It mistakes the honesty of abandoning pretense for the wisdom of abandoning purpose. It looks at performative mission language and concludes that mission itself is fake. But that is too easy. The harder, more useful conclusion is that purpose has to be practiced or it decays.
This feels especially important now because AI is accelerating the speed of optimization. Agents do not wait for quarterly business reviews. They do not naturally pause to ask whether the metric still represents the mission. They execute. They improve. They compress cycle time. They make the optimization loop faster.
That is powerful. It also raises the cost of neglect if the stewardship loop does not accelerate with it.
The future does not need more laminated missions. It needs organizations with internal mechanisms for renewal. Teams that revisit their goals as often as their metrics. AI systems that are not merely aligned once, but continuously realigned through memory, reflection, review, and correction. Contracts that do not wait until renewal to rediscover the business purpose they were meant to serve.
Because organizations do not fail because they stop optimizing.
They fail because they forget what they were optimizing for.
And missions do not fail when people stop believing in them.
They fail when they are laminated and hung on a wall.