'''## The Ops Hiring Trap: Stop Hiring 'Athletes' 🚫
You've seen this hire before. They have a pristine resume, interview like a seasoned consultant, and radiate an aura of "high agency." They're a "general athlete"—a smart, scrappy problem-solver you can throw at any fire. You hire them into a critical operations role. The first 90 days are great. Then, the fires get bigger, the systems they were meant to build never quite materialize, and 12 months later, they quietly churn, leaving you with the same problems you started with.
The problem isn't the athlete. It's your game plan.
Ops-heavy businesses love the idea of a generalist who can "figure it out." But relying on raw talent without a system is a recipe for stagnation. You can't scale a business on a series of heroic, unrepeatable efforts.
The "General Athlete" Fallacy
Early-stage companies run on generalists. When you have five employees, everyone does a bit of everything. Hiring for intelligence and drive is all that matters.
As you scale, this habit becomes a liability. The belief that a smart person can simply absorb complex, undocumented processes through osmosis is a fallacy. What actually happens is they spend their first six months just trying to map the existing chaos. They create their own ad-hoc fixes and workarounds, which adds another layer of complexity for the *next* person who has to learn the role. The business becomes a tangled web of individual preferences, not a system that can be managed and improved.
This approach doesn't just create process debt; it burns out your best people. Athletes want to win. If they can't tell what winning looks like—or if the rules keep changing—they will leave for a team that has its act together.
Onboarding Is a System, Not a Vibe
What does onboarding look like for your ops hires? If it's a series of coffee chats, a link to a messy shared drive, and a pat on the back, you are failing your new hire.
Effective operational onboarding is not about cultural immersion. It is a systematic transfer of knowledge and a clear definition of success. It is a product, and you are the product manager. It must be designed, documented, and consistently executed.
A successful system includes:
- A "Single Source of Truth": A well-organized knowledge base (we use Cendryva, but Notion, Confluence, or even a structured Google Site can work) that documents all core processes. Not just *what* to do, but *why* it