Sometimes product delivery status is communicated in "watermelon" form - Everything is green and good externally, but everyone on the teams knows status is red internally. Blocked helps you see real-time what work is flowing and what isn't.
Understanding the number of blockers in progress helps understand and manage the risk of delay. Observing the trend over time helps you anticipate future blocker loads on teams and establish strategies to mitigate and avoid bad outcomes.
Blockers can be tagged in ways that help you identify the sources and reasons work gets blocked. You can see in an instant what are the most frequent and most impactful blocker types - so you can fix the root cause and avoid FUTURE blockers!
Shepherding product features from idea to customers is a lot like herding cats. You have to be vigilant to see where some cats get distracted with other balls of yarn and help them get back on course. "Blocked" can help you monitor features' progress and manage coordination to keep the flow in a more forward trajectory.
"Blocked" brings all of the past and current blocker data into clear analytics. These analytics help sense and respond to changing delivery teams' pressures, giving you ways to anticipate next week's and months' problems and mitigate them. It might be a downstream constraint that is becoming critical to your success. The ability to see that constraint earlier means you can lessen its impact or avoid it altogether.
"Blocked" is about avoiding problems, not just dealing with them faster. Just by using "Blocked" you can see real-time what sources and reasons workflow is blocked and frequency and impact rankings compared to prior months. Solving the root causes for the top three causes means that future work isn't "Blocked." - this was the intention of Lean and Agile practices for software development, removing waste. "Blocked" quantifies what waste is worth removing.