Blocker Impact | Zyeon UI

ready · 76 tasks, 8 blockers, radii adding to 59 over 38 tasks actually held up

Blocked work · Squad Atlas

Every card on the board, with the ids each one holds up

38

tasks held up

of 76 on the board · 8 blockers · worst is Retire the search index writer, holding 31

held by 2 or more15 · 20%
held by exactly 123 · 30%
not held up38 · 50%

Blockers

ranked by blast radius · as of Mar 20

Blocked on a decision about whether we keep the legacy endpoint.
31 tasks held up · 18 only through this one · furthest is 6 hops away
- Harden the search index writer · 1 hop
- Cache dunning emails · 1 hop
- Batch the export queue · 1 hop
- Split the session store · 1 hop · also held elsewhere
- Harden the plan upgrade path · 2 hops
- Ship tenant onboarding · 2 hops
+25 more held up by this one

Bar length is the blast radius against the worst one (31); the solid part is what only that blocker holds, the faint part is also waiting on someone else.

2 further blockers are not listed; none of them is holding anything up.

Adding every blast radius gives 59, yet only 38 distinct tasks are held up. 15 of them wait on more than one blocker, so 21 of that total is the same task counted twice — clearing the top blocker alone will not release them.

Open a row to see what it is holding up.

empty · no board was returned

Blocked work · Squad Atlas

Every card on the board, with the ids each one holds up

No board to read

Blast radius is counted over a dependency graph, so this card needs the whole board — not just the blocked part. Send every task and the ids each one holds up.

loading

Blocked work · Squad Atlas

Every card on the board, with the ids each one holds up

error · transport failure, Try again recovers

Blocked work · Squad Atlas

Every card on the board, with the ids each one holds up

Couldn’t load this chart

The data source didn’t respond.

ready · radii of 5 and 4, yet only 6 tasks held up — 3 of them wait on both

Blocked work · shared fan-in

Two blockers, one shared fan-in

6

tasks held up

of 12 on the board · 2 blockers · worst is Vendor sandbox credentials, holding 5

held by 2 or more3 · 25%
held by exactly 13 · 25%
not held up6 · 50%

Blockers

ranked by blast radius · as of Mar 20

The vendor has not issued sandbox credentials for the new tenant.
5 tasks held up · 2 only through this one · furthest is 3 hops away
- Contract tests for the client · 1 hop · also held elsewhere
- Sandbox smoke suite · 1 hop
- Wire the checkout page · 2 hops · also held elsewhere
- Record vendor fixtures · 2 hops
- Enable checkout for beta tenants · 3 hops · also held elsewhere

Bar length is the blast radius against the worst one (5); the solid part is what only that blocker holds, the faint part is also waiting on someone else.

Adding every blast radius gives 9, yet only 6 distinct tasks are held up. 3 of them wait on more than one blocker, so 3 of that total is the same task counted twice — clearing the top blocker alone will not release them.

Open a row to see what it is holding up.

ready · ranked by task-days held up, top 4 only, board split hidden

Blocked work · Squad Atlas

Every card on the board, with the ids each one holds up

38

tasks held up

of 76 on the board · 8 blockers · worst is Retire the search index writer, holding 31

Blockers

ranked by task-days held up · as of Mar 20

Blocked on a decision about whether we keep the legacy endpoint.
31 tasks held up · 18 only through this one · furthest is 6 hops away
- Harden the search index writer · 1 hop
- Cache dunning emails · 1 hop
- Batch the export queue · 1 hop
- Split the session store · 1 hop · also held elsewhere
- Harden the plan upgrade path · 2 hops
- Ship tenant onboarding · 2 hops
+25 more held up by this one

Bar length is the blast radius against the worst one (31); the solid part is what only that blocker holds, the faint part is also waiting on someone else.

4 further blockers are not listed; 1 task wait only on them.

Adding every blast radius gives 59, yet only 38 distinct tasks are held up. 15 of them wait on more than one blocker, so 21 of that total is the same task counted twice — clearing the top blocker alone will not release them.

Open a row to see what it is holding up.

ready · a board with dependencies and nothing blocked at all

Blocked work · all clear

Same board, the week after the freeze lifted

Nothing is blocked

All 18 tasks on this board are free to move. There is no blast radius to rank, which is the answer people open this card hoping for.

ready · every blast radius is zero, and the clock falls back to the newest blocked task

Blocked work · nothing downstream

Stuck, but nothing is waiting on them

0

tasks held up

of 9 on the board · 3 blockers

held by 2 or more0 · 0%
held by exactly 10 · 0%
not held up9 · 100%

Blockers

ranked by blast radius · as of Mar 16

Waiting on a security questionnaire the customer has not returned.
Nothing downstream waits on this one — clearing it frees only itself.

Bar length is the blast radius, so every bar here is empty.

Nothing downstream waits on any of these: they are stuck, but they are not holding the board up.

No clock was supplied, so ages are measured from the newest blocked task (Mar 16) and that one reads as blocked today.

Open a row to see what it is holding up.

ready · a dependency cycle, an edge off the page, an unknown age and a future start

Blocked work · awkward feed

A cycle, edges off the page, and two ages that cannot be trusted

4

tasks held up

of 8 on the board · 3 blockers · worst is Reconcile the migrated epics, holding 3

held by 2 or more2 · 25%
held by exactly 12 · 25%
not held up4 · 50%

Blockers

ranked by blast radius · as of Mar 20

Imported from the retired board; half its links point at cards that are gone.
3 tasks held up · 1 only through this one · furthest is 3 hops away
- Extract the identity service · 1 hop · also held elsewhere
- Extract the accounts service · 2 hops
- Extract the billing service · 3 hops · also held elsewhere

Bar length is the blast radius against the worst one (3); the solid part is what only that blocker holds, the faint part is also waiting on someone else.

Adding every blast radius gives 6, yet only 4 distinct tasks are held up. 2 of them wait on more than one blocker, so 2 of that total is the same task counted twice — clearing the top blocker alone will not release them.

1 blocker can reach itself: this board has a dependency cycle. The walk visits every node once, so a loop is counted once rather than followed round.

2 edges were ignored — 1 pointing at ids this board does not carry and 1 pointing from a task back at itself. Dropping an edge can only make a radius too small, so every number above is a lower bound by that much.

1 blocker carry a start time after the clock; its age is reported as zero rather than negative.

Open a row to see what it is holding up.

error · two tasks exported under one id, refused by the contract

Blocked work · duplicated ids

Two cards exported under the same id

This board can’t be ranked

Two tasks share the id "step-d". Ids are how edges find their target, so a duplicate silently merges two cards and every radius downstream of them is wrong.