Only she knows how: dependence on one person does not fit in a folder
Find the work that stops when one expert is absent and test cover with real tasks, clear decision boundaries and proper access.
Article language: English

In this article
An ordinary order arrives at nine on Monday. The form is complete, the materials are in the company folder and the instructions even have a table of contents. Only Agnieszka is missing: she has taken three days off. Within an hour the team knows that a table of contents cannot take a supplier's call. Someone must recognise the exception, choose the right variant and check whether the result makes sense.
This is a fictional situation, but it illustrates a dependency that a document count will not reveal. A business can have an extensive knowledge base and still need one person for every unusual order. The question is: what can someone else actually do, on what basis and up to which point?
Start with the work that stops
“Nothing works without Agnieszka” is too broad to act on. It could mean a missing application permission, knowledge of a client's history, the ability to evaluate material or authority to decide. Each needs a different response. Training on software does not grant permission to approve an exception, and a new folder cannot replace practice in judging an outcome.
NASA's knowledge management material connects critical knowledge to mission delivery and informed decisions, and notes experience that is difficult to replace quickly. This is the perspective of a technical institution; in a small company it helps ask about a specific needed capability instead of counting saved pages.
In our example Agnieszka prepares unusual sets of display materials. Others can reproduce the standard variant but stop when a client sends a file with different dimensions and adds, “please do it as last time”. The dependency is recognising the earlier agreement and assessing the effect of the change, not the whole job, a personality or a mysterious talent for rescuing Mondays.
Choose one recurring task and name its outcome. Include when consultation is needed and what happens if the right person is unavailable. Does everything wait? Does someone attempt part of it? Does the client receive an unchecked answer? This picture is more useful than a list of people marked red in a staffing-risk spreadsheet.
Distinguish frequent dependencies from rare but important ones. In our example the standard set may be needed daily, while identifying a special variant arises a few times a year. The company may choose different continuity arrangements for each. Not every skill must be transferred to every employee to the same degree.
Also ask whether an apparent knowledge dependency is really an access problem. If only one person can see current agreements, another cannot perform the task even with good preparation. Before planning a skills transfer, check whether the person attempting the task can reach the necessary material in accordance with company rules. A missing permission should not be recorded as a missing skill.
A document can be available while knowledge remains inaccessible
Good company knowledge architecture helps people find the right material. The guide to organising company knowledge (in Polish) describes how to structure it. Covering for someone needs another step: check whether it is enough to act. Instructions may describe the standard precisely while omitting an exception that makes up half the actual difficulty. They may also assume vocabulary a new person does not yet know.
APQC distinguishes knowledge continuity from activities used to preserve knowledge. Capturing information and transferring it between people are means. Continuity means the necessary knowledge remains available for use. In material from October 2026, the organisation also identifies the problem of collecting content without actual use.
In our order, a folder might say “check dimensional compatibility”. The substitute asks: which dimensions, against what, and at what difference must work stop? If the answer always requires calling the author, the document is a reminder for the expert. That can still be useful, but it does not establish that a substitute can work independently.
Do not try to document every possible exception before the first trial. That can produce an encyclopaedia whose maintenance depends on the same person. Test a normal case and one known variant, with a clear boundary: we can handle this situation; that one goes for consultation. The boundary helps the expert too: she need not guess whether silence means success or a developing problem.
Test cover by doing the work
Arrange a short trial in which another person leads the task and the specialist observes. Choose material without immediate client pressure and with appropriate data permissions. This is not a memory exam or a trap. It is a way to see where execution needs knowledge, access or a decision.
Preparation should include starting conditions, the expected result and how to check it. The observer records stopping points rather than immediately taking over the keyboard. If help is given, name its kind. Pointing to a file is different from recognising that received material is unsuitable for further work.
In the trial the substitute finds the order and correct template but selects an outdated client agreement. The technical instructions work; recognition of currency fails. A visible link between the order and approved variant could help. There is no need to rewrite the whole knowledge base or train everyone on every company tool immediately.
After the first trial, repeat independently with a comparable case. Someone who watched may remember movements without understanding why choices were made. Onboarding and confirmation of a particular cover arrangement should therefore connect clearly to the task. The guide to introducing an employee to company knowledge (in Polish) discusses how to check the work in practice. Attendance at a meeting does not itself establish the skill.

