Operations Isn't a Hire
A founder I work with is about to interview his sixth operations hire in eighteen months.
He's hired and fired an EA, a chief of staff, a business ops lead, an AI tinkerer, and another EA. Each one arrived with the same promises: visibility into what his team was working on, fewer things escalating to him that shouldn't be, his calendar back so he could actually think.
Six months in, every time, he'd find himself building his own mental list of what was on track and what was slipping. He’d be back to anxiously pinging people in Slack to ask what was happening with their work.
He didn’t have much hope that a new hire would be different. He was going to do it anyway. He was exhausted and couldn’t see an alternative. But nothing about that math adds up: six months of recruiting, two hundred thousand in base salary, another onboarding cycle, another quarter of running it himself in the meantime.
I told him to stop looking. He didn't need a sixth operations hire. He needed an operations system. We built one in a single afternoon using Slack and Claude.
The version of this that actually works is unsexy and small. It runs in the background and surfaces the things you'd otherwise have to chase your team for: what shipped, what's stuck, where time is getting lost.
It doesn't reinvent your workflow. It doesn't ask you to learn a new tool. The reason your last operations hire failed isn't that they didn't have a good framework. It's that they tried to install a new operating rhythm on top of your existing one. If your team lives in Slack, build it in Slack. If they live in Notion or Linear, build it there.
Here’s what that simple system looks like.
It starts with a daily check-in bot. When someone logs in, the bot DMs them. Ready to start? When they say yes, it reads their calendar, their to-do list, and whatever project tool you use. Then it checks against the team's priorities.
The bot asks team members three questions: what shipped yesterday, what's the one thing you're moving today, anything blocked or behind. These take about five minutes to answer. They're also easier to answer because the bot, unlike a manager, doesn’t judge. It just collects information.
Then, at the end of each week, the bot sends you an email. There’s no dashboard or document, you get four lines: how many hours the system gave back to you that week, where each of your top priorities actually stands, what's slipping, what changed to put it behind.
You get the same email every Friday in the same shape. The point of the simplicity and the regularity is that you don't get lost digging for that information. Because once you start sticking your nose in other people’s work, it’s easy to get sucked in and stuck micromanaging.
Most of what the system does is simple automation: pulling data, summarizing it the same way every time, pinging people on a regular cadence. The thinner layer on top, where the system has to decide what's important enough to escalate, is where you let the AI think. But the judgment doesn't originate with AI. You set the rules. The tool applies them.
For example, you tell the system that product launches are the top priority this quarter. You tell it that anything more than two days behind on a launch task is something you want to know about. You specify the tone you want the summary written in. Then it does that, consistently, every Friday at 4 p.m., without you needing to remember to ask.
The last piece is the most important. It's what separates a system from a surveillance tool. You send the same weekly summary that you receive to the team: what's on track, what's slipping, where the focus is for the coming week.
The first time I saw this set up well, it was for a team whose CEO kept getting in the way of his own people. They were good, but he was anxious. He had a suspicion that his EA wasn't doing her job well. He'd regularly ping her at midnight asking if things were done. Once he had a system, he could actually see the hours she was saving him. He stopped micromanaging. He started focusing on what he actually had to do.
The system itself is easy to build. CEOs resist it because it doesn’t promise the same relief as the idea of a hire. Hiring an operations person feels like solving the problem. Building an operations system feels like sitting with it.
There's a big difference between offloading work and offloading anxiety. The operations hire is almost always an attempt at the second. When you hire a chief of staff to "make sure the team is aligned," what you're really hiring is someone to manage the part of your day that makes you anxious.
You don't want a system. You want a person who will absorb the chaos so you don't have to look at it yourself.
This isn't an argument against hiring. The first EA still belongs in your business, the same way a head of product or a finance lead does. Those are real roles solving real problems. The chief of staff you've been trying to hire for the third time isn't filling a role. They're filling a feeling.
That's the part the system actually exposes. There's no human in the middle anymore. The data comes straight to you. You can see what's slipping and what you're avoiding. The bot doesn't soften it. It just reports.
Most founders find that uncomfortable for about two weeks. Then they realize the chaos they were paying someone two hundred thousand a year to translate was never actually chaos. It was just unconnected data. Once you can see it cleanly, you don't need a translator. You need to make a few decisions.
Reply or comment with the chaos you've been paying someone to translate. I read every one.
-Christine
If You Want To Go Deeper...
Here's where to start:
⚫️ Private Coaching: for early and growth-stage entrepreneurs who want to lead with more clarity while increasing their resiliency. See if we're a good fit here.
⚫️ The 20 Hour CEO Self-Paced Course:The frameworks, systems, and playbooks to stop being the bottleneck — on your schedule.
⚫️ The 20 Hour CEO Live Cohort: 3 weeks, 6 live sessions. Bring your actual business, rebuild how it runs, and leave with systems already in motion.
