We’ve written before about high-performance meetings (HPMs) and why they are a must. If you haven’t checked that one out, start there. This post assumes you know what an HPM is and are trying to figure out why yours keeps drifting back into a status update with slides.
The meetings that produce the biggest leverage are also the hardest to sustain. Here’s why, and what to do about it.
HPMs are simple to set up. They’re genuinely challenging to maintain. Almost every founder who tries them lets them slip within a quarter or two, drifts back into the old rhythm, and then feels bad about it.
The slippage isn’t a discipline failure. It’s a design feature. HPMs are hard on purpose. The difficulty is actually where the value is.
The core reframe: HPMs are the end of a process, not the beginning
The single most important thing to understand about a high-performance meeting is that the meeting itself isn’t the real work.
The real work happens before the meeting. Owners prepare written material. Everyone reads it in the first fifteen minutes. The remaining forty-five are spent on the things that actually need discussion. If the meeting feels efficient because there’s nothing interesting to say, you’re doing it wrong. If it feels efficient because everyone came prepared and the meeting is where you collect the value of that preparation, you’re doing it right.
That distinction is why HPMs are hard. The default mode for how meetings work in most companies is the opposite. You show up. You riff. You improvise for an hour. You leave without much to show for it, but you also didn’t have to prepare, and neither did anyone else.
An HPM demands preparation from everyone. That’s expensive. It feels especially expensive at the beginning, before people have felt the payoff. If you’re a founder who runs on charisma and in-the-moment thinking (which many founders are), you’ll find HPMs deeply uncomfortable at first. They take away the improvisation you’re good at and force a discipline that doesn’t come naturally.
Key 1: The agenda is the actual product
The single biggest predictor of whether an HPM culture takes root or not is whether the founder sat down and did the hard work of designing a high quality agenda.
Not once. Every quarter. With each person who owns a section of the meeting.
That work looks like this. You sit down with the person who owns a function or a project. You talk through what success looks like for them. You agree on what they should report on, how they should measure it, and what kind of updates matter. You make it specific. You make it real. You leave with an understanding that will hold for at least a few months.
That is a lot of upfront time. But if you don’t invest this prep time, you end up with meetings where people just report vanity metrics and phone it in. Founders who do invest it end up with meetings that unlock genuine leverage.
Key 2: It’s on your team to prepare, and they’ll resist at first
The unlock for CEOs, once they get this, is enormous. In a functioning HPM culture, it’s your reports’ job to make sure the meeting is good, not yours.
You show up. You read the prep. You engage. You leave. The responsibility for the meeting being useful sits with the person reporting, not with you.
That is the great CEO relief. If you’re the founder currently drowning in requests of “Can you just look at this real quick?”, it can feel like getting swarmed by piranhas. Each request is tiny, but the compounding effect eats you alive.
Imagine those requests batching into a weekly forum where the person has prepared, thought it through, and is coming to you with a real ask. Every small interruption is redirected into a scheduled, contained conversation. The piranha bites stop.
But there’s a catch. Your team will resist this at first. Almost every implementation we’ve watched includes at least a few people who think the prep work is busywork. They’ll grumble. They’ll do the minimum. They’ll try to phone it in.
What you’re looking for, within a meeting or two, is the shift. You’ll hear someone say “I can’t believe how much we got done today.” That’s gold you’ve been working toward. Once they realize that putting real information into the prep gets them real help in the meeting, they lean in. Before that moment, you’re pushing a rock uphill. After it, they push it themselves. You just have to survive the first weeks.
Key 3: You have to resist taking over
The temptation, when your team’s first HPM prep isn’t very good, is to take over.
Don’t.
The failure mode is easy to fall into. Someone reports on their section. It’s shallow. It doesn’t cover the actual issue you know they’re facing. So you jump in, redirect the conversation, start driving it yourself. Now you’re the one running the meeting, they’re the one being interrogated, and the ownership dynamic you were trying to build has quietly collapsed.
The better move is to ask a pointed question. You know what’s actually going on. Use that knowledge to ask something specific that surfaces the real issue rather than lecturing them into it.
But here’s the part most leaders get wrong. The pointed question is only half the skill. The response to the answer is the other half, and arguably the more important half. When someone finally gets vulnerable and admits the thing they were dodging, what you do next determines whether they ever do that again. If you punish them, or turn it into a lecture, or use it as an occasion to demonstrate how much more you know than they do, you’ve just taught them to hide the next hard thing. On the other hand, if you say, “It’s great that we’re talking about this. How can I help?” then you’ve just built the muscle of honest reporting.
Key 4: Figuring out what to report on is genuinely hard in a startup
One of the recurring struggles for early-stage founders trying to run HPMs is knowing what to have people report on. The default answer, borrowed from bigger companies, is KPIs. Report on your metrics. Show the numbers.
The problem is that in a startup, the numbers are often too volatile or too small to be meaningful week over week. Ten customers becomes eleven becomes nine becomes twelve. Reporting on that in isolation tells you nothing.
The frame that tends to work better is unlocks. What are you trying to unlock next? Product-market fit. The next fundraise. The first repeatable sale. The tenth customer that lets you build a system around a real cohort. Every function in a startup is oriented around unlocking the next thing. If you organize reporting around what each owner is working to unlock, you get much more useful conversations than if you organize around fixed metrics that don’t yet mean much.
The unlock frame also protects against the demoralization problem. If you set a quarterly target of “10x sales” and miss it four quarters in a row, your team stops trusting the goal-setting process. If you say “The unlock this quarter is repeatable systems, which requires at least ten customers,” then you’re pointing at a real threshold. Hit it, and something opens. Miss it, and you know what you didn’t get to.
Key 5: You have to blow it up periodically
The last reason HPMs are hard is that, even when they’re working, they eventually stop working.
Humans are naturally good at optimizing. Once people get used to the format, they optimize for it. They report on the same things in the same order. The prep becomes easier because it’s routine. And routine, in the context of an HPM, is death.
The whole point of the meeting is the developmental stretch. If it’s easy, it’s not doing its job. The zone of developmental challenge, the middle band where things are hard but achievable, is where humans actually grow. Too much challenge and people give up. Too little and there’s nothing to push against.
The move, roughly two or three times a year, is to blow up the agenda. Destroy the format you’ve built. Design a new one that stresses the thing your team most needs to stretch on right now. Then, run that for a few months until it, too, becomes comfortable, and blow it up again.
It’s exactly like an exercise program. Do the exact same workout for three months, and it stops helping you. Same principle applies here.
One last thing: HPMs surface politics fast
There’s one more reason HPMs are hard to maintain, and it’s worth flagging separately. HPMs surface political dynamics very quickly. In a healthy team, that’s a feature. In an unhealthy one, it’s a threat.
The whole point of the meeting is that people show up and say the thing that needs to be said. If your organization has developed norms around not talking about the difficult things (the underperforming leader, the misaligned strategy, the customer who’s about to churn), the HPM becomes uncomfortable, and people find ways to route around it. They talk offline. They soften what they report. They hide behind vanity metrics.
That drift is your signal that something has gone off in the culture. The HPM didn’t cause it. The HPM revealed it, which is exactly what a good meeting should do.
If yours is drifting, the question isn’t how to fix the meeting. It’s what conversation your team no longer feels safe having, and what you’re going to do about that.
HPMs are hard because they demand the things most meetings let you avoid. Preparation. Ownership. Honesty. Discomfort.
The founders who stick with them do it because they’ve felt the payoff. The team is more aligned. The CEO is less drained. The important issues surface faster. The politics stay in check. All of those benefits are downstream of the hard work of building a good meeting.
The meetings aren’t the work. The meetings are where the work pays off. Keep the work going upstream, and the meetings take care of themselves.