The meeting that runs your company isn't on the calendar

Here is something I've seen often enough that I've stopped being surprised by it.

A leadership team spends two days offsite. They align on priorities. They make commitments. They leave energized. The CEO feels good about where the team is headed.

Forty-eight hours later, two of the senior leaders are in the parking lot having a completely different conversation. About what was really decided. About what they're actually going to do. About whose idea they're going to quietly sideline.

The real meeting happened in the parking lot.

The accountability meeting, the one where people actually say what they think and decide what they'll actually do, isn't happening in the room where it should be happening. It's happening in the spaces around it. In hallway conversations, in sidebar texts, in the "can I have five minutes?" that follows the official meeting.

Most CEOs know this is happening. They don't always know what to do about it.

The reason those parking lot conversations exist isn't that your leaders are sneaky or disloyal. It's that the official meeting didn't create enough safety for the real conversation to happen there. So it migrated somewhere it could breathe.

The fix isn't a better offsite. It's not a stronger facilitator. It's not asking people to "be more direct" in a culture that has rewarded the opposite for years.

The fix is a structure I've started calling the Honest Number Meeting. It's deceptively simple and most leadership teams resist it at first.

Once a week, every direct report shows up with one number. Not a deck. Not an update. One number that represents the single most important thing they are accountable for this week. They say the number out loud. They say whether they're on track or not. And they say what they are changing if they're not.

That's it. No presenting. No context-setting. No "here's all the reasons the number looks like this."

Just: here's my number, here's where it stands, here's what I'm doing about it.

The first few times you run this, it will feel uncomfortable. Some of your leaders will struggle to name a single number. That's information. A leader who can't name the one metric that tells you if they're winning this week doesn't have clear ownership of their role.

Some will try to bring three numbers. That's also information. Three numbers means no real priority. It means they're spreading accountability thin enough that nothing is truly owned.

What you're building with this meeting isn't a reporting structure. You're building a shared reality. Because right now, there's a decent chance each person on your team has a slightly different idea of where the business actually stands. And decisions made from different maps lead to different places.

The owners I've watched do this well say the same thing after about six weeks. The parking lot conversations don't disappear. But they change. Instead of relitigating the meeting, people are actually problem-solving between meetings. The sidebar becomes functional instead of political.

There's a deeper principle underneath this. Accountability isn't a conversation you have once a quarter in a review. It's a rhythm. And rhythms require repetition, regularity, and a format simple enough that they don't collapse under their own complexity.

Your leadership team isn't going to become more accountable because you tell them accountability matters. They're going to become more accountable because you build a meeting structure where accountability is visible, weekly, and inescapable.

The parking lot can still exist. But it should be where your leaders decompress, not where they make the real decisions.

THIS WEEK'S KEY QUESTION

Ask each of your direct reports this week: what is the one number that tells you whether you're winning? See how long it takes each of them to answer. See how specific the answers are. If someone can't answer in under thirty seconds, you have a clarity problem, not a performance problem.

Start there.

-N.F

P.S. Hit reply and tell me: does your leadership team have a weekly meeting built around individual accountability, or does accountability only surface when something goes wrong? I'm curious how many of you are running the parking lot version and already know it.