Given the audience on Indie Hackers, I’m betting a lot of you have read the book The Lean Startup.
One of the central themes in the book is to “fail fast.” I agree with a very limited application of that mantra, but I’m begging everyone to stop giving this advice. Here’s why.
Failing fast is the idea that you need to sprint to get a product in front of customer faces as quickly as possible. There are enormous benefits to the application of this approach to building startups:
Decrease wasted time — You don’t want to spend a year and a half in “stealth mode” building a startup that is going to completely flop.
Fight perfectionism — Perfectionism is a startup killer. I’ve had to fight it for a long time with Malparse and still fight it daily as I spend too much time in the “planning phases” of development.
Validate your idea — Piggybacking off the first point, you want to validate that your idea is a good one. Ensure that before you put all this effort into building your unicorn-to-be that you’re actually going to get a couple of customers.
The list of potential benefits goes on and on… Like I said, they basically wrote the book on this with The Lean Startup so I’m not going to belabor the point.
The problem is that we’re wrong about the application of “fail fast.” We have to stop telling people to fail fast when the methodology is supposed to apply to start-ups. When businesses fail fast, you get
When people fail fast, you get
I write Malparse on my free time not because I don’t think it will succeed, but because I have a wife and two kids depending on my comfortable income to eat. I have savings, but I don’t want to have to burn through it to build something that may flop instead of using it for unforeseen medical bills or a new house some day.
Frankly, it’s often a silly financial decision as well as a sign of a developer’s lack of patience, to quit their day job to found their startup instead of developing their business more slowly and sustainably with a comfortable, secure job.
If you’re reading this and take offense, or if you’re already writing out your angry reply about this or that unicorn that was built by this or that all-star founder, you’re missing the point.
If you want to quit your job to pursue your dreams, by all means go for it. That’s your own choice and frankly in a way I envy you for your courage.
This post is written to all the Indie Hackers out there shaming or trying to convince others to quit their jobs to chase the clouds when that’s simply bad advice for the majority of people.
Let startups fail fast and founders succeed slowly.
Stop telling people what to do and what not to do.
If you read the post, I'm telling people not to tell others what to do. :)
If you’re reading this and take offense, or if you’re already writing out your angry reply about this or that unicorn that was built by this or that all-star founder, you’re missing the point.
...
This post is written to all the Indie Hackers out there shaming or trying to convince others to quit their jobs to chase the clouds when that’s simply bad advice for the majority of people.
Let startups fail fast and founders succeed slowly.
And you did exactly the same.
I don't feel offended at all but I don't like the manner you expressed your thoughts. You sound like you are a teacher before the students. But any proof you can teach others? How many startups did you launch? How many startups did you fail and succeeded? I guess you launched only one. Would you trust a math teacher who just know the multiplication table? ... me neither.
Instead, I would recommend just telling about your feelings and experience, but not in the "teacher manner".
One more note.
Don't you think you are pretty contradictory here? You spent your time on something you even don't think will succeed? And in the same sentence, you told us about your dependant so trust me you would never waste your time on something you don't believe in, taking into account your situation.
Good luck.
I'm assuming there's something lost in translation here.
I am telling people to let others take their own route. In the excerpt I posted in the comment you replied to, I told people to just let others do things the way they want to do them and to let them take a more conservative route than the "fail fast" methodology.
"How many startups did you launch"
Well, if you had taken the time to read my last post which is fairly easy to find, since you're asking for my credibility without doing too much looking into it, you'll find I've failed at least one launch. I can add two others to that that I failed to launch because of a similar "fail fast" methodology. I've also watched friends fail to launch their startups for similar reasons.
If you had issue with my tone, that's sort of odd, because I wasn't going for a "teacher manner" in the way I spoke. I was offering my feelings and experience, as you suggested.
If you read the excerpt you quoted a bit more clearly, you'll see I wrote "I write Malparse on my free time not because I don't think it will succeed..." Meaning I do think it will succeed, but I'm not willing to bet the safety of my dependents on it.
Based on your comments, I don't think you read the post very clearly.
👏🏻
This comment was deleted 3 years ago.
I'm not sure I follow. The idea of failing fast isn't to "fail big as soon as possible". It's more of a scientific method to learning the truth about your business idea. If you take forever to validate an idea, you're more likely to build up mountains of debt, waste time, and ruin your career. If, on the other hand, you test out a small idea and it fails, you can bail quickly.
Another way to look at it is that learning is all about failing. If you are trying to do something new and are not learning, chances are you either already know how to do it, or you're not trying hard enough to push your abilities. It's only when you hit your abilities that you fail and learn something new.
Hopefully, you've set yourself up so you can recover from that failure and try again. If you don't have the ability to recover, maybe it's not worth it to take on such a large risk.
I agree with you.
I have a feeling the post author gets the "fail fast" concept differently than it was supposed to. It just means that if you fail - and nobody knows if you do or not, before you do - don't waste your time, money, and other resources. Put a minimal of them to see if you fail or not. That's it.
I find this discussion rather pedantic.
When people say "fail fast," they basically just mean "remember to move on if it's not working, don't get married to one idea."
I think you're reading into/dramatizing it too much.
I 1000% agree with this. Everyone should read the story about Daymond john and FUBU. Don't quit your day job right away and jump into your startup. Build it on the side and use that steady income to help you build it. Yes, it's harder to do two things at once, but trust me, it's easier to build knowing you have a secure paycheck and no rushed limit to"make it"
Agreed! While I think "fail fast" was originally an antidote to over-building and not shipping, there are in my experience concepts where I was simply too early in the market, or another 6 months would have made all the difference.
Love that. I think you summarized it perfectly. Fail fast with your product, not with your life. Ship that product out ASAP and get that feedback, but don't burn through your savings without even seeing what the market needs or wants at the moment.
I don't take offense from this post at all. Ad You might as well be talking directly to me. I am a big proponent of "Fail Fast, Fail Often", even when I don't take my own advice :)
I also, quit my job almost a year ago so I could focus on building a project and finally finishing it. (if I think deeply about it there were other reasons but this was the primary excuse). I burned through savings and have subsequently had to go back to FT work with no finished project to show for it. I did not fail fast...I just failed.
I think a lot of people misunderstand the "fail fast" advice. It doesn't necessarily mean "quit your job, go balls to the wall, burn out, and fail at your dream". If it did, this would be AWFUL advice.
The way I (and I think others who give this advice) understand this advice is:
"Build the smallest thing you can that solves the simplest problem you are focusing on and get it in the hands of as many users as possible as quickly as you can so they can tell you if it's garbage or not. If it's garbage drop it and pivot to something else immediately."
No breaking that down a bit, all it is saying is build an MVP you can show some real potential users and get their feedback quickly so you know if you have something people want. If these first few users tell you they don't like it, you've failed. Move on. Don't waste more time on a doomed project.
Now maybe this timeframe is 1 weekend. Maybe it's 1 month. But it shouldn't be 1 year. If you are spending time and money on a project for too long, you are going to lose a lot of time and money. And this wasted time and money could have been spent on some other idea which could have been more likely to be successful.
While I agree with much of what you say in this post, I think you fundamentally misunderstand the point of "fail fast". No one wants your start up to fail, but you should move on from doomed projects...now if only I could follow this sage advice :)
Hmm, 'fail fast' doesn't mean 'build fast'. It just means 'build minimal and validate' before investing significant (time/energy/money), else move on quickly.
It's a trick to avoid 'Mountains of debt', not to have them. It's also independent of whether someone pursue a side hustle or quit their day job.
Although I agree to your general sentiment that
Indies shouldn't get too excited and quit their day jobs, without having a sustainable + validated business backup. A counter point someone may raise is that - if you don't put your 100%, you are significantly less likely to succeed - agree to that too.Agreed with you Scotalia. Let people decide what works for them. Because people and circumstances are different. Someone may quit a job to get the 100% push they need to build it, and this idea may not work for another person. These would be based on many factors such as how much you need to function and cover your monthly bills, married or single, your intuition. So, this is why it is wrong to generally tell people the dos and don´ts.
“fail fast but don't fail often”
Great article, I think there is a lot of good insight here. We are building our own SaaS platform and agree with the idea behind "Let startups fail fast and founders succeed slowly".
I think the only way for a founder to succeed slowly is to make small experiments that validate an idea. If it didn't work, pivot. You can fail fast 1000 times if they are small experiments that will hopefully lead to a gradual understanding and growth in the long term.
Hi Mitch, thanks for your post and your honest words. I agree with you, cause I did the exact opposite of what you wrote and took my lesson. We are heavily biased by all those success stories in the media and hearing only from startups that made it. However, over 90% of startups fail. Things might not work out as expected or initially planned. This happened to me. I quit my job, jumped into my startup idea. Successfully applied to a tech incubator. Made it to the finals. I expected to get pre-seed investment quickly only to find out that most of the investors and big names in our country won't risk pre-seed investments. I thought I would find a capable team and that we will build a prototype together in a couple of months. It took as a year. I burned a significant amount of my funds. I lost my relationship. I got back to live at my parents basement. I was doubting myself and was consumed by fear and disappointment. Then I started to code websites just to have some cashflow for the startup and to make a living. Got my live straight again. Now we are slowly getting out of the valley of death. But, it took much more than I initially thought. All the best to you and your team! Regards, Alex.
Hi Mitch!
The post has a contradictory feeling. On the one hand, it's kind of a waste of time to treat one failure as a total failure, but on the other hand, it's like, "Don't go where you don't know what you're doing. I could be wrong. It seems that a starter, on the contrary, needs to be partly adventurous, a person who listens to the council of creative opinion. Being able to create a team and work through an idea. And even if it doesn't go off, don't give it up, but improve it.
It's long to build a community and have a good SEO strategy. I would say start with a side project and take your time when the traction starts Go
You are right.
I see your point. I am one of those that decided to quit the job to pursue a bootstrapper career but many entrepreneurs in the WBE Space are taking it slow and building their projects on the side and some times I have to admit that I envy them for having stability. In the end I think that the grass is always greener in the other side...
Do you also agree that in the end, the amount of time you put into Startup, would as well be the kind of result you will get out of it?. That is, if you put in 90hrs a week, the result wouldn´t be the same as 40hrs a week?.
I think that building a startup requires a lot of mental energy. I am not working all the time but I am thinking about it 24/7. I felt that while working I could not do that...
Test your riskiest assumptions first...this is the takeaway and it applies to startups, businesses, founders, enterprises, etc.
The fail fast mantra, as intended by the author, has definitely been used and abused since he wrote the book. Testing your riskiest assumptions upfront lets you say, "If I'm wrong about XYZ, this won't work. How can I quickly learn if I'm wrong about this?"
I’ve been doing software side hustles over 25 years. In that time I’ve met hundreds doing the same thing and a large portion have quit their jobs to peruse it. For the ones who quit and were successful more than a couple years that number is definitely under 5%. The real life numbers on this might be a lot higher with greater number samples, but my experience is dont waste your savings. Take care of your family and work hard in your free time. Keep hustling, but don’t gamble unless you’re really young with no real responsibilities.
I like this post. Mitch expressed his opinion. I do not get why people started to argue with his view of work and life given his stage in life.
I am commenting here only because something related crossed my mind recently. I used to read startup theory pieces because I like a good theory, in general. But for me, even the most revered and famed theory is just a starter for critical thinking. Only I know my inner state: experience, skills, goals... Only I can tell if a given theory has any bearing on my unique situation.
One of the interesting trends I'm noticing in a lot of these comments is, oddly enough, an understanding of this post that seems to ignore even the title of the post itself.
I'm not telling you what to do, like @NorNorsu's odd commentary about me sounding like a teacher and whatnot. I'm asking that you let people launch their start-up how they want to, without shaming them into quitting their job or crashing and burning.
Further proof that a lot of this misunderstanding is coming from either not reading the full post or not really trying to hear it out is that I literally stated that I envy people with the courage to take that leap, and that you should do it if you want to.
I'm not knocking the decision, I'm literally stating that you should let people make the decision on their own without pressuring them into it.
Great thoughts.
I've not been on the site in a while, so I can't speak to what others are saying, but you make a good point.
It took me 2 years building Dabble in my spare time. I have 6 kids! But I did launch early.
When I launched, I did not have all the features I wanted, even those I thought would be necessary for launch, but I had a deadline which I imposed by dropping $12k to sponsor a big event (money I had saved up and if not recouped, I'd be ok, but still not money I would want wasted!).
I learned immediately that mobile support was the #1 feature request, something I could never have guessed before that. Who would want to write a novel on their phone?! Apparently, writers don't want to have to put away their books for silly things like social events or grocery store trips. Launching early helped me understand my customers better, and it gave me a greater passion and confidence in what I was doing!
2.5 years later I had a full salary. And the company just keeps growing! I'm so glad I did it.
I agree with your points, although the risk tolerance of people differ. So what works for A is different for B. And quitting a job is another risk level. And you can´t advice people against it or for it. Like you mentioned, you are married with kids, so this might be a wrong idea. But it could be a risk another is willing to take because She or he is single, has very moderate living cost, and high risk tolerance level etc. In the end, there is no general rule, because people have played the game from both sides and succeeded or failed. DO WHAT WORKS FOR YOU: A business is a reflection of It´s maker, not opinions.
The negative responses you're getting are evidence that you've exposed a legitimate issue. Keep up the good work.
Yeah didn't figure this would be the thing that people get irritated about, but I suppose that comes with the territory!
You have to add "Start small, think big, move fast". You obviuosly shouldn't fail fast at something that has broad negative implications on your life. But if you can fail at something without consequence, and you will gain important learning, then that is the fastest path to success!
IH has turned into Hacker News, look at all the haters in the comments. This used to be place that built each other up, rather than engaging in peevish criticism.
This is a brilliant, much needed perspective. Thank you for your insights.
The one time I didn't follow the general concept... which in this case... fail fast... I ended up in a startup for close to 3 years. Got significant equity that worth $0. From all sort of metrics (or common sense), that this is not going to work past 6 months...
So do fail fast and learn from it.
Also... the fail fast concept works in America better than most other countries. I have a book call "The Decision Book" and it outlines the differences between Americans vs Europeans (or most other countries). Specifically, Americans tend towards a trial-and-error approach: they do something, fail, learn from this, acquire theories and try again. Europeans (or most others) tend to begin by acquiring theories, then do something. If they then fail, they analyze, improve and repeat the attempt.