Přejít na obsah
Peak Atlas

Peak Docs · Use case · Knowledge base

One source for
team knowledge.

A knowledge base your team trusts: wiki pages, search, one valid version per topic and answers straight from the document. Explained with a made-up example.

Which change do you want to check?

Your next review briefExample · question collection

Answers sit in chats, folders and heads. Collect the ten questions the team asks most often. They are the first pages of your knowledge base.

You can take the brief with you at the end of the page. The original evidence stays open.
See the structure
For
Growing B2B teams
Example
Made-up consulting team
Stav
Use case · no customer story
Dossier · demo template

Find instead
of asking.

Original evidence pending
  1. 01Scattered
  2. 02Organised
  3. 03Maintained

A real story starts with its release.

The starting point

Knowledge nobody finds gets asked for again every day.

A knowledge base in Peak Docs consists of wiki pages with subpages, a library with views and search, and one authoritative version per topic. In every document, “Ask this document” answers questions from its content. Answers across several documents are planned.

Customer release still open

This pattern shows the structure. It doesn't tell a real customer case yet.

Starting point → change → evidence

The path to change

A knowledge base in three stages.

  1. Scattered knowledge

    Answers sit in chats, folders and heads. Collect the ten questions the team asks most often. They are the first pages of your knowledge base.

    A list of the most common questions
    Evidence format · not filled in yet

    The starting point.
    In the original.

    Original excerpt

    Insert the released passage here.

    A / ObservationWhich concrete friction is visible in this source?
    Example · question collection

  2. Organised pages

    Create a start page and hang topics below it as subpages. Before you write a new page, Peak Docs looks for a matching document and points out possible duplicates.

    A wiki with a start page and topics
    Evidence format · not filled in yet

    One step.
    Traceable.

    BeforeOriginal processSource evidence required
    ChangeConcrete interventionProduct view and date required
    Example · wiki navigation

  3. Maintained knowledge

    Each page has an owner. Freshness signals show where something may be outdated, and backlinks show which documents point to a page.

    Pages that stay current
    Evidence format · not filled in yet

    The result.
    With a yardstick.

    Observation
    Not evidenced yet
    Period
    Open
    Source & release
    Pending

    Without released data this statement stays open.

    Example · page with freshness signal

What can be evidenced

How you notice it gets used.

The evidence is still pending

No customer results. You can tell the knowledge base works when the same question shows up in chat less often.

Space for a released perspective.
The sculpture does not depict a customer.
Room for a real voice

One perspective.
With name and release.

No released customer quote on file.

Beyond the single case

What keeps a knowledge base reliable.

  1. Start with the most common questions

    Ten good pages help more than a hundred empty headings. The knowledge base grows with every question asked twice.

    Key idea

    Start small and useful

  2. One page per topic

    Flag the authoritative page as canonical and link to it instead of copying content. That way there are no conflicting versions.

    Key idea

    Link instead of copy

Sources & context

What this article is based on.

Editorial use case with a made-up sample team, not a customer story and no measured values. Wiki pages, the library with views and search, find-or-create, duplicate detection, the canonical flag, backlinks and “Ask this document” exist in Peak Docs today. AI answers across several documents are planned.

  • Editorial demo

    Editorial example with made-up sample data. It describes features Peak Docs has today; everything else is marked as example, concept or planned.

  • Evidence pending

    No released Peak Docs customer story. No customers, quotes or results are shown.

The next step

Your knowledge base starts with one question.

Create a wiki start page in Peak Docs and answer the question you get asked most.

Start Peak Docs for free

Frequently asked questions

How do I avoid duplicate pages?

Peak Docs detects likely duplicates and lets you mark one document as canonical.

Can I import existing content?

Partly: Markdown and plain text can be imported, other formats cannot.

Can external guests read along?

Guest access is planned. Today you can share single pages with a read-only link.

More in Peak Docs