Intentional Leadership: 6 Leadership Lessons from Dr. Ken Wagner

These lessons come from a conversation I had with Ken Wagner on The Learning to Lead Show.

Every so often, a guest shows up with a framework so simple and so useful that you find yourself applying it before the episode even airs. That's exactly what happened when I sat down with Dr. Ken Wagner. What follows is drawn directly from that conversation, distilled into six lessons I think every leader needs to hear.

What if the culture you have is exactly the culture your environment is designed to produce?

Sit with that for a second. Because I've learned, and so has every leader who has worked with my guest in this chapter, that behavior is rarely random.

It follows the rules of the environment it's placed in. And if you want to change what people do, you don't start with their hearts and minds. You start with what gets encouraged and what gets discounted in the systems, the rituals, and the daily moments when a leader either notices the right things or doesn't.

Dr. Ken Wagner is the founder of Daylight Advisory, an organizational performance consultant, and a doctor of cognitive and behavioral psychology.

He trained at Florida State University under one of the foundational icons of applied behavior analysis and spent two decades with Aubrey Daniels International, traveling to more than 30 countries on six continents, helping organizations of every size and industry translate the science of behavior into the daily practice of leading people.

That's the part you'd find on a bio page. Here's the part that matters more: Ken has spent his entire career in the space between what leaders intend and what actually happens on the ground. He's watched well-meaning executives undermine their own supervisors without realizing it.

He's watched safety programs fail not because people didn't care, but because nothing in the environment was built to reinforce caring. And he's spent thirty years turning those observations into a discipline any leader can learn.

I've known Ken for more than two decades. He gave me something I didn't know I needed: not just a framework for leading organizations, but a framework for understanding people. Once you see it, you can't unsee it.

Here are six of his most powerful lessons.

Most organizations define culture as shared beliefs, shared values, and a collective mindset. Ken understands why: it's intuitive. But it has a serious problem: you can't see beliefs. You can't measure a mindset. And if you can't observe it, you can't change it reliably.

So he offers a definition of culture that is both more practical and more powerful:

Patterns of behavior- what people say and do consistently- that are encouraged or discouraged by the systems around them or by other people.

This shift changes everything. If culture is patterns of behavior, the questions become actionable:

What are people doing consistently?

What is the environment around them encouraging and discouraging?

And is that happening on purpose, or by accident?

Ken tells a story about a manufacturing plant where the morning meeting had three parts.

Production: supervisors took notes.

Quality: supervisors took notes.

Safety: pens down. Nobody was disengaged.

They were nodding, present, participating. They just didn't write anything down. Later, out on the floor, the manager's behavior tracked exactly: production questions, quality checks, and almost no time on safety.

The safety culture wasn't broken. It was working exactly as designed. The design was just wrong.

"We define culture as a pattern of behavior, what people say and do consistently, that are encouraged or discouraged by all the performance systems or by people."

Reflect: If Ken walked into your organization this week and observed for two hours, what patterns would he see?

Are those the patterns you want?

Stephen Covey told us to begin with the end in mind. Ken adds a crucial next step: once you know where you're going, you have to be able to describe what it looks like when you get there. Not in abstract terms. In behavioral terms.

When Ken starts working with a leadership team, one of his first questions is this:

If we achieved the culture you're after, what would you see people doing?

What would they do when you showed up?

What would they do when something went right?

What would they do when something went wrong?

This question stops most leadership teams cold. They can tell you what they're trying to feel. They can't tell you what they're trying to see. And if you can't see it, you can't measure it. If you can't measure it, you can't know if you're getting there.

The second half of this principle is cascading accountability. Every level of the org chart has a role in building the culture, and when ten leaders give ten different messages, the culture fractures. When every leader is aligned around the same behavioral definition of success, it compounds.

"If we can define what it looks like, we can gauge our progress. We can be more focused on whether we're going to get there or not. That is one of the first starting steps."

Reflect: Could you describe, behaviorally, what success looks like in your culture?

If you can't, that's the work to start with this week.

Applied behavior analysis, the technical name for the science of behavior, sounds academic until Ken explains what it actually studies. Then it sounds like the most practical thing a leader could ever learn.

Albert Einstein described the environment as everything that isn't me. Your boss. Your direct reports. The systems. The metrics on the dashboard. The machine that just broke down. The customer who just escalated.

The colleague who acknowledges you or doesn't. All of that is the environment. And all of it is shaping, in every moment, what you choose to do.

The science focuses on observable, measurable actions because actions are the most direct and reliable indicators of what's actually happening. Ken can see you nodding and asking questions, but he doesn't know what's going on inside your head. And the more he makes assumptions about your internal state, the more risk he carries.

For a leader, this is liberating. You don't have to peer into people's souls to lead them well. You have to understand what the environment around them is reinforcing and design it more deliberately. The morning meeting where safety gets no notes isn't a culture problem. It's an environmental design problem. And environmental design problems are solvable.

"While I care that people have the right mindset, I'm not sure what that looks like. The science of behavior focuses on what people do, and then on creating an environment that encourages what we want more of."

Reflect: What behavior on your team have you been trying to change through inspiration alone?

What in the environment might be quietly reinforcing the opposite?

