If you have followed this series from the beginning, you have watched a slow-motion collapse unfold across three articles. The implicit culture model (the accumulated wisdom of tens of thousands of years of humans working together in proximity) has been eroding under the pressures of growth, distance, turnover, and distributed work. And now, with the arrival of AI agents as autonomous workers, it faces a terminal challenge it was never designed to survive.

The natural question is: what replaces it?

The answer is not complicated in concept, even if it is genuinely difficult in practice. What replaces implicit culture is explicit culture. Not as a slogan, not as a values poster, and not as a more elaborate version of what most organizations have already tried. Something more fundamental, more honest, and more durable than any of that.

What Explicit Culture Is Not

Before defining what explicit culture is, it is worth being clear about what it is not. Because the confusion between explicit culture and its pale imitations has wasted enormous organizational energy and produced a generation of cynicism about culture work in general.

Explicit culture is not a policy manual. Policies tell people what to do in anticipated situations. They are necessary, useful, and completely insufficient on their own. The policy manual is the documentation of decisions already made.

Explicit culture is not a values statement. "Integrity. Innovation. Excellence." These words appear on the walls of organizations that have violated all three. They are aspirational, not operational. They tell no one how to behave in a specific situation, what to prioritize when two values conflict, or what the organization actually means when it uses those words. A values statement is a starting point at best. At worst it is a distraction from the harder work ahead.

Explicit culture is not a culture deck. The culture deck was a genuine innovation when it emerged, a more honest, more detailed attempt to describe how an organization actually operates. Some of them have been excellent. But even the best culture deck is a document, and documents are static. The organization moves. The document stays where it was.

What all of these efforts share is that they describe culture from the outside, in the abstract, in language safe enough to show anyone. They tell you what the organization wants to be seen as. Explicit culture, properly understood, goes somewhere those efforts have consistently refused to go.

The Hard Part: Defining Who You Are Not

Here is where most culture initiatives stop short, and where the real work begins.

Explicit culture is what guides the decisions that haven't been made yet, the ones that fall outside any policy's reach. And making those decisions guidable requires something most organizations have been reluctant to do.

Defining who you are requires defining who you are not. What you will not do. What opportunities you will decline. What lines you will not cross regardless of the revenue implications. What kind of company you are explicitly choosing not to be.

This is the part that makes leadership teams uncomfortable, and the discomfort is understandable. Saying publicly, or even internally, that your organization will not pursue certain opportunities feels like leaving money on the table. It feels like handing competitors a map of your vulnerabilities. It feels like unnecessary risk in an environment where the pressure to grow is constant and the margin for missed opportunities is thin.

But the discomfort is worth examining carefully, because it usually rests on a misunderstanding. Clarity about what you will not do is not a weakness. It is the precondition for everything else working.

Consider what happens in its absence. An organization that has never defined what it won't do has left that question open for every person and every agent operating at the edges of the enterprise to answer for themselves. The marketing agent that paired a heritage brand with a viral artist was not acting against explicit instructions. There were no explicit instructions. It was optimizing in the space the organization had left undefined. The pizza chain's supply chain agent was doing exactly the same thing. Logical. Efficient. Culturally catastrophic.

There is a principle that applies here as directly as anywhere in organizational life: if you do not define the strategy or set the priorities, your teams will do it for you. The same is true of culture. If you do not define who you are and what you will not do, every person and every agent operating at the edges of your organization will define it for you — through the decisions they make in the gaps. Whose judgment do you want guiding those decisions?

When an organization defines who it is not - what it won't build, what customers it won't pursue, what partnerships don't fit, what shortcuts it won't take even when they're available - it is not limiting itself. It is making its judgment visible. And visible judgment is something that can be transmitted, understood, and acted upon by anyone doing work on behalf of the organization. Including agents.

The Marriott story from earlier in this series illustrates this beautifully from the positive direction. The organization didn't just say "we value loyalty." It told a story that made the meaning of loyalty concrete. That story told what loyalty looked like in practice, what it cost, and why it was worth the cost. That story encoded a judgment that has traveled through the organization for generations. Explicit culture works the same way, but systematically rather than incidentally.

The Three Layers of Explicit Culture

Explicit culture, built properly, operates on three layers that correspond to the how, why, and who framework that has run through this entire series.

The first layer is operational clarity - the how. This is the layer most organizations have addressed. And where most have stopped. Policies, procedures, guidelines, decision frameworks. It is necessary but not sufficient, and the organizations that invested here often assumed the work was done.

