Blocked-Card Triage: Surfacing Stalled Work Before Launch Dates Slip
Most task boards look healthy until a launch week arrives and three cards that have sat untouched for nine days suddenly matter. The board did not hide the problem on purpose. It simply lacked a consistent way to show that work had stopped moving. Blocked-card triage is a small habit that fixes this: a defined way to mark stalled work, name what it is waiting on, and review those cards on a fixed schedule. For busy teams and founders running launches or fast planning cycles, it is often the difference between a slip that gets caught on Tuesday and one that surfaces on Friday night.
Why blocked work hides in plain sight
A card in the In Progress column implies someone is working on it. In practice, many of those cards are waiting on a designer's review, a legal answer, a vendor's reply, or a decision nobody has made yet. Because the card has not moved columns, it looks like normal flow. The team's attention goes to the cards that are visibly changing, and the stalled ones drift.
The fix is not more columns for every possible wait state. Adding a complicated status taxonomy tends to get ignored within a month. A better approach is a single, explicit marker for "blocked," paired with one required piece of information: what the card is waiting on. If the reason cannot be written in a few words, the card probably is not blocked yet; it is undefined, and that is a different problem to solve.
Define what counts as blocked
Before anyone tags a card, agree on a definition the whole team can apply the same way. A workable one: a task is blocked when progress requires an input from a person or event outside the card's owner's control, and that input has not arrived. Work that is merely slow, or that the owner has deprioritized, is not blocked. Mixing those categories inflates the blocked column until nobody trusts it.
Write the definition where people will see it, such as at the top of the board or in the team's planning notes. Revisit it after the first two review cycles. Teams often find they need one or two exceptions, for example, work waiting on an internal freeze date, and it is better to name those explicitly than to let people improvise.
A triage routine that takes fifteen minutes
Triage works best as a short, fixed meeting or asynchronous pass held on a regular cadence, ideally twice a week during active launches. The goal is not to solve every blocker in the room. It is to make each blocked card answer three questions: what is it waiting on, who owns the unblock, and by when does the team need that answer to hold the current date.
Walk the blocked column from oldest to newest. For each card, confirm the wait reason is still accurate. If the blocker has resolved, move the card back into flow immediately rather than letting it sit with a stale tag. If the blocker has no owner, assign one during the meeting. If the blocker threatens a launch date, flag that to whoever owns the schedule.
Keep a simple tally as you go. Teams find it useful to note how many blocked cards are older than a set number of days, since age is a better early signal than count.
Questions to ask about any blocked card
A short list of questions keeps triage focused and prevents it from turning into a status debate:
- What specific input is missing, stated in one sentence?
- Who can provide that input, and have they been asked directly?
- When was the request made, and is there a reply date?
- If the input never arrives, what is the fallback, and what does it cost?
- Does this blocker touch a date someone outside the team is relying on?
If a card cannot answer the first two questions, it needs rewriting before anything else. Vague blockers such as "waiting on feedback" almost always stall because no one is clearly responsible for producing the feedback.
Keeping the habit alive
Triage routines decay when they feel like extra paperwork. Three habits help. First, make blocking cheap: tagging a card should take seconds, not a form. Second, reward the unblock rather than the block; celebrate when a long-stalled card moves, so people see the routine as useful. Third, end each triage session by naming the single blocker most likely to hurt the next milestone, and give it an owner before anyone leaves.
Over a few weeks, the blocked column becomes an honest picture of where the team is waiting on itself and on others. That honesty is the real value. A board that shows its stalled work early gives founders and busy teams time to act, which is far cheaper than discovering the same problem when the launch is already at risk.