Regeneration as Operating System

The question beneath the questions

It changed how I looked at companies. A company can grow while exhausting its people, meeting targets while slowly depleting judgment, attention, creativity, and trust. The dashboard can look healthy while the human system underneath is becoming brittle.

Food looked different too. A food system can produce volume while damaging soil, weakening nutrition, and distancing people from the sources of life that sustain them. It can be efficient in logistics and still extract from the biological system that makes food possible.

AI raised the same question in newer clothing. AI can optimize output while eroding human judgment, attention, accountability, or resource discipline, and a model can make work faster while leaving people less able to understand what is happening. Automation can remove friction and also remove the moments where responsibility used to live.

Capital completed the pattern. Capital can scale activity while demanding the wrong rhythm, accelerating useful work or forcing a system to grow faster than trust, adoption, soil, people, or markets can mature. These are not separate issues. They are system issues.

The SuperCIO and the New Enterprise Mandate ended with governed intelligence: as enterprises become intelligent systems, leadership must learn to govern capability, authority, accountability, infrastructure, data, risk, and human judgment as one connected architecture. That remains true, and governance alone is not enough. Governance asks whether intelligence can be controlled responsibly. Regeneration asks what that intelligence is serving.

That became the deeper question for me.

Reserves no one is measuring

I did not arrive at regeneration through ideology. I arrived there through systems. I had spent enough years watching systems succeed and fail to know that performance can hide depletion for a long time, because a system may appear strong while it is extracting from reserves no one is measuring.

People can be the reserve, and so can soil, community trust, institutional memory, founder energy, ecological health, and capital patience.

When those reserves are depleted, the system begins to lose coherence, sometimes slowly and sometimes suddenly, and the loss was usually being prepared long before it became visible. This is why regeneration began to matter to me, as operating discipline rather than sentiment. Regeneration names what narrow optimization leaves out.

Optimization asks how to improve the output of the system, and that question has value. I have spent much of my life working on it, and better planning, better infrastructure, better reliability, better decisioning, better software, and better platforms are real contributions. Optimization becomes dangerous, though, when it forgets the source.

A farm can optimize yield while losing soil health, a company can optimize revenue while burning out its people, a platform can optimize engagement while degrading attention, a supply chain can optimize cost while weakening resilience, an AI system can optimize task completion while obscuring accountability, and a venture model can optimize growth while misaligning time, trust, and maturity.

That question returned me to soil, and not as nostalgia. Soil was where the first lesson began. A crop grows visibly while the real conditions are often underneath, in moisture, organisms, roots, minerals, time, care, and season, and if those conditions are depleted, growth may continue for a while while the future is being weakened. The same pattern appears in companies, in AI, in capital, and in communities.

Five domains, starting with the self

This is where the Regenerative Prosperity Model began to take shape for me. I call it RPM because it needed to be more than an idea. It had to become a way of reading systems and building companies, helping ask whether value creation was increasing or depleting the capacity of the system that produced it.

RPM has five domains: Self, Nature, Community, Design, and Capital. I do not think of them as a decorative framework, a poster, or branding language. They are the domains through which a durable system must be examined.

Self comes first because the builder is part of the system, and this took me years to understand. In earlier seasons, I thought primarily about the systems I was building: products, platforms, companies, infrastructure, decision workflows. Over time, especially through the hard season at Quantiply, I learned that the founder’s inner condition affects the company’s outer behavior.

A founder carrying too much pressure can transmit that pressure into the system, a leader who cannot listen prevents learning, a leader who confuses intensity with clarity can create motion without coherence, and a leader who is depleted may keep performing while losing judgment. Self is not a private wellness category detached from work. It is operational.

The condition of the builder shapes the condition of the company. This is uncomfortable because it removes the illusion that leadership is only external. The system is also inside the leader, in attention, fear, ambition, patience, humility, energy, ego, trust, and the capacity to absorb truth. If the self is depleted, the company eventually feels it.

Nature is the second domain because all value finally rests on living systems. For me, this begins with soil, and soil is not a metaphor alone. It is biological infrastructure, carrying life through processes too complex to reduce to a spreadsheet, responding to care, depletion, weather, biology, chemistry, and time.

Modern systems often forget this because they are far from the field. Software can make distance feel clean, finance can turn living processes into abstractions, and logistics can make food appear as inventory, while the body still depends on nourishment, food still depends on soil, and soil still depends on life. A food system can produce abundance while weakening the very source of abundance. That is not efficiency. It is delayed failure.

Nature in RPM means soil, ecology, biology, water, climate, health, and the living systems that sustain value before value becomes economic, and it asks whether the system returns capacity to life or only extracts from it. This does not make regeneration anti-technology. Quite the opposite: technology becomes more important when it learns to serve living systems with humility, and AI, sensors, data platforms, traceability, decision infrastructure, and markets can all help regenerate soil, improve food systems, strengthen health, and align incentives. Technology must be placed in service of life, not above it. That distinction matters.

Community is the third domain because no durable system is built from transactions alone. Community means trust, belonging, stakeholders, reciprocity, and shared prosperity. A company may have customers, employees, suppliers, investors, and partners and still lack community in any meaningful sense, because the relationships may be transactional, fragile, and extractive. When pressure comes, those relationships reveal their quality.

I learned this in factories, partnerships, enterprise sales, and founder life. Work moves through relationships, and trust determines how quickly truth travels. When trust is strong, people can surface problems early, adapt, and carry difficulty together. When trust is weak, people hide, delay, defend, or protect themselves locally while the larger system suffers.

