The questions that reach you are data.

Look at one week of an owner’s phone. Which form for a second opinion referral. Whether Friday afternoon is covered. Whether an intake can be scheduled before the payer responds. Whether the new hire is cleared to chart independently. Whether the lab courier invoice was approved. Five questions, five domains, one person answering all of them, usually between patients.

It is natural to see this as the price of ownership. Availability feels like leadership. It is more useful to treat it as measurement. Each question marks a decision that had no owner, no threshold, or no documented answer.

Every escalation marks the exact point where the system stops.

Two piles

Sort a week of questions into two piles. The first is genuinely novel: a new payer contract, a difficult clinical judgment, a hire, a real exception. Those belong at the top. That is the work of ownership. The second pile is repeat: the same question, asked by different people, every few weeks. Repeat questions are an authorship opportunity. A decision was made once, correctly, and never written where a second person could find it.

What the interruption costs

The cost lands on both sides of the interruption. Research on interrupted work found that people compensate by working faster and pay for it in stress, frustration, and time pressure.¹ In clinical settings the stakes are higher. A study of medication administration found that each interruption was associated with a twelve point one percent increase in procedural failures and a twelve point seven percent increase in clinical errors, with risk rising as interruptions accumulated.²

Westbrook et al., Archives of Internal Medicine 2010 · Mark, Gudith and Klocke, CHI 2008

Practices often respond to the repeat pile by becoming more available. That grows the pile. Faster answers teach the team to route more through the owner, until leadership bandwidth is consumed by decisions already made.

Bandwidth as an operational resource

The alternative is to treat leadership bandwidth as a finite operational resource and design what is allowed to consume it.

1. Decision rights named by role, so questions stop traveling upward by default.
2. Thresholds written as numbers, so a scheduler knows the line without asking.
3. Standard work documented at the point of use, in the workflow rather than a binder.
4. Escalation paths defined, so exceptions route in one step instead of three.
5. An operating rhythm, so recurring questions have a scheduled place to land.

Starting points

Five ways to turn questions into structure.

1. Log one week of questions. Write down every question that reaches you, who asked, and the topic.
2. Sort into two piles. Novel or repeat. Count each.
3. Write down three repeat answers. Put them where the team works: the EHR, the shared drive, the front desk binder.
4. Name one decision owner. Pick one recurring decision and assign it to a role with a clear threshold.
5. Set a weekly question huddle. Give non-urgent questions a scheduled home.

Resources