Your Synagogue Has a Knowledge Problem

The most valuable information in your organization may be the information no one can find.

Ask a synagogue employee where to find the most important information about a program, a vendor, a recurring event, a donor, or a longstanding congregational practice, and you may hear: “ask so and so; she knows.”

Or perhaps: “I think it’s in an email somewhere.”

Maybe it lives in a Google Drive folder with a name that made perfect sense three years ago. Maybe it’s in the notebook of the person who has worked there for 17 years. Maybe the former executive director knows, but no one thought to document it before they left.

This is not primarily a technology problem. And it is certainly not a problem of employees being disorganized or unwilling to share information.

It is a knowledge management problem.

And for synagogues – organizations where relationships, institutional memory, ritual knowledge, and highly specific community practices are central to the work – it can be an especially costly one.

When institutional knowledge walks out the door

Most organizations don’t realize how much they rely on invisible knowledge until someone leaves.

A longtime staff member retires, and suddenly no one knows which caterer the congregation uses for certain events, how the High Holy Day registration process actually works, why a particular vendor was selected, or which board member needs to be consulted before a certain decision is made.

A new employee is hired and spends weeks asking colleagues questions that someone has already answered dozens of times.

A program director takes a vacation and discovers that three other people are unable to move a project forward because they don’t know where the relevant files are, or even which files are relevant.

None of these situations necessarily indicate that anyone has failed.

The organization has simply been operating on implicit knowledge rather than explicit knowledge.

And implicit knowledge is fragile.

It depends on people remembering things, knowing who to ask, understanding unwritten rules, and being present at the right moment. It works reasonably well when an organization is small and stable. It becomes increasingly risky as organizations grow, staff change, responsibilities shift, and more work becomes distributed across teams.

The irony is that synagogues often have enormous amounts of institutional knowledge. The problem is that they haven’t necessarily built systems for managing it.

Your Google Drive is not a knowledge management system

The instinctive response to this problem is often: “We need to organize our files.”

Of course, file organization matters. But a perfectly organized collection of documents doesn’t necessarily solve a knowledge problem.

Consider the difference between these two questions:

Where is the document?

and

How does this organization do this thing?

The first is a file-management question. The second is a knowledge-management question.

A synagogue might have a beautifully organized folder containing everything related to its annual gala. But does anyone know:

• When planning should begin?
• Who owns each part of the process?
• Which decisions require senior leadership approval?
• Which vendors have worked well in the past?
• What mistakes should be avoided?
• Which communications need to go out, and when?
• What information needs to be captured in the CRM?
• What happens differently every year—and what should happen the same way every year?

That knowledge may be scattered across documents, email threads, calendars, people’s memories, and years of accumulated practice.

The goal isn’t to document every possible thing.

The goal is to make the right knowledge accessible to the right people at the right time.

Start with the question: “What would someone need to know?”

Good knowledge management begins with the work itself, not the software. Before choosing a platform, ask what information people actually need in order to do their jobs.

For a synagogue, that might include:

Recurring processes.
How do we run registration for religious school? How do we prepare for the High Holy Days? What happens when a new member joins?

Roles and responsibilities.
Who owns this work? Who needs to be consulted? Who makes the final decision?

Institutional history.
Why do we do things this way? What has been tried before? What decisions have already been made?

Key relationships.
Who are our important vendors, partners, funders, volunteers, and community contacts – and what does someone need to know about those relationships?

Templates and tools.
What can be reused instead of recreated?

Decision-making context.
What has leadership already agreed to? What is still open for discussion?

Organizational norms.
How do we communicate? Where do things live? When do we use email versus meetings? How do teams hand work off to one another?

Once you start asking these questions, you may discover that what your organization needs isn’t another folder. It needs an organizational memory system.

Make the organization less dependent on individual memory

There is a subtle but important cultural shift that happens when organizations take knowledge management seriously.

Instead of asking:

“Who knows how to do this?”

they begin asking:

“Where does the organization keep what we know about doing this?”

That’s a significant difference.

The first question reinforces dependency on individuals. The second creates organizational resilience.

This doesn’t mean removing expertise from people’s roles. On the contrary, people’s experience and judgment are among an organization’s most valuable assets. But expertise shouldn’t disappear when the expert takes a vacation.

A staff member should be able to take two weeks off without becoming the only bridge between everyone else and the information they need.

A new employee should be able to learn how something works without conducting a months-long archaeological dig through their colleagues’ inboxes.

And when someone leaves, their departure should mean losing a person, not losing an entire body of institutional knowledge.

Don’t document everything. Document what matters.

There is another trap here: turning knowledge management into a documentation project so enormous that nobody actually does it.

You don’t need a 75-page manual explaining how to answer the phone. Instead, identify the places where information is:

• frequently requested,
• difficult to find,
• known by only one or two people,
• critical to recurring work,
• likely to be lost when someone leaves, or
• necessary for a new employee to become effective.

Start there.

A two-page checklist for running an annual program may be more valuable than dozens of pages of generalized policies.

A simple explanation of who approves communications may eliminate more confusion than a comprehensive communications manual.

A clearly documented “how we do this” process can save hours of staff time every year.

Good knowledge management is not “creating more information.” It’s reducing the amount of information people have to hunt for.

The synagogue of the future needs organizational memory

Synagogues are built on continuity.

We preserve Torah. We preserve ritual. We preserve stories, traditions, melodies, relationships, and communal memory. We understand instinctively that what has been learned should not disappear simply because one generation has moved on.

Our organizational practices deserve some of the same intentionality.

A healthy synagogue should not require every new employee to reconstruct the institution from scratch.

It should not depend on a single person remembering why something happens every year.

It should not confuse “we’ve always done it this way” with an actual documented process, or force every new leader to rediscover what previous leaders already learned.

And it should not assume that buying a new piece of software will solve a problem that is fundamentally about how people create, capture, organize, and share knowledge.

When knowledge is accessible, work gets easier. When it is documented, people can build on it. When it is shared, teams become less siloed. And when institutional memory becomes organizational memory, a synagogue becomes more resilient – not just when someone leaves, but every day.

The best-run organizations aren’t necessarily the ones where everyone knows everything.

They’re the ones where people know how to find what they need to know.