The Best Chiefs of Staff I Know Have Gotten Very Good at Saying No

I remember the exact meeting. Someone on the leadership team was walking through a vendor transition that had stalled — the person who used to own it had left the company two months earlier, and nobody had formally picked it back up. About ninety seconds into the explanation, they looked at me and said, "You're just good at this kind of thing." It wasn't really a question. By the time I said "sure, I can take a look," the vendor transition was mine, stacked on top of everything that was already mine, and I hadn't actually decided anything. The decision had been made for me, inside a compliment.

That's not a dramatic story. It's not even an unusual Tuesday for a Chief of Staff. What made me pay attention wasn't that meeting specifically — it was noticing, a few months later, that the pattern had repeated itself at least six times since: a project with no clear owner, a version of "you're good at this," and me saying yes before I'd actually weighed whether I should. It took most of a quarter to notice what the pattern was costing me. Not hours, though there were plenty of those. The real cost was quieter: every project I absorbed because I was capable of handling it was time I wasn't spending on the two or three decisions that quarter that actually needed a Chief of Staff's judgment — not a competent generalist's spare bandwidth.

Start by Calling It What It Is

Saying no to non-strategic work as a Chief of Staff starts with naming the pattern out loud — most scope creep doesn't arrive disguised as an obvious overreach, it arrives disguised as a compliment. The strongest operators treat their mandate as something to actively protect, not something that expands automatically to fill whatever capacity they have, because every non-strategic task absorbed is time not spent on the judgment calls only they're positioned to make.

Scope Creep Doesn't Look Like an Overreach — It Looks Like a Compliment

Nobody has ever walked up to me and said, "I'd like to expand your role beyond its actual mandate." If they had, I'd have said no immediately — that's an easy no. What actually happens is smaller and harder to catch: "you're the only one who can pull this off in time," or "you already know all the stakeholders," or my personal favorite, "it'll take you twenty minutes, tops." Each one is true, narrowly. Each one is also a request to spend real time on something that isn't strategic, dressed in language that makes refusing feel like refusing the compliment itself.

Earlier this year I watched a webinar recording built around exactly this question — a founder of a Chief of Staff community, an operator who'd been the same principal's CoS for three years through a five-hundred-person headcount jump, and someone who'd worked the role across several fast-growing companies, all asked what the hardest part of the job looks like in 2026. The answer that came back fastest from all three wasn't burnout in the abstract. It was scope creep, specifically: when a project doesn't have a clear home, it lands on the Chief of Staff's plate by default. Their read on it was blunt — the Chiefs of Staff who thrive are the ones being ruthless about which projects they take, saying yes to the most strategic ones and no to nearly everything else. The ones who struggle are trying to be all things to all people, and they either burn out or quietly become invisible, doing more and more work that nobody notices because none of it was ever the work they were actually hired to do.

I recognized myself in that second description more than I wanted to. The office relocation committee. The all-hands run-of-show for two straight quarters. A customer advisory board deck that had nothing to do with anything I actually owned, except that I was the one who could format a deck fast. None of it was bad work. All of it was someone else's work, wearing my name because I hadn't said no.

What Every Yes Actually Costs

Here's the arithmetic I wish someone had walked me through earlier: a Chief of Staff role doesn't come with unlimited hours, it comes with a fixed number of hours and an unusually wide aperture for what counts as "in scope." That combination is exactly why the role attracts scope creep in a way other functions don't. A finance director who gets handed an unrelated marketing task will say, correctly, "that's not my job" — and everyone will nod, because the boundary is obvious. A Chief of Staff who says the same thing about a genuinely unowned, genuinely urgent problem sounds like they're refusing to be useful. So most of us don't say it. We absorb the vendor transition, the relocation committee, the deck. And the hours have to come from somewhere.

They came, in my case, from exactly the work that made the role worth having in the first place. I stopped reading the board deck line by line before it went out, because I didn't have the two hours it took to actually think about what the numbers implied — I only had the twenty minutes it took to format them. I stopped following up on a cross-functional disagreement between two VPs that needed someone with enough context to broker it, because I was in a meeting about the office move instead. Nobody flagged either of those as a problem in the moment. They just quietly stopped happening, the way things stop happening when the person responsible for them runs out of runway for anything but the loudest request in front of them.

This is the specific thing Rhythms' Reviews pillar was built to fix for the part of the job that is legitimately mine — pulling the executive review together from live, connected data instead of my hand-assembling it every cycle means the hours that used to disappear into deck prep are hours I can spend on the judgment calls, not the formatting. It doesn't solve the compliment problem. But it does mean fewer of my actual hours are already spoken for before someone asks me to take on something new.

The Question I Ask Before I Say Yes Now

I use one filter now, and it's embarrassingly simple: does this request touch a decision the CEO or the leadership team genuinely needs made, or is it administrative work that just needs a competent person attached to it? Urgency and strategic importance get confused constantly, and almost all scope creep hides inside that confusion. The vendor transition was urgent. It was not strategic. Those are different questions, and I'd been answering the first one as though it answered the second.

