Lessons from a failed startup
Unless someone cares, don't waste your time

Thursday 16 June 2022 at 18:00 CEST

In failing to build a company, I have learned many things. Core to all of them is that a company is not a product. Ideas change, products change, people change. We “pivot”, rapidly, relentlessly, sometimes ruthlessly.

Managed well, change is a catalyst. Managed badly, it can be catastrophic.

In this series, I try to explain the various ways in which I failed to understand this, and how I would endeavour to do better next time. You may notice that the style of these posts is more instructive than usual. Remember that these are mostly addressed to my future self, and as such, I am telling myself what to do; you, my dear original thinker, can do whatever you want.


I write software, and I thoroughly enjoy it.

Despite reading a lot of books along the lines of The Lean Startup, I thought that in my role in my company, I’d mostly be writing software.

This was, in hindsight, quite foolish.

Until you grok your potential customers, you don’t need any software.

Go out and talk to people. Understand their woes. Figure out what keeps them late in the office. Ask them what happened to cause their latest catastrophe, and help them conduct a root-cause analysis to truly get to the point.

Be generous with your time.

And if you can’t get in the door, that’s one more reason why you don’t need to write any code yet.

I’m finding this hard to write. I don’t want to talk to people, I want to code!

But code is not the end, it’s the means.

More in the series

  1. Introduction
  2. Focus on the problem, not the solution
  3. If the company goals change, the company should probably change too
  4. "Do research" is not a corporate strategy
  5. Your corporate values transcend your product vision
  6. Trust your gut, understand your heart, and open your mind
  7. Go to therapy with your co-founders
  8. Explore the terrain first
  9. Unless someone cares, don't waste your time
  10. Code is a liability; ship without coding, if possible
  11. Do less, and do it better
  12. Agile methods are tools to try more ideas in less time
  13. Until you have traction, money is a trap
  14. If you don’t know how to do it, that’s your biggest problem
  15. Roles can be fluid, but they must be defined
  16. Camaraderie is helpful, but no substitute for working together

If you enjoyed this post, you can subscribe to this blog using Atom.

Maybe you have something to say. You can email me or toot at me. I love feedback. I also love gigantic compliments, so please send those too.

Please feel free to share this on any and all good social networks.

This article is licensed under the Creative Commons Attribution 4.0 International Public License (CC-BY-4.0).