TechCrunch likes to stir the pot and create controversy, but I do get tired of them acting like they do no wrong. Maybe it's just me but I rarely see them mocking themselves. As mentioned in the comments by another entrepreneur: When I launched OtherInbox at TechCrunch50 in 2008, being “stealth” was a requirement for participation. We had to be launching something new that no one had heard about and secrecy was so im…
That's a sign of a maturing media outlet. Wouldn't it be bizarre if the New York Times never had differing opinion pieces? (Note: I'm not putting TC and the NYT in the same bucket, but this is a bad point to call them out on.)
Stealth Startups, Get Over Yourselves: Nobody Cares About Your Secrets
11–20 of 37 posts
Re: Stealth Startups, Get Over Yourselves: Nobody Cares About Your Secrets
#12Re: Stealth Startups, Get Over Yourselves: Nobody Cares About Your Secrets
#13I think this exception can be generalized to pure technology development, even without the patent legal requirement of non-disclosure. It applies if you are developing a new technology that already has a known market; or an entirely new technology (in which case you are more an inventor or scientist than an entrepreneur). So, Edison got his light-bulb working well enough; Birdseye discovered the freezing rate for fish that worked well enough.
Of course, most internet startups are not pure technology. They're mostly about market development, and at best, applying technology to that new market.
A final factor is that, even for pure technology, it helps if you can discuss it with someone. So it's good to have a team. This is one benefit of working in a big corp lab.
Re: Stealth Startups, Get Over Yourselves: Nobody Cares About Your Secrets
#14Re: Stealth Startups, Get Over Yourselves: Nobody Cares About Your Secrets
#15Make no mistake, even the biggest preachers of being open withheld information. I'd like to see a more nuanced discussion about what to share and what not to.
Re: Stealth Startups, Get Over Yourselves: Nobody Cares About Your Secrets
#16Re: Stealth Startups, Get Over Yourselves: Nobody Cares About Your Secrets
#17Re: Stealth Startups, Get Over Yourselves: Nobody Cares About Your Secrets
#18I have one. We launched Twttr in a stealth private beta for at least a few months. I think the period coincided with the period it took to get an official SMS short code. During the stealth period we were serving SMS traffic out of an SMS modem attached to an office laptop. We got the normal benefit of polishing the product that you'd get from a private beta. Plus we got to develop the product without any public scrutiny. But we were very conservative about who we let know about the project, basically close friends and family who didn't work for a major internet company.
I think the hardest part about changing your product strategy is going back on your promises (in our case we'd promised customers, investors, and employees that we were going to build a world-changing podcast product). I don't know if it would have been fatal, but it definitely would have been uncomfortable to be accused of abandoning our initial product before knowing we had a success (and contrary to some statements, there were a big chunk of internal users who knew we had something important from the first day we used it).
Re: Stealth Startups, Get Over Yourselves: Nobody Cares About Your Secrets
#19Saying that you're stealth is actually a great excuse to not have to spend half an hour yakking to people when you actually want to code.
Re: Stealth Startups, Get Over Yourselves: Nobody Cares About Your Secrets
#20The smartest guys give the illusion that they are very open. But that is only because they have so much to share, they can keep talking(without being boring) and yet not get to the stuff that can really hurt them. That has been my experience. Make no mistake, even the biggest preachers of being open withheld information. I'd like to see a more nuanced discussion about what to share and what not to.
1. The idea itself in the way you'd present it to the layman
2. The engineering problems you face in implementing the idea
3. The solution to said problems
You can come off as being "open" by disclosing only the first part. If another person overhears (1) in your discussion, in order to implement the idea they first need to figure out (2) what makes it hard before even (3) devoting resources to solving the problem. And how you approach (2) and (3) in addition to just (1) is what determines success (read: execution). Note that I am making an assumption that whatever you're working on requires actual engineering.
So for the example of Google,
1) A search engine that lets you find stuff
2) Relevance is really freakin' hard
3) PageRank
None of this of course applies to negotiations with VCs, where the rules turn on their head and you don't want to make yourselves look like you are effortlessly delivering solutions. And unless you're looking for a certain type of leverage, acknowledging the fact that negotiations exist to other people is probably a bad idea too.