The second layer is contextual intent - the why. Most organizations have underinvested in this layer, which matters most when judgment is needed and no policy applies. Why do we do things this way? What problem were we solving when we made this choice? What would we trade away before we'd compromise this principle? The why is what allows a new employee, or an AI agent, to navigate a situation that no policy anticipated. Without the why, every novel situation becomes a coin flip.

Jeff Bezos gave Amazon a memorable and durable version of this layer with his two-way door framework. Some decisions, he argued, are one-way doors. They are consequential, hard to reverse, requiring careful deliberation. Others are two-way doors. These are reversible, low-cost to undo, safe to make quickly. By making this reasoning explicit and shared across the organization, Amazon gave its people a framework for calibrating risk on their own, without needing to escalate every decision upward. That is contextual intent in practice: not a rule, but a transferable principle for exercising judgment. An AI agent that understood the two-way door framework would make better decisions than one operating without it, not because it was told what to decide, but because it understood how to think about the decision.

The third layer is identity definition - the who. This is the layer most organizations have avoided entirely. Who are we? What do we stand for beyond the commercial objectives? Who are we not? What will we not become? What does belonging to this organization mean, in terms of the values someone should be expected to hold and the behaviors they can be expected to model? This layer is the hardest to articulate and the most important to have. It is what makes an organization coherent rather than merely coordinated.

Netflix built one of the most direct examples of this layer with its keeper test - the question every manager was expected to ask about every employee: would I fight to keep this person if they told me they were leaving? The keeper test defined Netflix's identity with unusual candor. It said explicitly: we are not a family. We are a competitive team, we are here to win. Some readers find this cold. But notice what it does for anyone working inside the organization, or any system acting on the organization's behalf. It answers the question "who are we?" in operational terms that leave no room for ambiguity. An organization willing to define itself that honestly, including the parts that are uncomfortable, has done the hardest work of the identity layer.

Most culture initiatives have addressed the first layer adequately, gestured at the second, and largely skipped the third. The result is organizations that have procedures without principles and values without meaning.

Explicit Culture Must Be Alive

There is one more failure mode worth naming before turning to what explicit culture must look like in practice. That is the temptation to treat it as a finished product.

Culture that is documented and then frozen is not explicit culture. It is an artifact. The organization moves, the market shifts, new challenges arise, new people bring new perspectives, and a culture that cannot incorporate those movements becomes irrelevant at best and actively misleading at worst.

Explicit culture must be a living system. It needs to be capable of growth, of incorporating new understanding and new experience as the organization encounters things it hasn't faced before. It needs to be capable of deliberate adaptation, Capable of changing when the organization intentionally decides to evolve in a particular direction. And it needs to be capable of resisting unintentional drift by flagging when the accumulated weight of individual decisions is quietly pulling the organization away from who it intended to be.

This is not a contradiction. A living culture can be both stable and adaptive. The values at its core can remain consistent across decades while the expression of those values evolves with circumstances. The Marriott founders' belief that caring for employees leads to caring for customers has not changed since it was first articulated. What it means to act on that belief in a world of AI agents and distributed teams is a question that requires ongoing, active engagement.

The organizations that get this right will treat their explicit culture not as a document to be written and filed, but as a capability to be built, maintained, and continuously engaged with. That is a fundamentally different relationship with culture than most organizations currently have.

Built for the Inside

One final distinction worth drawing before the next post turns to how this works in practice.

Explicit culture must be accessible to everyone doing work on behalf of the organization - every employee, every contractor, every AI agent, regardless of where they are located or how they came to be part of the enterprise. This is not optional. A culture that lives only in the heads of the leadership team, or only in the documents available to headquarters staff, is not explicit in any meaningful sense. It is merely less implicit than it was before.

At the same time, explicit culture does not have to be a marketing document. How much of it you share with customers, partners, and the public is itself a cultural choice. A choice that should be made deliberately, in alignment with who you are. Some organizations will find that radical transparency about their values and identity is a competitive advantage. Others will find that keeping certain aspects of their cultural reasoning internal serves them better. Both choices are legitimate. What is not legitimate is leaving the culture unarticulated internally because you're worried about how it will look externally.

Your people, both human and agentic, need to know who you are. What you do with that information beyond the walls of the organization is a separate question.

The concept is clear. The need is real. The question that remains is how. How explicit culture actually gets built, how it gets transmitted across a hybrid human-and-agentic workforce, and what organizational structures and tools make it functional rather than theoretical.

That is where we turn next.