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 guideA PRACTICAL PUBLICATION FOR THOUGHTFUL MAKING
A little clearer.
A lot more buildable.
Good work begins with a shared understanding. Make the goal clear, name the boundaries, and turn an idea into examples someone can actually check.
Build an acceptance briefNo account. No automatic saving. A working copy you can keep.
01
Name the user goal
02
Describe the conditions
03
Make the result observable
THE OPENING COLLECTION
From a rough request
to a shared understanding.
Three guides. One reproducible study.
Files and worksheets worth keeping.
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 guideA 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 guideWrite 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 guidePut 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 guideWrite 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 guideMake 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 guideCheck the boundaries of a promise
Choose useful failure and edge cases, document the reason for each and keep untested risks visible.
Read the guideA 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 guideA WORKBENCH, NOT A BLACK BOX
Your words.
A clearer agreement.
The builder organizes a goal, constraints and up to eight acceptance cases. Review a live brief, then keep a Markdown or JSON copy.
It checks required fields and length limits. You decide whether the examples describe the right thing to build.
Open the criteria builderA SMALL EDITORIAL PROMISE
Make assumptions visible. Keep expectations separate from observations. Leave a record someone else can follow.
Read our editorial standards