4 ms·
My first thought was, "Hmmm...so this guy had several co-founders, and all of them left in disgust. What's the common variable?" Sounds like OP has some perso
by SwellJoe 18y ago
My first thought was, "Hmmm...so this guy had several co-founders, and all of them left in disgust. What's the common variable?"
Sounds like OP has some personality issues that need to be worked out. And, I got a distinct "mad with power" vibe, as well. Early stage company founders do not need a boss. If they do, they're already doomed to failure. It sounds like this fellow just likes the idea of being chief of something, and isn't all that good at it. Many nerds have started companies without management chops or a good personality, but they made up for it by producing code that solved a problem. I'm getting the distinct impression the OP (who may or may not be strong on the code front) is definitely weak on the management and personality front, but wanted to spend all of this time managing and "networking".
I don't claim to be an expert on this stuff, but I am a nerd, and I do produce (when it's my place to do so, though in my current startup, I produce far less code than my co-founder), and I think I would have ditched this startup, too. Nerds, in general, aren't good at being bossed around, and the kind that start companies definitely aren't good at being bossed around.
But, I agree with you. The guy probably does actually have a good company in him (because dedication and a healthy appetite for risk are the primary requirements...everything else pales in comparison). He just needs to keep assessing how he can do things better next time, particularly when it comes to interacting with co-founders.
- webwright 18y agoSecond the "mad with power" vibe. Wow-- I think the OP failed to learn a few lessons. The biggie is the seeming lack of empathy for his partners and his apparent belief that he's in charge. At this level, it's a partnership. As a CEO, it's not your job to lead and have your partners follow. It isn't your job to make unilateral decisions on how you spend your time (networking versus coding). With a small team, you can be a cheerleader, a tiebreaker, and a buck-stops-hear guy... But for the most part-- it's a damn partnership. And it's pretty clear to me that the poster didn't treat it like one, which is a shame. I think he's very right about the team needing to have the same level of commitment... His deeper commitment is probably why he felt entitled to "lead", even when PG suggested that that might be the problem.
- orianmarx 18y agoThe first one left with no ill will. We are still friends. It's the rest of us that left in disgust :-)