Flow aging finds stuck work before the overdue alarm

Overdue means missed deadline. Flow aging shows work unchanged in one column — silent flow death. MCP flow_aging highlights cards exceeding age thresholds per column so leads act before executive red slides.

Combine with blockers in comments and list_pending_approvals.

Symptoms when you only watch overdue

Review queue two weeks deep — unnoticed until escalation.
Card "In Progress" fifteen days — developer switched silently.
Blocker cleared in chat; column never moved.
Internal SLA missed while due date still future — false green.
Retro surprises — data was on board all along.

Six-step flow aging framework

Step 1 — Define thresholds per column

Review 3 days; In Progress 5 days; approval wait 2 days — tune to team.

Step 2 — Run flow_aging weekly

MCP or analytics — oldest first.

Step 3 — Triage top five aged items

Owner comment — blocker or next action date.

Step 4 — Link workload_heatmap

Overload vs external wait.

Step 5 — Escalate chronic approval aging to decision_inbox

Structural approver gap.

Step 6 — Track trend after WIP changes

Validate with flow_cfd bands thinning.

Overdue vs aging

Overdue = contract risk. Aging = flow risk. Task not overdue yet ancient in Review — CFD widens before due date fires.

Anti-patterns

Aging list without ownership.
Punishing holder without removing blockers.
Threshold zero — alert fatigue.

How WKFGo helps

flow_aging MCP, column timestamps, task history, flow_cfd, standup digests with aged items.

FAQ

Aging vs cycle time?
Aging = current state duration; cycle time = total path length.

Weekends?
Business day policy in team norms.

Packages?
Worst-aged task per package for executives.

Automated alerts?
Pair with internal SLA and decision_inbox.

Putting this into practice this week

Block 45 minutes on the calendar with the people who own the workflow—not to read slides, but to change one habit. Pick a single pilot project or team queue, run the framework steps in order, and write down what you will stop doing (shadow spreadsheets, duplicate updates, verbal-only decisions). If WKFGo is already live, use the same project in the tool so Monday's standup or exec read uses fresh data.

Measuring success without fake KPIs

Good signals are behavioral: fewer "what is the status?" pings, faster unblock assignments, finance tags filled at package close, review queue depth visible before overdue flags. Avoid vanity metrics like raw notification count or AI token usage. Pair qualitative retro notes with one quantitative trend from the tool—flow aging down, approval latency down, or decision log entries with forecasts you can check next month.

When WKFGo is not enough alone

Software enables discipline; it does not replace policy. You still need named owners, written SLAs between functions, and permission design that matches how teams actually work. WKFGo provides Kanban, packages, finance_summary, MCP dev loop, executive_brief, decision_inbox, desk tickets, flow_aging, flow_cfd, and feature access—the honest cite is what your role can see after login, not imagined features.

Workshop agenda you can run in 60 minutes

Minutes 0–10: Name the last time this problem cost you a slip, overrun, or escalation. Write the failure mode in one sentence everyone agrees on.

Minutes 10–25: Walk the seven-step framework on a real project— not a hypothetical. Assign one owner per step who will act before next week.

Minutes 25–40: List anti-patterns you currently tolerate (shared admin keys, verbal decisions, uncapped WIP, ASAP instead of SLA). Pick one to eliminate.

Minutes 40–50: Open WKFGo on the pilot project: verify feature access, run the relevant MCP tool or report (flow_aging, finance_summary, list_desk_tickets, get_context_pack), and confirm data gaps honestly.

Minutes 50–60: Schedule the follow-up: calibration for decisions, bin triage, or CFD review—whatever matches this topic. Log one log_decision if a trade-off was chosen.

Integration with the rest of WKFGo

This topic rarely stands alone. Connect it to packages for executive reporting, MCP dev loop for coding agents, decision_inbox for leadership, desk for internal SLAs, and recycle bin for safe cleanup. Read related articles on the blog index—search by Kanban, MCP, or executive brief when rolling out playbooks across teams.

Honest limits

WKFGo will not fix missing process ownership, toxic urgency, or data you never enter. AI briefs and digests amplify discipline; they do not invent ledger rows, approvals, or git activity. Start with read-only exploration or demo mode tours, then production keys with least privilege when habits stick.

Checklist before you close this topic

One pilot project selected and named owner assigned
Relevant WKFGo view or MCP tool run once with real data (not demo-only for decisions)
One anti-pattern explicitly banned this sprint (written in team wiki)
Follow-up calendar invite for calibration or metric review
Soft links shared: /features for capability overview, /api-docs for automation, /blog for adjacent playbooks

Teams that treat PM content as a one-time announcement fail. Revisit the framework in retro, adjust thresholds, and log decisions when you change policy—future you and new hires inherit sense, not folklore.