Put a builder in a mature operating role and watch them get restless. Everything already works, so they start breaking things just to have something to invent. Put an operator into a 0-to-1 mess and watch them freeze — there's no system to optimize yet, no data to trust, nothing to make more efficient. Both are talented. Both are miserable. And both look like performance problems when they're really fit problems. I've watched this play out on team after team. The builder who was electric in the early days becomes the bottleneck once the thing needs to scale. The seasoned operator who took someone else's company from ten million to a hundred can't get a blank page off the ground. Neither failed. They were each asked to do the other one's job. There's research behind why this is so predictable. Studying 200+ startups, Noam Wasserman found that founders are most likely to be pushed out right after their biggest wins — because success changes the job. What comes next rewards a different set of instincts than what got them there. The person didn't get worse. The job changed under them. The takeaway isn't "builders are better" or "operators are better." It's that they're different, and the strongest ventures pair them on purpose — an inventor to make it exist, an operator to make it endure. The mistake is expecting one person to be both, or hiring the wrong one for the moment you're actually in. So before you hire, get honest about which one you are — and which one you're missing. Are you the builder or the operator on your team? And who's the counterpart you still need?