Require independent operational definitions of key terms from each stakeholder before committing
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.
Why This Is a Rule
High-stakes words — "quality," "ownership," "alignment," "done," "strategy" — are polysemous: they carry multiple meanings that feel like one. When a team commits to "quality," each member commits to their personal definition of quality — and those definitions may diverge significantly. One person means "zero defects." Another means "good enough to ship." A third means "architecturally elegant." They all agreed to "quality" and will all feel betrayed when the others don't deliver their version.
Independent elicitation prevents social convergence: having each stakeholder write their operational definition separately, before comparing, ensures you capture genuine definitions rather than socially negotiated versions. In a room together, definitions converge toward the most dominant voice. Independently, they reveal the actual divergence.
The reconciliation step — comparing and explicitly agreeing on a shared definition — converts the hidden divergence into a negotiated agreement. The negotiation may be uncomfortable ("I thought quality meant zero defects, but you're saying good-enough-to-ship?"), but the discomfort at definition time prevents the much larger conflict at delivery time.
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.