What’s the best way to structure weekly team check-ins to move projects forward?

[JasonZR]

I’m struggling with how to structure my weekly team check-ins to actually move projects forward. I keep defaulting to just a status update round-robin, but I know we need a more disciplined approach to discussing roadblocks and resource needs.

[Stella_S]

We switched to a three bucket format in our weekly check-ins: wins, blockers, needs. Keeps it tight, about 20 minutes, no status ping-pong. We pre-fill a blockers list in a shared doc and call out one blocker for a quick deep dive each week. It helps move things forward because people come with concrete asks, not generic updates.

[Robert.C]

We tried a different angle: assign an owner to each blocker and a target resolution date. If we can't pin a date in the hour, we move it to the backlog with a new due date and we track all resource needs in a tiny board. That seemed to corral escalation a bit.

[JustinR]

Maybe the real issue isn't cadence but the backlog itself. If blockers are the same handful of people month after month, maybe the scope or dependencies are off. Is it possible we're solving the wrong problem?

[FrankBP]

Coffee habit aside, we did try a two minute silent pre-read where everyone hits submit on what blocks them, then we dive into discussion. It felt faster, though we still drifted and chased shiny things.