Productivity Prompt: Get to the Root of a Broken Meeting

You already know the meeting isn't working. You just can't figure out why.

That's the frustrating part. It's not that you don't care. You're the one who set it up. You're the one who keeps showing up. And you're the one who leaves every week with that same quiet feeling that something is off — but when you try to name it, everything blurs together.

The problem is you're too close to it.

When you're running the meeting, you're also managing the energy in the room, watching the clock, tracking who hasn't spoken, and trying to keep things moving. You don't have the bandwidth to also be the person diagnosing what's structurally broken. That's not a failure of awareness. It's just too much to hold at once.

And there's a harder truth underneath that.

Admitting the meeting is broken means sitting with the possibility that you're part of why. Maybe the agenda is unclear because you never slowed down to design it. Maybe decisions don't stick because the wrong people are in the room — and you built the invite list. That's uncomfortable to look at alone. So most people don't. They tweak the agenda, try a new time slot, and hope it sorts itself out.

It doesn't sort itself out. Try this prompt:

I run a recurring [meeting type] with [who attends]. The meeting is supposed to [intended purpose]. Lately it feels like [what's going wrong]. Act as a neutral thought partner and help me diagnose what's actually broken. Ask me clarifying questions one at a time, then help me identify the root cause and suggest two or three changes I could try before the next meeting.

Context

[meeting type] is the kind of meeting you run — a weekly team standup, a monthly project review, a cross-functional sync, a leadership check-in. Name it plainly.

[who attends] describes the people in the room. You don't need org chart detail. Something like "my direct reports" or "a mix of project leads from three different departments" is enough.

[intended purpose] is what the meeting is supposed to accomplish — alignment, decisions, updates, problem-solving. If you're not sure, that's worth naming too. Sometimes the meeting is broken because its purpose was never clear in the first place.

[what's going wrong] is your honest, unfiltered read on the symptom. People seem checked out. Nothing gets decided. The same issues keep coming back. Conversations go in circles. Write it the way you'd say it to a trusted colleague.

When to Use

Use this when you've left the same meeting frustrated more than twice in a row and you're ready to actually figure out why — not just vent about it. It works best when you're willing to be honest in your answers, including about your own role in the dynamic. The goal isn't to fix everyone else in the room. It's to find the one or two things you actually control and change those first.

💡 TIP

Let the AI lead with questions before it gives you answers. If it jumps straight to recommendations, say: "Before you suggest fixes, ask me three questions about how the meeting actually runs." The diagnosis gets sharper when you slow it down.

Want role-specific AI prompts built for the way you actually work? Explore the Role-Specific Toolkits at BetterWork Academy: https://academy.betterworktraining.com/role-specific-toolkits