Early in my career, I worked for a visionary. Real wide-eyed, no-limits type. I was the integrator. I took his ideas and turned them into plans, teams, products. My instinct, every time he pitched something, was to find the obstacle. I was very good at finding obstacles.

One day he stopped me.

"Mike, all the problems you're trying to solve for right now would be great problems to have. Today we don't have a product. We don't have customers. Are we even a business? Your job is to make this a business. If we spend all our energy solving for problems we don't have yet, we may never reach the point where we can consider ourselves successful."

I've thought about that conversation hundreds of times since.

I've realized most founders eventually have the same one.

The Fear That Doesn't Sound Like Fear

The fear of success doesn't usually announce itself as fear. It sounds like planning. It sounds like due diligence. It sounds like being responsible.

What it actually is: A limiting belief. It’s spending today's energy on problems you'll only face if you win.

I spoke with a colleague recently who'd had a record year. Growing faster than he could staff it. Missed a few deadlines. Quality slipped on a couple of jobs. He shared that he felt deflated.

He wasn't afraid of failing. He was overwhelmed by his own success. The growth had started to feel like evidence of a problem rather than evidence that he was doing something right.

I reminded him that ninety percent of the founders who started when he did never reached this point. It landed differently than he expected.

The Pattern

I see it in how founders approach launching.

A founder I worked with delayed going to market for four months to build six more features. I asked what would happen if she launched and users asked for things she hadn't built yet.

"That's the problem," she said.

No. That's customers. That's a great problem to have. She was solving for feedback she'd only receive if the product was worth using.

I see it in sales, too.

Unlike the colleague I mentioned in the intro, a founder might be afraid to sell their products or services too quickly. They may even hold back on hiring a salesperson.

What if sales grow faster than operations can handle? What if customer service suffers?

They are spending today’s energy solving problems that will exist only if the company wins. And, as a result, preventing the company from winning in the process.

In both cases, the obstacle they were building around didn't exist yet. It would only exist on the other side of success.

Another Boss, A Different Frame

Later in my career, a different boss made the same point a different way.

He sat me down after a particularly hard meeting and said: “Mike, if I ask you whether we can build a bridge to the moon, don't tell me no. Come back and tell me how long it would take and how much it would cost."

He wasn't telling me to ignore reality. He was telling me to change the sequence. Commit to the destination first. Then figure out what's in the way.

Don’t interrogate the plan before you've even committed to the direction. Otherwise, the obstacles kill the idea before it ever gets a real shot.

That's not prudence. That's protecting yourself from the discomfort of committing to something before you know it will work. You're not managing risk. You're managing fear.

Keep Your Eye on the Horizon

Having a vision doesn't mean the path is clear. It means you know where you're headed even when you can't see the whole road. You'll recalculate the route more times than you expected. The destination stays.

When the obstacles feel overwhelming, the question isn't whether you should have started. The question is what the next step back toward the course looks like.

The founder with the record year has real problems. Labor is a real constraint. Quality matters. I'm not dismissing any of it. What I told him is: the problems you have right now are exactly the ones you signed up for when you decided to build something worth building. You don't get to skip them.

They're not evidence that something went wrong.

They're evidence that something went right.