A standing meeting with a previous-to-do review creates accountability for long-running projects that no one owns full-time.
Key Takeaways
The core mechanic: open every meeting by reviewing action items from the last one, creating pressure to show tangible progress.
Targets the “nobody’s full-time job” failure mode where strategic, multi-month work sinks under daily fires and email.
Works across org boundaries: consulting firms can use a steady cadence to surface when client-side tasks haven’t moved.
Weekly, bi-weekly, or monthly all work; cadence choice should match project urgency, not habit.
The standing meeting gives a cross-functional effort a shared heartbeat when no single owner can mandate prioritization.
Hacker News Comment Review
Strong pushback that the meeting becomes the deliverable: once a recurring block is on the calendar, the implicit contract shifts from “make progress” to “show up,” and the block outlives its purpose.
A counter-pattern had real support: scheduling meetings only when there is something specific to discuss, with a written agenda per event, reportedly drove more actual team communication than fixed recurrences.
Commenters who have run multi-person projects flagged that recurring meetings often mask a root cause – leadership failing to protect time for long-term work – and that managers should diagnose that before adding calendar pressure.
Notable Comments
@msteffen: argues managers who can’t explain why strategic goals stall are substituting “arm-twisting and event-planning” for actual decision-making.
@gwbas1c: lists specific failure modes to watch: meetings used as group procrastination, as ego platforms, and confusion of meetings with actual collaborative work.
@Brystephor: tried a fully async project structure with Slack channel and milestone ownership; found it broke down in practice and shifted toward structured check-ins.
