Pressure-test the method's decision rules
Stress-tests a drafted method's decision rules against edge cases and counter-scenarios, surfacing ambiguities and mis-routing risks.
In / outDraft method skeleton → stress-test findings with ambiguous rules, under-specified steps, and mis-routing cases identified
You might say…
“A method that only works when you wrote it isn't transferable. This is the test that finds out if someone else could follow the rules.”
What it does
Takes a drafted method and stress-tests its decision rules and sequencing against edge cases and counter-scenarios, surfacing where the rules are ambiguous, under-specified, or would mis-route. Used after a skeleton exists, before the method is declared transferable to a producer who did not invent it.
Trigger: Use after a method skeleton exists and before the method is declared teachable to producers who didn't invent it.
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation