|
Most companies have too many meetings and too little clarity.
The calendar fills up with check-ins, syncs, status updates, and "quick calls." And somewhere in the noise, the actual work of leading the business to the outcomes everyone is looking for gets lost.
Here's the fix: six meetings. That's all any business needs to run with intention.
Every other meeting on the calendar is either a symptom of not having these or a sign that the most important things in the business are being avoided altogether.
|
|
|
Meeting 1: Annual Planning
No business can move forward if no one has agreed on where "forward" is.
I watched a $4M business nearly implode because the leadership team hadn't been in the same room (truly present, phones down, no agenda except the business) in three years.
They were busy. There was always a reason to push it. And so they kept running hard in slightly different directions, each convinced they were aligned, none of them stopping long enough to check.
An Annual Planning meeting is simple. It's two days, off-site, with the full leadership team. Day one, you look back — what you hit, what you missed, and what you were lying to yourselves about. Day two, you look forward — resetting the 3-Year Picture, locking in the 1-Year Plan, and setting the 90-day Rocks that will actually move the needle.
It's not a retreat. It's not a team-building exercise. It's the single most important two-day stretch your leadership team will spend together all year.
|
|
|
Meeting 2: The Annual Same Page Meeting
Most teams don't skip the Annual Same Page meeting on purpose. They just don't know it shoudl exist and they confuse it with the Annual Planning and collapse them into one (efficiency, am I right?).
That's the first mistake.
The Same Page meeting isn't about strategy or Rocks or numbers. It's a dedicated session to ask a simpler, harder question: Do we still believe the same things? Core values. Company vision. The kind of business we're trying to build and why.
The second mistake is treating it as a formality. Teams read the values off the wall, nod, and move on. That's not alignment. Alignment gets tested with questions like: Can you tell me what this value looks like when we're under pressure? When did we violate it last?
The third mistake is skipping it because things feel "fine." Misalignment doesn't announce itself. It shows up six months later as a hiring decision that didn't sit right, a strategic call nobody fully committed to, a culture conversation that's harder than it should be.
Run this meeting before the year kicks in. An hour or two should be enough. And the goal isn't consensus, it's clarity.
|
|
|
Meeting 3: Quarterly Planning
Ninety days is the right unit of time for a business to think and move.
The rhythm of quarterly planning should be one day, off-site, every 90 days. Here's exactly how it should run:
Open with personal and professional check-ins. No small talk. Real check-ins. What's going on personally, what's the biggest professional win or challenge right now? It sets the tone and reminds the room these are humans, not just functions in the business.
Review last quarter's Rocks. Go one by one. Complete or not complete. No partial credit, no narratives. If it's not done, it's not done. This is where accountability either lives or dies.
Do a business and people review. Look at your key numbers. Talk about who's thriving, who's struggling, and whether you have the right people in the right seats heading into the next 90 days.
Identify and set new Rocks. What are the three to seven most important things in the company that each leader must accomplish in the next quarter? Not everything. The most important things. Write them as outcomes, not activities.
Work the Issues List. Bring your biggest unresolved problems into the room and solve them. Not discuss them. Solve them. An issue isn't closed until you have a clear decision and a clear owner.
Close with next steps and a rating. What does everyone leave with? And how did the meeting itself go on a scale of 1-10? The rating keeps the meeting honest over time.
That's the whole day. It sounds simple because it is. The discipline is in actually running it every quarter without skipping it when things get busy, which is exactly when you need it most.
|
|
|
Meeting 4: Weekly Standup
Ninety minutes once a week sounds like a lot until you realize what it replaces.
It replaces the Monday morning "what are we even doing this week" fog. It replaces the Friday afternoon "wait, that still isn't done?" conversation. It replaces the three Slack threads, two side conversations, and one tense one-on-one that happens when a team doesn't have a shared pulse.
The Weekly Standup runs the same agenda every week without exception:
- Good News (5 min) — one good thing, personally and professionally. Transitions the room from reactive to present.
- Scorecard (5 min) — are your key numbers on track? No scorecard means you're managing by feeling instead of fact.
- Rock Review (5 min) — on track or off track. No narratives. This is the meeting's early accountability check.
- Headlines (5 min) — customer and employee news worth the room knowing. Keeps everything connected to ground level.
- To-Do Review (5 min) — did we do what we said last week? A team that misses To-Dos consistently has a culture problem, not a task problem.
- IDS (60 min) — Identify, Discuss, Solve. The most important issues get real time and real decisions. This is where things in the business actually move.
- Conclude (5 min) — rate the meeting, assign next steps, leave clean.
The IDS block is the unlock here. Sixty uninterrupted minutes to work real problems with the people who can actually solve them. Most teams never get that. They get a calendar full of 30-minute syncs that end with "let's follow up offline."
The Weekly Standup ends that cycle.
|
|
|
Meeting 5: Daily Huddle
Here's what a real Daily Huddle looks like:
- #1 Priority — Individually, what's the #1 priority for every single person on the team (note: if your team is larger, you may need departmental Daily Huddles for time's sake)?
- Scoreboard — Where did we land on the top 5-15 metrics in the business yesterday? Were we green or red?
- Issues — Where are people on the team blocked? What answer(s) are they waiting on to keep moving a project forward? What software do they need access to?
- To-Dos — Review any past due To-Dos and remind the team of commitments.
- Who Got Caught Being Awesome? — Celebrate each other. Even the small wins matter.
I'll say, not every team needs this one, but I couldn't recommend it enough. The Daily Huddle is the cheapest insurance you can buy against misalignment. Fifteen minutes standing up, every day, and the whole team stays in sync without an extra meeting on the calendar.
|
|
|
Meeting 6: One-on-Ones
It's easy to deprioritize one-on-ones for the same reasons you would any other meeting, and all of them are wrong.
"We talk all the time." Casual conversation isn't a one-on-one. Hallway updates and Slack threads don't surface what a direct report actually needs from you, where they're struggling, or whether they're quietly checking out.
"I don't have time." The alternative is a disengaged employee, a performance issue that festers, an unexpected resignation...All of which cost exponentially more.
"They'd tell me if something was wrong." Most people won't. Not without a dedicated space to do it. The one-on-one creates that space on purpose, so problems surface before they compound.
Done well, one-on-ones aren't check-ins; they're the primary tool for keeping the right people in the right seats and making sure they know it. Are they living the core values? Are they good at their job? Do they want what the role requires?
Thirty minutes. Once a quarter at minimum (preferably weekly for each of your direct reports). The conversation your team needs you to make time for.
|
|
|
The honest truth about meeting culture
Bad meetings aren't a calendar problem. They're a structure problem.
When you don't have the right meetings, you fill the gap with the wrong ones. Ad hoc syncs. Reactive calls. "Let's jump on a quick Zoom." Every one of those is a tax on focus.
Build the stack. Run it consistently. The noise disappears on its own.
|
|
|
