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

Onboarding

Introducing & onboarding newly employed

Onboarding is the first real test of how well the organization knows itself, and poor onboarding wastes the knowledge you worked hard to hire.

A new person arrives with no context. Every question they cannot easily answer, every system they have to figure out by asking around, and every cultural norm they violate because no one explained it is a small failure of organizational memory. Good onboarding is a direct export of what the organization knows about itself.

Documenting onboarding means capturing both the structured part (what happens in week one, what access people need, what they read first) and the tacit part (who to ask for what, how decisions actually get made, the things everyone assumes you already know). The second part is where most onboarding falls short.

Onboarding documentation also serves as a useful audit. If you cannot explain it clearly enough for a new person to follow, the process itself may need work.

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.

First-week checklist

The practical steps every new person goes through: accounts, access, introductions, and the documents they need to read, because this is the easiest part to systematize and the one most often handled ad hoc.

Tacit knowledge transfer

The things that are not written anywhere but that every experienced person knows: how decisions actually get made, the informal hierarchy, and the norms that new people violate without knowing, because these take the longest to absorb without a guide.

Key relationships to build

Who a new person needs to meet early and why, because the right introductions in the first month shape how quickly someone becomes effective.

Role-specific ramp-up

What a person in this particular role needs to understand, access, and be able to do within thirty, sixty, and ninety days, because generic onboarding leaves gaps that are specific to the job.

Questions to explore

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

  1. What does a new person absolutely need to know in their first week to not be confused or make mistakes?

  2. What do people typically figure out on their own in the first three months that they should have been told at the start?

  3. Who are the most important people for a new hire to meet early, and what is the best way to make those introductions?

  4. Where do new people get stuck most often, and what would fix that?

  5. What would you want someone to tell you on your first day that no one actually told you?

Things to notice

  • Onboarding documentation gets outdated quickly as tools, processes, and teams change; assign ownership and review it after every significant hire.
  • Over-relying on informal buddy systems means onboarding quality depends on who happens to be available rather than on a real system.
  • Good onboarding documentation double-checks whether the things you are asking new people to do are actually documented somewhere they can find.