Decision record
The choice, the reasoning, the owner, the options dropped and the review date, at a glance.
SLATEPATH / PRODUCT TOUR
Follow one product decision from start to finish
Follow a fictional but concrete "bulk export" request and see how a team turns scattered feedback into a decision with evidence behind it and a date to revisit it. Read-only: nothing you do here is saved.
WORKSPACE / PRODUCT DECISION 024
Should bulk export make next quarter’s roadmap?
Context: support tickets and renewal calls keep mentioning export limits, while engineering is weighing permissions and audit requirements. Below is a read-only sample decision; the customers and numbers are illustrative.
| Status | Decided · review pending | Decision owner | Head of Product |
|---|---|---|---|
| Involved | Engineering / Support / Data | Review | 30 days after CSV ships |
Scope
This round only decides whether to offer a minimal export. Full audit trails, fine-grained permissions and automated sync are not part of this commitment.
Inputs received
| Source | Evidence | Still unknown |
|---|---|---|
| Support tickets | Export comes up again and again | Whether demand is concentrated in a few large teams |
| Renewal interviews | Some teams want to keep a decision archive at handover | Whether CSV is enough for a handover |
| Counter-examples | Small teams find the current manual process acceptable | Whether usage will grow |
The records and roles are illustrative; what matters is how the strength of evidence and the counter-examples are kept, not the numbers.
From input to decision: four traceable steps
- 1
Collect inputs
Support, renewal interviews and counter-examples sit side by side, each with its source and uncertainty. Votes never stand in for judgment.
- 2
Compare options
A: full bulk export, broad but costly. B: CSV first, to test the most common use. C: API only, relying on customers to build on it.
- 3
Write down the trade-off
Choose B and solve the most common handover need first; full audit is not promised yet. Record why the other options were dropped and the known risks.
- 4
Set a review
30 days after CSV ships, look at usage, ticket volume and audit feedback, then extend, expand or close the decision.
What the decision leaves behind
Evidence trail
Tickets, interviews and counter-examples all lead back to their original context, so nobody has to rely on memory when the conclusion changes.
Follow-up work
CSV export, usage tracking and audit interviews each have an owner and a definition of done.
Review point
In 30 days, decide again with new evidence instead of leaving an old decision on the roadmap forever.