Work Nobody Was Waiting For
Read what each party saw, commit to a cause, and only then find out which of them was right. The root cause, why the obvious reading was wrong, and the fixes are all held back until you have answered.
The symptom
What was reported, before anyone knew what was happening.
What each party saw, and what each concluded
The evidence, in the form it actually arrived in — several parties, several partial views, several confident conclusions.
| Who | What they could actually see | What they concluded | Verdict |
|---|---|---|---|
| Search backend | A steady stream of valid queries and its own queue growing. | Demand exceeds capacity; every queued query must be executed. | ✕ wrong |
| API gateway | Requests exceeding its 3s deadline; returned 504 and closed the connection to the client. | Request over; move on. | ✕ wrong |
| Search frontend (middle tier) | Its call to the backend still open; no cancellation from the gateway. | The client is still waiting; keep the request alive. | ✕ wrong |
| Capacity engineer | CPU pinned at 100% with a request rate only 1.4× normal. | The backend needs 2× the fleet. | ✕ wrong |
4 of 4 parties reasoned correctly from what they could see and still reached the wrong conclusion. Nobody in this table is careless. Each one acted on complete-looking local information, and the information was local. That gap — between what a node can observe and what is true — is the whole domain, and one of these readings will usually be yours.
Commit before you read on
Request rate rose only 1.4× but useful throughput collapsed. Commit before reading on: explain how a 1.4× increase in arrivals produces a majority of wasted work, and say why doubling the fleet might not have fixed it.
Write it down even if you are unsure. An unwritten guess quietly becomes “that is what I thought” the moment you read the answer.