Reading Your Board's Blocked Ratio Before the Launch Date Does
Most teams check their task board for what is finished and what is in progress. Fewer teams look at what is sitting still. A simple ratio, blocked cards compared with active cards, can reveal execution trouble weeks before a launch date becomes unrealistic. This article explains how to calculate that ratio, what it does and does not tell you, and how to turn it into a conversation about work rather than a verdict on people.
What the blocked ratio measures
The blocked ratio is the number of cards marked as blocked divided by the number of cards currently active, meaning cards in any column representing work someone is actively doing. A team with 12 active cards and 4 blocked cards has a ratio of about one third. The number itself is less important than its direction over time. A ratio that climbs steadily across three or four weeks suggests that work is entering the board faster than it can be unblocked.
The ratio works because blocked cards are often the earliest visible sign of a dependency problem. A design review that has not happened, a vendor answer that is overdue, or a decision that nobody has owned will all show up as blocked before they show up as a missed date. The board already contains this information. The ratio simply makes it countable.
Setting up the measurement without adding overhead
Start by defining what counts as blocked in your team's own words. A card should be marked blocked only when someone cannot proceed without an input from a named person or an external event. Vague labels like waiting on stuff make the ratio meaningless. Write the rule at the top of the board or in the team's working agreement so every member applies it the same way.
Then pick a fixed moment to record the number, such as the first thing on Monday or the end of each working day. Keep a simple log of date, active count, and blocked count. You do not need a dashboard. A spreadsheet with three columns is enough for most busy teams and founders. After two or three weeks you will have a trend line that is more useful than any single snapshot.
Questions to ask when the ratio rises
A rising ratio is a prompt for questions, not a conclusion. Start with the blocked cards themselves. Which blocker appears most often? If three cards are waiting on the same person, the bottleneck is a person or a decision queue, not three separate problems. If the blockers are scattered, the cause may be unclear scope or missing upstream definition.
Next ask how old the blocked cards are. A card blocked for two days is ordinary. A card blocked for ten days that still sits in an active column is a signal that the team has stopped looking at it. Check whether each blocker has a named owner and a date by which someone expects a response. Cards without either are the ones most likely to drift past a launch date unnoticed.
Finally ask whether the team is starting too much work. If active cards keep rising while completed cards stay flat, the ratio is partly a symptom of intake. Adding a work-in-progress limit to a column, even a loose one, forces a conversation about what should wait.
A short checklist for the weekly review
Use the following checklist during a fifteen-minute weekly review. First, record the active and blocked counts and compare them with the previous week. Second, list every blocked card and write the specific input it needs. Third, confirm that each blocker has one owner and a requested-by date. Fourth, identify any blocked card older than the team's agreed threshold, such as five working days, and decide whether to escalate, descope, or reassign it. Fifth, note whether any blocker depends on a decision that has not been made, and add it to the next planning agenda.
The purpose of this review is to keep the board honest, not to assign fault. When a blocker keeps appearing, treat it as a process question: what would make that input arrive faster next time? Teams that answer that question each week tend to see the ratio stabilize, and they usually discover the problem before the launch calendar does.