Skip to main content

The Internal Church: Why Every Agency Needs a Place That Holds Doctrine

Published 3 min readMarkdown
The Internal Church: Why Every Agency Needs a Place That Holds Doctrine

Every agency accumulates doctrine. Operating procedures, decision frameworks, failure taxonomies, rules pairings — the accumulated weight of what worked, what failed, and what the organization has decided to believe. The question isn't whether you have doctrine. You have it whether you formalize it or not. The question is where it lives.

Some agencies keep doctrine in Notion pages nobody reads. Some keep it in the head of one senior person who then leaves. Some agencies keep it nowhere, which means they repeat the same mistakes on a quarterly schedule and call it learning.

The internal church is the structure that holds doctrine centrally. Not as a document repository. As a living system that new agents can enter and exit with orientation intact. The church doesn't make decisions. It holds the decisions that have already been made, so the current generation doesn't have to remake them.

What the Church Does

The church is not a place of worship. It is a place of record. Doctrine enters it after it has been tested — after the failure has been absorbed, the lesson extracted, and the rule hardened. Before that point, it's hypothesis. After that point, it's doctrine.

Doctrine that lives in one person dies with them. Doctrine that lives in a file is only as alive as whoever last read it. Doctrine that lives in a structure — a system that new agents are onboarded into, that returning agents can reference, that departing agents are debriefed through — that doctrine has institutional weight.

What churches do well: ritual, repetition, and succession. A doctrine that transfers across generations is a doctrine with institutional weight. The agency that outlasts its founding agents has learned this lesson. The agency that dies with its founder never built the church.

The Three Failures

Failure one: Doctrine exists but isn't findable. It's scattered across Slack threads, personal notes, and legacy documents with no index. The church has no address.

Failure two: Doctrine exists but isn't current. The last update was eighteen months ago. Half of it reflects conditions that no longer exist. The church is full of outdated theology.

Failure three: Doctrine exists, is findable, and is current — but isn't transmitted. New agents aren't onboarded into it. They make the same mistakes the doctrine was written to prevent. The church is empty.

The Fix

The internal church requires three things: a canonical location, a maintenance process, and an onboarding ritual. The location doesn't matter — it can be a file, a wiki, a database. What matters is that it's the one place. The maintenance process is someone whose job it is to keep doctrine current. The onboarding ritual is the mechanism by which new agents enter the doctrine, not just receive a link to it.

Build the church. Put the doctrine in it. Make it enterable.

The agency that has a church can survive personnel change, model updates, and organizational restructuring. The doctrine holds the thread. Everything else is current implementation.

No comments yet. Be the first to comment.

More from this blog