When the President of the United States makes an offhand comment, markets move. When a senior executive asks a casual question on the shop floor, ten hours of work can be generated for people who were already stretched thin.

Ken calls this the President of the United States Effect, and it's one of the most common, costly, and least-discussed problems in organizational leadership.

A senior executive walks the floor with good intentions. They ask technical questions directly to operators. They want to see what's happening at the ground level.

All of this feels like great leadership. But without the right structure, it produces a cascade of unintended consequences. The operator is intimidated. The supervisor is cut out, and their credibility is quietly eroded.

The message the operator hears from the executive may even contradict what the supervisor has been saying all week. The middle layer, the people most critical to culture change, has been inadvertently undermined.

The alternative is elegant. The executive comes to the floor with the supervisor, not instead of them. The executive looks for what the supervisor has been working on. And when they find an operator doing something right, they say, in front of that operator:

"Your supervisor told me about what you've been doing here."

Ken calls this positive gossip. The supervisor's credibility is amplified, not undercut. The operator feels seen. The executive's walk reinforces the culture rather than disrupts it. One small structural change. An enormous difference in outcome.

"I always ask executives to go to the area manager or the supervisor and ask, 'What have you been emphasizing? Tell me somebody who's really doing a great job, then come along with me."

Reflect: When you do a floor walk, a store visit, or a check-in with a junior team, are you reinforcing your middle managers' credibility, or accidentally undermining it?

Roughly 70% of organizational change efforts fail.

Six Sigma. Safety programs. Lean rollouts. Culture transformations. And the reason, Ken argues, isn't that change is inherently hard. It's that a predictable set of steps keeps getting skipped.

The first skipped step is helping people understand why, not just why it's good for the organization, but why it's good for the function, the team, and the individual.

Three different conversations. The announcement that says, "We're making this change, get on board," is not a change strategy. It's an assumption that the case has been made when it hasn't.

The second skipped step is the supervisor and middle-manager layer. Most change plans are detailed about what the workforce needs to do differently and vague about what supervisors need to do.

The supervisor is the most influential person in any contributor's daily experience. If they aren't equipped, the change won't reach the floor.

The third skipped step catches most leaders off guard: milestone design. Stretch goals feel heroic. Ken has watched what they actually produce in practice:

discouragement.

The gap between where people are and where they're supposed to be is so large that progress feels invisible. Effort doesn't seem to matter. So people stop trying.

The football game has first downs before it has touchdowns.

The military has milestones throughout training, not just at the end. The best change efforts are built the same way: many early wins, consistent momentum, habits forming long before the big goals are reached.

"We want lots of small targets in the beginning to build momentum. We want people to be successful early and often. If the milestones are so far off, we tend to quit, disengage, or leave."

Reflect: Is your current change effort built with enough early wins to keep momentum alive, or is the next visible win still months away?

If you wanted to build an avatar of a high-performing team, what would it look like? Ken has a precise answer that might surprise you with its simplicity.

High performers don't do everything right. They don't do more things than everyone else. What distinguishes them is consistency, specifically, consistency on the critical few behaviors that actually produce results.

The middle performers do the critical things inconsistently. The low performers do other things: they're busy, often genuinely busy, but the things they're doing don't move the needle.

They're doing what feels right, what's most visible, or what's most comfortable, rather than what has the most impact.

This has a profound implication for leaders. If you want more high performers, your job is not to inspire people to work harder. It's to help them identify the critical few behaviors, the things that, done consistently, produce the outcomes you're after, and then build an environment where those behaviors get practiced, reinforced, and eventually habituated.

"High performers do the critical things with the right quality, in the right way, at the right time, and that's consistent. It's a habit. It shows up on a regular basis in a predictable way."

Reflect: What are the two or three critical few behaviors on your team that, if done consistently, would move your most important metrics?

Are you reinforcing them on purpose?

At the end of our conversation, I asked Ken for a parting thought for leaders who want to grow. He said something I've been sitting with ever since.

"Intentionality means I know what I'm looking for, I know what I'm gonna say when I get there, and I know what I hope to hear. You don't need to do that 50 hours a week. A couple of times a week, a couple of times a day, to be deliberate and purposeful, focusing on the things that really make a difference."

That's the whole thesis. Not a heroic effort. Not dramatic transformation programs. Not stretch goals that leave people feeling defeated. Deliberate, consistent, well-designed attention to the behaviors that matter most.

When you understand that behavior follows the environment, you start looking at everything differently. You stop asking, "Why won't people do what I need them to do?" and start asking, "What is the environment around them encouraging?"

Those are not the same question. And the second one has an answer you can actually do something about.

Pick one principle and put it into practice. Not all six. Just the one your gut already knew you needed when you read it.

Maybe it's defining, behaviorally, what success looks like for your team.

Maybe it's adding three early-win milestones to a change you're leading.

Maybe it's rewriting how you do floor walks so they amplify your supervisors instead of undercutting them.

Whatever it is, take the step. Then come back next week and take another one.

You can do this.

• Flawless Consulting, Peter Block

• Influence, Robert Cialdini

• Wooden on Leadership, John Wooden

• The Power of Moments, Chip & Dan Heath

• The Coaching Habit, Michael Bungay Stanier

• Run to Daylight, Vince Lombardi

• LinkedIn

• Website

• Email: kwagner@daylightadvisory.com