AI makes it effortless to produce a strategy deck, a training guide or a forty-page plan. That’s the problem. When anyone can create a slightly different version of what the company believes, and agents act on whichever one they were given, the scarce thing isn’t content. It’s agreement.
Most of what a company knows lives in slide decks, meeting recordings, chat threads and people’s heads. It was always hard to keep aligned. Two things just made it harder. Anyone can now generate a polished forty-page version of the strategy overnight. And agents now do real work based on whatever context they were handed, which means an outdated version of the goals doesn’t just confuse a person; it quietly steers a system.
People also need to understand why the agents do what they do. If employees can’t see the reasoning, they can’t spot when it’s wrong or suggest something better.
I’ve been building internal deep-dive articles to help a team learn a product, its customers and its domain, and AI makes that material far better than it used to be. It also made me notice the opposite problem: when everyone can generate their own version, nobody is sure which one is real.
The ideaKeep one approved version of everything the company has decided. Teach it to people in formats they actually retain, in their own language. Sync it automatically to every agent’s skills, and ship every change like a release, with the reasoning attached. Encourage pushback on the approved version rather than new versions of it. And put a governor on new content, so creating another version is a deliberate choice.
Anyone who has worked in a growing company knows this week. The CEO stays up late and writes a new strategy deck. Sales has its own version for the board meeting. Someone makes a “final” with slightly different priorities. Each is reasonable. Together they mean nobody is quite sure what was decided.
Switch to see the copies collapse into one approved version, with the audience-specific versions linked to it rather than competing with it.
When people did most of the work by hand, the pace itself was a safety net. There were meetings every week, and a wrong assumption got caught before it went far. Agents remove that net. An engine running on the wrong goal, an outdated persona or an old pricing rule doesn’t drift slowly. It goes the wrong way at full speed, across hundreds of decisions, before anyone notices, and every one of them has to be undone.
That makes approved knowledge more precious than it has ever been. It’s no longer background reading. It’s the steering.
Illustrative. Distance from the intended direction over a quarter. Press play.
A Ferrari pointed the wrong way doesn’t get you there sooner. It gets you lost faster.
Company knowledge comes in two sizes. Deep dives teach: who the customer is, how we sell, how we build, what the market looks like. Atoms decide: one position, one sentence, with an owner, a status and a date. “We don’t offer on-premise deployment.” “Our primary buyer is the operations lead, not IT.” Deep dives are built from atoms, so when an atom changes, the deep dives that use it know.
Search or pick an entry to see the full atom. Every approved atom has one owner and one current version.
Here’s the mechanism that matters most. When an owner approves a change, it shouldn’t be announced in a meeting and hoped for. It should flow, automatically, to every place people learn and every place agents work.
The quarter’s top goal changes from “grow new logos” to “expand within existing accounts.” Press publish.
If approved knowledge steers the engine, a change to it is a production release, and it should be handled like one. Nothing should shift quietly overnight so that an agent starts making different choices and nobody can say why. Every change gets release notes: what changed, why, everything it touches, and which skill versions move.
The reasoning travels with the change. People read it in the release note; agents read it in the updated skill. So when an agent does something differently, both the person watching it and the agent itself know what changed and why.
Expansion revenue grew fastest last quarter, and retention economics beat new-logo acquisition at our stage. Two dissenting comments from sales were answered on the atom.
Sales, customer success, marketing and product. A two-minute update video in six languages, a one-page brief per role, and two quiz questions on days 1, 4 and 15.
| sales-playbook | 3.4.0 → 3.5.0 | Prioritizes expansion plays in account plans |
| account-research | 2.1.2 → 2.2.0 | Flags expansion signals first |
| marketing-content | 1.8.0 → 1.9.0 | Customer stories over acquisition campaigns |
| product-context | 4.0.1 → 4.1.0 | Goal and bets updated |
Each skill re-ran its evaluations before release. Each carries a short note explaining the change, so agents apply the reasoning, not just the rule.
The same logic behind a governor on AI spending, and a budget on how much product change customers can absorb, applies to internal content. We don’t need more of it. We need the right version of it.
A knowledge server that every agent can reach, using the Model Context Protocol, can sit quietly behind anything anyone creates. When a question matches approved knowledge, it guides people to that version. When a new deck would duplicate an approved one, it says so.
Just as valuable is what it learns from the questions it can’t answer. Every unanswered question is a signal. When the same one keeps coming up, from people or from agents asking for clarification, it becomes a request for new knowledge, routed to the owner who should decide it.
Pick a request. The responses come from the approved library, not from a model’s guess.
Creating a new version should be a decision, not an accident. “Why does this need to exist, and does it change the original?”
Publishing isn’t the same as people knowing. Everyone is busy, and a long document is easy to skip. AI helps here too: the same approved knowledge can become a short article, a narrated walkthrough in each person’s native language, an interactive explainer, a quiz and a one-page brief for each role, without anyone rewriting it five times.
There are two kinds of training, and both matter. Onboarding teaches the whole picture: customers, product, strategy, how we sell and build. Updates teach what changed and why, in two minutes, every time a knowledge release ships.
The research on memory is clear about one thing. Rereading feels productive and fades quickly. Being asked to recall something, a little later, and again a little later after that, is what makes it stay.
Highlighted formats are the primary one for each. Every piece also gets a short quiz and a “what this means for your role” brief.
Roediger and Karpicke, 2006.
Spaced check-ins after a changeTwo questions each, in the tools people already use.
Approved knowledge is a living thing, and keeping it right is everyone’s job. A locked version isn’t a gag order; it’s the thing to push against. If something is outdated, wrong, or overtaken by new information, people are expected to say so.
What changes is how. Not by ignoring the approved version and writing a new forty-page one, but by pointing at the specific part you disagree with and saying why, or how to make it better. The owner answers. The approved version either changes for everyone, through a knowledge release, or the reasoning for keeping it is written down where everyone can see it.
Too much central control turns a knowledge base into a bureaucracy, and people route around it. Approval has to be fast and owners have to answer pushback, or “locked” starts to mean “ignored.” Generated videos and quizzes can be confidently wrong, so the owner reviews what’s generated from their atom. Not everything should be locked; early thinking needs room to be messy. And a server that watches what people create has to be clearly about helping them, never about surveillance.