Organizational Memory
Employees card, MethodKit for Memory & Reminiscence
Card 16 of 66 · MethodKit for Memory & Reminiscence
  • ThemePeople & Culture
  • CardCard 16 of 66
  • Questions5 to explore
People & Culture

Employees

Contacts, skills & professions

A current picture of who works in the organization, what they know, and what they are responsible for is the foundation everything else rests on.

When someone leaves, the first question is usually: who else knows this? If the answer requires detective work, you have a knowledge risk. An up-to-date employee record is less about HR admin and more about being able to answer that question quickly.

This is not just a contact list. It is a map of expertise: who has deep knowledge in which areas, who holds key relationships, who is the informal go-to for what. That map matters most precisely when someone is about to walk out the door.

Keep it simple enough that it actually stays current. A sprawling skills matrix no one updates is less useful than a lean list that people can maintain in ten minutes.

What to capture

For this part of the company brain, what is worth writing down and keeping current. The goal is not a complete archive but a living record that new people can read and returning people can trust.

Roles & responsibilities

Who is formally responsible for what, so that when a role changes hands, there is a clear starting point rather than a blank page.

Expertise & deep knowledge

The areas where each person holds knowledge that is not written down anywhere else, because that is what is most at risk when they leave.

Key contacts & relationships

The external relationships each person holds on behalf of the organization, since those often need a warm handover rather than just a name transfer.

Tenure & institutional memory

How long people have been around and what periods of history they witnessed firsthand, so you know who to ask when a decision from three years ago needs context.

Questions to explore

Use these on your own or in a group. There are no right answers, only better conversations.

  1. If this person left tomorrow, what would immediately stop working or slow down?

  2. What does this person know that is not written down anywhere?

  3. Which external relationships does this person own, and how dependent is the organization on them personally?

  4. Who in the organization has the broadest view of how everything connects?

  5. Where are skills concentrated in one or two people rather than spread across a team?

Things to notice

  • Contact lists go stale fast; build in a trigger to review when someone joins, changes role, or leaves.
  • Expertise maps tend to focus on formal skills and miss the informal ones (who knows the customer history, who can fix the server) that are often more critical.
  • Avoid over-engineering this; a spreadsheet people actually use beats a system no one updates.