Team Training & Knowledge Base Creation
Turn scattered tribal knowledge into a resource new hires can actually use on day one
Every agency has a knowledge problem
Ask a new hire where to find “how we structure a paid social report” or “what our brand voice actually sounds like,” and the honest answer at most agencies is “ask Priya” or “it’s somewhere in Slack from eight months ago.” That’s not a training failure — it’s a knowledge-capture failure. The SOP work from Lesson 9 covers processes; this lesson covers everything else new hires need: context, judgment calls, and the reasoning behind decisions that never made it into a document.
Capture judgment, not just steps
An SOP tells someone what to do. A knowledge base entry tells them how to think about a situation that doesn’t have a clean checklist. These are different documents with a different prompting approach — you want Claude to preserve the reasoning, not compress it away.
I want to write a knowledge base article for new account managers
on "how to handle a client who's upset about missed deadlines."
This doesn't have a fixed script - it depends on judgment. Let me
explain how I actually think about it, and turn my explanation
into an article with a clear structure: the situation, the
principles to weigh, 2-3 realistic examples with different
outcomes, and common mistakes to avoid. Keep my reasoning intact -
don't flatten it into a rigid 5-step process it isn't.
Here's how I think about it: The first thing I always figure out
is whether we actually missed the deadline or the client's
expectations were never aligned with the real timeline in the
first place, because the response is totally different depending
on which one it is. If it's genuinely on us, I don't make excuses...Structure the library so people can actually find things
A pile of well-written articles nobody can locate is barely better than no library. Organize by the situation someone is in, not by department — a new hire searches “client is angry,” not “account management philosophy.”
| Category | Example entries |
|---|---|
| Client situations | Upset client, scope creep request, client going quiet, renewal conversation |
| Service delivery | How we structure a paid social report, our SEO audit process, brand voice do’s and don’ts |
| Internal operations | How to request time off, our project management tool basics, who owns what |
| Tools and templates | Where the proposal templates live, how to access the shared asset library |
Tip: After you draft several articles, ask Claude to generate a short FAQ-style index — one line per article, phrased the way a confused new hire would actually search, not how a manager would file it.
Use it for onboarding, not just reference
A knowledge base pays off fastest when it becomes the backbone of new-hire training rather than a reference nobody opens until week six. Ask Claude to sequence your articles into a first-two-weeks reading order, paired with real (redacted, per Lesson 3) examples from actual client work.
Using the 12 knowledge base articles I've written (titles listed
below), build a two-week onboarding reading plan for a new account
manager. Sequence them from foundational to situational, roughly
1-2 articles per day, and suggest which ones pair well with a
shadowing session rather than solo reading.
[list article titles]Key principle: The test of a knowledge base isn’t how complete it looks — it’s whether a new hire’s first “can I ask you something?” question three weeks in is genuinely novel, not something already answered in an article they never found.
Watch out: Knowledge base articles often reference real client situations for realism. Apply the same redaction discipline from Lesson 3 — anonymize client names and specifics unless the example is generic enough not to need it.
Build it: Pick one judgment call you’ve explained verbally to more than one new hire (a client-handling situation, a pricing edge case, anything without a clean checklist). Draft it using the first prompt above.