0487 058 065 Book a session

Start here · fixed scope

Knowledge-base pilot: one product area, and the defects hiding in it.

Pick the part of your product nobody can fully explain. In about four weeks we capture what it does, check it against what the business intended, and review the result with your product owner. You get five reconciled capabilities, every open question with an owner, and the places where the code disagrees with the intent. From $15,000 + GST.

What you get

Documentation that pays for itself in week two

On our reference platform the first thirty capabilities surfaced ten divergences between intent and code before any reviewer looked, including shipped defects. The pilot runs the same method on your product, on a scope small enough to judge.

  • Five capabilities written as cited, versioned rules, readable by the business and by engineers
  • Open questions with owners, so gaps are closed rather than guessed at
  • Divergence findings: where the code and the intent disagree, with the evidence, for a person to decide
  • A review session with your product owner, and their answers fed back into the base
  • A scoping report for the rest of the product: capability count, effort and order

The four weeks

Capture, reconcile, review, hand over

  1. Step 1

    Week 1 · Capture

    Code, tests, tickets, wiki and the people who know the area, mined into one structured base.

  2. Step 2

    Week 2 · Reconcile

    Behaviour checked against intent; agreements confirmed, disagreements raised as findings.

  3. Step 3

    Week 3 · Review

    Your product owner answers the open questions and confirms or rejects each finding.

  4. Step 4

    Week 4 · Hand over

    The base, the findings and the scoping report for the rest of the product, in your repository.

Fixed scope

From $15,000 + GST

Five capabilities in one product area. Larger areas or more sources (several repositories, a test-management system, permission matrices) are quoted after a short call; the upper end is $25,000.

The base lives in your repository from day one. Nothing leaves your systems.

  • About four weeks
  • Read-only access to code, tickets and documents
  • About three hours of your product owner's time
  • 50% to start, 50% at hand-over

Questions

Which area should we pick?
The one that generates the most questions, incidents or arguments: a pricing engine, an approval flow, a permissions model. The pilot is most convincing where the knowledge is most contested.
Will it find defects in our product?
We cannot promise a count, and we would not trust anyone who did. What we can say is that every reconciliation compares what the business intended with what the code does, and on every product we have run it on, some of those comparisons disagreed.
What happens to the base after the pilot?
It is yours, in your repository, with the tooling to keep it current. Most clients continue with the full knowledge base across the product; some run the next areas themselves with our support.
Does our documentation have to be good already?
No. The base is derived from the code and from the people who know the product; existing documentation is one source among several, and the pilot tells you how much of it was still true.

Related

The knowledge base

The full capability, across the whole product.

 Case study: the knowledge base

Ambiguities resolved, development three times faster, defects found before customers.

 Readiness assessment

When you want the whole picture before choosing an area.

Which part of your product can nobody fully explain?

Book a free 30-minute call and tell us. We will say whether it is a good pilot, and what it would show.

Book a free call Call 0487 058 065
Call Book a call