A question can be quick for the person asking and still interrupt the owner long after the message is answered. It arrives between sessions, during payroll, or while you are trying to solve something that already required your full attention. You answer because you care, because you know, and because answering feels easier than letting someone wait.
Then it happens again. The problem is no longer one message. The practice has quietly learned that the owner is the fastest route to almost everything.
“Send fewer messages” will not fix that. People need to know where a question belongs, who can answer it, when to expect a response, and what truly needs escalation.
The conversation behind the quick question
In The “Quick Question” Trap · Listen on Spotify, Emily Mori connects small requests to invisible labor and owner dependence.
Her examples come from experience, not a universal policy. Every practice still has to account for its services, staffing, contracts, clinical obligations, and jurisdiction.
A boundary should make support clearer, not colder
The operating lesson is simple: a healthy boundary is not a wall. It is a dependable route.
The goal is not to make staff handle everything alone. It is to stop one informal message channel from carrying clinical consultation, workflow questions, employment concerns, confidential issues, and owner-level decisions all at once.
Give each kind of question a first stop
Start with the routes people actually need:
| Internal need | First route | Backup route | Bring in the owner when |
|---|---|---|---|
| Clinical consultation | approved supervisor or consultation process | named clinical backup | the defined threshold requires owner authority |
| Workflow or access issue | operations route | designated coverage | the exception exceeds that role's authority |
| Employment question | manager or reviewed people process | qualified alternate route | an accountable owner decision is required |
| Confidential concern | documented confidential channel | external or alternate process where appropriate | policy gives the owner a specific role |
| Strategic exception | decision owner for that area | scheduled leadership review | risk, resources, or direction require it |
This is an operating example, not clinical, crisis, employment, or legal language. The people responsible for those areas must design and review the actual routes.
If the table feels hard to complete, that is useful information. It usually means the practice has been depending on familiarity—who happens to know whom, who responds fastest, or who feels safest to ask—instead of a support system everyone can understand.
Make the request easy to recognize
Most internal questions fit one of five classes:
- Information: the answer should already live somewhere reliable.
- Action: someone needs to complete a bounded task, such as updating access or correcting a workflow.
- Decision: a person with authority must choose among valid options.
- Consultation: the request needs judgment or expertise.
- Escalation: safety, material risk, a policy conflict, or another practice-defined threshold is involved.
People do not need a forty-page manual to use these categories. They need a few examples that sound like their real work. If staff routinely disagree about where a question belongs, improve the example or the route. Telling people to “use judgment” cannot rescue a system that never made the judgment call clear.
Set a response promise the practice can keep
For each request class, write down:
- the approved channel;
- who owns the first response;
- the normal response window;
- what information the sender should include;
- what moves the request to another route;
- who provides backup coverage.
Be honest about timing. A realistic response window builds more trust than an unwritten expectation that the owner is always available. Care does not require instant access. It requires people to know what will happen next.
Stop rewarding the shortcut
This is the uncomfortable part: owners often teach the dependency they are trying to escape. You answer first, step around the assigned lead, or solve the same exception again without fixing the missing rule. Each rescue makes the next direct message completely rational.
When a question lands in the wrong place, redirect it without punishing the person who asked. Name the correct route, explain when it will be reviewed, and notice whether the official route was genuinely unclear. If it was, fix the system. If it was not, keep using the system.
Staff should feel safe asking for help. The owner should not have to be the only safe person to ask.
Review the pattern, not the person
Once a month, sample the questions coming through the busiest channel:
- Which categories appeared most often?
- Which requests arrived without enough information?
- Which routes were skipped?
- Which decisions still required owner approval?
- Which answers should become documentation, training, or an automated acknowledgement?
The goal is not zero questions. Silence can hide confusion and risk. The goal is for questions to reach the right person with enough context and a predictable next step.
Choose the channel creating the most interruption and map one recent week. Define the first route and escalation point for each request, then test the map with the people who will use it before you call it policy.
Put the operating question to work
Replace one recurring interruption with a route, an owner, and a response window.
Use the health check to place this question in the wider operating picture. The result is a starting point for review—not a legal, financial, employment, clinical, or supervision determination.
Draft a communication-and-escalation map