Nothing is documented: it's all in one head
We get the knowledge out of people's heads and into writing: processes, access, procedures, decisions, so the company no longer depends on one person being there.
What’s probably happening
Everything works, as long as the right person is there. The procedures were never written down, the access sits in someone’s head or notebook, and every departure, every absence, every holiday becomes a risk. It’s nobody’s fault: documentation is always what gets put off, because it produces nothing visible, until the day its absence costs a great deal.
What we do
We observe the work as actually done, not the theoretical version: who does what, with which tool, in what order, and where it gets stuck. Then we write: a map of the processes, an inventory of access, step-by-step procedures, documentation of the technical estate. This work is done by questioning the people who know, without disrupting their day: a few hours of conversation are worth weeks of reverse engineering.
What you get
Documentation that belongs to the company: a newcomer can step into a role, a stand-in can cover, an outside provider can work, without everything going through the same person. And if a project has to follow, the brief is already half written.
What comes next, if you want it
The work described here stands on its own, with no commitment to what follows. The topic below covers it, and the rest if you decide to.
Tell us about your project, or your problem.
Describe your situation in a few lines, however it comes to you. You get a first reading in writing: what we understand, what we would do, where to start. Not an automatic acknowledgement, and no sales follow-up: an answer you can use, even if it stops there.