4 ms·
Former employees are often biased by their job function. At the first startup I worked at, I had a role that straddled Eng & QA, and the lesson I took away fro
by nostrademons 10y ago
Former employees are often biased by their job function. At the first startup I worked at, I had a role that straddled Eng & QA, and the lesson I took away from it was "engineering quality is critically important; we failed because there were too many bugs." In hindsight - having now seen v1 of many other startups - we failed because a lack of nerve, because many other startups charge thousands of dollars a month for product quality significantly worse than what we had. We should've shipped it, had money coming in, used that to negotiate another funding round, and then used the funding to fix the bugs. But without visibility into common sales & fundraising practices of startups, there was no way that 19-year-old-programmer-me could've known that.
- bluGill 10y agoMaybe, maybe not. If you have an all new product you need to get into the market fast. Once you have the basic features working you need to see if customers really exist. Even if it means your customers have to try everything twice because you crash the first time, if they buy your product you fix the bugs they see so that it mostly works and move on. However if you don't have a new product you cannot do that. If you want to release something where the market already exists you can just do one part better you need to be as good in everything else. Tesla didn't release their original roadster without a heater, in the 1950s heaters were optional. You need to figure out which market you are in and release accordingly. Getting this wrong means the death of your company. If you are in the first investors are taking a risk that people will want your product - it would be stupid to invest in perfection when customers might decide your product doesn't fill a need, better to abandon your interesting but useless product early. However when you are in the second you need to meet your user's expectations - thus I don't need to check the feature list to tell you Tesla comes with a working heater standard. Expectations is also why the early reviews of Tesla showed a tow pulling it away with a dead battery - the equivalent stupidity in a gas car would be the tow truck charging $10/gallon for gas and you are on your way in a few minutes. (Tesla has been mostly successful in managing expectations in the years since - now everyone knows it isn't the best car for cross country trips but you can do it once in a while with a little planning - there is a lesson in this too when you are a little different in an existing market make sure the downsides of your different are understood)
- crdoconnor 10y ago"Former employees are often biased by their job function." Aggregating their reviews would cancel this effect out though.
- nostrademons 10y agoIf you can. I thought the context of this thread was free-form postmortems, where people give a narrative explanation of why the startup failed. It's hard to aggregate that. Also, there's the risk of aggregate counts simply reflecting the population of each job function, unless you weight them. Then it'll just say that every engineering-focused startup failed for engineering reasons and every sales-focused startup failed for sales reasons, which may be true but isn't terribly helpful for a founder trying to figure out what to do.
- jstandard 10y agoIt's an interesting thought, almost like a "glassdoor.com" on startup failures. I'd be curious if Glassdoor actually implements some sort of a weighting scheme to counter the bias that unhappy people are more likely to post reviews, so a poorly run group would have an outsize impact. It's because of that case I think free-form postmortems might be more insightful, despite their own obvious faults. Perhaps NLP and sentiment analysis could shed some light.