Prodigent

Product Knowledge Base

What belongs in a product KB — and what should live somewhere else.

A product knowledge base is not a dump of every Google Doc ever written. It is a curated, connected layer of what matters for building: decisions, rationale, user evidence, and initiative history.

Belongs in product KB

  • Decision records with alternatives
  • Initiative snapshots and scope history
  • Tagged user feedback and research themes
  • Open questions and their resolution
  • Links to designs, tickets, and external docs

Belongs elsewhere

  • API reference (developer docs)
  • HR policies (company wiki)
  • Raw meeting recordings without summary
  • Duplicate PRD copies per squad

Standing up a product KB

  1. 1

    Start from decisions

    Backfill the last quarter's major choices — highest ROI content.

  2. 2

    Link initiatives

    Group knowledge by what you are building, not by document type.

  3. 3

    Ingest feedback continuously

    Capture from Slack, support, and interviews into the same stream.

  4. 4

    Make search the primary UI

    If people cannot find it in 30 seconds, it does not exist.