What you are asking for
Your team needs bearings: how things are done here, why, what has already been tried. Those bearings are in your head.
What the system hears
“If you want to know, you have to ask them.”
What that produces
You are the missing reference. Everything you know and have not written down, your team has to ask you, one question at a time. The day you leave, it disappears.
A colleague often helps prepare customer meetings. She writes a sheet of questions and an annotated example. A newcomer tries it and says where they still get stuck. The sheet improves, and she no longer explains the same thing ten times.
Writing has never been faster. Record an explanation, turn it into a first draft with an AI, correct it. One hour a month is enough to leave bearings the team will find without you.
What serves inside often serves elsewhere. A method, a lesson learned, a solved case: publish them when they can help other teams. That is how a trade gets built, and how your team becomes a reference.
The decision
→ Pick what you get asked most often. Write it down this week, with an example.
→ Have someone who does not know try it, and fix what is missing.
→ Every month, add one bearing. Publish the ones that can help outside the team.
To discuss
Where is the answer to the question we get asked most often written down?