The Five Questions Every Chief of Staff Should Ask Their CEO in Week 1

You're Already Behind

You walked into the role with a title and a mandate. What you didn't get was context. Your CEO's communication style. Their decision-making patterns. The things that drain them. The things that light them up.

Most Chiefs of Staff spend the first three to six months reverse-engineering all of this through trial and error. You sit in meetings and try to read the room. You send an email when they wanted a conversation. You bring three options when they wanted one recommendation. You protect their calendar when they actually wanted you to fill it.

Every misread costs you credibility. And in this role, credibility is currency.

I spent 20 years as a Chief of Staff. The pattern I saw over and over was the same: new Chiefs of Staff working harder instead of working smarter. Absorbing instead of asking. Observing instead of decoding.

You don't need six months. You need one conversation.

Communication Cadence

"How do you prefer to process information — verbally in real-time, or written so you can think it through?"

This question alone saves you months of miscommunication. Your CEO either thinks out loud or thinks on paper. The distinction changes everything about how you prepare them for meetings, how you deliver updates, and how you handle the moments when they say something in a meeting that sounds like a decision but isn't.

If they're a verbal processor, half of what they say in a room is thinking, not directing. Your job is to listen, capture, and circle back later to confirm what was an actual decision versus what was processing. If you execute on every verbal thought, you'll drown.

If they're a written processor, showing up to a conversation without a pre-read is wasting their time. They need to see it before they can think about it. The meeting is for questions, not for discovery.

Decision Architecture

"When you need to make a call, do you want options with my recommendation, or just my recommendation?"

This reveals how much intellectual space your CEO wants you to occupy. Some CEOs want to see the full landscape — three options, pros and cons, your recommendation highlighted. They want the decision to feel like a choice.

Other CEOs want you to do the thinking and just tell them the answer. They hired you so they could stop processing every decision. When you bring them three options, they hear: "I couldn't decide, so I'm making you do it."

Get this wrong and you either look indecisive (too many options for a CEO who wants your call) or presumptuous (one recommendation for a CEO who wants to choose). Neither is recoverable quickly.

The follow-up question is just as important: "At what dollar amount or risk level does this change?" Because the CEO who wants your recommendation on a $5K vendor decision might want three options on a $500K hire.

Strategic Orientation

"Where does your attention naturally live — external (market, customers, vision) or internal (team, operations, culture)?"

This tells you where the gaps are. Your CEO's natural attention creates a blind spot, and that blind spot is your territory.

If your CEO lives externally, they are energized by market trends, customer conversations, partnerships, and the big picture. They come back from every conference with twelve new ideas. The internal operations quietly erode while they're chasing the next horizon. Your job is to be the operational anchor. You own the internal machine so they can keep scanning the landscape.

If your CEO lives internally, they are deep in team dynamics, process improvements, and organizational structure. They know every employee's name but miss the competitive shift happening outside. Your job is to be their external radar. You surface the market intelligence, competitive moves, and customer signals they're not seeing.

The best Chief of Staff partnerships are complementary, not identical. You fill the space they leave empty.

Energy Management

"What drains you that I can take off your plate? And what recharges you that I should protect?"

This is the question that separates a Chief of Staff from an executive assistant. An EA manages the calendar. A CoS manages the energy behind the calendar.

Every CEO has activities that drain them and activities that fuel them. The CEO who is drained by board prep but lit up by product reviews needs a Chief of Staff who owns the board deck end-to-end and protects product review time on the calendar like it's sacred.

The CEO who is drained by one-on-ones but energized by strategy sessions needs a Chief of Staff who triages people issues before they escalate and ensures that strategy blocks never get eaten by HR fires.

When you know what drains them, you can intercept it before it reaches them. When you know what recharges them, you can protect it from getting crowded out. That's not calendar management. That's leadership support at the operating system level.

Partnership Expectations

"What does 'Chief of Staff' mean to you — and what do you need me to own versus consult on?"

This is the question that prevents the slow-motion authority crisis that derails most Chief of Staff tenures. The word "own" and the word "consult" mean very different things, and most CEOs have never been asked to clarify the difference.

When a CEO says "I want you to own the leadership team meetings," do they mean you set the agenda, run the meeting, and make decisions about follow-ups? Or do they mean you prepare the agenda for their approval, sit in the meeting, and take notes?

Without this conversation, you'll find out the hard way. You'll either overstep into territory they weren't ready to give you, or you'll hold back and they'll wonder why they hired a Chief of Staff who acts like an assistant.

The best way to do this: create a simple two-column list. Left column is "I Own" — full authority to act. Right column is "I Consult" — advisory role, CEO makes the call. Walk through the major areas together. Revisit it at 30, 60, and 90 days because the line will shift as trust builds.

Why Five Questions Instead of Six Months

These five questions aren't random. They map directly to the CoS Operating System I built over 20 years of doing this work.

Communication Cadence tells you how to deliver information. Decision Architecture tells you how to frame choices. Strategic Orientation tells you where to focus. Energy Management tells you how to protect capacity. Partnership Expectations tells you where your authority begins and ends.

Together, they give you the operating manual that nobody handed you on Day 1. They decode your CEO's patterns so you can stop guessing and start executing with precision.

The Chiefs of Staff who thrive don't work harder than the ones who struggle. They ask better questions earlier. They build the relationship architecture in Week 1 instead of Week 26.

That's the difference between surviving the role and owning it.