Let me tell you about a document I've met at almost every agency I've ever worked with.

It's called Renewal Process FINAL.docx. There is also a Renewal Process FINAL v2.docx, and a Renewal Process FINAL v2 (USE THIS ONE).docx. Nobody knows which one is current. Everybody knows it isn't any of them.

Here's what happens when a new hire opens it. Step 4 says to click a button that hasn't existed since the last Applied Epic update. Step 7 references a carrier the agency stopped writing with in 2023. Step 11 just says "ask Carol."

So the new hire asks Carol. Carol explains the real process in ninety seconds, flawlessly, because Carol has done it four thousand times. The new hire asks whether the document could be updated. Carol laughs — not unkindly, just the laugh of someone who has been asked that in three consecutive annual reviews — and says she'll get to it.

Carol will not get to it. Carol is the most interrupted human being in that building.

The Part Our Industry Is Sleepwalking Into

Carol retiring is a slow problem. You can see it coming. What you can't see coming is Tuesday.

Because the agency that had one system now has fourteen. An AMS, a rating tool, a comparative rater, a payments platform, an e-signature tool, a data-enrichment thing somebody bought at a conference, two carrier portals that count as platforms now, a CRM, a texting tool, and whatever got added last quarter to "streamline" something.

Every one of those vendors has a product team. Every one of those product teams ships changes. Constantly. And every change quietly rewrites part of how your agency actually works.

You know the email. "We've improved your experience!" Which is vendor for: the button moved, the field is now required, that export is gone, and there's a new screen between the two screens your workflow assumed were adjacent.

Nobody at the agency reads that email. Why would they? It's one of nine vendor emails that week. But the workflow it just broke is the one your service team runs eleven times a day.

So here's the actual math. Documentation used to decay at the speed of your own agency changing its mind. Now it decays at the combined release velocity of fourteen software companies who have never heard of you and are not going to call first.

You are not maintaining documentation. You are maintaining documentation downstream of fourteen roadmaps — and you're doing it with Carol, who has a day job.

That's not a documentation problem. It's an operations problem wearing a documentation costume.

So This Month We Went After Maintenance

The idea: the conversation you already have about a process should be the thing that updates it. You hold the review meeting you were going to hold anyway, walk the guide with the people who actually do the work, and the update comes out of that conversation. A human approves every change before it publishes. We took the expensive part — spotting what drifted and rebuilding the document without breaking it — off Carol's plate.

And when someone hits a surprise mid-process, which is exactly how most vendor changes get discovered, they flag it right on the guide. It lands in that guide's queue. No ticket, no email thread, no "I'll mention it at the next meeting," which is where good intentions go to die.

Also Shipped This Month

The Boring Foundation

Every agency I talk to has an AI initiative. Most are about to point a very expensive chatbot at the FINAL v2 (USE THIS ONE) folder. Garbage in, confident garbage out — at scale, and in a lovely font.

The real foundation is a library that's accurate this week, with a cheap way to keep it accurate next week. While your vendors keep shipping. That's the whole game.

So which is closer: your Carol retiring, or your next vendor update?