> **The question:** My work is stuck waiting on my VP / another team / a dependency I don't control. I've flagged it. Nothing moves. Do I just wait and protect myself on the status update, or is there a smarter way to use the time without looking like I'm inventing busywork?
>
> *(a Staff Engineer / tech lead at a mid-size software company)*


The real question is not "wait or look busy." It is whether any work on your critical path only needs **time**, not the blocker.

Call that move **prefetch**. Do the work that does not need the missing decision, hire, or dependency. Do it only if the payoff is clear the day the blocker clears. Arrival day should not be day zero on your side.

Three steps:

- **Name the blocker.** One sentence. If you cannot name it, you are not blocked. You are scattered.
- **List what only needs time.** Specs, dry-runs, data pulls, stakeholder maps, draft decks, risk memos. Anything that lets you ship once the gate opens.
- **Write the arrival-day ROI in one line** before you spend attention or political capital. If you cannot finish that sentence, do not call it prefetch. Just wait.

The failure mode is cargo-cult parallel work: a pile of "useful" tickets that burn focus and look like motion while the real path stays stuck. Prefetch is not "keep busy." It is schedule you buy with judgment.

On the status update, say both halves out loud. Name what blocks you. Name what you are prefetching for clearance. That protects you. It also stops the org from treating your wait as normal, and it stops you from inventing theater.