Do I need my whole team in these meetings, or can I run them solo?

Both meetings work solo. A Google doc and honest answers to the right questions is enough to surface most of what's been grinding at you. If you have a leadership team, the monthly review in particular gets sharper when one or two other people are in the room, but don't let "I can't get everyone together" be the reason you skip it.

What's the difference between a weekly scan and a normal team standup?

A standup is forward-looking, what are we doing today. The weekly scan is backward-looking first: what did we say we'd do last week, and what actually happened. That distinction matters. Most teams are good at planning forward and bad at honestly accounting for drift. The scan is specifically designed to catch the gap between intention and reality before it compounds.

Why 90 minutes for the monthly? That feels long.

It's less time than you'll spend reacting to the problem it would have caught. The 90 minutes buys you the slower pace you need to see patterns that don't show up in any single week. If you try to compress it to 45, you'll spend the whole time on recent news and never get to the structural questions, the ones about what keeps coming back and who's quietly overloaded.

How do I know if my monthly review is actually working?

One signal: you stop being surprised by things. Problems that used to blindside you mid-quarter start showing up in the monthly review first, when they're still manageable. A second signal: the same issue stops appearing in multiple months' notes. If it keeps coming back, the review is catching it, but something in how you're closing the loop isn't working yet.

All insights

The two meetings that get you out of firefighting mode

Last updated 8 June 2026

A 30-minute weekly scan and a 90-minute monthly review will do more for your stress levels than better time-blocking. The weekly catches drift before it compounds. The monthly catches slow-moving patterns, the kind that don't show up in any single week's numbers but are quietly making every week harder. ===END ANSWER===

Two Meetings That Will Calm Your Weeks Down

Why your weeks feel chaotic even when nothing's on fire

You know the feeling. Revenue is fine. Nobody's quitting. No single thing is on fire. And yet every week feels like you're running slightly behind something you can't name.

A founder I was working with described it exactly that way, "chaotic for no reason." We were doing a monthly review together when we found the actual reason: her team had fixed the same onboarding bug four separate times over two months. Different engineers, different weeks, nobody owned the root cause. It had been quietly consuming engineering hours and eroding customer goodwill the whole time. The pattern only became visible when we looked at four months of updates side by side.

She hadn't skipped the monthly review because she was careless. She skipped it because it felt like overhead, a meeting about meetings. When you're already stretched, that's the first thing to go.

That's also exactly when it matters most.

What the 30-minute weekly scan actually does

Monday morning, 30 minutes. You're looking at actuals versus plan from the previous week. Not a deep dive, a scan. Did we do what we said we'd do? Where did we drift?

Founders who run this consistently report catching resourcing gaps two to three weeks earlier than they used to. In practice, it tends to kill most of those mid-week "hey, what's going on with X?" Slack threads, because you're asking the question before the week has a chance to spiral around it.

The questions are simple:

What did we say we'd do last week?
What actually happened?
Where did we drift, and does that matter?

That's it. Thirty minutes. You don't need a team present. A Google doc and honest answers is enough.

What the 90-minute monthly review catches that the weekly can't

The weekly scan is good at catching immediate drift. It's not good at catching slow-moving problems, the kind that look fine in any given week but are quietly compounding across months.

For that you need a wider window.

Once a month, 90 minutes. You're not looking at the numbers here; you're looking at the shape of how you're operating. The questions shift:

What keeps coming back?
What's taking longer than it should, and has been for a while?
Who's overloaded and hasn't said so yet?
What problem have we "solved" more than once?

The onboarding bug story above is a monthly-review catch. In any single week, fixing a bug looks like forward progress. Across four months, it looks like a systems failure. You need the monthly window to see the difference.

Ninety minutes sounds like a lot until you calculate how much time you'll spend reacting to the thing it would have caught.

How to run both meetings

You don't need a team for either of these. Both work solo, just you, a doc, and the right questions.

| Meeting | Cadence | Length | Core question | |---|---|---|---| | Weekly scan | Every Monday | 30 min | Did we do what we said? Where did we drift? | | Monthly review | First week of month | 90 min | What keeps coming back? What's making every week harder? |

The act of sitting down with the right questions, on a predictable schedule, is usually enough to surface whatever's been quietly grinding you down. You don't need a facilitator. You need the time blocked and the questions written down in front of you.

[Download the two-meeting template and run it once this week, even solo, just to see what surfaces.](#)

===END BODY===