Learning Isn’t the Goal. Changing What You Do Is.

How organizations turn lessons into action

Over the past few weeks, I’ve been writing about leaders and organizations going back to school.

We’ve talked about continuing to learn.

We’ve looked at the lessons organizations teach people every day.

And last week, we explored the importance of unlearning assumptions that may no longer be true.

But there’s one more part of learning that deserves attention.

Doing something differently because of what you’ve learned.

Think about school for a moment.

You can attend every class.

Read every book.

Take pages of notes.

Even pass every test.

But if none of that changes what you understand or what you’re capable of doing, it’s fair to ask how much learning actually happened.

Organizations aren’t that different.

They collect enormous amounts of information.

Employee surveys. Customer feedback. Project reviews. Performance data. Strategy sessions. Leadership programs. AI pilots. Lessons learned.

But collecting lessons isn’t the same as learning from them.

Which raises a question I think every leadership team should occasionally ask:

What does our organization know today that we still haven’t acted on?

The answer might be uncomfortable.

Most Organizations Already Know a Lot

Think about some of the conversations happening inside organizations today.

This process is too complicated.

We have too many priorities.

Employees don’t understand the strategy.

That meeting isn’t particularly useful.

Our customers find this frustrating.

Our leaders need to delegate more.

People are spending too much time on low-value work.

AI could eliminate or fundamentally change some of these tasks.

None of those necessarily requires another study.

In many cases, people across the organization already know they are true.

Yet organizations can spend months, or sometimes years, knowing something without changing it.

Eventually, someone says:

We’ve known about that for years.

Whenever I hear that phrase, I think there’s an interesting follow-up question:

If we’ve known about it for years but haven’t changed anything, did the organization really learn it?

Because organizations don’t become more capable simply by knowing more.

They become more capable when what they know changes what they do.

The Knowing–Doing Gap

The challenge often isn’t learning.

It’s what happens after the learning.

Sometimes a lesson competes with existing priorities.

Everyone agrees something should change, but Monday morning arrives and today’s urgent work takes over.

Sometimes learning challenges an established way of working.

The lesson might imply changing a process, role, structure, priority, or leadership behaviour.

Acknowledging the lesson is easy.

Changing the organization because of it is harder.

Sometimes the lesson challenges something we already believe.

As I wrote last week, learning something new occasionally requires us to unlearn something old.

And sometimes everyone agrees with the lesson—but nobody owns what happens next.

That’s how organizations can become very good at identifying lessons without becoming particularly good at applying them.

From Learning to Change

So how do we close that gap?

I think leaders can start with four simple questions.

1. LEARN: What Did We Discover?

Something happened.

A project succeeded or failed.

Employees gave us feedback.

Customers behaved differently than expected.

A new competitor entered the market.

An experiment produced an unexpected result.

AI made something possible that wasn’t possible before.

Before moving on, ask:

What did we learn?

It sounds obvious.

But organizations often move quickly from one priority to the next without taking the time to answer it.

2. REFLECT: What Does It Mean?

Capturing a lesson isn’t enough.

We need to understand what it’s telling us.

Ask:

What does this challenge about how we currently think or operate?

An employee survey might tell us engagement has declined.

That’s information.

Reflection asks why, and whether workload, leadership behaviour, organizational priorities, work design, or something else needs attention.

An AI pilot might tell us a task can now be completed in a fraction of the time.

That’s useful.

But the bigger insight might be that the entire workflow should be reconsidered.

Reflection turns information into insight.

3. APPLY: What Will We Do Differently?

This is where learning begins to matter.

Ask:

What are we going to change because of what we’ve learned?

Maybe it’s a decision.

A behaviour.

A process.

A priority.

A meeting.

A role.

A leadership practice.

Or how resources are allocated.

Not every lesson requires a major organizational transformation.

Sometimes the right response is a small change.

But if the answer is consistently nothing, it’s worth asking whether the organization is actually learning, or simply collecting information.

4. CHANGE: What’s Actually Different?

Finally, close the loop.

A commitment to change isn’t the same as change.

Ask:

What is different today because of what we learned?

Can employees see it?

Has a process changed?

Are leaders behaving differently?

Did a priority move?

Did we stop doing something?

Did the way work gets done actually change?

That’s when learning starts to become an organizational capability.

LEARN → REFLECT → APPLY → CHANGE

What did we discover?

What does it mean?

What will we do differently?

What’s actually different?

AI Is Giving Us a Real-Time Test

AI provides a useful example of this challenge.

By now, most organizations have learned that AI can change how work gets done.

Employees are experimenting with it.

Organizations are running pilots.

Tasks that previously took hours can now be done in minutes.

Leaders are seeing new possibilities for productivity and capacity.

But here’s the more interesting test:

What has the organization actually changed as a result of what it has learned?

If AI makes a task dramatically faster but the surrounding workflow remains exactly the same, we’ve learned something, but perhaps haven’t fully acted on it.

If technology changes what’s possible but roles, approvals, processes, meetings, and decision rights remain untouched, we may simply be adding a new tool to an old organization.

The opportunity isn’t only to learn that AI can make existing work faster.

It’s to rethink the work because of what we’ve learned.

Leaders Make Learning Visible

There’s another important part of this.

If leaders want to create organizations that learn, people need to see leaders change because they’ve learned something.

Imagine hearing a leader say:

We believed this.

The evidence showed us something different.

So we’re changing what we do.

That’s a powerful leadership signal.

It demonstrates that changing your mind isn’t necessarily a weakness.

That questioning an assumption is acceptable.

That evidence matters.

And that learning is expected to lead somewhere.

One of the strongest signals that learning matters is seeing leaders change what they do because of what they’ve learned.

One Final Lesson

September seemed like a good time to play with the idea of leaders and organizations going back to school.

We started by asking leaders to keep learning.

Then we looked at what organizations are teaching people every day.

We explored the importance of unlearning assumptions that may no longer serve us.

There’s one final lesson.

Do something differently.

Organizations don’t become more adaptable simply by gathering more information.

They become more adaptable when they’re able to turn new information into new behaviour.

So perhaps the final question in our back-to-school series is also the simplest:

What does your organization know today that it still hasn’t acted on?

Pick one thing.

Then ask:

What are we going to do differently because we know it?

Because learning isn’t the goal.

Changing what you do is.