Before you hire, ask yourself this: am I ready for a new team member?
A lot of founders are in pain. Overwhelmed. Buried in tasks. Stretched too thin and running on fumes.
So they do what feels logical: they hire someone. Maybe a VA, maybe an operations manager, someone to finally take things off their plate.
And here’s what I’ve seen again and again: if the foundation isn’t ready, the hire won’t save you. Most people don’t come in and build systems for you. They execute what’s already there.
So before you hire, ask yourself:
• Are your workflows documented?
• Do you know what success looks like in this role?
• Is there one central place for tasks and communication?
• Are you available to onboard and give context for the first two to four weeks?
If the answer is no, even the best hire will feel lost—and so will you.
Hiring doesn’t fix chaos. It amplifies it.
And yet, this happens all the time: founders hiring to feel productive instead of getting prepared, adding people instead of fixing systems, confusing motion for progress.
Hiring isn’t about making you feel less lonely in your business. It’s about making it run better. And that only works when there’s clarity.
So the next time you’re tempted to post that job listing, pause and ask yourself: are my systems ready?
The right hire can be transformational, but only when the business is ready to receive them.
-
Every decision in your company shouldn’t merge into a single lane
Every decision in your company shouldn’t merge into a single lane.
A founder once told me his company had a “people problem.”
Projects were slow.
Decisions stalled.
Small issues kept escalating to him.
His conclusion was simple:
“The team isn’t proactive enough.”
So we mapped how decisions actually moved inside the company.
It looked like a highway system.
Except every road — sales, operations, client delivery, finance — eventually merged into a single checkpoint.
His desk.
Every approval.
Every exception.
Every “quick confirmation.”
The team wasn’t the bottleneck.
The design was.
When every decision has to pass through one person, the company doesn’t slow down because people are incapable.
It slows down because the structure forces them to wait.
Founders often think scale means hiring more drivers.
But if the road still leads to the same toll booth, traffic only gets worse.
Real scale happens when decisions move closer to the work.
When authority is clear.
When ownership is visible.
When escalation is the exception, not the system.
The question isn’t whether your team is capable of moving faster.
The real question is:
How many decisions in your company still have only one lane?
-
Control and scale rarely coexist
Control and scale rarely coexist
Some founders say they want freedom.
But structurally, they design to be needed.
I once worked with a founder who was exhausted.
12-hour days.
Constant calls.
Slack always buzzing.
He told me, “I just need stronger people.”
But when we mapped the decision flow, the issue was obvious.
Every major decision required him.
Pricing.
Hiring.
Client exceptions.
Leaders made recommendations.
Then they waited.
Not because they weren’t capable.
Because authority had never been transferred.
Control can feel valuable.
But control and scale rarely coexist.
The real question isn’t:
“Is my team capable?”
It’s:
Have I structurally allowed them to be?
-
Don’t Hire a Captain If the Ship Isn’t Built
“Should I hire an operations manager?”
Maybe not.
The inbox is overflowing, deadlines are constant, and you’re still the one catching the details. The instinct is to think, “If I just find the right person, they’ll clean this up.”
I used to believe an operations manager would save me. Until the third one quit.
Here’s what I’ve seen inside my own company, Gorilla Stationers, and in many others: operations and building are two separate things. Most operations professionals are great at optimizing, but not at building systems from scratch.
If intake happens five different ways, case handoff depends on memory, and no one’s really sure who owns what, most operations managers will struggle. They first need to understand what’s going on, then build a system, and only then can they run it. When they realize it’s not about running but about building, they often leave.
So before hiring someone to run the ship, ask yourself: is the ship built?
And by built, I mean:
• Standardized onboarding
• Clear case handoff
• A follow-up system that doesn’t rely on you at 10 p.m.These are the things we as founders have to create first. In my experience, maybe one in a hundred operations managers is both good at building and happy to do it.
They’re two different jobs.
Don’t hire an ops lead to figure it out. Build the system first, then hand over the keys.
Because even the best captain can’t steer a ship that’s still under construction.
