Most teams I join are stuck between two modes: too many meetings or nobody knows what anyone is doing. Both kill execution. The fix isn't more discipline — it's a cadence that does the alignment for the team, so the team doesn't have to manage themselves into burnout.

This is the operating rhythm I install on day one of every engagement. It scales from a 5-person founder team to a 50-person org with minimal modification.

Why Cadence Beats Control

Micromanagement is what happens when you don't have visibility. You ping people on Slack at 9pm because you don't know if the work is on track. They respond because they don't want to lose your trust. Everyone burns out.

A good cadence gives you visibility without surveillance. Each layer answers one question:

  • Daily — "Is anyone blocked right now?"
  • Weekly — "Are we on track for the week's commitments?"
  • Monthly — "Are our numbers moving in the right direction?"
  • Quarterly — "Are we still working on the right things?"
📌 Principle

If you can answer all four questions at the right cadence, you don't need to micromanage anyone. The system answers for you.

The Daily Layer — 15-Minute Async Standup

I don't run live standups. I run async ones in a Slack channel. Three lines per person, every morning by 10am:

  1. Yesterday: One thing that moved a goal forward.
  2. Today: One thing I'm shipping.
  3. Blocked on: What I need from someone else (tag them).

That's it. Total reading time: 4 minutes. Total writing time per person: 2 minutes. Cost of a 30-minute video standup with 6 people: 3 person-hours per day. Async wins by 10×.

💡 Async standup rule

If you can't write your standup in 3 lines, you don't actually know what you're working on. The discipline of brevity forces clarity.

The Weekly Layer — Review + Plan (45 min)

One meeting a week, same time, same agenda. Two parts:

Weekly Review & Plan

1

Numbers (10 min)

Walk the 4–6 KPIs that matter for the week. Are we on track? What changed? No discussion of why — just visibility.

2

Wins & misses (10 min)

Each person: one win, one miss from last week. 60 seconds each. No commentary.

3

Blockers (10 min)

Anything blocked that needs a decision today. Decide in the room.

4

Next week commitments (15 min)

Each person commits to 2–3 outcomes for next week. Written down. This is what gets reviewed next Monday.

The genius is the commitment loop. Saying "I'll ship X by Friday" in front of peers is 10× more accountable than telling your manager privately. By month two, people start over-delivering because they don't want to miss in front of the team.

The Monthly Layer — Metrics Review (60 min)

Monthly is when you zoom out. Different audience: function heads, not the whole team. Different format: a dashboard, not a slide deck.

  • Show: Last 4 weeks of trend lines for each KPI
  • Ask: Which KPI is most off-track, and why?
  • Decide: One thing to change next month

Monthlies fail when they become status theatre. The cure is to focus on what's broken, not what's working. Celebrate wins in the weekly. Use the monthly to fix what's leaking.

💡 Format tip

Send the dashboard 24 hours before the meeting. Anyone who shows up without reading it forfeits the right to ask basic questions. Saves an hour of recap every month.

The Quarterly Layer — OKR Reset (Half-Day)

Once a quarter, half a day, off-site if possible. This is when you ask the strategic question: are we still working on the right things?

I use a simplified OKR format:

  • 3 objectives max per quarter. Any more and nothing gets done.
  • 3 key results per objective. All quantitative. "Improve marketing" is not a key result. "Generate 40 qualified meetings/month from outbound" is.
  • One owner per objective. Shared ownership = no ownership.

The quarterly is also where you kill things — initiatives that aren't moving, projects that have lost relevance. If you can't list 2–3 things you're stopping this quarter, you're probably overcommitted.

Async Tools That Make It Work

The cadence only works if the tools support it. My minimum stack:

  • Slack channels for async standups (one per team)
  • Notion for weekly commitments and quarterly OKRs (one page, archive monthly)
  • A single dashboard for KPIs — Mixpanel, Metabase, or even a Google Sheet. The tool doesn't matter; the consistency does.
  • Loom for monthly metric narrations — record once, watch async, save the meeting hour
⚙ Tooling principle

The simpler the tooling, the more likely the cadence survives a busy quarter. I've seen elaborate OKR platforms abandoned by month two. A Notion page lasts forever.

TL;DR — Install This in Week One

  1. Day 1: Set up async standup channel in Slack
  2. Day 2: Schedule the weekly review for the same time every week
  3. Day 3: Build the single KPI dashboard
  4. Week 1: Run the first weekly. Take notes on what felt awkward.
  5. Week 4: Run the first monthly metrics review
  6. Week 12: Run the first quarterly OKR reset
  7. Forever: Resist the urge to add more meetings

If you want help designing the operating rhythm for your team — including the Notion templates I use — I'm happy to do a free 30-minute call.

Execution Cadence OKRs Operating Rhythm Team Operations Async Work Startup Operations