Why this lesson exists. The previous lesson drew the line around what a shared knowledge base must not contain. This lesson builds the thing itself: a small, organised set of documents that gives the model (and every new hire) your company's context every time, so nobody has to paste the about page into every conversation again. This is certification part 1.
By the end of this lesson you will be able to write the first three pages of a second brain, because you will have seen what a new starter's first day looks like with and without one, and then written yours.
Without a knowledge base. A new account manager starts on Monday. She spends the week asking questions: what do we actually sell, what is the difference between the Business and Enterprise plans, how do we describe ourselves to a housing association versus a training company, why did we stop offering the mobile app, what tone do we use with customers. Each answer comes from a different person, some of them out of date, two of them contradictory. On Friday she writes her first customer email and gets it gently corrected by three colleagues, differently.
With a knowledge base. Same person, same Monday. She is pointed at seven short pages: who we are, what we sell, who we sell to, how we sound, how we work, what we have decided, what has changed. She reads them in an hour. On Tuesday she writes her first customer email, and it is right, because the pages told her the price, the positioning and the tone, and the "what we have decided" page told her why the mobile app is not on offer. The AI tool she uses to draft it had read the same seven pages, so its draft was right too.
Nothing clever happened. Somebody wrote down what everyone already knew, once, in one place.
The term comes from personal productivity, where it means an external store for your own notes. For a business it means the company's shared memory, written down so that both people and AI tools can use it. It works for the reason Lesson 1 gave: the model is only as good as what it can see, and a second brain is a permanent, curated answer to "what should the model see about us?" Point the model at it (attach it, load it into a skill, or connect it as a source) and every conversation starts with a colleague who has read the manual.
A good one is boring. Plain documents, each answering one question, short enough to read in a few minutes, dated, and linked to each other:
Who we are. Company, founders, mission, what you sell in one paragraph.
What we sell. Products, plans, prices, what is and is not included.
Who we sell to. Customer types, the problems they have, the objections they raise, the words they use.
How we sound. Tone, words you use, words you avoid, three examples of writing that sounds like you.
How we work. The steps for the things you do repeatedly: onboarding a client, closing the month, handling a complaint.
What we have decided. Decisions with dates and reasons. The most neglected and most valuable page, because it stops the model (and the team) re-opening settled questions.
What has changed. A short log of facts that are no longer true. Lesson 7 explains why this page matters more than it looks.
Fewer, better pages beat many half-right ones, because every page is something the model will treat as true.
You need somewhere easy to write in, easy to organise, shareable with the right people and not the wrong ones, and readable by your AI tools. When using it for AI, it doesn't want to be in PDF's or other proprietary formats that the AI has to scan or perform expensive actions to get to the information.
Merve works particularly well, and not only because this is a Merve course. Its Libraries are designed for exactly this shape of content: a browsable, organised set of resources with rich text, files and video, gated so only invited people can see it. The draft-and-publish workflow means you can quickly draft an update to a page and publish the update once it's ready. Progress reporting shows who has actually read the onboarding material. And because it is hosted in the UK/EU with GDPR-compliant handling, you are not creating a new privacy problem while solving a knowledge one. If your team already trains customers on Merve, keeping the internal second brain in the same place means one system to maintain instead of two.
Some alternatives are: Notion or Obsidian. However, we've personally found Notions connectors to be a bit hit and miss. Obsidian is recommended and we do use this internally, but it's quite a steep learning curve for those non-technical.
It's recommended when working with AI tools to stick with .md (markdown) files and formats, they are simple, lightweight, can be used by almost any digital product, and the AI tools natively create markdown files. Merve pages are exactly that, markdown files that have additional attachments if needed.
