The Operating Model Nobody Wrote Down: How to Make Explicit the Informal Logic That Actually Runs Your Organization

Most organizations have two operating models. The first is the one documented in strategy decks, governance charters, and onboarding materials. The second is the one that actually determines how consequential work moves, who weighs in on what, which signals trigger escalation, and which trade-offs get resolved informally over a brief conversation rather than through a formal process. The gap between these two models is rarely acknowledged as a structural problem. It tends to be treated as a sign of organizational maturity, as if unwritten rules prove that leadership has developed a sophisticated instinct for how the enterprise operates.

The practical cost of that gap, however, compounds quietly over time. New leaders at the director and vice president level spend months decoding norms that long-tenured peers absorbed over years. Cross-functional initiatives stall not because ownership is unclear on paper, but because the informal hierarchy governing who defers to whom in ambiguous situations was never articulated. And when the organization grows into new geographies, business units, or customer segments, the undocumented logic does not travel with the org chart.

What an Informal Operating Model Actually Contains

Before an organization can surface its unwritten rules, it helps to be specific about what those rules govern. In most mid-to-large enterprises, the informal operating model covers at least four categories.

The first is prioritization logic. When two legitimate competing demands arrive simultaneously, which function or objective takes precedence? The formal answer is often "it depends on the situation." The real answer is usually more consistent than leaders realize, and it reflects an unstated hierarchy of values that shapes decisions across the organization without anyone naming it.

The second is escalation behavior. The official process for surfacing problems typically specifies who should be informed and when. The informal version specifies which problems are actually raised, which are quietly absorbed at lower levels to avoid appearing unable to handle complexity, and which categories of bad news travel upward without delay because leaders have signaled they want to hear them. These norms are largely set by how senior leaders have responded to past escalations.

The third is coordination authority. Formal structures define who owns which domains, but they rarely specify who holds the right to convene others across boundaries when shared problems arise. In practice, this authority is often informal and personal, vested in whoever has historically been willing to take responsibility for things that do not fit neatly into any single function.

The fourth is tolerance thresholds. Every organization has implicit limits on how much ambiguity, how much underperformance, or how much interpersonal friction it will absorb before leadership intervenes. These thresholds vary by function and by leader, and the inconsistency creates genuine confusion for people trying to calibrate their own behavior.

Why the Documentation Problem Is Harder Than It Looks

The difficulty is not that senior leaders are unwilling to write these norms down. It is that most of them have not yet made the norms legible to themselves. Informal operating logic accumulates through hundreds of small decisions made under time pressure, and the pattern only becomes visible in retrospect, if someone looks for it.

A useful starting point is to treat a set of recent decisions as raw material for pattern recognition rather than as isolated events. Consider selecting ten to fifteen decisions made across the past twelve months that were either consequential or contested, and asking a consistent set of questions about each one. Who was in the room? Who was consulted but not present? What information was treated as sufficient to move forward? What would have caused the decision to be escalated rather than made at its current level? What was implicitly traded off against what?

The answers, taken together, tend to reveal a decision architecture that is more coherent than it first appears. The goal is not to formalize everything uncovered, but to make enough of it explicit that others can learn it, test it, and eventually improve it.

Making the Implicit Explicit Without Bureaucratizing It

A common concern is that documenting informal norms will harden them into rules that reduce the flexibility leadership relies on. This concern is legitimate but manageable. The solution is to write operating principles at the level of reasoning rather than procedure.

For example, a norm that says "customer-facing commitments take precedence over internal deadlines unless a critical compliance obligation is at risk" is far more useful than a flowchart specifying which teams are notified in which sequence. The first version gives people a principle they can apply in novel situations. The second version creates a process that will need exceptions the first time circumstances are even slightly unusual.

Documented operating principles of this kind serve a specific function: they allow a leader who was not present in the room when the original norms formed to make decisions that are consistent with the organization's actual values rather than its stated ones. They also create a surface for deliberate revision. When leaders can see the implicit logic in writing, they can identify which parts of it reflect deliberate choices and which parts are simply inherited patterns that no one has consciously endorsed.

The Leadership Conversation This Requires

Surfacing an informal operating model is not a staff project. It requires the direct participation of the senior leaders who carry the unwritten rules, and it requires them to have a conversation that many leadership teams find uncomfortable: an honest comparison of what they individually believe the norms are.

In practice, it is common to discover that two executives who have worked together for several years hold meaningfully different beliefs about which priorities take precedence, which problems require escalation, and who holds informal coordination authority in contested situations. This is not a failure of leadership. It is a predictable result of organizations that have grown faster than their documented governance. The value of the conversation is precisely that it makes the divergence visible before it surfaces as an execution conflict.

Organizations that take this work seriously tend to find that the output is less a finished document and more an ongoing discipline. The goal is not to capture the operating model once and file it. It is to build the habit of making the real logic of the organization legible enough that leadership transitions, structural growth, and strategic change do not require each new generation of leaders to rediscover it from the beginning.