A team can have a full calendar and still lose its day to questions arriving one by one. Telling everyone to “interrupt less” leaves them guessing which issues matter enough to raise. A shared triage rule makes that decision more explicit.
Define urgency through consequences
Ask what happens if the question waits until the next planned check-in. A blocked customer service, an immediate safety concern or a time-limited decision may need a different route from a routine request for wording feedback. Use examples from the team’s actual work rather than an abstract definition of urgent.
Keep the categories few enough to remember. One possible arrangement is immediate contact for agreed critical issues, a scheduled question window for work blockers, and a shared queue for ordinary requests. This is an example to adapt, not a universal productivity system.
Make the request easier to assess
Ask the requester to include the decision needed, the deadline and what they have already checked. “Can you help?” creates another exchange before anyone knows the problem. “I need approval for this change by 14:00 because dispatch closes at 15:00” gives useful context.
The receiving person also has responsibilities. A queue that nobody reviews encourages people to bypass it. Name an owner, a review rhythm and a way to escalate when the agreed response time is missed.
- Agree which channel serves each urgency level.
- Protect a route for sensitive or private concerns.
- Allow people to correct a mistaken urgency judgement.
- Review recurring questions for missing documentation.
Try the arrangement for a short period and discuss specific examples. Did an important issue wait too long? Did the queue become a hidden backlog? Change the rule when the evidence shows a problem.
The purpose is clearer coordination, not making people earn permission to speak. A good interruption rule helps someone raise a genuine concern promptly while giving ordinary questions a dependable place to go.