Running that filter out loud, in the moment, changes the conversation more than I expected it to. "This is time-sensitive, but I don't think it needs a Chief of Staff — it needs someone who can own the vendor relationship going forward. Who's the right owner?" is a different sentence than "no." It doesn't sound like refusal. It sounds like triage, because it is triage, and most people asking for help actually want the problem solved, not specifically solved by me. Half the time, naming the real owner is more useful to them than my doing the work myself would have been.

We built Radar for the earlier version of this same problem — surfacing a stalled initiative or an off-track metric on day three of a cycle instead of day thirty, so nobody finds out something's at risk only once it's already become an emergency that lands on whoever's closest. The vendor transition that got handed to me was exactly that kind of emergency: something that should have been caught and reassigned weeks earlier, before it needed a compliment to get someone to take it. Catch the gap early enough, and it never becomes a favor anyone has to ask for.

What Changed When I Started Saying No

The uncomfortable part came first. I said no to owning the next all-hands run-of-show, and there was a beat of real silence before someone else picked it up. I felt, for about a week, like I'd let people down — like the thing that made me valuable was precisely the willingness to be handed anything, and I'd just proven I wasn't that anymore. That feeling is real and I'm not going to pretend it isn't. It's also, I've come to think, the exact feeling you're supposed to sit through on the way to doing the job properly.

What actually happened after that beat of silence surprised me. The requests didn't stop. They changed shape. Instead of "can you take the relocation committee," I started getting "we need someone in the room when we decide how to handle the two competing product roadmaps" — the kind of ask that's genuinely mine, that uses the judgment and cross-functional context I actually have, instead of the availability I used to advertise by saying yes to everything. Leadership didn't route less work to me. They routed better work to me, because my bandwidth was visibly protected for the things that needed it.

Rhythms' Playbooks runs a piece of this for me now too — the recurring cadences, the weekly check-in prep, the QBR sequence, all of it pulling from connected data automatically instead of requiring me to personally kick it off every cycle. That's not a small thing when you're trying to protect time for judgment calls: it means the recurring operational work doesn't quietly expand to fill the hours I've freed up by saying no to the one-off stuff. The freed time actually stays freed.

I still think about the better you are at this job, the less anyone notices — because saying no runs directly against that instinct. If invisibility is already the risk, refusing work feels like accelerating it. What I've learned since is closer to the opposite: the work that actually earns notice, eventually, is the strategic work you protected time for, not the miscellaneous work you absorbed to stay useful in the meantime. The job where nothing going wrong is the only proof you did it right is still true — but it's truer of the strategic work than the administrative work, and scope discipline is how you make sure there's still room for the former.

What I'd Tell Myself in That First Meeting

I don't think the answer is saying no to everything, or building a rigid job description and refusing anything outside its lines — that's not how this role works, and honestly, it's not why most of us took it. Some of the best things I've done for the companies I've worked for started exactly like that vendor transition did: a favor nobody else could do, handed to me without a formal process. The difference is what happened after. That vendor relationship turned into a standing seat at a quarterly supplier review, which turned into being the person leadership asked before any major vendor decision — a real, lasting piece of the role I actually wanted. The office relocation committee turned into nothing. Same shape of ask, opposite outcome, and the only difference was whether the work connected to a decision that mattered past the moment it was finished.

That's the actual test for the exception: not "is this technically outside my job description," but "if I do this well, does it become something, or does it just end when the task ends." I still say yes to plenty of things nobody assigned me. I've just stopped assuming every compliment-shaped request is one of the good ones.

If you're still saying yes to everything because saying yes is what got you the seat in the first place, I'd only ask you to try that test once on the next thing that lands on your desk uninvited. You might find, like I did, that it sorts your week faster than you expected.

If this sounds familiar, request a demo at rhythms.ai and see what it looks like when the system runs itself.

Frequently Asked Questions

How do I say no to non-strategic work as a Chief of Staff?

Start by naming what's happening — most scope creep doesn't arrive as an obvious ask, it arrives as a compliment disguised as a request. Once you can name it as scope creep rather than "someone needing help," it becomes a decision you're making consciously instead of a reflex you're not examining. From there, the actual no is often easier than it sounds: point to who the right long-term owner is instead of simply declining.

Isn't saying yes to everything part of being a good Chief of Staff?

No — it's often the opposite. The role's value comes from judgment and cross-functional context, not from being available for anything that lands on your desk. Every non-strategic task absorbed is time taken directly from the work only the Chief of Staff is positioned to do, and a role that expands to fill all available bandwidth eventually has none left for its actual mandate.

How do I know if something is actually strategic or just urgent?

Ask whether the request touches a decision the CEO or leadership team genuinely needs made, or whether it's administrative work that just needs a competent person attached to it. Urgency and strategic importance are frequently confused, and most scope creep hides in exactly that confusion — a task can be genuinely time-sensitive without being genuinely yours.

What happens if I start saying no more as a Chief of Staff?

Initially, some discomfort — you may disappoint someone who's used to you absorbing anything handed to you. Over time, the pattern usually reverses: leadership starts routing genuinely strategic work your way instead of miscellaneous tasks, because your bandwidth is visibly protected for it, and that's a better trade than it initially feels like.