Knowledge and onboarding · 5 min read

When the Process Lives in the Senior's Head: The Risk for Hiring and Growing Teams

November 4, 2026

When procedures live in the memory of long-serving employees, every hire is a risk and every absence is a blocker. Documenting the process also helps newcomers do good work.

When the process is one person's memory

In many small and mid-sized companies there is one person everyone turns to when something doesn't add up. They know how to handle the non-standard order, which customer needs a heads-up before the quote goes out, and in what order the checks are done before a delivery. It isn't written down anywhere: either there was no time, or they simply never needed a reminder.

As long as that person is around, the system holds. The bill comes due at two moments. The first is an absence: holidays, sick leave, a change of role or a resignation, and the case sits idle waiting for someone to pick up the phone. The second is a hire: the newcomer learns by asking, interrupts the senior, sometimes gets different explanations of the same rule, and becomes autonomous only as fast as the person answering is available.

The issue is not the senior's competence, which stays valuable. The issue is that the process and their memory are the same thing. For those who hire, those who are growing, and those who cannot afford to depend on a single person, getting the process out of one head is a practical matter before it is an organizational one.

What Panopto reports, and how to read the figure

According to Panopto's “Workplace Knowledge and Productivity Report” (2018), based on about 1,000 US workers, 42% of institutional knowledge is unique to the individual in their role and is not shared with colleagues.

The limits need to be stated. The survey was run by Panopto, a company that sells knowledge-sharing software and therefore has a direct interest in the topic. The sample is American, the data is self-reported, meaning it reflects what workers perceive rather than a measurement, and the survey dates from 2018. The figure cannot be carried over as-is to an Italian SME.

We use it for what it is: an order of magnitude that describes the problem, not proof that any solution works, ours included. To see how much knowledge is concentrated in your own company, a more local question helps: which activities would stall if a specific person were out for a few days, and who could pick them up?

The flowchart as a map for newcomers

In FlowSharp the process is modeled as a Flow, in line with the idea of “measure first, then automate”: first make visible how the company really works. From that Flow you get the flowchart, a documentation view that answers three questions: who does what, in which phase, with what result. It comes in three layouts (sequence, lanes by owner, sequence with owners) and can be downloaded as a PDF.

For someone who is hiring, the feature that matters is a different one: the flowchart is generated from the Flow itself, so when the process changes, the flowchart changes with it. It is not a second drawing to maintain, which lowers the risk of documentation drifting away from what people actually do.

The FlowSharp guide lists it as useful for showing the process to a new colleague, to an auditor (ISO certifications, internal controls) and to management, as well as for keeping know-how from staying only in the head of the person who performs it. For a newcomer, that means starting from the big picture: who steps in, in what order, where the baton is passed. The tool itself is covered in the article “Il Flussogramma: la documentazione di processo che finalmente si aggiorna da sola”; here the focus is how it helps in the first days on the job.

From map to procedure, with human review

The flowchart shows the overall picture; people working on a case also need the how. With “Converti in Procedura” (Convert to Procedure), FlowSharp generates from the Flow a procedure (SOP) linked to phases and activities. The generation is AI-assisted and requires human review and confirmation before it is applied. That is the moment for the senior to correct it, add the exceptions only they know, and remove whatever is not true.

Procedures have immutable versions, each with an author, a change note and a content fingerprint. The text is written in Markdown or extracted from a PDF, which helps when a document already exists to start from. It becomes possible to trace who changed what and why.

Guides are attached to individual tasks and phases in the designer and are visible to whoever works on the case. The task detail shows the operational contents “Do It” and “Guida”, so someone new finds the instructions where they are needed instead of having to track down a colleague. When a new version of the procedure is created, the old links are flagged as needing realignment, so a guide does not quietly stay attached to outdated text.

Where to start in practice

There is no need to document everything. A reasonable path starts with one process that currently depends on a single person and moves in small steps: model it together with the person who knows it, read the flowchart with a colleague who has never run it and note where they get stuck, convert it into a procedure and have the senior review it, then attach guides to the tasks that draw the most questions.

The case timeline helps too, because it keeps a record of who did what. It shows where the work really passes through and which steps keep landing on the same person, and therefore where knowledge is most concentrated.

One limit is worth keeping in mind: a procedure does not replace the judgment of someone with years of experience. It gives newcomers a shared starting point and gives the people already there a way to pass on what they know without repeating it out loud every time. The Panopto figure, with all the caveats above, is a reminder to do this before an absence or a hire makes it urgent.