The desk at the back
Most venues have one. A desk, or a rack, or a corner with cables, that one or two people understand and nobody else touches.
It was not designed to be that way. It accumulated. Someone added a thing, someone else configured something, a fix was applied that was never written down, and each addition raised the threshold slightly for anyone arriving new.
Eventually the only person who can operate it is the person who was present for all of it.
That is the barrier, and it is worth being precise about what it costs.
What the concentration costs
It makes the venue fragile. When that person is away, unwell, or has moved, something that used to work stops working. The knowledge left with them.
It excludes people who would help. Plenty of people would volunteer. Very few will volunteer for something that looks like it requires expertise they do not have, and a desk that only one person understands looks exactly like that.
It burns out the person holding it. Being indispensable is exhausting. It means you cannot be away, cannot be unwell, and every week is your responsibility whether or not you have capacity. People in this position frequently continue long past the point where they wanted to, because stopping means the thing stops.
It concentrates the failure. One person's bad day is the venue's bad day.
None of that is anyone's fault. It is what happens to a system that grows without anyone being responsible for keeping it learnable.
Two ways to respond
Transfer the knowledge. Train more people, write documentation, run sessions. Sensible, frequently attempted, and it usually decays. Documentation goes stale, trained people leave, and the system keeps accumulating. You are running to keep up with something that grows faster than you can teach it.
Reduce the knowledge required. Change the system so less has to be known. Fewer components, fewer steps, fewer invisible states, fewer things that must be remembered.
The second is harder to start and it compounds in your favour instead of against you. Knowledge that does not need to exist does not need transferring, cannot go stale, and does not leave when someone does.
What reducing it looks like
Fewer separate things. Every distinct piece of equipment or software is a boundary requiring someone to understand both sides. Four tools chained together needs someone who knows all four and how they connect. That person is rare, and you have made yourself dependent on them.
Visible state. A large share of specialist knowledge is knowing where to look to find out what is currently true. If the current state is visible without navigating, that knowledge stops being specialist.
Fewer invisible requirements. Anything of the form "you also have to remember to..." is knowledge that lives in a person. Every one you remove is one that cannot be forgotten by someone tired.
Defaults that are right. A setting that must be adjusted every time is a step someone must know about. A default that is correct for the common case removes it entirely.
A way back to known-good. The most valuable single thing. If anyone can return the system to a working baseline, then being wrong stops being frightening, and people will try things. Fear of an unrecoverable mistake is what keeps new volunteers from touching anything.
The uncomfortable part
There is a reason this does not happen naturally, and it is worth naming.
The person who understands the system is usually the person who would have to simplify it... and simplification often means removing things they built, or admitting that a clever arrangement is a liability.
It also reduces their indispensability, which is a strange thing to ask someone to do. Being needed is a real form of belonging, and "make yourself less essential" is a harder ask than it sounds, particularly for someone who has given years to this.
I would put it the other way round: being indispensable is a trap that looks like appreciation. The person who cannot be away is not being valued; they are being depended upon in a way that removes their choices. Making yourself replaceable is what lets you be there because you want to be.
Why I care about this
This shapes what I build, and it is worth being explicit rather than implying it.
Every time I consider a feature, there is a version that is more capable and a version that requires less knowledge. Those pull in opposite directions, and the capable version is usually more impressive.
I lean toward the second, and it costs me things... features that would demonstrate well, controls that expert users would want, flexibility I could have offered. That is a real trade and I make it deliberately, because a venue where only one person can run the system is a venue that will eventually stop running it.
I have watched that happen. Someone who had carried a booth for years left slowly, without a note and without a sound, because the weight had quietly stopped being a privilege. The passion that once kept him there until midnight getting the audio right had become a burden. Nobody replaced what left with him, because most of it had never been written down.
The booth should not be the barrier. Not to volunteering, not to a service reaching people, not to someone being able to take a week off. If a building's ability to gather depends on one person's availability, the technology has failed at something more important than any feature.
What you can do
If you are the person who understands it:
Write down the three things that only you know. Not documentation... three lines. The things that would leave with you.
Find the one step that could be removed and remove it. Not all of them. One.
Let someone else run it while you watch. Do not help. Note where they struggle. That is your list.
Take a week off deliberately, while you are still available to be called. Better to find the gaps when you are reachable than when you are not.
If you are the person who wishes they could help but does not feel qualified:
You are probably more capable than the desk makes you feel. The complexity you are looking at is accumulated, not necessary... and most of it is not something you need to know.
Ask for one job. Not the desk. One job.