Good onboarding does not only teach what to do. It teaches why.
A new hire never truly starts from zero.
They join a company that has already made choices, lived through mistakes, abandoned paths and created rules.
Yet teams often pass on the rule without the story.
A rule without context is fragile
“We always do it this way.”
That sentence can be useful. It can also stop a good question.
The person joining can apply the rule without knowing which problem it was meant to prevent. They do not know whether the constraint still exists, or when they should challenge it.
They follow an instruction instead of understanding a decision.
The cost is rarely visible on day one
A poorly transmitted rule does not always create an error immediately.
But it slows autonomy. It forces the most experienced people to explain the same things again. It makes decisions opaque. And it allows old mistakes to return because nobody knows what the team had learned.
Onboarding is not placing a library of documents in front of someone. It is giving them the reference points to understand the company they are joining.
What every important rule should leave behind
For important rules, a team should be able to retrieve:
- the original problem;
- the decision made;
- the constraints or evidence behind it;
- what would justify revisiting it.
This is not documentation for documentation's sake. It is what lets someone use their judgement without starting from zero.
The role of shared memory
Verbasil is designed to preserve that path, starting from sources and signals a team can verify. Decisions, their context, experiments and learnings stay connected over time.
The goal is not to automate onboarding or provide unchecked answers.
The goal is to let a new person understand not only what to do, but why it made sense.
For more, read why startups forget their decisions and how to keep track of decisions.