Blocked, Not Blamed

The problem in one breath

Monday you read the promise list and three things aren't done. Your gut says find out who dropped the ball and let him have it. So you do — and the next week that guy just gets better at dodging, not at delivering. The promise still didn't happen, and now he's hiding the next one from you too.

Why it happens

A missed promise looks like a people problem, so you go at the person. But most promises don't die because a man is lazy — they die because something got in the way and nobody cleared it. The permit never got pulled because the county line was busy all afternoon. The supplier callback never happened because the number lived on a sticky note that blew out the truck window. Chew the man out and that snag is still sitting there, ready to eat the next promise the exact same way.

The play

When a promise comes up not-done, you run three questions — calm, same three, every time. That's the blocked-not-blamed review. Not "why didn't you," but "what got in the way."

1. What stopped it? The real snag, not the excuse. "The permit's not pulled" — fine, what actually stopped it? The office sat on hold with the county for an hour and gave up. That's the snag. Name the thing, not the man.
2. Do we still need it? By when? Sometimes the answer is no — the job moved, the homeowner pushed the date, it stopped mattering. Kill it and move on. If yes, put a fresh due date on it right there. A promise with no new date is a promise that dies twice.
3. What one change keeps this same snag from blocking it again? This is the whole point. One fix, small and specific. "Office pulls permits first thing at 8, when the county line's open — not at 4 when it's jammed." That fix becomes its own promise on the list: named, dated, owned.

Then wire it back to the board. Mark the promise Stuck on the promise list, and write what stopped it and the fix you agreed in the blocker column beside it — a few words is plenty. Next Monday you're not guessing why it stalled; it's written down. Stuck isn't a scarlet letter. It's a flag that says "this one needs a fix, not a lecture."

Do this enough and something shifts in the crew. Men stop hiding the misses, because a miss isn't an ambush anymore — it's just the moment the two of you fix the system. The guys who used to cover their tracks start bringing you the snag early, while there's still time to clear it.

Do this this week

Next time a promise on the list comes up not-done, swallow the "why didn't you" and run the three questions instead: what stopped it, do we still need it and by when, what one change stops the same snag. Mark it Stuck and write the blocker beside it. One promise, handled that way. That's the shift.

The tool

No new tool — this runs on the promise list from the anchor play (Module 2, Play 1). The three questions live in your mouth; the Stuck status and the blocker column next to it hold what got in the way and the fix you agreed to.

If your crew is 1099

The same three questions work with a sub, but keep the frame contractual. You're not coaching an employee through his blockers — you're finding out what stalled a deliverable you're paying for, and setting a new date under the agreement. "What one change" is a conversation between two businesses about how the work gets handed off — who calls the supplier, who confirms the permit — not you reaching into his crew to fix how they run. Adjust the deal and the handoff; leave his methods to him.