Write operational definitions for every high-stakes term…
For every high-stakes term in your reasoning (quality, success, productive, fair), write an operational definition specifying observable conditions that must be true for the term to apply, then store that definition as a canonical reference atom in your knowledge system.
When This Fires
- Making or evaluating decisions where high-stakes terms drive the outcome
- Noticing recurring disagreements that seem to be about values but might be about definitions
- Setting goals or success criteria for projects, teams, or personal practice
- Any time you use a word that would cause confusion if two people defined it differently
Common Failure Mode
Writing definitions that are just synonyms: "Quality means excellence and craftsmanship." This is a definition that defines nothing operationally. The test: can someone verify whether the term applies without asking you? If the definition requires interpretation, it's not operational. "All tests pass" is operational. "Code is well-crafted" is not.
The Protocol
For each high-stakes term in your reasoning: (1) Write the term. (2) List the observable conditions that must be true for the term to apply. Each condition must be verifiable by someone other than you. (3) Store the definition as a canonical atom in your knowledge system with a unique ID. (4) Link it from every note that uses the term. (5) Review and revise definitions quarterly — your operational understanding of "quality" or "success" should evolve as you learn.