Before high-stakes categorization, name the actions…
Before committing to a category assignment in high-stakes decisions, explicitly name what actions that category triggers and what you would do differently if the item belonged to an adjacent category.
When This Fires
- Before acting on a high-stakes categorization (incident severity, performance issue, strategic classification)
- When the category assignment will trigger significantly different response protocols
- During triage when items are near the boundary between two categories
- Any decision where miscategorization would produce materially worse outcomes
Common Failure Mode
Committing to the first categorization without checking what changes if you're wrong. The first label feels right, and you proceed to action without ever asking "what if this is actually [adjacent category]?" The pre-commitment check takes 60 seconds and prevents action based on unchecked categorization.
The Protocol
Before committing to a high-stakes category assignment: (1) Name the assigned category explicitly. (2) Name the actions it triggers: "If this is [category], I will [specific actions]." (3) Name the adjacent category: the next most likely classification. (4) Name what changes: "If this were [adjacent category] instead, I would [different actions]." (5) If the actions are dramatically different → verify the categorization with additional evidence before proceeding. The stakes of miscategorization equal the difference between the two action sets.