A handbook, not a folder of documents.

Articles nest into the sections your business actually has. Anyone can write, the people who own a subject decide what lands, and finding something takes a search rather than asking whoever has been here longest.

PeopleHow leave is approvedDraftPublish
In the handbookUnder Peoplenot a folder
FindableBy meaningnot by title
OwnedBy a personnot a department
Priya is on leave next week. It does not matter.
Somebody writes itThe answer stops living in one person

The thing only Priya knows becomes an article in four minutes, and the next person who needs it does not have to find Priya.

Writing

Four things that decide whether anybody uses it.

A wiki fails on habit, not on features. These are the four places that habit is won or lost.

Write it the way you would write it anywhere.

A plain editor with headings, lists, tables, images and code. No syntax to learn and no template to fill in, because an article somebody had to fight to write is an article that does not get written.

In an article

  • Formatting that survivesHeadings, lists and tables, not a wall of text
  • Images and filesA screenshot beats three paragraphs
  • Links between articlesSo one answer can point at the next
Why it gets used

It is in the tool people already have open.

A wiki in a separate product gets read in the first week and never again. This one is beside the deals, the tickets and the chat, so looking something up is not a decision to go somewhere else.

Where it shows up

  • In searchAlongside records and files
  • In chatWhen somebody asks a question your team has answered before
  • In the chat on your websiteAnswering the same question for a customer

See Wiki on your own data.

Half an hour. Bring the ten questions your team asks most and watch the chat start answering them.