The Better You Are at This Job, the Less Anyone Notices

The quarter I remember most clearly is the one nobody talked about.

Planning landed clean. Every functional leader submitted their input by the Friday before the offsite, which had happened exactly twice in four years. Two cross-functional fires — one between GTM and Product, one that would have become a board-level conversation if it had surfaced three weeks later — got resolved quietly in week two. The CEO's board prep was done forty-eight hours ahead of schedule, the narrative tracked cleanly against Q2 actuals, and nobody called me at 9pm the night before.

At the end of that quarter, nobody mentioned it. The quarterly review was efficient. The board presentation went well. Three people thanked the CFO for the clean financials. A week later, there was a formatting error in a slide deck — a misaligned table, visible on the projector but not in the preview — and I received three separate messages about it within the hour.

I've thought about that asymmetry a lot. Not bitterly — the formatting error was mine and I should have caught it — but analytically. Because it clarifies something about this role that is otherwise very hard to explain: when you do the job well, you produce nothing visible. You prevent things. You resolve things before they escalate. You hold the context that allows other people to make good decisions. And the better you get at this, the more natural it feels to everyone around you — and the more likely they are to assume it would have worked out anyway.

This is not a perception problem you can manage your way out of. It is the architecture of the job. And once you understand it as that — a structural reality rather than an interpersonal failure — the path forward becomes clearer.

The Short Answer

A Chief of Staff demonstrates value to a CEO not through visible wins but through the absence of preventable failures — which makes the role structurally difficult to evaluate using standard performance frameworks. The most effective approach is to define value in terms of CEO capacity: how many decisions did the CEO not have to make because the CoS made them correctly? How many cross-functional fires were resolved before they reached the executive layer? The value is real; it simply requires a different measurement frame than most roles use.

Why Competence Makes You Disappear

Every other senior role I can name rewards high performance with a visible artifact. Revenue attained. Product shipped. Headcount hired. A VP of Sales hits 127% of quota and there is a number that represents that performance. A VP of Engineering ships a feature on time and there is a product that represents that execution. The artifact exists. It can be pointed to.

The Chief of Staff's highest-quality work produces the opposite of an artifact. It produces the absence of incidents. A planning cycle where every leader shows up aligned and the CEO doesn't have to reset priorities in real time — that disappears into the experience of the quarter. Three cross-functional conflicts resolved before they became visible to the leadership team — those never show up anywhere. The board presentation where the CFO says "the narrative was really clean this quarter" lands as a compliment to the CFO.

This is not ingratitude. Most of the executives I've worked alongside genuinely don't know what's been quietly resolved on their behalf, because the design of the role is to keep it quiet. When I tell someone "I handled the Product-GTM misalignment before the all-hands," the implicit message is "you didn't need to be involved in that." Which is the desired outcome. But it also means the CEO never develops a felt sense of the specific problem that was prevented — they just experience a smoother quarter.

The recognition paradox runs deeper than appreciation. Even with a strong relationship with your CEO, articulating the value in concrete terms is harder than it should be. "I prevented a problem" is structurally less compelling than "I solved a problem," even when the prevented problem would have been worse. This is not a communication failure. It is a consequence of how humans naturally track and attribute outcomes — and understanding it as structural, not personal, is the first shift worth making.

The Science Behind Why This Role Feels Different

A meta-analysis published in May 2026 — drawing on 515 studies conducted over 60 years and covering 800,000 workers — found that role ambiguity is the single largest predictor of workplace stress. Greater than workload. Greater than interpersonal conflict. Role ambiguity accounts for 70% of declines in work engagement and 80% of declines in task performance across the full dataset (ScienceX / Metaintro, 2026).

I read this and felt a specific kind of recognition — the feeling of finally having a word for something I'd been experiencing without language for it.

The Chief of Staff role is structurally the highest-ambiguity executive role in most organizations. Not because it's poorly designed. Because it has to be. The role sits at the intersection of every function and takes its shape from whatever the CEO and the company need at a given moment. In Q1, you are running planning. In Q2, you are resolving a board-level concern nobody else is positioned to own. In Q3, you are leading a cross-functional initiative that doesn't fit cleanly in anyone's job description. The mandate is to handle whatever matters most, which means the mandate is always changing.

This is a feature, not a flaw. But it also means the CoS is operating in conditions that, according to six decades of research, are structurally harder on cognition, engagement, and wellbeing than almost any other work environment. A separate 2026 survey found that the share of employees citing lack of recognition as a burnout driver nearly doubled year over year — from 17% to 32% (Meditopia for Work, 2026). HBR, in April 2026, identified "responsibility without authority" as a leading driver of executive burnout specifically. Chiefs of Staff typically have high responsibility and diffuse authority. The stress is not weakness. It is arithmetic.

Naming this structurally matters because it changes the conversation you have with yourself and with the people you work with. You are not struggling because you are doing it wrong. You are operating in conditions that are genuinely harder than they look from the outside.

Measuring What Didn't Happen

The frame that changed how I have the conversation with CEOs about this role is deceptively simple: stop measuring what you did and start measuring what your CEO didn't have to do.

How many decisions were made correctly below the executive layer because you were tracking them and had the context to call them? How many cross-functional standoffs got resolved in a Slack thread rather than in a Friday afternoon CEO meeting? How many board prep sessions started from a clean narrative because you'd already closed the gaps in the story? These are all real outcomes. They are all real capacity returned to the CEO. They simply require a different kind of accounting.

