Why your agenda never survives the founder

You have THREE things on the agenda. You sent it the night before.

The meeting starts and he’s already talking. You can feel it before he’s finished his first sentence, that familiar mix of excitement and urgency that means he’s been thinking since last night.

And you already know what’s coming…

“Before we get into your stuff, I was on a call with a customer yesterday and I think we’re solving the wrong problem completely.”

Or: “I saw what [competitor] just released and I don’t think we can go to market without an AI angle now.”

Or it’s just some really cool new idea that bubbled up in his head on the way to the call.

He’s not wrong, exactly. These things matter, and it’s his company. So you listen. You try to redirect. By the time you get to the first thing on your list, it’s 32 minutes later and you’re scrambling.

You leave with a few things half-covered, one deferred to next week, and this feeling that next week probably looks exactly the same.

It does.

This is how months pass on decisions that could have been made in a week or two.

I hear some version of this almost every week from COOs, Heads of Product, VPs of Engineering, CFOs: the people running execution who don’t necessarily own the vision.

Your 1-1 meeting with the founder/CEO has a standing time on the calendar. What it doesn’t have is a defined scope. Which means that whoever shows up with the most urgency that day sets the agenda.

The default diagnosis is a personality problem. Wrong diagnosis. The meeting can be fixed.

The obvious fixes don’t work. If you’ve been in this situation a while, you’ve probably tried at least one of them…

Be more assertive: Push back harder when the founder redirects. Hold your ground at the start of the meeting. The problem is that it turns every sync into a negotiation with someone who has more authority, more urgency, and no shortage of opinions.

All it does is make the meeting more tense.

Send a better agenda: More detail, clearer structure, sent earlier. But the founder has seen your agendas. What happens in the meeting ends up having almost nothing to do with what was on your perfect agenda doc.

Manage up: Have a separate conversation about the dynamic. Talk about it directly. This gets closest to the real issue. And if you’ve tried it, you probably remember the cautious optimism going into the next meeting, and the recognition partway through that nothing had changed. It still frames the problem as a relationship problem. If the meeting never had a defined purpose, no conversation about the meeting will give it one.

Better communication doesn’t fix a broken container.

What’s happening is that no one ever decided what this meeting is actually for. So he walks in and does what founders do. He thinks out loud, he reacts, he generates ideas. It’s his strength. But there’s no space or structure to hold it.

That changes how we go about fixing this.

This is where the conversation usually turns.

What I’ve found, in almost every case: you’re not running one meeting. You’re running three. And they’re all getting squeezed into the same hour.

Your 1-1 (your topics). You set the agenda, you drive it, you decide what gets covered. The founder’s role is to listen, react, and unblock. This is the one meeting where you are explicitly in the chair.

The long game (your strategy session). This one is shared. No status updates, no urgent decisions. Just the big directional questions. Where are we trying to be? What are we betting on? Both of you thinking out loud, together.

The feedback meeting (your professional development). Also shared, but grounded in your role. How you’re performing, what’s working, what needs to shift. This happens every four to six weeks.

When all three blur into one meeting is when shit gets chaotic. The founder defaults to whatever’s loudest in his head that day.

Some people can cover all three in one meeting. It only works when both people know which conversation they’re in and when you shift gears to the next mode together.

I used to work with a Head of Product. I’ll call him Vince.

He was the first product-focused hire at the company and was promoted to lead the function, but his meetings with the founder were chaotic and frustrating, to say the least. The same pattern kept repeating over and over and over.

So, we split his syncs: His 1-1 happens every other week, where he set the agenda and drove the conversation and the “long game” meeting (strategy session) on alternating weeks, focused on long-term direction.

They required different preparation. And both stopped being a free-for-all. The first thing he brought to his dedicated 1:1 was a headcount decision that had been deferred for three weeks. He left with a decision in 20 minutes.

This meeting runs every other week. The frequency matters. It gives each conversation enough weight that you prepare for it, and enough space that it doesn’t become a dumping ground for whatever came up that week.

Send the agenda 24 to 48 hours in advance. A list of specific asks, not topics:

“Tomorrow I want to cover the hiring decision on the engineering lead, align on the Q3 rocks, and get a decision on the vendor contract.” The founder knows what’s coming. You’ve given him time to think. You’ve signaled that this meeting has a job to do.

Open by restating the agenda out loud. Most operators send the agenda and consider that done. They walk into the meeting assuming the document did the work. It didn’t. Just name the scope at the beginning of the meeting. Something like: “I’ve got three things I want to get through today. I’ll make sure we leave time for anything on your end too, but if we can start with mine, I think we can move through them quickly.”

