Picture an ordinary morning.
9:12 — Can I confirm this price?
9:26 — Where can I find the latest version of the quote?
10:03 — The client wants to change a condition. What should I do?
None of these questions sounds serious. Each answer may take less than a minute, so it is easy to treat them as an unavoidable part of the job.
But if someone has to interrupt you before they can continue, that minute is not the real problem. The problem is that, at that point, the process does not exist without you.
Being informed is not the same as being indispensable
An owner can want to know about an important decision without being the only person able to make it. You can receive a summary without authorising every step. You can maintain a client relationship without being the only person who knows its agreements, history and limits.
The difference is simple:
- if people update you afterwards, you are informed;
- if they must wait for your reply first, you are a required step in the process.
This is not a personal failure. A business can grow this way: one decision, one password and one client at a time. The owner solves the problem quickly, and the solution stays in their head. The mechanism works until that single point of passage slows everything else down.
Four different types of dependency
Not every interruption can be solved by writing a procedure.
1. Decision
Can I offer this discount?
A threshold may be missing: how far the person can decide independently and when they need to ask.
2. Information
Which version is the latest?
A reliable, recognisable and up-to-date source may be missing.
3. Access
Can you log in to the portal?
The problem may be a permission held by one person, a personal account or the lack of an authorised substitute.
4. Exception
The client is asking for something outside the usual process.
The answer is not necessarily a longer manual. People need to know which criteria to use and which boundary they must not cross.
Calling everything a “lack of autonomy” does not help. Naming the dependency lets you choose a small, specific response.
When there is no one to transfer it to today
You do not need to invent a manager or wait for an employee to join Slegato. The owner can start alone.
In that case, the mission does not promise a transfer that cannot happen yet. It looks for what to remove, reduce, batch or simplify; sets a safe default; makes the minimum context visible; or prepares the handoff for when a real lever becomes available.
A lighter dependency, transfer-ready work and a missing capability are useful outcomes, but they are not verified autonomy yet.
Do not start by mapping the whole company
The first impulse is to create procedures for every activity. The project immediately becomes enormous, so it gets postponed.
Slegato starts from the other direction: one real event.
Take the latest interruption you received and write down:
- what needed to happen;
- which blockage, slowdown or deterioration appeared;
- what only you had;
- the smallest step you can control directly;
- which real lever exists, if any;
- how you would observe the next event.
The smallest step might remove an exception, set a default, capture one essential note, prepare safe access or test a real case. If a lever is available, it can become a transfer. If not, it reveals the organisational capability that is missing.
The useful question is not “how indispensable are you?”
That question invites a judgement about the person. The operational question is:
What was the latest situation in which someone knew what to do but could not continue without your reply?
That is where the process still coincides with you.
Because it is a concrete event, you can change it without “reorganising the whole company”.
One less dependency
This week, do not count every call. Choose one real event that:
- has already happened more than once;
- is likely to happen again;
- can at least be reduced or simplified by you;
- produces an observable result.
Complete the owner-only step and observe the next event. If a real lever exists, prepare and test the transfer. The measure is not the document: it is what requires less intervention and what is still missing.
Start with the latest real event
Write down the latest point where the outcome depended on you. Not just a call: it may involve execution, knowledge, decisions, access, relationships, coordination, quality or handling an exception.
Start there. Not with the whole company.