Observe Without Judgment

The Problem with Judgment

When a manager labels something as "good" or "bad," the conversation shifts from understanding reality to defending positions. Positive evaluations create pressure to maintain appearances. Negative evaluations trigger defensiveness. Both distort the information flow that a team depends on.

What "Awareness of What Is" Means

Instead of evaluating, observe and describe:

• Replace "This code is bad" with "This code has no error handling for network failures" — The first is a judgment that puts people on the defensive. The second is a factual observation that naturally leads to a solution.
• Replace "Great job on the release" with "The release went out on time with zero rollbacks" — The first is a vague evaluation. The second acknowledges specific facts, which is more meaningful and informative.
• Replace "You're not communicating well" with "I noticed the design change wasn't shared until the PR was open" — The first labels the person. The second describes a specific event that can be addressed.

Why This Works

• People stay open: When there's no judgment to defend against, people share information more freely
• Problems surface earlier: Team members are more likely to flag issues when they know the response will be curiosity, not criticism
• Solutions are better: Factual observations lead to root-cause discussions. Judgments lead to blame or complacency
• Trust deepens: People feel respected when their manager engages with reality rather than handing down verdicts

How to Practice This

• In code reviews: Describe what the code does and ask questions. "This function handles both parsing and validation — what do you think about splitting them?" instead of "This function is too complex."
• In 1:1s: Ask "What happened?" before "What went wrong?" Often the answer reveals things that went right and wrong simultaneously.
• In retrospectives: Frame discussions around observations. "We merged 3 PRs without tests last sprint" states a fact the team can reason about together.
• When giving feedback: Describe the behavior and its impact. Let the person draw their own conclusions — they usually arrive at the same place, but with ownership rather than resentment.

The Discipline

This is harder than it sounds. We are wired to evaluate. The practice is to notice when you're making a judgment, pause, and translate it into an observation. Over time, this becomes the default mode of thinking — and the quality of your conversations will transform.