Require 3 recent decision examples for each schema — fewer than 3 means aspirational, not operational
In your schema inventory, require behavioral proof by identifying three decisions from the last month that each schema governed—if you cannot find three, reclassify the schema as aspirational rather than operational.
Why This Is a Rule
The gap between "schemas I say I operate on" and "schemas that actually govern my decisions" is one of the largest self-knowledge blind spots. You list "I prioritize quality over speed" as an operational schema, but when pressed to name three decisions from the last month where quality won over speed, you can't — because operationally, speed won every time. The schema is aspirational (what you want to believe about yourself) rather than operational (what actually guides your decisions).
Three decisions from the last month is the behavioral proof threshold. It's recent enough to be verifiable (you can recall specific decisions) and frequent enough to indicate genuine operation (a schema governing fewer than 3 of ~100 monthly decisions isn't operationally important). Three is the minimum — a schema governing one decision might be coincidental. Three indicates a pattern.
Reclassifying aspirational schemas doesn't mean discarding them — it means being honest about their status. They're goals, not current operating rules. This honesty prevents the dangerous middle ground where you believe you're operating on a schema you're not, which produces a self-image that doesn't match your actual behavior.
When This Fires
- During schema inventory construction (Inventory what you actually do — not what you should do — before redesigning your operating schemas)
- When you suspect a gap between stated values and actual behavior
- After receiving feedback that contradicts your self-description
- During any self-assessment where you want to verify operational vs aspirational schemas
Common Failure Mode
Counting vague "I probably used this" moments as decisions: "I think I considered quality when reviewing that PR." Was quality the deciding factor in the review's outcome, or just a thought you had? Behavioral proof requires the schema to have governed the decision's outcome — not just appeared in the deliberation.
The Protocol
For each schema in your inventory: (1) Try to name three specific decisions from the last month that this schema governed. Not "influenced" or "was relevant to" — governed: the schema was the primary factor in the decision's outcome. (2) If 3+ examples → operational schema. It genuinely guides your behavior. (3) If 0-2 examples → aspirational schema. Reclassify it honestly. It's something you want to operate on, not something you currently do. (4) For aspirational schemas you want to become operational: design the implementation (Attach 'When [situation], I will [action]' to every written goal — goals without triggers don't fire implementation intentions, Stack behavior change: cue visibility first, then friction reduction, then reward design behavior stacking) that would make them govern actual decisions.