Office Hours and Asynchronous Request Queue¶
Coordination protocol — instantiates Distraction Minimization for Deep Engagement
Routes ordinary coordination into published response windows or a shared request queue, giving collaborators a reliable path to a reply without any of them getting to interrupt the work in the moment.
Most of the interruptions a focused worker absorbs are not emergencies — they are ordinary coordination arriving synchronously: a "got a sec?", a quick question, a review request, a status check. Each is reasonable on its own, and each is a real-time bid to pull someone out of deep work now. Office Hours and Asynchronous Request Queue does not try to block those requests or make a boundary visible; it gives the deferred request somewhere legitimate to land. Ordinary coordination is routed into known service windows (posted "office hours") or a durable queue (a ticket channel, a shared request list), where it is answered in batches on the responder's schedule rather than the asker's. Its defining move is that deferral comes with a reliable path to a reply — so protecting focus doesn't strand the collaborator, and no single ask gets to claim the present moment simply by being asked out loud.
Example¶
A staff engineer on a platform team has become the person everyone pings — teammates DM her all day for help with the deployment tooling, and her own project never advances more than fifteen minutes before the next "quick question." She stops answering in real time and stands up a protocol instead. Non-urgent tooling questions go to a #platform-help channel that she and one teammate triage; anything there gets a first response within one business day. On top of that she posts two live office-hours windows a week — Tuesday and Thursday, 2:00–3:00 — when she is genuinely, cheerfully available for whatever the queue has surfaced or whatever anyone wants to walk through. She announces the change once, pins the norm, and then holds the line: a mid-morning DM gets a friendly "drop it in #platform-help or grab me at office hours." Within two weeks the drive-by questions nearly stop, the channel fills with well-formed asks that are often answered by other teammates before she gets to them, and the questions that do reach her arrive batched into a window she has budgeted for exactly this. The team is no less supported; it is supported on a schedule.
How it works¶
- Publish the windows and the queue. Name specific times you are available for coordination, and provide a single durable place (a channel, a form, a board) where requests accumulate between windows. Both must be easy to find, or people default back to interrupting.
- State the latency contract. Promise a response horizon — "answered within a day," "handled at the next office hours" — so the delay is a known agreement, not a silence people have to worry about.
- Triage and batch in the window. During the window, work the queue in one pass: cluster related asks, answer the common ones publicly so the next person finds the answer already there, escalate the few that need more.
- Redirect gently but consistently. An out-of-band request is met with a pointer to the queue, not an answer. The protocol only holds if the easy path and the reliable path are the same path.
Tuning parameters¶
- Window frequency and placement — how often and when the live windows sit. Frequent windows keep latency low but fragment the responder's own week; sparse windows protect depth but back the queue up.
- Queue vs. live office hours — how much coordination is handled purely asynchronously in writing versus reserved for a synchronous window. Async scales and creates a searchable record; live windows resolve ambiguous or relational asks that text drags out.
- Latency promise — how quickly the queue is worked. A tight promise reassures askers but pulls the responder back often; a loose one protects focus but tempts people to bypass a queue they don't trust.
- Triage staffing and rotation — who works the queue, and whether the duty rotates. Concentrating it protects everyone else's focus but loads one person; rotating it spreads the interruption fairly.
- Coverage scope — which requests are in-scope for the channel versus genuinely belong elsewhere. Too broad and the queue becomes a catch-all no one can keep up with.
When it helps, and when it misleads¶
Its strength is that it reconciles the two things a maker and a team both need — deep continuity and real responsiveness — by moving coordination off the interrupt path and onto a scheduled one. It is the practical answer to the clash between the maker's schedule and the manager's schedule: a maker needs long unbroken blocks, and a single "quick sync" can wreck an afternoon; office hours offer a manager-compatible slot without surrendering the day to it.[n1]
Its failure mode is the queue that becomes a black hole: if requests languish and the latency promise isn't honored, people stop trusting the channel and revert to DMs, and the whole protocol quietly collapses back into interruption. A related misuse is displacement — the responder protects her focus, but whoever staffs the queue simply absorbs all the fragmentation, so the interruption burden is moved rather than reduced. The guarding discipline is to treat the latency contract as a real commitment, rotate or share the triage duty so no one role eats the cost, and watch the queue's health (age of the oldest open ask) as closely as the focus it protects.
How it implements the components¶
interruption_policy— it is the standing rule for ordinary coordination: such requests are routed to the queue or deferred to a window rather than answered in the moment. Where Notification Batching or Blackout governs the delivery of digital alerts, this governs where human requests are allowed to land.attention_budget— the posted windows dedicate a bounded, deliberate slice of attention to coordination and wall off the rest for deep work, making explicit how much capacity goes to responsiveness versus depth.collaboration_expectation_set— the published windows and latency promise give the whole group a shared, dependable contract for how and when to get help, so no one has to guess whether interrupting now is acceptable.
It does not reserve or name the protected interval itself (that is Time-Blocked Focus Session), keep the narrow break-glass path for a true emergency (that is the escalation side of Notification Batching or Blackout), or help the person rebuild the thread after a break (that is Reentry Checkpoint).
Related¶
- Instantiates: Distraction Minimization for Deep Engagement — routes ordinary coordination off the interrupt path so continuity can survive.
- Sibling mechanisms: Time-Blocked Focus Session · Notification Batching or Blackout · Quiet Zone or Focus Signal · Single-Task Surface Preparation · Focus Start Ritual · Reentry Checkpoint · Stimulus Audit Walkthrough
Editorial Notes¶
Form Classification¶
Form family: Protocol, Workflow & Routine
Rationale: Office Hours and Asynchronous Request Queue operates as a repeatable ordered procedure or handoff sequence that coordinates action because it routes ordinary coordination into published response windows or a shared request queue, giving collaborators a reliable path to a reply without any of them getting to interrupt the work in the moment.
Independent corroboration: The frozen evidence defines Office Hours and Asynchronous Request Queue as 'Routes ordinary coordination into published response windows or a shared request queue, giving collaborators a reliable path to a reply without any of them getting to interrupt the work in the moment', so its operative form is Protocol, Workflow & Routine.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Work design and coordination practice developed published availability windows and shared queues that preserve reliable access without continuous interruption.
Related originating lineages:
- Education & Pedagogy — Academic office hours provide an established independent lineage for bounded, predictable access to an expert outside the flow of primary work.
- Human-Computer Interaction — Asynchronous collaboration tools supply the shared queue and visible response path.
Review resolution: Both independent reviews agree on primary origin organizational_management; reconciliation resolves alternate_origin_disagreement, origin_mode_disagreement. Formative alternate lineages retained: education_pedagogy, human_computer_interaction. The broader reach of later applications is kept separate as domain_reach=multi_domain; origin_mode=cross_disciplinary_synthesis describes the historical relationship among lineages. Confidence is conservatively reconciled to high, and encyclopedia_synthesis=true preserves the reviewers' boundary judgment.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
This mechanism is the receiving half of a pair: it only earns its keep when some boundary is actually deferring requests toward it. Time-Blocked Focus Session explicitly consumes it for that reason — a focus block that defers a colleague needs a real place for that colleague to go. Stood up on its own, with no boundary sending traffic its way, an office-hours channel is just one more inbox to monitor.
[n1] Maker's schedule, manager's schedule — Paul Graham's distinction between people who work in long uninterrupted blocks (makers: writers, programmers, designers) and those who work in hourly slots (managers), for whom a meeting costs little. A single synchronous interruption can cost a maker a whole session, which is why offering a scheduled window is not rudeness but the maker's way of staying reachable without surrendering the day. ↩