Wait for a Way. Get in the Way. Make a Way.

Wait for a Way. Get in the Way. Make a Way.

I’ve worked with more than 1,000 startup founders through Startup Ignition Bootcamp, and I’ve noticed something interesting.

When founders encounter an obstacle, they generally respond in one of three ways.

They wait for a way. They get in the way. Or they make a way.

But here’s what took me years to understand.

These aren’t three different types of people. They’re three different behaviors, and the same founder can demonstrate all three.

The goal isn’t the obvious one. It isn’t becoming some founder superhero who always makes a way, because nobody is that. The goal is to recognize when you’re waiting, when you’re getting in your own way, and how to spend more of your time making progress.

I’ve seen all three up close. The cool thing about the bootcamp is that at some point in the three days, it forces every founder into a situation that shows which behavior they’ll reach for.

All three behaviors are common, and which one a founder picks can change where the startup ends up. So let me go deeper on each one: what it looks like from the inside, and a founder I watched handle it that way.

1. Wait for a way

I remember a few years back, Ryan came in with a software idea for construction companies. He’d already talked to a developer and knew roughly what building it would cost. His plan was to raise $150,000 before doing anything else.

When we pushed him to talk to contractors during the three days, he explained that without a working product there wasn’t much to show them.

He wasn’t wrong. He really did need money to build the software. But he didn’t need money to find out whether contractors wanted it. He was waiting on funding to answer a question he could have answered that afternoon.

That’s what waiting looks like from the inside. It doesn’t feel like avoidance, it feels like sequencing, and the reason is usually true. The market really is soft. The round really hasn’t closed. The product really doesn’t exist yet. A true reason and a decision to stop aren’t the same thing, and the gap between them is where months go.

The test: what could you find out without it? Name the thing you’re waiting for, then ask what you’d still learn if it never arrived.

For Ryan the answer was almost everything. Whether contractors had the problem. What they do about it today. What they’d pay to stop doing that. None of it required $150,000. It required a phone.

He got there in the end. When he finally talked to contractors he found a better opportunity than the one he’d walked in with, which is the good news. The waiting cost him four months, and it nearly sent him a long way down the wrong road first.

Some waiting is right. Some doors are genuinely closed, and some decisions need information you don’t have yet. The problem isn’t that founders choose to wait. It’s that most never notice they chose.

2. Get in the way

Another story from a bootcamp alum. Natalie had a growing software startup and a co-founder who wasn’t delivering. Deadlines kept slipping. Customers were frustrated. She was quietly picking up the slack.

She knew the two of them needed a difficult conversation. Instead she spent weeks building new project management systems, rewriting responsibilities and scheduling accountability meetings.

At bootcamp we asked what was actually holding the business back. She finally said it out loud. It wasn’t a process problem, it was a people problem. She had been doing everything she could think of to fix the company except the one conversation that might have fixed it.

Natalie wasn’t avoiding work. She was doing an extraordinary amount of work to avoid a single conversation.

Nobody blocks a founder quite like the founder.

This behavior hides because it looks like diligence. A new system looks like leadership. A rebuilt process looks like progress. Both are easier than the conversation, and both can be shown to other people, which is a large part of the appeal.

The test: does the work touch the real obstacle? Say out loud what is actually in the way. Then look at tomorrow’s calendar. If nothing on it touches the thing you just named, you aren’t behind. You’re avoiding.

Work that cannot change the outcome is not progress. It’s avoidance with a calendar entry.

The same pattern runs through customer discovery, where the call you won’t make is the only thing on the list that can tell you no. If the blocker there is not knowing what to ask, that’s solvable, and we keep the questions that actually work written down.

Natalie had the conversation. She lost the co-founder and got her momentum back.

Sometimes the biggest obstacle in a startup isn’t the team. It’s the founder’s unwillingness to deal with it.

3. Make a way

Then there’s Alex. He wanted to build software that automated administrative work for small service businesses. He wasn’t technical and couldn’t afford a developer.

Rather than work out how to get the software built, he found a business owner and offered to do one repetitive task by hand. A spreadsheet, an email account, and a great deal of copying and pasting, delivering the result the software was eventually supposed to produce.

It wasn’t impressive technology. It was tedious. The owner paid him for it anyway.

Alex left the bootcamp without a product. He left knowing somebody would pay to have that problem solved, which is worth considerably more than a product nobody has agreed to buy.

He now has four paying customers and $1,200 in monthly recurring revenue, and a product roadmap built from workflows he has watched up close rather than guessed at.

The founders who do this aren’t smarter than the ones who don’t. I’ve watched both sit in the same room with the same information. The difference shows up somewhere smaller than talent. When the first route closes, they treat it as one road out of several. Everybody else treats it as the road.

The test: what’s the version nobody has to approve? Take what you’re blocked on and strip it until no part of it needs a budget, an introduction, a hire, or anyone’s sign-off.

  • Waiting on a developer? Do it by hand for five customers, the way Alex did.
  • Waiting on funding? Pre-sell it and find out whether anyone pays.
  • Waiting on an introduction? Write to the person directly with one specific question.

None of those is the good version. Each is the available version, and the available version is the one that gets you an answer.

The twenty second test

Ryan, Natalie and Alex came through different cohorts, years apart, with different ideas. Each of them got the same three days and stood in front of their own version of the same wall. What separated them wasn’t talent, funding or timing. It was what each of them did next, and the gap between four lost months and $1,200 a month is mostly that.

Before you open your inbox tomorrow, take the thing you’re most stuck on and ask three questions.

  1. What am I waiting for, and what could I find out without it?
  2. What am I avoiding because it could tell me no?
  3. What’s the smallest version of this that needs nobody’s permission?

Write the answers down rather than thinking them. Said in your head they come out generous, and the whole point is to catch yourself.

Then do the third one before anything else on your list. It’s the only item nobody else can delay.

You won’t always make a way. I don’t. But the founders who keep going are rarely the ones with the fewest obstacles. They’re the ones who can tell you, without flinching, which of the three they’re doing right now.

Founders at work during a Startup Ignition Bootcamp session Startup Ignition Bootcamp 3-day intensive. Zero equity. Long enough to find out whether anyone wants what you're building. See Upcoming Cohorts →
Back to All News