Product walkthrough

The evidence.
The decision. The outcome.

Synthetic example · read-only
This is an authored preview of the intended experience. No system is connected and no decision can be submitted.

Engineering delivery EXAMPLE-014

Illustrative work request

Improve the reporting dashboard empty state

SYNTHETIC
Illustrative next step: review the planA person decides whether the scope is appropriate.

Proposed scope

A bounded, useful outcome.

Replace an empty table with a short explanation and a link to create the first report. Preserve existing permissions.

Resources
Example repository: northstar/reports
Change boundary
Empty-state view and its tests
Proposed outcome
A draft pull request for human review
Outside scope
Production data, permissions, merge and deploy

What the reviewer would see

Questions before permission.

  • Does the request have clear acceptance criteria?
  • Are the affected resources and side effects understood?
  • Which checks will independently verify the result?
  • Is the evidence current enough to make a decision?
In the connected product, a decision will require an eligible identity, a reason, the current context and an expiry.

Start with one useful workflow

What would a good
first outcome look like?

Choose a bounded use case, name the human decisions and define the evidence you would need.

Plan your pilot ↗