A name on the page is not a finished check
One row per name. Leave the result cell empty until you have an action you could fail.
Read the guide ↗THE READING LIST
Field guides
Useful methods, clear examples, and references you can follow.
A name on the page is not a finished check
One row per name. Leave the result cell empty until you have an action you could fail.
Read the guide ↗A named connector is not a finished link
A launch post can name nine firms. A name on the post is not proof the connection works.
Read the guide ↗Write acceptance checks before handing off a brief
Turn each promise in a brief into a check with a starting state, an action and an observable result, and keep it apart from implementation instructions.
Read the guide ↗Put the out-of-scope line in the brief
A brief can be checked only when it says what the work will not do, in the same place as the promise.
Read the guide ↗Write a brief that can be checked
Connect a small user goal to explicit boundaries, concrete examples and a review record that preserves open questions.
Read the guide ↗Make the outcome something you can observe
Replace broad promises with a starting condition, a specific action and a result a reviewer can inspect.
Read the guide ↗Check the boundaries of a promise
Choose useful failure and edge cases, document the reason for each and keep untested risks visible.
Read the guide ↗A structural rubric for fictional project briefs
A reproducible eight-check run across six deliberately varied fictional briefs, with the fixtures, results and chart available for inspection.
Read the guide ↗