I failed before I even completed the MVP
Hey everyone,
I was working on building a Shared Inbox application directed for customer service/sales/logistical purposes. I come from a JS background but I wanted to try to build this project in Laravel(PHP), which is absolutely awesome.
I wasted around three weeks searching for solutions to configure IMAP and SMTP in a way that worked best for my application, but I couldn't find the right set up and I figured that after this long, I would just set the product on the shelf for a while and develop my skills on a more intermediate product.
My take aways:
- Ensure core features are built and tested
- Build a user base to test and provide feedback
- Ask for help and feedback sooner
All in all, I wasted way too much time working on various parts of the product, instead of working on the core features. In the future, when I revive this product, I will flesh out the core product and test it with users to ensure features work flawlessly rather than work on 'nice to haves'
Back to the drawing board...
Honestly, this doesn't sound like a failure. It sounds like a very cheap lesson.
A lot of founders spend months building around technical challenges before validating whether users actually want the product. Realizing that after three weeks is far better than realizing it after six months.
Your takeaway about focusing on core features is spot on. The fastest path to validation is usually the shortest path between the problem and a working solution.
One thing I've seen repeatedly is that founders often overestimate what needs to be in an MVP. That's why foundersbar.com puts so much emphasis on MVP scoping and validation before development. The goal is to learn whether the idea works, not to solve every technical challenge on day one.
Back to the drawing board isn't always a setback. Sometimes it's where the best decisions get made.
As a developer, I'm sure there is a certain amount of pride or satisfaction that comes with creating your own solution on your own but sometimes you have to prioritize the business. Instead of giving up, why not try another approach? If you look at all the great product managers, makers, developers, ceo's, anyone in the business of building and selling technology, you'll find that they are super resourceful people who have mastered the art of solving ANY problem, not just problems they can personally code themselves. Their success isn't limited to their coding abilities.
Although I don't know exactly what you're trying to accomplish, I'm willing to bet that any strong senior level engineer would know how to find the solution you're looking for. It's just a matter of them wanting to help you or having an incentive to do so. Not always, but money usually works.
Starting points to find someone who will help you:
-stackexchange
-github
-builtwith.com to find companies using that technology in a similar way, then use linkedin to track down the employees or contractors or firm hired to build the system, then contact them and see if they will help you
-relevant instructors at coding schools/bootcamps
-developers of the technology
-product managers with blogs
-prolific bloggers who like to help people, which is probably most of them.
-either find someone who has the direct experience or find someone who is resourceful enough to help.
If you have a hard time finding help, it's your approach.
Don't give up!
Actually, this is not bad advice. I never really reached out to anyone. I can't afford to pay someone currently, two babies at home, but I will definitely reach out to see if I can gain some insight.
I find that since I have made it this far, I have truly become a better programmer and designer. I won't give up entirely on my project, I will just shift my approach and see if I can get some more eyes on it.
Thank you!
It's all about how you approach them. Most senior engineers are accomplished people who have their shit together professionally so if they feel something has a worthy cause, they have the time to spare.
Unless you have a beautiful single sister, you probably don't have much to offer them in terms of a barter for their time so I would recommend leveraging your current relationships to see if anyone you're close to can call in a favor for you. Linkedin works great for finding connections. You will owe your friend a favor and your friend will owe them a favor, which works among friends and usually gives people an excuse to catch up with an old friend you haven't talked to in awhile.
Try not to take it too seriously and don't put too much pressure on yourself, that only makes it harder. If nothing more, you'll up your soft skill game from the effort.
It doesn’t need to “work best” for your application.
For the first iteration, it really just needs to work!
If you really think this product has potential, and are out of ideas/less passionate for other projects, you should give it another go.
Thank you! I will try to learn about what I think is missing to see what I can do.
This comment was deleted 6 years ago
This comment was deleted 5 years ago
That is inspiring! I feel good about realizing I need to take a step back.