The measurement conversation is one worth having explicitly — and early. Not in a performance review. In the first thirty days of an engagement, or at the start of a new quarter. The version I've found most useful goes something like this: "I want to define what success looks like in this role together. My job is to handle the things that shouldn't reach you. Can we name what those are — the fires you never want to be the last to know about, the cross-functional tensions that should be resolved below your level? If I'm doing this well, you won't see those conversations. If something breaks down on my side, they'll surface to you. Let's use that as the metric."

Most CEOs respond well to this because it maps directly to what they want from the role. It also creates a shared definition of success that doesn't depend on the CoS cataloguing their own accomplishments — which is structurally awkward and usually undersells the real contribution.

Part of why we built Rhythms' Reviews feature was to make this kind of invisible work visible in a way that doesn't require anyone to argue for it. The auto-generated review shows what's been resolved, what's running, and what's been caught before it escalated — pulled from live data across connected systems, not assembled by hand. The CEO doesn't have to reconstruct that picture from memory. It's there.

What to Do With This, Practically

The structural reality of the role doesn't change. But a few things make it more navigable.

Name the role's structure explicitly with your CEO — before you need to. Most CoS roles are scoped in the first conversation and then never revisited until something goes wrong. The more useful approach is to have an explicit conversation early: "Here is how I define success in this role. Here is what I'll own below your level. Here is how you'll know if it's working." This is not a protection conversation — it's a design conversation. Having it once means you don't have to re-litigate it every quarter.

Build a habit of naming what you prevented, not just what you produced. There's a natural pull in status updates to highlight visible completions — the projects finished, the deliverables shipped. Those matter. But if your status update reads like a project manager's completion list, it misrepresents the actual leverage of the role. Practice naming the prevented thing: "The GTM-Product misalignment that was heading toward an all-hands incident got resolved in a Slack thread last Tuesday." That sentence is worth more than five items checked off a project list.

Create a record of caught problems as a byproduct of doing the work. The Chiefs of Staff who use Rhythms' Radar feature aren't just solving problems — they're building a history. Every off-track initiative that surfaces on day three instead of day thirty, every risk resolved before it reaches the executive layer, gets captured automatically. The CoS no longer has to argue for what they did. The record exists, from live data, without anyone having to maintain it separately.

Have the measurement conversation again at every transition point. New CEO, new quarter, new company phase — each one is an opportunity to reset what success looks like in the role. The CoS who defines their value metric clearly at the start of each chapter doesn't have to reconstruct it under pressure later.

The Quarter That Changes Your Thinking

I still think about that perfect quarter occasionally. Not because I want the credit retroactively, but because it clarified something I needed to see: the absence of acknowledgment wasn't evidence that the work didn't matter. It was evidence that the work had landed exactly as intended.

That's a strange thing to make peace with. The better quarter went unnoticed not despite the quality of the execution but because of it. The formatting error got noticed because it disrupted the experience of a smooth meeting. The invisible quarter didn't disrupt anything — it just ran.

There's a version of this role where that asymmetry still stings, where you measure the value by whether anyone stops to name it. I've mostly moved past that version. What I've found more useful is being very clear — with myself and with the people I work with — about what the role is actually supposed to produce, and then building the systems that make that production visible on its own terms.

The quiet quarter was a good quarter. I'd like to be able to show that.

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 does a chief of staff demonstrate value when most of the work is invisible?

The most effective approach is reframing the performance conversation around CEO capacity rather than CoS output. Define success in terms of what the CEO didn't have to do: decisions made correctly below the executive layer, cross-functional fires resolved before escalation, clean information at the right moments. These are measurable — they just require a different accounting than most roles use. The conversation is significantly easier to have at the start of an engagement than during a performance review.

Why do chiefs of staff burn out faster than other executive roles?

The structural conditions of the role — high ambiguity, high responsibility, diffuse authority — are precisely the conditions research identifies as most damaging to engagement and performance. A 60-year meta-analysis covering 800,000 workers found that role ambiguity is the largest single predictor of workplace stress, accounting for 70% of engagement declines. Chiefs of Staff operate in structurally high-ambiguity conditions by design, and HBR's April 2026 research specifically identified "responsibility without authority" as a leading executive burnout driver. Burnout in this role isn't personal failure — it's a predictable consequence of the architecture.

What is the recognition paradox for chiefs of staff?

The recognition paradox is that competence in this role produces invisibility rather than visibility. Every other senior role rewards high performance with an artifact — revenue, product, headcount. The CoS's highest-quality work produces the absence of incidents: prevented problems, resolved conflicts, clean operating cadences. Humans naturally track and attribute visible outcomes, which means the better the CoS executes, the more natural everything feels to everyone else — and the less salient the CoS's contribution becomes. Understanding this structurally is the first step to addressing it.

How do you make the chief of staff role more visible without undermining it?

The goal is not to make yourself visible — it's to make the value of the work visible. Build a habit of naming what you prevented alongside what you produced in every status update. Have the measurement conversation explicitly with your CEO at the start of each engagement or quarter: define the things you'll monitor and resolve below their level, and establish the absence of those conversations as the metric. Use tools that create a record of caught problems automatically — so the CoS can show a history of off-track initiatives surfaced early, risks resolved quietly, and information cleaned before it reached the executive layer, without having to maintain that record manually.