Why blockers are first-class objects

Most PM tools treat a blocker as a comment or a status. Both are weak. A comment scrolls past. A status is just a label.

We made blockers their own object. They have an owner, a duration, and a nudge cadence. They show up on the Blockers Board independent of which ticket they're attached to. They can be resolved without resolving the underlying task.

The change in behavior was immediate. Teams that previously logged one or two blockers a week started logging five or six. Not because there were more blockers. Because the cost of logging dropped.