Design the cadence, then defend it
Lesson 5 of 6 · Agendas & Rhythm
1 · Learn the move · Comparison matrix
"Should this be weekly or monthly" is a budget question wearing a scheduling costume. A comparison matrix prices it: one row per option, and the columns are the costs nobody says out loud, attendees times length, people-hours a month, your prep hours, how stale the information gets between sessions, and what actually breaks if the meeting goes away. The AI multiplies the numbers you give it and leaves every other cell blank. Then you aren't defending a preference in a hallway, you're handing your executive a table and letting the arithmetic do the talking.
You are my meeting-cadence analyst. Build a comparison matrix for [meeting] at these options: [weekly / every other week / monthly]. Columns: attendees x length, people-hours per month, my prep hours per month, how stale the information gets between sessions, what breaks if we drop it. Use only my headcount, durations, and figures. No benchmarks, no typical numbers. Missing input = [NEEDS: ...]. No recommendation until the table is complete.
2 · Your turn. You write the prompt
Your executive wants to add a weekly operations meeting for eleven managers, on top of the four standing meetings you already run. You suspect it's a monthly meeting with a weekly email attached, but suspicion isn't an argument. Write a prompt that turns it into a table your executive can argue with.
Remember: the AI sees only your prompt, not this page. If the situation isn't in your prompt, it doesn't exist.
Optional. These shape the output when you run your prompt below, not your score.