Require independent operational definitions of key terms…
For each high-stakes word in decisions or commitments (quality, ownership, alignment, done, strategy), require independent operational definitions from each stakeholder before proceeding, then compare and reconcile the definitions explicitly.
When This Fires
- Before committing to any multi-stakeholder decision involving abstract terms
- At project kickoff when establishing success criteria
- When a team agrees on a direction using words that everyone nods along to
- Any commitment where the same word might mean different things to different people
Common Failure Mode
Accepting surface agreement: "We all agree quality is important." Everyone nods. Nobody defines quality. Six weeks later, the engineering team delivers with no bugs and the product team says it's not "quality" because the UX feels clunky. The agreement was on the word, not the meaning.
The Protocol
For each high-stakes word in a multi-stakeholder decision: (1) Identify the load-bearing terms: "quality," "ownership," "done," "alignment," "strategy." (2) Have each stakeholder independently write their operational definition — what observable conditions must be true for this word to apply? (3) Compare definitions side by side. (4) Where definitions diverge: negotiate and reconcile explicitly. Where they align: confirm the shared definition. (5) Write the agreed definition and reference it throughout the project. Definitional clarity at the start prevents interpretive conflict at the finish.