Judgment Fails When Leaders Won’t Define the Words They Use
Most judgment problems are really definition problems. Leaders ask teams to make good calls, then leave the operating language vague enough for every function to interpret differently.
Judgment breaks down when leaders use important words without defining them.
“Critical.” “Approved.” “Material.” “Sensitive.” “Ready.” “Done.”
These sound like operating terms. In a lot of companies, they are vibes wearing a badge.
Quick Answer
Judgment fails when leaders won’t define the words they use because teams cannot make consistent decisions with inconsistent language. If leaders won't define “critical,” “approved,” “material,” or “done,” the organization is not using judgment; it is negotiating vocabulary in real time.
- Shared definitions turn vague leadership intent into usable operating constraints.
- Undefined words create different decisions across security, legal, product, engineering, and finance.
- The practical move is to define the terms that trigger decisions, approvals, risk reviews, and handoffs before teams have to improvise.
The part nobody likes to admit is that many execution problems are really definition problems. Teams are not always misaligned because they are careless. They are misaligned because leadership left the nouns fuzzy and then expected grown-up judgment to magically fill the gaps.
A security team says a system is critical. Product hears “important customer experience.” Engineering hears “do not touch without change control.” Legal hears “possible disclosure risk.” Finance hears “expensive if it breaks.” Everyone is acting rationally. Everyone is also building a different company in their head.
AI makes this worse, not because AI is mysterious, but because it is obedient. Ask it to classify sensitive data against vague rules and it will scale the vagueness beautifully. Ask teams to govern “approved use” without defining approved, use, and who can decide, and you get policy theater with better formatting.
Leaders often want dashboards, workflows, and committees before they do the boring work of shared language. Bad trade. The tool is not the control. The workflow is not the agreement. The committee is not the operating model.
Good judgment needs constraints. Not micromanagement. Constraints.
Define the words that drive decisions. Write down what “critical” means. Decide what “done” includes. Separate “high priority” from “loud stakeholder.” Make risk tolerance plain enough that a decent manager can act without scheduling a spiritual retreat with Legal.
This is not wordsmithing. It is operational infrastructure.
The strongest teams do not have perfect certainty. They have enough shared meaning to move without constantly renegotiating reality.
If people keep making “bad judgment calls,” check the dictionary you handed them. It may be blank.