There is a hidden tax on every project. It is called the Ambiguity Tax. It happens when two people use the same word but mean different things.
-
Boss: “I need this done ASAP.” (Means: By Friday).
-
Employee: “I’ll do it ASAP.” (Means: Whenever I finish my current task, maybe next Tuesday).
-
The Result: A fight on Friday afternoon.
The “Jack” Paradox
In the original post, a manager says: “Jack is responsible for the module.”
-
Jack thinks: “I code my part.”
-
Peer thinks: “Jack does most of the work.”
-
Manager thinks: “If this module fails, I am firing Jack.”
This is not a “Communication Problem.” This is a Definition Problem. We rely on “Low-Resolution Words” (Responsible, Lead, ASAP, Better, Fast) because they are comfortable. High-Resolution Words (Accountable, Owner, By 5 PM, < 200ms latency) are scary because they leave no room to hide.
The Protocol: High-Resolution Speech
To eliminate the Ambiguity Tax, you must increase the resolution of your language.
1. Ban “Soft” Words
Words like “Soon,” “Better,” “Handle it,” and “Review” are banned from the lexicon of a Sovereign.
-
Bad: “We need to improve performance.”
-
Good: “We need to reduce page load time from 3s to 1.5s by Oct 15th.”
2. The Briefing Back-Check
Never ask: “Do you understand?” (People always say Yes to avoid looking stupid). Ask: “How do you interpret what I just said? What are your first 3 steps?” When they explain it back to you, you will spot the bugs in their understanding immediately.
3. The Dictionary of Done
Every project needs a Glossary.
-
What does “Done” mean? (Code committed? Or Code deployed and tested in Production?)
-
What does “Urgent” mean? (Drop everything now? Or do it by EOD?)
#DhandheKaFunda: Vagueness is the refuge of the incompetent. Specificity is the language of the master.