Knowledge Base Creation

A structured wiki from zero. Four page types (SOP, playbook, onboarding, post-mortem), each with mandatory properties: owner, review date, role tags, status. You drop existing docs in, tag them, and the wiki is live. Every new page inherits the shape automatically.

Most wikis are a dumping ground. Everyone writes, nobody owns, pages drift, the team loses trust. This template enforces ownership on creation. No owner, no publish. The wiki stays correct because staying correct is somebody's job, not an afterthought.

One database. Pages holds every SOP, playbook, onboarding path, and post-mortem with owner, review date, role tags, and status. Views: By role (what a marketer reads), By type (all SOPs), Past review date (staleness), Unowned (governance), Recently updated.

You set up the four page templates with their required fields. Existing docs get imported and tagged. New pages have to pick a type on creation and fill the required fields before saving. The wiki lives. Every Friday, the ops lead clears the Past review date view.

The first failure is properties that are optional. Optional means missing, missing means unowned, unowned means stale. Fix: owner and review date are required on create.

The second failure is too many types. Seven page types that nobody remembers. Fix: four types, maximum. If something does not fit, it becomes a subpage of one of the four.