Assess the conditions under which the result was achieved. One calm example does not establish readiness to take over a full day's orders. In our studio the second person might handle the standard variant but need more time to check client history. Keep that information in the cover plan. Assigning the expert's full normal workload immediately would assume something the trial did not test.
A simple record can say: independently performs the standard case; consults on dimensional changes; does not approve departures from the agreed scope. This is more honest and useful than “trained”. It allows work to be assigned without inventing abilities that have not been checked.
Compare both the result and the checks performed. A substitute may do the work in a different order from the instruction's author while preserving the correct result and required controls. Do not reject that route merely for a different sequence of movements. Establish whether an omitted step was a habit or a condition of correctness. That distinction needs a conversation between someone who knows the task and the person who just performed it.
If the trial stops, record the precise point and help needed. “She could not manage” does not reveal whether a criterion lacked explanation or material was outdated. Return to that point after the fix instead of repeating the entire demonstration. The next trial then tests the actual change, and the learner knows why another exercise is needed.
The expert needs time to hand over too
If the specialist answers urgent questions all day, preparing cover can continually lose to the next order. The team says continuity matters and then consumes every available hour of the person on whom it depends. Adding “transfer knowledge” to the end of her list will not resolve this.
Define a small scope and reserve shared time. One task prepared for genuine handover can be worth more than a promise to describe an entire role. The learner needs a chance to do the work; the expert needs conditions in which to explain how she recognises a situation, rather than call out an answer between phone calls.
Ask: how do you know the material needs checking? Which small detail changes the decision? Where do you look when the standard does not fit? Answers may concern experience invisible in a screen recording. A video shows a click, but not necessarily why someone chose not to press a button. Before planning a change, observe the expert’s normal work to identify what they notice, what they wait for and when they consult someone. The article on observing work (in Polish) discusses how to agree the scope of that observation.
Dependence also appears in interruptions to team work. Ten small questions may reveal the same missing knowledge or basis for a decision. Instead of automatically silencing contact, identify which question can be answered by material, which needs practice and which should remain a specialist consultation. Reducing messages without building the ability to perform the work only hides the dependency. Returning to an interrupted task takes time; the article on interruptions at work (in Polish) examines this cost.
Private shortcuts can become a company bottleneck
In some teams an important part of work takes place in an AI tool owned by one person. It contains the conversation history, working instructions, a document connection or a manually corrected result. The company folder has the final file, but no one else can reproduce how it was produced. A prompt copy may not suffice if the result also depended on data, settings and human correction.
The Aeneia Audit offer describes a review of AI tool use and information flows. The team’s needs and possible scope of work for a specific case require discussion.
Aeneia Audit Describe a task dependent on one account and what is known about the tools. Discuss your needs and the possible scope of a review of AI use and data flows. Discuss the scope of an AI review
The trial should follow company access rules. Sharing someone else's login is not a good way to prove work can be taken over. Establish which permissions and materials a second person actually needs and whether they can be provided properly.
In a tool preparing a working description of the display set, try reproducing the result with appropriate company access. Check whether the second person can identify the source document, recognise missing data and review the description before handing it on. If the result looks similar but its basis is unknown, the dependency remains unexplained. Generating text and using it responsibly at work are separate checks.
Define the limits of independence and a route to help
Even successful cover does not mean everyone can decide every case. Agree who confirms an unusual decision and what happens during that person's absence. Distinguish the person performing work from the process owner. The article on process ownership and responsibility (in Polish) discusses the owner’s authority, decisions and resources. Operational cover should not quietly alter decision authority.
Provide a way to raise difficulties. If a learner hides a question to prove independence, the trial loses its purpose. A route like the first conversation after noticing an error can help: a specific fact, what is unknown and the next check. A doubt may expose a gap before it becomes an error sent to a client. For the effect of the first response on reporting, see the article on discussing mistakes (in Polish).
After confirming the task, decide when the ability to take over will be used again. A gap of many months, a tool change or a new kind of order can make an earlier result unrepresentative. Connect cover with a handover of open cases. The guide to handing over a shift (in Polish) discusses how to record the state of each case. The ability to perform the work and knowledge of its current state are both needed.
When an experienced person spots a risk, ask for a recognisable signal. Instead of “you just have to feel it”, it may be possible to name a discrepancy, a client question or a condition for stopping. Some judgement may still require practice. Clearly identifying that point helps determine what support must remain available after handover.
Return to Monday's order. Can the second person find the current agreement, prepare the correct variant and recognise when to consult? If so, the business has confirmed one part of work continuity. If one condition stops them, it knows what still needs practice. That is more concrete than another folder called “Final knowledge v7”.










