Your Organization Already Has a Curriculum. You Just Haven’t Named It Yet.

When we hear the word curriculum, we often think about schools.

We picture courses, instructors, lesson plans, learning objectives, and assessments.

But through our work at Legacy Collective, I’ve started to think about curriculum differently.

Every organization has one.

It lives in the experiences of its people. It shows up in the processes that have been refined over time. It exists in the stories employees tell new colleagues, the lessons leaders learned the hard way, the practices that make one team particularly effective, and the institutional knowledge that rarely makes its way into a manual.

The curriculum is already there.

The opportunity is to recognize it.

Knowledge Is Everywhere

Think about the people inside an organization who have been doing their work for five, ten, or twenty years.

They know things that may never appear in an employee handbook.

They know why a particular process works.

They remember why an important decision was made.

They understand the relationships that make the organization successful.

They can recognize problems before others see them because experience has taught them what to look for.

That knowledge has value.

But much of it remains informal—passed from person to person through conversations, meetings, mentoring, and observation.

When someone retires, changes roles, or leaves the organization, some of that knowledge can leave with them.

This raises an important question:

What knowledge exists inside your organization that other people could benefit from learning?

That question has become increasingly important to how I think about our work at Legacy Collective.

Not Everything Needs to Become a Course

Recognizing organizational knowledge does not mean turning every process into a training program.

In fact, I would argue for the opposite.

Start small.

Identify something useful that another person should be able to understand, apply, or carry forward.

It might be a process.

It might be a leadership lesson.

It might be the story behind an organizational practice.

It could be expertise developed through years of working with customers or communities.

Once we identify that knowledge, we can begin asking a different set of questions:

Who needs to know this?

Why does it matter?

What should someone be able to do with this knowledge?

What is the simplest way to help them learn it?

Those questions begin to turn institutional knowledge into a learning experience.

From Expertise to Learning Experience

This is one reason I believe micro-courses can be particularly useful for organizations.

We do not have to take everything someone knows and put it into a course.

Instead, we can identify a meaningful piece of their knowledge and give it structure.

At Legacy Collective, that process often begins with three things:

Ideas. Stories. Experience.

From there, we can organize that knowledge around a clear learning outcome, build a simple learning pathway, invite the learner to reflect or respond, and create an opportunity to apply what they have learned.

Something that once existed primarily in one person's experience can now become something others can access and learn from.

That is an important shift.

The People Closest to the Work Have Something to Teach Us

Traditional approaches to training often begin at the top.

Someone determines what people need to know, develops the content, and distributes it across the organization.

There is certainly a place for that approach.

But there is also tremendous value in looking in the other direction.

Ask the people doing the work.

What have they learned?

What do they wish someone had taught them?

What practices have made them successful?

What mistakes could help the next person avoid unnecessary challenges?

What stories explain the culture of the organization better than an employee handbook ever could?

When we begin asking those questions, we discover potential educators throughout an organization.

They may not call themselves educators.

They may simply be people who know something worth sharing.

Capturing Knowledge Is Also About Legacy

The name Legacy Collective has always meant something important to me.

Legacy isn't simply what we leave behind.

It is also what we intentionally pass forward.

Organizations accumulate knowledge over time. That knowledge represents investments made by employees, leaders, communities, partners, and customers.

Capturing it allows the next person to begin with the benefit of what others have already learned.

That can support onboarding.

It can strengthen leadership development.

It can help with succession planning.

It can preserve institutional history.

It can create professional learning opportunities.

And, when appropriate, it can allow organizations to recognize that learning through credentials that make new knowledge and skills visible.

The micro-course becomes more than a piece of content.

It becomes a vehicle for transferring knowledge.

Start With One Question

You don't need to map everything your organization knows.

You don't need to build an entire learning ecosystem tomorrow.

Start with one question:

What does someone in our organization know that we cannot afford to lose?

Find that person.

Listen to the story.

Understand the experience.

Identify the lesson.

Then begin giving it structure.

You may discover that your organization already has more curriculum than you realized.

You just haven't named it yet.