Company Wiki

Company Wiki is the single place a new hire opens on day one. SOPs, playbooks, onboarding paths, post-mortems, org chart, tool list. Not buried in a Slack search, not scattered across Google Docs, not locked in one founder's head.

You type a question into the workspace, Claude answers from the wiki itself, and links the source page. The team reads the wiki instead of DMing the founder the same five questions every quarter.

Most wikis fail for the same reason. Someone writes 40 pages in the first month, nothing gets updated, and by month four the content is wrong enough that people stop trusting it. Then they go back to Slack search.

Company Wiki is built around maintenance, not first write. Every page has an owner and a review date. A view shows pages past their review date. The owner gets pinged when the date passes. The wiki stays correct because staying correct is someone's job on the dashboard, not an afterthought.

Three databases. Pages holds every SOP, playbook, and reference doc with owner, review date, and tags. Onboarding Paths holds ordered page sequences for each role. Post-mortems holds incident write-ups, linked to the pages they updated.

Ask the workspace any question and Claude searches the Pages database first, surfaces the three most relevant, and cites them. No hallucinated answer. The source page is always linked.

The wiki is not a weekly ritual, it is a background process. New hires open their onboarding path on day one and check off pages as they read them. Existing team members open the wiki when they have a question. Claude answers inside the workspace.

Every Friday, the ops lead opens the "Pages past review date" view. Owners update their pages or archive them. The wiki stays alive because stale pages get flagged, not left to rot.

The first failure is everyone writing pages, nobody owning them. Six months in, ops has to archive 60% of the workspace. Fix: every page requires an owner property on creation. Unowned pages cannot be published.

The second failure is onboarding paths that skip the politics. New hires learn the tools but not who to ask for what. Fix: every onboarding path includes a "People and how they work" page, not just a tool list.

The third failure is search that returns the wrong answer. Fix: Claude answers only from the Pages database, with the citation visible. If the cited page is wrong, the owner gets an update task.