The Founder's Weekly, Monthly, Quarterly Rhythm

Running a company without operating rhythm is like navigating without checkpoints. You're moving, but you don't know if you're on course until you've gone too far to correct.

The best founders establish a cadence that creates regular opportunities to check direction, surface problems, and make decisions. Here's the rhythm that works for 25-75 person software companies.

The three horizons

Different cadences serve different purposes:

Weekly (Ground level): Progress, exceptions, immediate decisions.

Monthly (Treeline): Patterns, course corrections, team health.

Quarterly (Summit): Direction, strategy, major decisions.

Each horizon catches different problems at different time scales.

Weekly: Progress and exceptions

Purpose: Surface blockers, make tactical decisions, maintain momentum.

Time commitment: 30 minutes sync + 15 minutes prep.

What happens

1. Async updates (before meeting): Every owner updates their OKRs with status, confidence, and blockers. 5 minutes per person.
2. Pulse check (5 min): Any major news, urgent cross-team issues, quick wins.
3. Exception review (20 min): Only discuss what's off-track or needs a decision. 3 minutes per item max.
4. Decisions and actions (5 min): Recap what was decided, who owns what, by when.

What to watch for

• Confidence dropping on the same OKR for consecutive weeks
• Dependencies that have been stuck for more than 2 weeks
• Any item that gets discussed every week without resolution

Monthly: Patterns and health

Purpose: Step back from week-to-week to see patterns. Course correct before quarterly.

Time commitment: 60-90 minutes.

What happens

1. Metrics review (20 min): Look at KPI trends over the past 4-6 weeks. What's improving? What's declining? What's concerning?
2. OKR trajectory (20 min): Are we on pace to hit quarterly goals? Which ones need intervention? Which should we consider adjusting?
3. Team health check (15 min): How are teams doing? Any burnout signals? Resourcing issues? Morale concerns?
4. Strategic questions (15 min): Anything surfaced this month that should change our direction? Any decisions we're avoiding?
5. Actions (10 min): What will we do differently next month?

What to watch for

• Same issues appearing week after week
• Metrics moving in the wrong direction consistently
• Teams that seem stuck or demoralized
• Important decisions that keep getting deferred

Quarterly: Direction and strategy

Purpose: Set direction, allocate resources, make big decisions.

Time commitment: Full day for planning, half day for retro.

The closing ritual (half day)

Before planning the next quarter, close out the current one:

1. Grade OKRs: Score each objective and key result on 0.0-1.0 scale. Quick, factual, not debated at length.
2. Retrospective: What assumptions proved wrong? What decisions had outsized impact? What would we do differently?
3. Capture learnings: Write down 3-5 insights to carry forward. Surface patterns across teams.

The planning ritual (full day)

1. Review context (1 hr): What did we learn last quarter? What's changed in the market? What constraints are we working with?
2. Company objectives (2 hrs): What 2-3 things must be true by end of next quarter for the company to succeed? Leadership debates and decides.
3. Team planning (2 hrs): Teams draft how they'll contribute to company objectives. What OKRs will they own?
4. Alignment review (1 hr): Cross-check alignment. Resolve conflicts. Ensure every company objective has clear team ownership.
5. Final commit (1 hr): Leadership approves final OKRs. Cycle begins.

What to watch for

• Carrying forward the same failed OKR without changing approach
• Teams that set only operational goals, not strategic ones
• Objectives without clear ownership
• Too many objectives (more than 2-3 per team)

The calendar rhythm

Here's how this looks across a quarter:

Week 1 (quarter start): Quarterly planning complete. OKRs published and active. First weekly review.

Weeks 2-4: Weekly reviews. End of Month 1: First monthly review.

Weeks 5-8: Weekly reviews. End of Month 2: Second monthly review.

Weeks 9-11: Weekly reviews. Check: Are we on track for quarter end?

Week 12 (quarter end): Final weekly review. OKR grading and retro. Transition to next quarter planning.

The minimum viable rhythm

If this feels like too much, start here:

Must have

• Weekly review (30 min)
• Quarterly planning (1 day)
• Quarterly retro (half day)

Nice to have

• Monthly review (60 min)
• Weekly async updates

You can add monthly reviews once the weekly rhythm is solid.

Common mistakes

Over-meeting: Rhythm doesn't mean more meetings. Each cadence should serve a distinct purpose. If you're reviewing the same things weekly and monthly, consolidate.

Under-preparing: Rhythm only works with async prep. Without it, every meeting becomes status gathering instead of decision making.

Skipping retros: The temptation is to rush into next quarter planning without closing the current one. Resist. The retro is where learning compounds.

Inconsistent cadence: Cancelling reviews when things get busy teaches the team that rhythm is optional. Protect the cadence, especially when it's hard.

The principle

The goal is not to add process for its own sake. The goal is to create regular checkpoints where leadership can exercise judgment, make decisions, and keep the company on course.

Without rhythm, you're navigating blind. With rhythm, you're running.

For more on weekly reviews, see The 30-Minute Leadership Review Template and How to Prepare for Weekly Reviews in 5 Minutes.