Observation and Values

In the previous lesson, you built a toolkit for catching cognitive biases and managing the internal friction that comes with flexing your leadership style. But if you aren't relying on gut reactions, what are you basing your decisions on? The answer is observation—deliberate, systematic attention to team behavior, engagement, and performance. Adaptive leadership isn't about guessing; it's about seeing what people need through real data.

As you adapt your style, a legitimate concern will surface: "If I keep changing how I lead, am I still being authentic?" This unit addresses both sides of that equation. You'll learn how to gather reliable behavioral data without falling into bias traps, and you'll develop a framework for knowing when you're flexing your methods appropriately versus when you're compromising your core values. By the end of this unit, you'll have the ability to observe with precision and lead with integrity.

Most managers believe they have a good read on their team, but much of what we call "observation" is actually impression formation. True systematic observation is intentional, structured, and focused on behaviors rather than interpretations.

The first principle is to separate what you see from what you think it means. A behavior is objective: "Sloan spoke up three times during the meeting." An interpretation is the story your brain attaches to it: "Sloan is really engaged." Both might be correct, but the discipline of observation starts with recording the behavior and delaying the interpretation until you have enough data points to form a pattern.

To build this discipline, use a Behavior Log—a simple record of observable actions. It only needs three fields: the date, the behavior, and the context. For example: "Oct 12 — Jenna asked two clarifying questions about the new process during standup — first week after rollout." There is no judgment here. Over time, these entries reveal patterns. If Jenna is still asking those questions four weeks later, that is a meaningful data point.

Beyond logging, pay attention to engagement indicators. Active indicators include volunteering for tasks or proactively sharing updates. Disengagement might look like withdrawing from informal interactions or a drop in timeliness. Crucially, use your DISC knowledge to calibrate these. A quiet person isn't necessarily disengaged; they may simply be a high-S or high-C who processes internally. Finally, triangulate your observations. Look for at least three data points across different contexts (meetings, emails, 1-on-1s) before drawing a conclusion. This protects you from both the Recency and Halo effects.

As you practice adaptive leadership, you’ll eventually hit a deeper discomfort: the boundary between Method Adaptability and Value Compromise.

Method Adaptability means changing how you do something while keeping the underlying principle intact. If you value accountability, you might hold a high-D team member accountable through a direct, results-focused conversation, while holding a high-S member accountable through a private, supportive check-in. The method is different, but the value—that everyone is accountable for their commitments—remains. You are adapting the instruction, not the expectation.

Value Compromise occurs when the adaptation undermines a principle you hold as non-negotiable. If you value honesty, Method Adaptability means using positive framing for a sensitive employee. Value Compromise would mean omitting critical feedback entirely to avoid discomfort. To distinguish between the two, use the Adaptability Litmus Test:

1. Am I changing my method or my standard? (Delivery vs. expectation).
2. Would I be comfortable if every team member knew I was doing this? (Transparency).
3. Is this serving the team member's development or my own comfort? (Growth vs. avoidance).

To see what the Adaptability Litmus Test looks like in practice, consider this exchange between two peer managers working through a real dilemma:

• Jessica: I need to give feedback to one of my reports about missed deadlines, but he's a high-S personality and he takes criticism really hard. I'm thinking I might just wait until his next review and bring it up then.
• Ryan: Okay, let's run the litmus test. Are you changing your method or your standard?
• Jessica: I guess I'm changing my standard. I normally address performance issues the same week I spot them. Waiting two months isn't adjusting how I deliver feedback—it's avoiding delivering it altogether.
• Ryan: Right. And would you be comfortable if the rest of your team knew you were holding off on his feedback?
• Jessica: No. They'd probably think I was playing favorites or that deadlines don't actually matter.
• Ryan: So what would Method Adaptability look like here instead?
• Jessica: Probably having the conversation this week but doing it one-on-one, starting with what's going well, and framing the deadline issue as something we can solve together rather than leading with what went wrong.

Notice what happened in that exchange. Jessica's initial instinct—to delay the feedback—felt like adaptation but was actually avoidance that would have compromised her value of timely accountability. By running through the litmus test questions with Ryan, she was able to separate the what from the how and land on an approach that changes her delivery method while keeping the standard intact.

The concern that "I don't want to be fake" is based on the misunderstanding that authenticity requires behavioral consistency. In reality, authenticity is about value consistency. You speak differently to a child than to a peer, yet you are the same person; you are simply adjusting your output to the context. Adaptive leadership works the same way. Your core values—respect, growth, honesty—stay constant while your behavioral expression shifts.

To anchor this, build a Values Anchor List—three to five non-negotiable leadership principles. Be specific: instead of "integrity," use a statement like "I will address performance issues within one week." This gives you a concrete standard to hold yourself to, even as your delivery method changes.

With your Values Anchor List, every adaptation has a framework. When you step back to give a high-D more autonomy, you check: "Am I still holding them accountable?" Yes—you've agreed on outcomes; you've just removed the micromanagement. This consistency builds the deepest kind of trust. Your team will experience different approaches, but they’ll always experience the same principles. This brings the foundation full circle: you now have the tools to observe with discipline and adapt without losing yourself. In the upcoming role-play, you'll put this together by defending your adaptive approach to a team member who questions why you treat people differently.