Define Failure Conditions
Discipline requires explicit boundaries. Vague goals allow rationalization. When failure is undefined, failure is invisible.
This directive forces failure to be defined before execution begins.
The Core Principle
Ambiguity protects failure.
If execution criteria are flexible, the mind will move the goalposts to avoid discomfort. Defining exact failure conditions removes flexibility and forces accountability.
A disciplined system knows exactly when it has failed.
Why This Fails for Most People
Most people prefer “doing their best.” They avoid strict metrics because failing against a strict metric feels bad.
They set vague goals. They track effort instead of completion. They change the rules mid-execution. They excuse misses if they “tried hard.”
Undefined failure guarantees eventual collapse.
The Gyōji Directive
Define failure conditions before execution.
If you cannot instantly determine whether an action succeeded or failed, the system is invalid.
Implementation Protocol
- Define execution with binary criteria (yes/no, done/not done).
- Write the failure condition down.
- Remove all subjectivity.
- Do not change the condition during execution.
- Record failures immediately.
Failure must be impossible to rationalize.
Common Errors
- Tracking effort instead of outcomes.
- Leaving room for interpretation.
- Defining success instead of defining failure.
- Ignoring partial failures.
Enforcement Rule
If failure is arguable, it is failure.
Final Order
Define failure exactly. Remove ambiguity.