When You Don’t Have Anyone to Delegate To, Delegate to Structure

Build the structure once so that the same question stops costing you every time it lands.

On Monday, we talked about delegating up and sideways, renegotiating with whoever assigned the work, or trading with a peer. Both of those depend on another person being available and willing. Some weeks, they’re not: The supervisor is unreachable until next week. The peer is just as underwater as you are. The trade isn’t there to make.

That doesn’t mean delegation is off the table; it means the thing you delegate to changes. Instead of handing work to a person, you hand it to a system—something you build once that keeps absorbing the same request without your having to answer it personally each time.

When You Don’t Have Anyone to Delegate To, Delegate to Structure

1. Templates

   Notice which questions you answer more than once a week, in almost the same words each time: “When do grades post?” “How do I request a room change?” “What’s the deadline for X?” Each one feels small in the moment—which is exactly why it’s easy to keep answering them one at a time instead of noticing that they’ve become a pattern. A saved response, or a short FAQ doc you point people to, turns five individual replies into one thing you’ve only built once. The relief isn’t that the question stops coming—it’s that answering it stops costing you anything.

2. Standing Structures

   Office hours, a recurring drop-in slot, a shared doc where a team logs status instead of pinging you individually—these work the same way templates do, just on a slightly larger scale. Instead of fielding the same kind of request as it lands, scattered across the week and unpredictable, you contain it inside a structure that exists whether or not anyone uses it on that particular day. The unpredictability is often the more exhausting part, not the volume itself. A standing structure trades unpredictable interruption for a scheduled one.

3. Defaults That Don’t Require a Decision

   “Unless you hear otherwise, assume X” removes the need for anyone to check in at all. It’s delegation aimed at the decision itself rather than at the task. Fewer decisions routed through you means fewer moments where your presence is the bottleneck, even when you didn’t ask to be one.