Why your second attempt usually works.

Getting Started · 5 min read

A lot of the people who come to me have already tried once. They paid a developer who took the money and delivered something that didn't work. They tried building it themselves with an AI tool and hit a wall. They went to an agency and got back something generic that missed the point entirely. They're bruised, cautious, and wondering if the whole thing was a mistake.

It wasn't. That first attempt taught them something invaluable: what the process actually looks like when it goes wrong. And that knowledge makes the second attempt dramatically better. Not slightly better. Dramatically.

What the first failure teaches you

Before your first attempt, you didn't know what questions to ask. You didn't know the difference between a designer and a developer. You didn't know what a prototype was. You didn't know that going straight to code without a design was a risk. You didn't know what a reasonable timeline looked like or what a fair price was. How could you? You'd never done it before.

After the first attempt, you know all of those things. You know what bad communication looks like, so you can spot good communication. You know what happens when there's no design phase, so you understand why it matters. You know what it feels like to be out of control of the process, so you know to ask about milestones, check-ins, and deliverables.

Research on entrepreneurial learning from Harvard Business Review suggests that founders who have experienced a prior failure are significantly better at evaluating opportunities, managing risk, and making decisions the second time around. The failure wasn't wasted. It was tuition.

Second-time founders are better clients

I say this with genuine respect: the clients who've been burned before are often the best to work with. They're more engaged. They ask better questions. They understand why the design phase exists. They respect the process because they've seen what happens when you skip it.

They're also more realistic about scope. First-timers want to build everything. Second-timers understand that an MVP is the smart move. They've already had the experience of a project that tried to do too much and ended up doing nothing well. So when I say "let's start with the core and build from there," they get it immediately.

The caution that comes from a bad experience is actually an asset. Cautious founders ask more questions. They do more homework. They take the process seriously. And they hold their service providers to a higher standard. That's not a disadvantage. That's exactly the mindset that produces a successful product.

How to make the second attempt count

Start by writing down what went wrong the first time. Not to dwell on it. To learn from it. Was it communication? Scope? Expectations? Did you skip the design phase? Did you go with the cheapest option? Did you not have a clear brief? Identify the specific failure points so you can address them this time.

Then look for the opposite of whatever failed. If communication was poor, find someone who communicates clearly and frequently. If the process was opaque, find someone who explains every step before it happens. If the output was generic, find someone who takes the time to understand your industry and your users. The red flags you ignored the first time become non-negotiable standards the second time.

Your idea survived the first failure. That's significant. You still believe in it enough to try again. That persistence, combined with what you've learned, is a stronger starting point than most first-time founders have. Don't let the bad experience stop you. Let it guide you.

Sources
Failing by Design (Harvard Business Review) - How prior failure improves entrepreneurial decision-making.
Iterative Design (Nielsen Norman Group) - Why iteration and learning from failure produces better outcomes.

Related blog posts:

How to prepare for your first app design project →

What to look for when hiring an app designer →

Don't forget to do your homework →