What is offered?
Book companion
Product
Product names the promise-bearing offering, not merely the app, screen, workflow, or service counter.
What is someone invited to rely on?
What changes when the product says done?
Exercise
Apply it before abstracting it.
Describe the offering without naming the interface first. Then write the relied-upon promise in one sentence.
A companion page should produce a usable artifact: one signal, one promise, one carrier, one proof standard, one betrayal risk, and one repair owner.
- Best input
- A recent case, customer-facing status, support label, AI answer, approval, or handoff.
- Best output
- A one-page review that another person can understand without hearing the whole theory first.
- Stop condition
- If the team cannot name proof or repair ownership, that is the finding.
Worksheet
Download the companion worksheet.
Use the worksheet to make the concept portable. It should survive being forwarded to someone who has not read the book yet.