🧞‍♂️ New to Exponential Scale? Each week, I provide tools, tips, and tricks for tiny teams with big ambitions that want to scale big. For more: Exponential Scale Podcast | Scalebrate | Scalebrate Hub

Founding Supporters: Support the following people and companies because they supported us from the beginning: DataEI | Dr. Bob Schatz | .Tech Domains | Fairman Studios | Jean-Philippe Martin | RocketSmart AI | UMBC

In today's newsletter:

Latest Podcasts: What You Missed

The "2-Week Lookback" Rule

Your calendar is full. Every day, back-to-back meetings. Some are valuable. Most are... fine. A few are complete time sinks.

But when's the last time you actually looked at your calendar and asked: "Which of these meetings should I delete?"

If you're like most founders, the answer is never.

Meetings multiply like rabbits. Someone suggests a "quick sync." It becomes a weekly recurring event. Three months later, you're still having that sync, even though the original reason for it is long gone.

Meanwhile, your calendar is a graveyard of zombie meetings—technically alive, but serving no real purpose.

The 2-Week Lookback Rule fixes this: Every two weeks, review your calendar and kill at least one meeting.

The Calendar That Ate 18 Hours a Week

Let me tell you about Amir, founder of an 8-person marketing agency.

Amir was drowning in meetings:

  • Monday team standup (1 hour)

  • Tuesday client check-ins (3 hours)

  • Wednesday 1-on-1s with each team member (4 hours)

  • Thursday strategy session (2 hours)

  • Friday status updates (1 hour)

  • Plus ad-hoc "quick calls" scattered throughout (7+ hours/week)

Total: 18+ hours of meetings per week.

Amir had maybe 12 hours left for actual work. He was constantly behind, working nights and weekends to catch up.

One day, his coach asked him: "If you could only keep half your meetings, which ones would you choose?"

Amir paused. Half? That would be chaos... wouldn't it?

So they ran an experiment. For two weeks, Amir tracked every meeting and rated it:

  • Essential (real decisions made, clear outcomes)

  • 🤷 Meh (could've been an email or Slack thread)

  • Waste (no clear purpose, mostly status updates)

The results were brutal:

  • Essential: 4 hours/week

  • Meh: 9 hours/week

  • Waste: 5 hours/week

Amir was spending 14 hours a week in meetings that didn't need to happen.

He started the 2-Week Lookback practice:

  • Canceled the Monday standup (replaced with async Slack updates)

  • Moved 1-on-1s to biweekly instead of weekly (cut 2 hours)

  • Consolidated 3 client check-ins into 1 batch call (saved 1.5 hours)

  • Deleted the Friday status meeting entirely (pure waste)

New meeting total: 8 hours/week.

Amir got back 10 hours. His stress dropped. His output increased.

"I thought I needed all those meetings to stay aligned. Turns out, most of them were just performative. We already had alignment—we were just talking about having alignment."

Why Meetings Multiply (And Never Die)

Meetings have a lifecycle:

Phase 1: The Birth

Someone says, "Let's have a quick sync to align on this project."

You agree. A meeting is scheduled.

Phase 2: The Recurring Event

After the first meeting, someone says, "This was helpful. Let's do this weekly."

You agree. It becomes a recurring calendar event.

Phase 3: The Zombie Meeting

The project ends. The original need disappears. But the meeting keeps happening because nobody explicitly killed it.

Think of meetings like subscriptions. They auto-renew until you cancel them.

Most founders never cancel.

Why This Matters for Microteams

Big companies can afford bloated calendars. They have middle managers whose job is literally "attend meetings."

Microteams can't.

For microteams, every meeting hour is an hour not spent on:

  • Building the product

  • Talking to customers

  • Closing deals

  • Writing content

  • Solving real problems

High-leverage teams protect maker time. Low-leverage teams fill calendars with manager theater.

The 2-Week Lookback Rule ensures your calendar stays lean, focused, and useful.

The 2-Week Lookback System

Here's how to implement this practice:

Subscribe to keep reading

This content is free, but you must be subscribed to Exponential Scale to continue reading.

Already a subscriber?Sign in.Not now

Recommended for you

No posts found