Blockers age like milk. Retros treat them like wine.

Ask a team "what's blocking you?" on Friday and you get history. Ask every morning and you get options. The difference between a three-hour-old blocker and a three-day-old one isn't severity; it's whether anything can still be done cheaply.

The three fields that make blockers actionable

Owner: not "the client is slow" but a name: whose action unblocks this. Age: hours or days waiting, counted automatically, because human memory systematically under-reports how long things have been stuck. Attribution: on the team, on a peer team, or external, because each routes differently. Internal blockers get a nudge; peer-team blockers get an escalation; external ones get a client conversation with a number in it ("this has been waiting on your sign-off for six days").

The most expensive sentence in operations is "oh, that? That's been stuck for two weeks, I mentioned it in standup."

Classification also produces the sentence every leader wants and no dashboard gives: "13 blocker themes this week. None waiting on you." When blockers carry attribution, a leader can see in one line that their own queue is clear and their job today is escalation, not unblocking. That's triage at the speed of reading.

Themes beat instances

One vendor stalling three projects looks like three separate complaints in three channels. Collected in one stream, it's a pattern with a name, and patterns are what leadership can actually fix. The blocker that repeats is rarely about the blocker; it's about the dependency nobody owns.

Efforti's blocker watch collects daily, attaches owner, age and attribution automatically, and chases the owner, not the victim.