The No-Surprise IT Playbook (Operator Insights)
If you’re joining on chapter three: Chapter one covers why work entering through side doors creates spend and delivery surprises, and why the first fix is routing exceptions into a single hub. Chapter two covers the One Queue Rule, because once work is routed, you still fail if the org runs on two backlogs.
This chapter assumes both are in place and addresses the override that breaks them: urgent work. Urgent will cut the line in every growth company. The only question is whether it does so with accounting or without it.
In growth companies, urgent work is normal. Customers are loud. Sales needs support. Ops needs fixes. Someone senior has a fire. IT is expected to be responsive, because IT sits underneath everyone’s workflow and becomes the last-mile resolver when reality doesn’t match the plan. The failure isn’t that urgent work exists. The failure is the accounting.
Most organizations treat urgent work as a free add-on. It cuts the line, but nothing gets paused. No one names the trade. No one records what got displaced. The system absorbs the hit until it can’t, and then everything slips at once, which is why “we were on track” turns into “everything moved” with no obvious trigger. Urgent didn’t break the plan by itself. Unaccounted urgent work did.
Delivery surprises are the obvious symptom: commitments slip, lead times get unpredictable, and the org can’t answer “when” without a performance. Spend surprises are the quieter follow-on effect. Once the system falls behind, it reaches for backpressure relief: vendors, overtime, expedited purchases, and “just get it done” shortcuts that feel temporary and then quietly become steady-state. The urgent item is visible. The debt you took on to process it is not.
This is also why status language degrades under load. When a team can’t make honest commitments, it starts using language to manage expectations instead: “almost done,” “in progress,” “blocked,” “waiting on,” and other phrases that often mean “we’re overloaded and the ordering is unstable.” Status becomes a coping layer for an ordering problem.
Urgent work is not the enemy. The enemy is treating urgent as if it doesn’t consume capacity. In any real system, capacity is finite. If something jumps the line, something else must move. If nothing moves, you’ve created hidden WIP and hidden delay, and the bill shows up later as a cluster of misses instead of one explicit trade.
Simple rule: urgent in requires something out. If leadership wants urgent responsiveness, leadership also needs the displacement and the impact to be visible, because leadership is already making the trade. They’re just making it silently through escalation and side channels.
The solution is explicit trading. Urgent can break the line, but it forces a decision: what gets stopped, and what is the impact. That decision belongs in the hub, where the queue is ordered, because the hub is the only place where the trade can be made against the full portfolio of “real work,” including the work nobody wants to admit will slip.
Explicit trading has three effects that matter:
When an urgent item shows up, the hub makes the trade explicit. The urgent work gets an owner and a definition of done. It gets placed in the ordering. Then the hub records what moved down or what paused, with a plain-language impact: “This urgent work displaces X; Y slips by two weeks,” or “We pause Z; it resumes after this closes.” The record is not for punishment. It’s for truth.
This is where the system stops rewarding escalation and starts rewarding clarity. If someone wants urgent treatment, the trade becomes part of the request. That single constraint changes behavior across the org, because people quickly learn the difference between “urgent” and “important,” and leadership is forced to spend urgency on what actually matters.
When it works, the org stops pretending it can do everything at once. Responsiveness stays high, but it’s paired with honesty about cost and displacement. Urgent becomes a controlled mechanism instead of a silent tax.
Simple principle: urgent requires a trade, named and visible.