Loading...
Answers
MenuDoes tolerance for failure in startups lead to dilemmas or is it indicative for sound entrepreneurial risk-taking?
This question has no further details.
Answers
Failure is a wrong concept, best to think about attempts as stamina builders that narrow the possibility of failure


I have two successful tech IPOs and counsel CEOs on topics just like this. Here's my answer:
It depends on what they are failing at. If they fail at a project (substitute "company" if that makes more sense to you) that has a very high chance of success, then that's a red flag. But, if they fail at a project with a low chance of success -but, they embarked on it because if it was successful the rewards would be big - then no big deal.
I know it's difficult to calculate but you should always try to do an analysis like this:
Project A: 30% chance of success but $10 million return if successful yields an expected value of $3 million.
Project B: 80% chance of success but $3 million return if successful yields an expected value of $2.4 million.
The other half of the answer is, how did they fail? Did they fail because of outside factors that they didn't recognize or plan for? Did they fail because of lousy execution? Did they fail because they hired the wrong people? DId they fail because they misjudged the market?
Lastly, optimism bias has us believe we are better than we are and that we control our own destinies. WRONG. Outside forces play a much bigger role than we think. We've all taken on assignments that we thought we could knock out in a day or two but actually took a week.
The other thing about optimism bias is that we hold on too long and won't admit defeat. We all know people who fail to kill a project and throw good money after bad. When we think we're going to lose then we tend to do risky things. (There is a reason the betting on long-shots goes way up at the race track as the night goes on - people are willing to take on more risk in an attempt to avoid losing.)
Related Questions
-
What are the key accomplishments for the first year of a startup?
A generalized question can only get a generalized answer. The most significant accomplishment is validating that the product you have built is a fit with your target market. This is demonstrated primarily by engagement (the people who sign-up or who previously visited, continue to return) and secondarily by growth, ideally based on word-of-mouth or viral growth but effectively converting paid traffic is a great second prize. Other significant accomplishments include: Not running out of money Recruiting and retaining great talent who believe in the founders' vision. Your loved ones not thinking you're as crazy as they thought you were a year ago. I'm happy to talk to you in a call to give you more specifics about what you want to set as your goals more specific to your startup.
-
Is it advisable to outsource to an agency to create our MVP? Are my security concerns unfounded?
It's not unusual at all. If you do outsource, try and make sure you have a project lead that you can trust. Once revenues get up to a certain point they might want to see the project through and come on board full time OR they will have enough pride in their work to make sure a proper transition takes place. As far as security, make sure you have an airtight non-disclosure/non-compete agreement with a penalty clause that includes financial remuneration.
-
How can I smoothly transition from full time worker to self-employment?
The ways I've done this in the past are 1) Find some customers that are willing to hire you (or your product) but know that you'll only be free nights & weekends to support/work with them. 2) Find a "partner" (co-founder or other) that's got a flexible schedule that can help build the business while you're at work. 3) Block out nights, mornings and weekends to build the business till you have enough orders to cover 50% of your salary. This might mean 7pm-11pm most nights, and 4 hours each day Sat & Sun. Make progress (sales $$$) and momentum. All that being said, it's risk reward. Sounds like you want to avoid taken the risk, and I get that .. but the upside is always smaller. Unless you put yourself in a position to have to succeed (ex: quitting your job) then you may never make the scary decisions that are required to build a company (like cold calling, going in debt, making a presentation, etc). I'm on company #5 with many other side projects started nights & weekends .. so I get it - but don't be afraid to bet on yourself and go all in.
-
What are ways to find and engage B2B beta users for a brand new application?
Find apps that are B2B and go to the review sections. Specifically going to Google's play or Chrome store and look at reviews and follow them to Google+ to engage. I took that same angle for B2C app I was building last year. Check it out. http://blendah.com/post/37331434653/lean-startup-hack
-
What are some important milestones for a bootstrapped startup?
If you haven't fully tested your app with the 100 individual accounts Apple allows you to test via TestFlight or Hockey, then I'd suggest you should test thoroughly with your email list before launching to the app store. Things to look for at this early-stage: Activation and Breakage Points: From app download to user onboarding, where are people getting lost? Your goal is not only to have them download the app, but complete whatever steps for them to become your user. Optimizing the flow to ensure maximum conversion is a key first step. Engagement: How often are they completing the tasks you deem most important based on your business model? How can you increase this number? User Understanding: How clear is the app's UI and messaging? Where are they getting lost? Virality: While true virality is hard to measure at this stage (given the constraints of pre-launch testing), you can evaluate the potential effectiveness of any distribution tactics you might employ (contacts, OAuth's etc) in terms of user opt-in and conversion issues. Real analytical data is easier to interpret than user interviews but there is a such a treasure trove of good customer development intel from customer interviews. Those first 100 people who download the app should be personally interviewed about their experience, what they like, how much it solves their problem, how much of a problem that is for them in the first place and so on. Before you go live in the app store, I highly recommend you max out your installs in a private testing environment. I'm happy to talk this through with you in more detail in a call.