Product failures are a good thing if you learn from them

I became a developer with no reason at all. When I was young my dreams were different, but when the school decided to not open up the courses for what I was interested in, I had to make a choice.

The IT Field seemed to have the most chances of employment and so, here I am, with over 15 years of experience on a topic that wasn’t my first choice and in which, at least to what I know, I excelled in many things and competences.

We all dream of a job that’s a job we love as much as we dream to be in love with the perfect soulmate.
Thing is, you can find beauty, happiness and rewards in things that were not on your radar.

We mistake the joy for the job with the joy of what our accomplishments can give us, how rewarding they can get.

It’s not the job that makes it fulfilling. It’s the work, it’s the people, the achievements, the results, the parties and the failures.

And failures can be a powerful thing.
Today I read of the rise and fall of Flow, an old asan competitor. It struck a cord with me, it resonated so strongly because, as a dev, product manager of my company, creator of a product, and also business owners, that story is my story.

I see many facets of what’s in the life of a product. The hope to find a niche to which you can connect, the idea that you can do better than the giants.

But a failure should give us the opportunity to ask ourselves “What did I miss?” What didn’t we see? What part of the idea wasn’t working?

Developing a product requires you to be in the midst between optimism and pessimism.
You need to be able to dream big, to have a vision, to imagine a new path and future and at the same time you need to be able to foresee the obstacles, the problems, the things that don’t go well, the many ways in which everything can and will go wrong.

If you are too much on any of those side and you’ll either ignore the warnings or be paralyzed.

%d bloggers like this: