Running a weekly team review in 15 minutes
Most managers never step back and look at their team as a whole. The week is a blur of meetings and Slack, one thing bleeds into the next, and the only time anyone takes stock is when something has already gone wrong. A short, deliberate weekly review fixes that — and it doesn’t need to take more than fifteen minutes.
This is a review you do for yourself, not a meeting you run. Same time every week, just you and your team’s reality, asking a handful of questions on purpose.
Why a weekly review is worth the time
Fifteen minutes a week buys you the thing managers most lack: perspective. It’s the difference between reacting to problems after they’ve surfaced and catching them while they’re still small. It keeps the quiet people from slipping through, the slow slides from becoming surprises, and the important-but-not-urgent from being permanently crowded out by the urgent.
The 15-minute structure
Four questions, a few minutes each.
1. What shipped, and what didn’t? (4 min)
The honest delivery picture. What got done, what stalled, what slipped and why. You’re not collecting a status report — you’re looking for the gap between what you expected and what happened, because that gap is where the real information is.
2. What’s at risk next week? (4 min)
Look ahead, not just back. What’s blocked, what’s behind, what depends on something shaky. Anything you spot here is something you can intervene on before it becomes next week’s fire instead of this week’s note.
3. Who needs my attention? (4 min)
Go person by person. Who’s overdue for a 1:1? Who’s been quiet? Who’s running hot, who’s stuck, who did something great that deserves to be named? This is the question that keeps people from falling through the cracks — and the one most managers skip.
4. What’s the one thing for next week? (3 min)
Pick the single most important thing for you to drive. Not a list — one thing. Naming it is what stops a week from being purely reactive.
The question that earns its keep: “Who haven’t I really paid attention to lately?” It’s almost always the person who needed it — the quiet ones don’t raise their hand.
What it looks like in practice
Made concrete, a single pass might run like this. What shipped: the checkout work landed, but the migration slipped a second week — worth understanding why. At risk: the Ledger epic depends on a devops change that keeps getting bumped, so you note it to chase on Monday. Who needs attention: Anna’s been quiet and is overdue a 1:1; Sam carried on-call solo and looks fried; Priya quietly unblocked two people and nobody’s said thanks. One thing for next week: protect the migration by clearing the devops dependency yourself. Total time: about twelve minutes.
Turn what you find into action
A review that ends in a list of observations you never act on is just worrying with extra steps. The value is in the small handful of things it prompts you to actually do — and most weeks that’s no more than three: a 1:1 to book, a blocker to chase, a person to thank. Capture them where you’ll see them, not in your head. The point of stepping back isn’t to feel on top of things; it’s to catch the two or three moves that change how next week goes.
Zoom out once a month
The weekly review keeps you current; a slightly longer monthly version keeps you honest about what a single week is too short to see. Once a month, look across the last four weeks and ask the questions that only make sense at that range: who’s been trending down for a while rather than just having an off week? Which “temporary” problem has quietly become permanent? Who hasn’t had real growth or recognition lately? The weekly cadence catches the moments; the monthly one catches the slopes — and the slopes are usually where the real risks live.
Why managers skip it — and how not to
Almost everyone agrees a weekly review is a good idea, and almost nobody does it, for the same reason: it’s never urgent. Nothing breaks the week you skip it; the cost is invisible and shows up later, as the person you didn’t notice slipping or the dependency you didn’t chase. The fix is to make it unskippable in the only way that works — a fixed slot on the calendar, the same time every week, treated as a real appointment. Fifteen minutes you actually take beats an hour you keep meaning to.
Treat the four questions as a starting point, not scripture. A team in a hardening phase might add “what did we learn this week?”; a team under delivery pressure might track “what did we say no to?” The exact prompts matter less than the discipline of asking the same ones every week, so the answers stay comparable and the drift becomes visible.
Make it a habit
A review you do twice and abandon is worth nothing. Two things make it stick: put it on the calendar at the same time every week — Friday afternoon or Monday morning both work — and keep a short written record, so each week you can glance at the last one and see what’s changed. The continuity is most of the value; a review with memory beats one that starts from scratch.
Or have it written for you
Even fifteen minutes of gathering — what shipped, what’s at risk, who’s gone quiet — is real work, and it’s the kind of work that’s easy to skip in a busy week. That’s exactly the gathering CoManager’s weekly reports do automatically: the moment a week closes, you get a plain-language recap — a headline, the highlights and watch-outs, the hard numbers diffed against last week, and the people you didn’t get to. It turns the fifteen-minute review into a two-minute read, and makes sure the week never closes unexamined.
Whether you do it by hand or have it written for you, the habit is the point. The managers who stay ahead of their teams are simply the ones who take a moment, every week, to look.