What a Chief of Staff Actually Does

The title is recent. The job is not.

What a chief of staff actually does is listen on behalf of someone who can't be in every room. The Romans had a version of this. So did medieval kings, every cardinal of any seriousness, every general worth remembering. The privy counselor at the English court was, functionally, a chief of staff. So was the praetorius in a Roman senator's household — the trusted man who heard what the principal could not be present to hear, and brought back the parts that mattered.

The modern version, the one with the LinkedIn title and the org-chart box, is a thinner version of the same thing. The job is still listening. Most descriptions of it pretend otherwise.

If you read what's written about the role online, you'll see a lot of language about strategic alignment, cross-functional initiatives, and operational cadence. This is not wrong, but it misses the point. The reason serious operators have a chief of staff is much simpler. They can't sit through every meeting their organization runs. They don't want to read every memo. They have, somewhere in their head, the worry that something important is being decided in their absence, by people who are perfectly competent but who don't carry the same context they do.

A good chief of staff fixes this. They sit through the meetings the principal can't. They read the memos. They flag the four things that don't add up. They don't run the meetings — they listen to them. They aren't a deputy. A deputy makes decisions. A chief of staff makes sure the principal has what they need to make decisions correctly.

The best ones are slightly skeptical by temperament. They notice when a number was stated and not supported. They notice when the same metric was defined two different ways across two meetings. They notice when the senior engineer answered a different question than the one the CFO asked. They write these down. At the end of the week, the principal gets a short list, and the list is almost always more useful than any deck.

The job is hard to hire for, because the skill it requires — sustained attention to language, math, and contradiction over the course of a long meeting — is a skill almost nobody trains for. It also doesn't show up well in interviews. The kind of person who is good at it tends to be quiet in groups, which reads as low energy in a hiring loop. The kind of person who is bad at it tends to be charming, which reads as high potential.

You can usually tell the good ones by what they do in their first three months. They produce, somewhere in week six or seven, a memo to the principal that contains five things nobody else had noticed. The memo is short. It's specific. The principal reads it twice.

Hoare's Bank, in London, has been run quietly for three centuries by partners who almost never give interviews. I don't know what they call the people who do this work for them. I do know the people exist, and that the bank's continuity is in some real sense the continuity of those people listening carefully and writing things down.

Frank is, at heart, an attempt at the same job. Not a replacement for the human chief of staff — the good ones are still the good ones — but a way to extend the same kind of attention to the meetings the human can't sit through.

The role is old. The form keeps changing.