

Late in the year, the same five leaders tend to end up in the same room. The CFO has a 2027 budget to close. The CIO and CTO have platform plans that need funding. The CISO has a risk picture that changed since spring, and the GRC leader has audit findings and new regulatory deadlines to place somewhere on the calendar.
These meetings matter, and they often disappoint. The cause is rarely the people. It's the executive meeting agenda: a list of topics written in a hurry, heavy on updates, light on decisions, and built as if every leader in the room needs the same thing from the hour.
A better agenda for CIO, CISO, CFO, CTO and GRC leaders isn't longer or more detailed. It's built around the decisions only that group can make together. Here's how to build one, with the CFO's seat in mind, since finance is so often the function that calls the meeting.
Why These Agendas Break Down
Senior leaders are not shy about how they feel about meetings. In research published in "Stop the Meeting Madness" in Harvard Business Review, Leslie Perlow, Constance Noonan Hadley and Eunice Eun surveyed 182 senior managers across a range of industries. Of those surveyed, 65% said meetings keep them from completing their own work, 71% said meetings are unproductive and inefficient, 64% said meetings come at the expense of deep thinking, and 62% said meetings miss opportunities to bring the team closer together.
Meetings that span five functions have their own failure modes on top of that. Each leader arrives with a different vocabulary, a different planning cycle and a different definition of risk. When the agenda doesn't account for those differences, the meeting turns into five parallel status reports. Everyone listens politely, and nothing gets decided that couldn't have been decided by email.
The fix starts before anyone writes a single line on the agenda.
Start With the Questions Only This Group Can Answer
Roger Schwarz, writing in Harvard Business Review on how to design an agenda for an effective meeting, argues that team meeting time should mainly go to issues that affect the whole team and need the whole team to solve. Those tend to be interdependent issues, where people hold different information and need to coordinate their actions.
For a technology, security, finance and risk group, those questions are not hard to find. Which 2027 initiatives get funded first, and which wait? Where does a security investment reduce a risk the board has already flagged? Which AI projects are ready for production, and who signs off on the controls? What happens to the plan if a major vendor fails or raises prices?
If a topic only needs two of the five leaders, it probably belongs in a smaller meeting. Keeping it off the main agenda isn't a slight. It protects the time of the other three.
Write Every Item as a Question
Schwarz's most practical advice is to list agenda topics as questions the team needs to answer. "Cloud costs" tells nobody what to prepare. "Should we commit to a three year cloud contract before the second quarter, and what would it cost us to wait?" tells everyone exactly what the discussion is for.
A question also tells the room when the item is finished. Once the question has an answer, the group moves on. Without one, a topic can absorb the whole meeting and still feel unresolved.
For the CFO, this habit has a useful side effect. Questions force the person proposing the item to state the decision, the money involved and the deadline. That makes it much easier to see which items carry financial weight and which are really updates in disguise.
Label Each Item: Inform, Input or Decide
Schwarz also recommends noting whether each topic is meant to share information, seek input for a decision or make a decision. Leaders participate differently in each case, and frustration builds when they guess wrong. A CISO who thinks the group is deciding on a security budget, when the CFO only wants input, will leave the room unhappy no matter how good the conversation was.
He adds that updates are better distributed and read ahead of time, with a short slot to answer questions. In practice, that one change can free up a large share of a quarterly planning session. If an item is labeled "decide," state the decision rule too. Is the group looking for consensus, or will one executive make the call after hearing everyone out?
Give Each Role a Real Stake
A shared agenda works when every leader can point to at least one item where their expertise changes the outcome. That doesn't mean equal airtime. It means no one is there just to listen.
CFO
The CFO needs items framed as tradeoffs with numbers attached: what an initiative costs, when the spending lands and what happens if it slips a quarter. Linking the discussion to budget strategy and enterprise risk appetite keeps funding choices tied to the risks the business has agreed to carry.
CIO
The CIO needs time on sequencing and dependencies. Many of the year's biggest decisions, from data platforms to application retirement, only work if they happen in the right order.
CISO
The CISO needs security framed as business risk, not a technical sidebar. The NIST Cybersecurity Framework 2.0, released in February 2024, added a new focus on governance and emphasizes that cybersecurity is a major source of enterprise risk that senior leaders should consider alongside others such as finance and reputation. That's a strong argument for putting security decisions on the same agenda as budget decisions, which is also the theme of the CFO's role in cybersecurity budgeting.
CTO
The CTO needs room for the technical reality behind the plan: what the engineering team can deliver, what it will take to maintain, and where a promising idea will run into architecture limits.
GRC
The GRC leader needs a standing place to raise regulatory dates, audit findings and control gaps before they become surprises. Placing that item early, rather than in the last five minutes, changes how seriously it gets treated.
Do the Time Math
Schwarz points out that leaders typically underestimate how much time a topic needs. His example is simple: ten people with ten minutes to make a decision means each person gets about a minute before the group has to decide. For a group of senior leaders discussing a seven figure investment, that's not a discussion. It's a formality.
Count the voices and the decisions before you set the times. A ninety minute session with five leaders can usually support two real decisions and a small number of input items. Anything more and the hardest topic will be rushed, which is often the one that mattered most.
Send the Reading Before, Not During
Few practices improve a leadership meeting faster than serious preparation. Amazon is the best known example. In his 2017 letter to shareholders, Jeff Bezos wrote that the company doesn't do slide presentations, and instead writes narratively structured six page memos that the group reads silently at the beginning of each meeting, in a kind of "study hall."
Not every organization will adopt that model. But the principle travels well. If a decision needs context, put the context in writing, keep it short and send it in time for each leader to read it. Then use the meeting for the part that only works live: questions, disagreement and the decision itself.
A Sample Agenda for a 2027 Planning Session
Here's one way a ninety minute session for the five leaders might look:
- Review and adjust the agenda (5 minutes).
- Decide: Which three 2027 technology initiatives get funded in the first quarter, and which move to the second half? (30 minutes, CFO leads)
- Decide: Does the third party risk program need more funding given changes in vendor exposure this year? (20 minutes, CISO and GRC lead)
- Input: What controls must be in place before the next AI use case reaches production? (15 minutes, CTO leads)
- Inform: Questions on the written updates sent last week (10 minutes).
- Confirm owners, dates and what gets communicated, then a quick review of the meeting (10 minutes).
Opening with a quick agenda check follows another of Schwarz's suggestions. Plans change between the invite and the meeting, and a minute spent adjusting the agenda saves twenty spent on the wrong topic.
Close With Owners and a Plus/Delta
The last ten minutes decide whether the meeting changes anything. Every decision should leave the room with an owner, a date and a clear line on what can be shared and with whom. That last point matters for planning sessions, where early numbers are easy to misread. It's also why some leaders test ideas in private conversations before public strategy is set.
Schwarz suggests ending regular meetings with a plus/delta: what did we do well, and what do we want to do differently next time? For a group that meets every quarter, five minutes of honest feedback on the agenda itself is the fastest way to make the next one better.
What Peer Rooms Teach About Agenda Design
Executive peer events face the same agenda problem at a larger scale. The ones that work are built around executive problems rather than vendor categories, and they rely on formats like executive roundtables for technology and risk decisions, where several functions look at one question together. The future of C-suite collaboration depends on that kind of structure inside companies too.
Leaders who spend time in well run peer rooms often bring the habits home. Through CFOMeet, finance leaders meet in intimate executive roundtables described as private, collaborative spaces to debate, challenge and refine corporate financial strategies. CIOMeet, CISOMeet, CTOMeet and GRCMeet do the same for their peers. As the CXO Inc. team notes, too many executive events deliver crowded agendas and generic presentations. Internal planning meetings can fall into the same trap, and they can get out of it the same way.
FAQ: Building a Better Executive Meeting Agenda
What should an executive meeting agenda include?
Each item should be written as a question, labeled as inform, input or decide, and given an owner and a realistic time. Updates should go out in writing beforehand, and the agenda should end with owners, dates and a short review of the meeting.
How many decisions should a C-suite meeting try to make?
Fewer than most agendas assume. A ninety minute session with five senior leaders can usually support two real decisions plus a small number of input items. More than that and the hardest topic tends to get rushed.
Why should agenda items be written as questions?
A question tells every leader what to prepare and tells the group when the discussion is finished. A topic label like "cloud costs" leaves people guessing about what the meeting is supposed to decide.
Why should the CFO care about agenda design?
Finance often convenes planning meetings and owns the tradeoffs they produce. A well built agenda surfaces cost, timing and risk for each decision, which makes it easier to fund the right work and defend those choices later.
Should security and risk topics sit on the same agenda as budget topics?
Yes, when decisions overlap. NIST's Cybersecurity Framework 2.0 emphasizes that cybersecurity is a major source of enterprise risk that senior leaders should consider alongside finance and reputation, so funding and risk choices belong in the same discussion.
Better Agendas Lead to Better Decisions
The best agenda for five senior leaders is short, specific and built around decisions that need all of them. CXO Inc. brings CFOs, CIOs, CISOs, CTOs and GRC leaders together through curated regional events, roundtables and strategic 1:1 meetings designed around the questions leaders are actually facing. More executive perspectives are available through CXO Inc. Insights.