System 6 of 6
Culture & Continuity
Make promises and knowledge survive pressure and absence.
Culture & Continuity is the operating system that ensures client promises, operating knowledge, decision routines, and critical workflows survive pressure, turnover, vacation, illness, disaster, and key-person absence. Its test is simple: does the agency keep behaving like itself when the person who built it is not in the room?
Who feels it, and how
- Critical knowledge — carrier quirks, client history, renewal routines — lives in one person's head.
- Quality and follow-through visibly dip when the owner travels.
- A single resignation would take an entire workflow's knowledge out the door.
- “How we treat clients” is real but unwritten, so new hires absorb it slowly or not at all.
- There is no tested answer to “what happens if the owner is out for a month?”
The mechanism
Culture and continuity fail silently because they are only tested by absence and pressure — exactly the moments when no one is watching the gauges. Undocumented knowledge concentrates in tenured people as a byproduct of normal work; every year it compounds, and so does the key-person risk. Under pressure, teams revert to whatever is written down and trained; if nothing is, they improvise, and the agency's promises drift client by client.
What to measure
Single-point-of-failure inventory. List critical workflows and mark each one that only a single person can run. The count of unmarked workflows is your continuity coverage.
Documentation currency. Share of critical procedures with a written version updated within the last review cycle — checked by having someone else actually run from the document.
Absence rehearsal results. What degraded during the last planned absence (vacation counts)? Each degradation is a continuity finding with a name and a fix.
Common misreads
- “We're small, everyone knows everything.” Usually one person knows most things — smallness concentrates key-person risk rather than removing it.
- Treating documentation as a someday project instead of a per-workflow countermeasure with an owner and review date.
- Assuming culture is safe because tenure is long. Long tenure often means the culture has never been written down — because it never had to be.
Countermeasures to test
- Build the single-point-of-failure inventory and fix exactly one exposure per month — document, cross-train, verify by absence test.
- Have the backup person run the documented procedure while the primary watches silently; fix what the document missed.
- Write the client-promise standards — response times, review cadence, tone — so “how we do it here” survives hiring.
- Schedule deliberate absence rehearsals instead of waiting for illness to run the test for you.
A worked example
Before a two-week vacation, an owner picks the three workflows only they can run, documents each, and assigns a trained backup with explicit escalation triggers. The vacation itself becomes the test. Two workflows hold; the third generates a queue that maps precisely to a missing decision rule. That gap — not a general “we need more documentation” resolution — becomes the next month's single countermeasure.
If the data is missing
If the agency has never listed its single points of failure, the exposure is Unknown — which for this system is the riskiest label of all, because the test that reveals it (unplanned absence) arrives on its own schedule. Build the inventory first.
Frequently asked
Where do we start when everything is undocumented?
With the single-point-of-failure inventory, not with a documentation blitz. Rank workflows by damage-if-absent, and fix one per month with a named owner and an absence test. Steady beats heroic — a blitz produces binders nobody verifies.
Is this only about the owner?
No. Any role whose absence would break a critical workflow is a continuity exposure — a veteran CSR's carrier knowledge can be as concentrated as the owner's. The inventory treats every workflow the same way.