5 Takeaways, 8 Months Deep

Eight months ago, I jumped into the deep end of the Chief of Staff world. I haven’t really come up for air since. So what did I learn?

When I first started, my only frame of reference was the White House Chief of Staff and a hunch that the role was becoming more common in the private sector. In one of my first articles, I explored whether a former founder could make a strong Chief of Staff. After all, founders know the weight of owning a P&L, making payroll, hiring and firing and translating vision into execution.

Eight months later, after studying the role, writing weekly and testing frameworks, here’s what I’ve learned: that hypothesis was only part of the story. What actually sharpened my perspective was the discipline of studying and writing week after week.

And I’m not talking about mechanics because you already know those. These are the truths that seasoned Chiefs wrestle with: the nuances, the sharp edges, the things that separate good from great.

Every single Chief I’ve met shares this trait: humility. It’s not optional, it’s a requirement of the job. Chiefs know the power sits in the seat, not in them personally. That mindset keeps ego out of the way and creates space to serve the principal, the team and the mission. The moment a Chief starts believing it’s about them or worse, that they know better, the role breaks.

Design taught me this: what you leave out is as important as what you put in. The same applies to the Chief of Staff role. Servant leadership doesn’t mean doing everything that’s asked. It means knowing what not to take on and creating space for your principal to do what only they can do. Great Chiefs balance empathy with judgment: when to lean in, when to hold back and when to sharpen the move. And if they get it wrong, they adjust without skipping a beat.

The best Chiefs don’t just solve problems. They create reusable models like decision logs, priority filters and notecards that make the complex tangible and simple. Frameworks let the principal and team move faster without you in the room. Codifying the work is what turns individual wins into scalable leverage.

Frameworks create clarity, but rhythms create durability. The temptation is to play firefighter, make the save, close the loop and pull off the big heroic fix. But durable impact doesn’t come from one-off rescues. It comes from rhythms that endure: weekly resets, structured cadences, decision reviews. A Chief’s real power is building operating systems that keep momentum alive long after the adrenaline is gone.

The Chief of Staff role doesn’t come with a manual. The ones who thrive treat it like a craft: they study, they read, they join networks, they write and they test frameworks. Curiosity and discipline compound into sharper judgment. Over time, that learning becomes leverage: not just solving today’s problems, but creating clarity that helps the principal and team move faster tomorrow.

These five truths build on each other: humility creates the posture, discernment shapes the space, frameworks turn judgment into leverage, rhythms make it durable and craft keeps it sharp.

The Chief of Staff role isn’t one you ever fully “master.” It’s a role that compounds. The more you study it, the clearer it becomes. And the clearer it becomes, the more effective you are in helping your principal and team move faster, better and with deeper alignment.

If there’s one thing eight months of immersion taught me, it’s this: great Chiefs don’t chase definition they build discipline and it’s the thing I love most about the role.

Affiliate Link Disclaimer: Some of the links in this email are affiliate links, which means I may earn a small commission if you buy through them, at no extra cost to you.