Live data from Hacker News

Things about being a founder I wish I knew years ago

speakerdeck.com

1–10 of 34 posts

Re: Things about being a founder I wish I knew years ago

#4
post #2

Every single point is spot on from my own experience. Subsequently many of the points won't sit well with the techie crowd.

"Subsequently many of the points won't sit well with the techie crowd."

I'm not sure what you mean? Why wouldn't battle-tested well-worn advice work with the techie crowd? And who is the techie crowd? Programmers? Tech lovers?

I'm just confused by your comment.

Re: Things about being a founder I wish I knew years ago

#5
post #4
post #2

Every single point is spot on from my own experience. Subsequently many of the points won't sit well with the techie crowd.

"Subsequently many of the points won't sit well with the techie crowd." I'm not sure what you mean? Why wouldn't battle-tested well-worn advice work with the techie crowd? And who is the techie crowd? Programmers? Tech lovers? I'm just confused by your comment.

Probably w.r.t. handling market risk before tech risk and the general dangers of growing an MVP.

Re: Things about being a founder I wish I knew years ago

#6
Echoing what I have learned myself. If you are an entrepreneur and you haven't read "Nail It then Scale It", do so now. No, really. There are few books I solidly recommend, particularly for business, but this book is the one I have found most valuable time and time again. When you finish reading it, go back to these slides and see how many were addressed. Absolutely zero affiliation with the book or authors, just a big fan.

http://www.amazon.com/Nail-then-Scale-Entrepreneurs-Breakthr...

Re: Things about being a founder I wish I knew years ago

#8
The only thing I'd consider changing on this deck is point 6 about hiring and firing.

The point has validity, but I've seen more (and larger) problems caused by likable but not-quite-qualified employees than I have by unlikable but qualified employees. A good board of advisors and broad feedback can help spot this problem and offer appropriate prescriptions.

Re: Things about being a founder I wish I knew years ago

#9
Question: "So why didn't anyone tell me?"

Answer: "Because it wouldn't have mattered."

Before I made the plunge and decided to form a startup, I read everything I possibly could about the process... what to do, what not to do, etc. I knew all the mistakes first-time founders make, and I was pretty sure I'd be able to recognize the issues and avoid making any of the really big ones. I didn't expect to get it all right on the first try, but I was certain that I wouldn't get it all wrong.

Guess what? I still made pretty much every mistake in the book. Almost every single thing that I'd read about basically went out the window as soon as I began.

Why? Because once you and you alone own something and put it out to the world to be used, judged, loved, hated, it becomes a very emotional and very personal experience. And once emotion enters the picture, it's very hard to step outside of yourself and assess the situation logically and pragmatically.

When you work for a large company, it's very easy to distance yourself from the product you're building, because most of the time you are not the only one involved in building it. You shipped a buggy piece of crap? Yeah, it sucks, but it's management's fault because they set an unreasonable schedule. And that contractor that worked on that one part didn't know what the hell he was doing. My stuff worked great.

But now this product is your baby. And when someone tells you it's ugly, you're almost certainly not going to be able to take a good hard look, and say, "You know what? I can see where you're coming from."

This presentation is great. Every single point is true. But speaking from experience, having someone tell you about lessons learned isn't the same as actually learning those lessons yourself.

Re: Things about being a founder I wish I knew years ago

#10
post #4
post #2

Every single point is spot on from my own experience. Subsequently many of the points won't sit well with the techie crowd.

"Subsequently many of the points won't sit well with the techie crowd." I'm not sure what you mean? Why wouldn't battle-tested well-worn advice work with the techie crowd? And who is the techie crowd? Programmers? Tech lovers? I'm just confused by your comment.

This was the first thing I thought as well. Honestly all of them seemed fairly common sense and obvious. Didn't really disagree with any.
Post reply on HN