Workboard Pro and the Two-Week Stall Test: Finding Where Execution Rhythm Goes Quiet

Workboard Pro is built for private workboards used in launches, planning, and fast-moving teams, and most teams using one share a quiet problem: work does not usually fail loudly. It drifts. A card sits in a column long enough that everyone stops looking at it, and by the time someone asks about it, the window to act has closed. This article describes a simple review method called the two-week stall test. It asks a single question of every active item on your board: has this card been in its current state long enough that a reasonable person would have expected it to move? The answer tells you where your execution rhythm has gone quiet, and it does so without requiring a status meeting or any new reporting ritual.
Why stalls are easier to miss than failures
A failed task usually announces itself. Someone reports a bug, a vendor says no, a deadline passes. A stalled task produces no event at all. The card simply stays where it was, and each day that passes makes it a little more normal for it to be there. Busy founders and team leads are especially prone to this because their attention moves toward whatever generated a message or a meeting that morning. Cards that have not generated friction tend to go unexamined.
The practical consequence is that you cannot rely on the board to tell you about problems through motion alone. A board with lots of movement can still hide a cluster of cards that have not moved in weeks. Execution rhythm, in the sense of a predictable pace at which work advances, depends on noticing the absence of movement as clearly as its presence.
Running the two-week stall test
Set aside about twenty minutes once a week. Open the board and look only at cards that are in active columns, meaning work someone has said they are doing. Ignore backlog and archive. For each active card, note how long it has been in its current column. Most boards display this or allow you to sort by last change. If your version of the board does not show time-in-column directly, you can estimate it from the last activity on each card.
Flag any card that has stayed in an active column for more than two weeks without a comment, a checklist change, or a moved date. The threshold is a starting point, not a rule. A research spike may reasonably sit for longer, while a launch asset due Friday should not. The point is to make the stall visible enough that someone must say whether it is intentional. For each flagged card, ask three questions: Is this still the work we intend to do? Who is the named owner, and have they touched it recently? What is the next concrete action, and when is it due?
Separating real waits from forgotten work
Not every stall is a problem. Some cards are waiting on something outside the team, such as legal review, a customer reply, or a dependency in another workstream. These are legitimate waits, and the useful move is to make the waiting explicit. Add a short note naming what the card is waiting on and who is responsible for that thing. A card that says 'waiting on pricing sign-off from the finance owner, asked on the 3rd' reads very differently from one that simply sits.
Forgotten work has a different signature. The owner cannot quickly say why it is still open, the next action is vague or missing, and nobody has asked about it. For these cards, the honest options are to re-commit with a date, reassign, or close them. Keeping a card open out of politeness is one of the most common ways a board loses its usefulness.
A checklist for the weekly review
Use this short list each time you run the review, and keep it in the same place so the habit stays consistent:
First, confirm that every active card has a named owner. A card without one is a stall waiting to happen. Second, check that each active card has a next action written in plain language, such as 'send draft to two reviewers' rather than 'work on proposal.' Third, flag any card unchanged for more than two weeks and record the reason in one sentence. Fourth, look for clusters: if three or more cards in the same workstream are stalled, the problem is probably a dependency or a decision, not three separate lapses of effort. Fifth, decide on each flagged card as one of four outcomes: continue with a date, add a waiting note, reassign, or close.
Teams sometimes ask whether this review should be shared with everyone or kept to the lead. In most cases a brief shared pass works better, because the people who own stalled work are the ones who can explain it, and a stall that surfaces in front of its owner gets resolved faster than one discussed behind their back. Keep the tone to questions rather than verdicts.
Keeping the habit alive
The two-week stall test only works if it becomes routine. Tie it to a recurring slot that already exists, such as the start of the week or the end of a planning session, rather than creating a new meeting. Watch for the failure mode where the review becomes a ritual of marking cards without changing anything. If the same cards are flagged three weeks running with no decision, the review itself has stalled, and the fix is to escalate the decision rather than add another flag. Over time, teams that run this check tend to notice their stalls earlier, write clearer next actions, and spend less energy reconstructing what happened to a launch item. That is the practical benefit of a steady execution rhythm: fewer surprises, not more meetings.