INSIGHTS

The Unwritten Curriculum of Organizations

Organizational Culture, Organizational Development, Workplace Culture
leadership, learning and development, organizational development

Have you ever considered what your organization teaches you without ever actually teaching you?

Every organization has an official version of how things work.

There’s the official stuff we all know. Policies, job descriptions, the employee handbook you probably skimmed when you started. There’s the org chart you pull up when you can’t quite remember who reports to whom, the onboarding process, the mission and values, and maybe even a strategic plan that everyone spent a whole lot of time putting together.

But then there is everything else we learn once we actually start working there.

It shows up in the everyday activities we all move through.

Who you copy on an email because you’ve learned it’s better to keep them in the loop.

Whether you can wait until tomorrow to respond or whether everyone seems to be answering messages at 9:00 at night.

How people dress for certain meetings. Who speaks first. Who everyone looks at when a decision needs to be made.

You learn pretty quickly what “professional” means in that particular place, even if no one ever sits you down and explains it.

And then there are the processes no one really questions anymore. You ask why something is done a certain way and the answer is some version of, “That’s just how we do it.”

None of this is necessarily written down. You just learn it.

“How We Do Things Around Here”

One of the simplest definitions I’ve heard for organizational culture is: how we do things around here.

I like that definition because culture can sometimes feel like this big, abstract thing. But so much of culture lives in the ordinary.

Over time, these things start to feel less like choices and more like simply how work gets done. 

I’ve experienced this both working inside organizations and coming in from the outside as a consultant.

Someone will explain a process, policy, or system to me and say, essentially, “This is how we do it.”

And because I’m newer to the work, I have the luxury of asking questions.

Although, if I’m being fair, I am absolutely wearing my consultant hat when I do it.

Part of the discovery process is asking questions such as:

  • When did we start doing this?
  • What was happening at the time?
  • What problem were we trying to solve?
  • Who was involved in deciding this was the best solution?

And maybe most importantly: Does the context that created this process still exist?

Because I’m increasingly noticing something in organizations:

The context changed, but the process stayed.

The Context Changed. The Process Stayed.

I don’t think “we’ve always done it this way” automatically means something is wrong.

Sometimes there is wisdom in what has been passed down.

Someone tried something. They learned from it. A process evolved. Over time, it became a reliable way to get something done.

That is institutional knowledge, and there is deep value in it. However,  sometimes a process made perfect sense for a particular moment.

Perhaps the organization was smaller then; technology was different, or a former leader had a particular preference. Maybe something happened once and a policy was created to make sure it never happened again.

Five years pass, then ten. And without us fully noticing, the context changes, but the process stays. Eventually, even the people who remember why it was created move on.

At that point the organization isn’t necessarily preserving institutional wisdom. It may simply be repeating an organizational habit.

And I think there is an important difference between the two.

The question isn’t simply, “How long have we been doing this?”

It is: What are we preserving and why?

For me, this marks an opportunity to take a closer look at some of the things we’ve stopped noticing.

And I want to invite you to actually try this.

Think about a process, policy, or workplace norm in your organization that feels so routine no one gives it much thought anymore. Maybe it’s the way you run meetings, how decisions get made, something in your hiring process, or a policy everyone just knows to follow.

Earlier, I shared some of the questions I tend to ask to understand how we got here. Once you understand that history, I think there’s another set of questions worth asking:

  • Does this still meet the need we have today?
  • What are we gaining by continuing to do it this way, and what might it be costing us?
  • If we were starting from scratch, knowing what we know now, would we design it the same way?

That last question is important, because the goal isn’t to change something simply because it’s old. We wan to keep the organizational wisdom in place.

But there’s a difference between preserving something because it still serves us and preserving it because we’ve stopped noticing that we have a choice.

Recent Posts

Sign Up for our Newsletter