Outcome 01
Shared intuition
Product managers recognize the gaps a requirement leaves open and know which ones produce defects no check can catch.
ObservableGiven a requirement, learners name the decision it avoids before proposing a solution.
301-PExecutable intent
Write specifications that can be built, evaluated and signed.
Diagnose what a requirement fails to decide, write criteria that carry their own evidence, bound the scope, survive independent ratification, then hold the product claim to the evidence that exists.
- Stages
- 9 225 minutes, a half day
- Fixture
- Payments The same Round 0 the engineers read
- Claims held
- 2 Product intent and scope, outcome acceptance
The practice225 minutes
01
Diagnosewhat the requirement does not decide
Stage 102
Specifycriteria that carry their own evidence
Stages 2 and 303
Boundscope and decomposition
Stages 4 and 504
Ratifyindependently, or record the objection
Stage 605
Decidethe policy no check can choose
Stages 7 and 8Stage 9 needs a facilitator-supplied outcome signal the room has not seen. Stage 8 is strongest run jointly with engineers on course 301, who escalate the same policy gap from the same fixture.
Learning outcomes
What these stages
should change.
The stages succeed when practitioners recognize the same risks, describe them in the same words and change what they do before approving work.
Outcome 02
Common language
Product and engineering describe criteria, evidence types, limits and unresolved policy with the same words.
ObservableLearners state what a clean evaluation run does and does not support, using the same evidence types the engineers use.
Outcome 03
Everyday habits
Before work starts, product managers write criteria with evaluation paths, bound the scope and submit the spec for independent ratification.
ObservableLearners produce a ratifiable specification for an unfamiliar outcome without the stage worksheets.
The learning path
Seven stages.
One decision each.
Each stage adds one decision and produces an artifact the next stage works from. Preparation happens before instructional time.
··010203040506070809››
Prepare
Sibling repository: ../payments-validation-fixture. Complete this before the first stage.
Diagnose the requirement
Read the product spec and the outcome signal, then decide what the requirement does not settle, ranked by the cost of shipping without an answer.
Separate outcome from solution
Rewrite the intent as an outcome hypothesis: the signal, the affected users and the business condition that should change, without naming a mechanism.
Write executable criteria
Turn the hypothesis into acceptance criteria where each one states observable behavior and carries an evaluation path.
Bound the scope
State what this slice does not do, so scope creep becomes a visible specification decision rather than an invisible delivery one.
Decompose so it survives Plan
Write the specification so it decomposes into four to eight file-scoped tasks, and split it when it does not.
Survive ratification
Submit the specification for independent ratification, then revise it until it is accepted or every objection has an owner and a date.
Read the evidence
Read the Round 0 evidence bundle the engineers read, and state what it lets you claim to a customer.
Receive the escalation and decide
Take the F8 escalation, make the policy decision, and state what it changes downstream.
Specify an unfamiliar outcome
Take an outcome signal you have not seen and produce a ratifiable specification, without the stage worksheets.
The workbench
Eight classes of AI mistake and the six types of evidence
Current versus V1
The fixture today is not the V1 target.
The target sequence is explicit about what exists now, what the new stages require and where delivery is still blocked.
The current fixture exposes diagnose, plan, validate and report. validate executes the workflow and report summarizes its evidence. Results may appear before Stage 2 method selection.
diagnose → review → eval → define → plan → run. Review methods are chosen before results are shown; define writes defects/*.md; plan writes tasks.json; run creates the next diff. Stage 7 is blocked until the unseen assessment change exists.
Where this sits
Before and after
these stages.
Tracks at the same number are peers on the same fixture. The 501 assumes both of them.