TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Why Founders Fail: The Product CEO Paradox (2013)

173 pointsby ggonwebalmost 10 years ago

10 comments

mpdehaan2almost 10 years ago
&quot;A friend of mine led his company from nothing to over $1 billion in revenue &#x2F; This worked brilliantly up to about 500 employees.&quot;<p>I&#x27;m often confused by the apparent VC assumption with excessive growth and not building right-sized companies sometimes. Is this failure?<p>To me, this is a great time to say &quot;I&#x27;m making lots of money, my employees are making lots of money, and it&#x27;s ok to be at this size and there&#x27;s nothing wrong&quot;<p>It might have been a great time to stop at 100, or even 25, and you could have had a fantastic time, doing one thing supremely well, too.<p>There&#x27;s honor in that.<p>I think the pressure to grow to unicorn sizes inherrent in VC things could often result in weird business choices.<p>It&#x27;s important to remember the VC is motivated by the final selling price, and big companies sell more -- but that&#x27;s totally not failure.
评论 #10083286 未加载
评论 #10083292 未加载
评论 #10083287 未加载
评论 #10084149 未加载
评论 #10083470 未加载
评论 #10083315 未加载
hobsalmost 10 years ago
And hidden in the middle of the post is:<p>Be the integrator – When Larry Page took over as CEO of Google, he spent a huge amount of his time forcing every product group to get to a common user profile and sharing paradigm. Why? Because he had to. It would never have happened without the CEO making it happen. It was nobody else’s top priority.<p>This is a good example where a strong leader can push the entire company in (what I think even Google would now admit was) the wrong direction, and because they are so powerful, the core products can suffer.
评论 #10085733 未加载
marktangotangoalmost 10 years ago
Just left an example of this, founder built a product with a core cadre of about 5 developers, after a slow first 5 years, the market caught up, and then sales doubled every year for next 5 years ($100M plus in sales).<p>CEO was highly involved with the product, even led the dev team for several years. Unfortunately he was little more than an enthusiastic amateur when it came to technical matters, and had strong opinions on how to implement things. His team was not experienced, so didn&#x27;t recognize the hole they&#x27;d dug themselves. This led to a lava layered mess that failed to scale to the largest customers.<p>Enter investors, a rewrite, and plummeting sales. CEO was replaced with a sales guy. See ya, good luck with that!
评论 #10084158 未加载
评论 #10086618 未加载
ryandrakealmost 10 years ago
Great article. While it&#x27;s great to have a CEO who stays engaged with the product even as the company scales up, it&#x27;s awful when they continue to micro-manage it the way they did when the company was 10 people. You hired product managers (and perhaps product manager managers). So let them do their jobs and create great products!<p>When you&#x27;re running a 500+ person company, you&#x27;re not going to go into the code and start optimizing the graph traversal algorithm--you hired smart engineers to do this. You&#x27;re not going to fire up Illustrator and start drawing buttons--you have artists for this. You&#x27;re not going to write the company blog yourself, or fix the automated test systems yourself, or design the marketing materials yourself. So why do you feel the need to over-ride your product managers on product direction, feature set, user acquisition plans, retention strategy, etc? Doing so de-motivates the professionals you have whose job is to do these awesomely.
评论 #10083291 未加载
评论 #10083294 未加载
评论 #10083274 未加载
评论 #10083521 未加载
paulsutteralmost 10 years ago
It&#x27;s important to delegate, but the one thing you can&#x27;t delegate is strategy. The product founder needs to step back from the details but maintain direct involvement in the product aspects related to company strategy.
vonnikalmost 10 years ago
Elephant in the room question: who is Ben talking about?
femtoalmost 10 years ago
The &quot;The Product CEO Paradox&quot; is applicable to anyone who leads the development of a product in a growing company, not just the CEO, but the Chief Engineer or CTO as well. It addresses the question of how to continue to make a useful contribution once the pace of development gets too rapid for a single person to keep up with.
graycatalmost 10 years ago
It sounds like the <i>failings</i> of the product CEO can be fixed with just a good COO. E.g., the OP has:<p>&gt; Then somewhere along the line, employees start complaining that the CEO is paying too much attention to what the employees can do better without her and not enough attention to the rest of the company.<p>Sounds like the CEO needs a good COO for &quot;the rest of the company&quot;. Okay.<p>It does appear that VCs commonly miss this point. Maybe someone could guess why, with three guesses, where the first two don&#x27;t count.<p>For a 101 level lesson on deception, watch, say, <i>Star Wars III</i> -- that lesson is in the movie because audiences are prepared to believe that it is close enough to reality, and many in the audience have good reason to so believe. Deception, etc., go way back, at least to Shakespeare. Don&#x27;t fall for it.<p>In the OP, the recommended solution for the product CEO is to write down the <i>vision</i> or whatever for the product. Good.<p>But now we are on the way back to the most rigid version of <i>waterfall development</i> -- documents mostly in advance for each <i>level</i> of the work. I tend to believe that those documents, etc. are a good, maybe nearly essential, approach for the scenario in the OP, but that approach is the polar opposite of <i>lean</i> and <i>agile</i> development. For small projects, sure, lean and agile are okay -- knock out some code, see if like it, else change it, rinse and repeat. But for significant projects, I never liked lean or agile anyway!<p>But, let&#x27;s see: The product CEO is to communicate only via a carefully prepared, written document and does prepare one or more such documents.<p>So, now the VCs can think what that they couldn&#x27;t before? Three guesses, and the first two don&#x27;t count.<p>There is:<p>&gt; The CEO skill set is incredibly difficult to master,<p>Hmm ... So, how did Gates, Ellison, Page, Zuck do it? Did they have years of experience managing people, from a lemonade stand to the decorations for the homecoming dance to the college PBK awards dinner to a division in the US Army, to salesman, local sales manager, district sales manager, chief marketing officer? Nope -- none of those. What about guys in the <i>flyover states</i> who build businesses big enough to let them have, say, a 60 foot yacht? But, still we&#x27;re talking something &quot;incredibly difficult&quot;?<p>IMHO the whole OP is to make excuses for what VCs still very much like to do -- have the CEO their puppet on their strings and, then, pull the strings to get what they believe they want where firing the founding CEO is to be expected. Such firing by VCs used to be expected, and now we see that with A16Z it is again.<p>Besides, this stuff about how much A16Z likes product CEOs looks like just <i>misdirection</i> to keep from talking about what A16Z really cares about: A company with traction significantly large and growing rapidly in a huge market but where the founders need&#x2F;want cash and are still willing to sign a standard term sheet that has the founders suddenly go from owning 100% of the company to owning 0% and a four year vesting plan to get back some of the ownership while the BoD can fire them before their stock is vested and, really, makes the VCs&#x27; investments more valuable -- it&#x27;s the VC&#x27;s <i>fiduciary</i> responsibility to their limited partners.<p>What is a founder to believe about a VC? What&#x27;s in a blog post or what&#x27;s in a term sheet and the other documents, maybe two inches thick, worked out very carefully by bright, well paid lawyers?<p>Instead, (A) plan the project so that get to positive free cash flow early on, (B) grow just <i>organically</i>, that is, from retained earnings, and (C) plan the project so that have some good barriers to entry to keep out competition long enough for the growth.<p>Guys, it looks like A16Z just wants your work, ownership, and company and wants to get those by having you sign an onerous term sheet while they give you some excuses about why you should give up your power as CEO and, thus, really, all or a lot of the financial benefit of your work. They are after the founder&#x27;s money, guys.
评论 #10084186 未加载
salimmadjdalmost 10 years ago
OT: There is a bug in this blog that when I tried to share it on Facebook, it shows: &quot;&lt;a data-width=&quot;300&quot; data-height=&quot;200&quot; data-bop-link...&quot;
评论 #10083583 未加载
daniel-cussenalmost 10 years ago
Typo:<p>&quot;I thought founders were supposed to better?&quot;<p>You accidentally a word.