Community is not softness. It is resilience. A system with strong community can absorb shocks differently, learn faster because people are willing to tell the truth, distribute value more responsibly because stakeholders are visible, and build longer-term trust because people experience the system as something they belong to rather than only something they are used by.

In food and agriculture, community includes farmers, families, local economies, consumers, and the trust between what is claimed and what is true. In AI, community includes the people affected by decisions, beyond those deploying the model. In venture creation, it includes founders, teams, customers, investors, and the ecosystems that support them. Community asks whether prosperity is shared deeply enough to endure.

Design is the fourth domain because systems behave according to what we build into them. Products, platforms, workflows, incentives, governance models, user experiences, and operating rhythms all shape behavior, and a system may declare one set of values while rewarding another. When that happens, behavior follows the design, not the declaration.

I saw this again and again. A factory planning system had to reflect real work or people would create workarounds, a cloud platform had to align incentives or teams would continue hoarding capacity, a risk intelligence system had to fit workflow or recommendations would remain unused, and an AI system has to embed accountability or it will create speed without trust.

Design is where intention becomes structure. This is why regeneration cannot remain a belief. It has to be designed into products, ownership models, metrics, decision rights, incentives, feedback loops, and governance, or the system will continue behaving according to the old operating logic while using new language. Design asks whether the architecture of the system makes the desired behavior likely.

Capital is the fifth domain because capital sets rhythm, and this was one of the hardest lessons of company-building. Capital is not only money. It is time, pressure, expectation, ownership, optionality, and obligation, and the rhythm of capital shapes the rhythm of the company, affecting hiring, product decisions, sales pressure, risk appetite, founder psychology, and the ability to wait for trust to mature.

Capital can be regenerative when it strengthens the source of value, helping build capacity, fund patient work, align incentives, share upside fairly, and support companies through the period when important systems are still becoming legible. Capital can also become extractive when it demands a pace the system cannot honestly carry.

I do not say this as a rejection of venture capital. I have raised capital, I have depended on it, and I understand its power, because capital can enable work that would otherwise remain impossible. Capital has to be designed with rhythm in mind, though. The wrong rhythm can damage a good thesis. The right rhythm can give a company time to mature into its market. In RPM, capital asks whether ownership, return, reinvestment, and responsibility are aligned with the life of the system.

These five domains are connected. Self affects leadership, leadership affects design, design affects community, community affects trust, trust affects capital, capital affects time, time affects nature, nature affects life, and life affects the meaning of prosperity. None of these domains stands alone.

That is why I think of regeneration as an operating system. It is a way of reading what a system depends on, what it depletes, what it strengthens, and what it returns.

From language to operating discipline

For 451 Ventures, this became central. The next era needs companies that are AI-native, trust-native, and regeneration-aware: AI-native because intelligence is becoming part of how companies sense, decide, act, and learn, trust-native because intelligent systems will fail adoption if they cannot be explained, governed, monitored, and held accountable, and regeneration-aware because intelligence and trust are incomplete if the system still depletes the people, communities, soil, and sources of life it depends on.

This is not a pitch. It is the operating conclusion of the journey. After years in infrastructure, enterprise systems, cloud, big data, AI, risk intelligence, and venture-building, I could no longer separate performance from source. A company that scales while exhausting its people is not fully healthy, a food system that produces volume while damaging soil is not fully efficient, an AI system that optimizes output while eroding trust is not fully intelligent, and capital that accelerates activity while destroying the conditions for durable value is not fully productive.

Regeneration gave me a language for what those systems were missing, and it changed how I thought about venture creation. A venture is not only a product, a market, and a team. It is a system of relationships among founders, customers, employees, investors, partners, communities, technologies, and sources of value, and if that system is designed only for speed it may outrun trust, while a system designed only for extraction may consume the very capacity that made it promising.

The question becomes: how do we build companies that return capacity?

Capacity to the founder and not only pressure, to the team and not only tasks, to the customer and not only features, to the community and not only transactions, to soil and health and not only yield and volume, and to capital as durable value and not only short-term return.

This is difficult work, requiring tradeoffs, measurement, product discipline, governance, patience, capital partners who understand time, and founders who are willing to examine their own operating condition as seriously as their market opportunity. It is much easier to use regeneration as language than to build it into operations, and that is why I keep returning to discipline.

Regeneration is not decoration. It must enter the way decisions are made. The questions are practical: what we measure, what we reward, what we ignore, who carries the burden, what source we are drawing from, what happens when the system scales, and what is returned. They belong in boardrooms, product reviews, AI governance meetings, investment committees, farm planning, food systems, healthcare, and company-building, wherever systems claim to create value.

The question I carry forward

The older I become, the more I see that the first lessons were already there. The field taught that growth depends on conditions, the circuit that behavior depends on pathways, the factory that software must serve work, the city that infrastructure must earn public trust, the database that institutions need memory, cloud that infrastructure shapes economics, big data that information needs sensemaking, AI that decisions need governance, and company-building that vision needs rhythm, trust, and stewardship.

Regeneration gathered these lessons into a more honest question. Can the system perform without depleting what makes performance possible?

That is the question I now carry into 451 Ventures. It is why the next chapter could not simply be another company. It had to become the company after the career, a vessel for building from the full curriculum rather than from ambition alone.

For now, I can say this much. Regeneration did not take me away from systems building. It made the systems question more honest, and it became the language for a responsibility I had been circling for years: build systems that perform while returning capacity to the people, places, and sources of life they depend on.