When he brings something new, acknowledge it. This is where the meeting either holds or falls apart. He always does. The move is to park it: “That’s worth discussing. Let me add it to the end and we’ll get to it after we cover what I sent you.” Then you go back to your agenda.

Pretty simple.

Next, the strategy session. It requires slightly different preparation.

Whether this is its own meeting or a defined block within a longer one, the structure is the same. Neither of you is fully “running it”. You’re both thinking out loud, together.

Frame the agenda as questions, not topics. This is the single biggest difference between a strategy conversation that works and one that slides back into tactics. Topics invite opinions. Questions invite thinking.

Instead of “Q3 roadmap” on the agenda, try “Where do we need to be in six months and what’s currently blocking us from getting there?” The question pulls both of you into big-picture mode before the meeting starts. The founder who arrives thinking about direction is less likely to relitigate last week’s feature decisions.

Say it out loud. Same move as your 1:1, different framing. “This one is about direction, not current features. I want us to stay zoomed out today.” You’re setting the scope.

When it drifts tactical, redirect it. It will. A long-term question will surface a short-term problem and suddenly you’re in the weeds. “That’s a good one for next week’s check-in. For right now let’s stay on the long-term piece.” One sentence. Then you move on. That’s the most important move in this conversation. It’s where you hold the container under real pressure.

This one runs every four to six weeks. In my experience, it’s the meeting most operators never formally ask for. And the one that shapes how you grow in the role more than any other.

Done well, it’s a clear read on how you’re performing against expectations, where the founder needs more from you, and where you’re stronger than you realized. When it slips, it gets replaced by informal feedback that’s usually too vague to act on (or worse, it never comes at all).

It has a predictable failure mode: The founder fills the time with what’s on their mind about the business, and your development never gets covered.

The conversation that was supposed to be about you becomes another strategy session.

Bring your own agenda. Most people wait for the founder to drive this one. That’s why it goes sideways. Come in with your own questions: where you think you’re performing well, where you feel uncertain, what support or clarity you need. The founder who gets a blank slate will fill it with whatever is loudest for them that day.

State the frame. “This one is about my role and how I’m doing in it. I want your honest read, and I want to share where I could use more from you.” One sentence. You’re setting the scope.

The meeting got derailed because no one defined what it was for. Including you.

The founder walked into an empty room. There’s no scope, no ask, no framing. Just a recurring calendar hold and a list of topics sent the night before.

The founder did what founders do in empty rooms: they filled it. The empty room was yours to design. You just hadn’t designed it yet.

That’s a starting point. It’s what makes the fix possible.

It’s also the reframe I come back to with almost everyone I work with on this.

You’re proposing a different architecture, not a personality fix. That distinction matters for how you make the ask.

Skip the grand announcement. Propose a small change in how you structure your time together.

The ask is simple: “I want to try something with our meetings. I’d like to try splitting them into two formats: one where I bring my priorities and we work through them, and one where we focus on long-term direction. Can we try it for six weeks?”

Six weeks is enough to test whether it works.

When he pushes back, work through these in order:

Understand the pushback first. Don’t defend the proposal before you know what the objection is. Ask what’s not working for him about the idea. The answer changes everything you say next.

Lead with the ask, not the rationale. State what you need and what you’re hoping to get out of it. Context goes second. The founder who gets the rationale before the ask is already constructing a counter-argument.

Figure out what can be async. Not everything needs a meeting. If his concern is too many touchpoints, ask what’s already on the agenda that doesn’t need to be there at all.

Get to yes on something. If he won’t restructure the format, align on what gets covered and when. At minimum, agree that you’ll name the agenda at the start of every meeting before anything else happens. If it can’t happen in this meeting, set up another.

Before you redesign the meeting, cut what’s in it. This is the one that usually gets skipped. Before you ask for a new structure, ask whether the meeting is carrying conversations it was never supposed to hold: the status check on the ops hire, the question about the feature that’s already been decided. You can handle those async, work them out with someone else, or just decide them yourself. Clearing that out changes the dynamic before you’ve changed a single thing about the format.

You can’t manage what you haven’t designed.

The operators who build this architecture recover more than their meeting time. They recover their authority. That’s what the rest of these conversations are about.

If you’re navigating this with a founder-CEO right now and want to think it through, reply (I read all of them). I’d love to hear from you.