OK, product vision is paramount — but a lack of it is no excuse for mediocrity!
If you’re not happy, leave. But don’t be a sloppy engineer!
If you’re not happy, leave. But don’t be a sloppy engineer!
The other day I was discussing with Sébastien Le Gall. We were arguing about whether Product Vision is that essential. Is it possible that people are simply missing the point, and that having an awesome Product Vision never happen in practice?
In that case, the question would become: as engineers, how do we work around an imperfect Product Vision?
How do we make tech so awesome that it actually supports business?
In other words: should we just stop whining and roll our sleeves up instead?
I must say that I was intrigued but these words of wisdom.
I mean, I’m still believing that having an awesome, supporting and helpful Product Vision is possible and that we should towards having one. I’m also proud to say that I have experienced what such a team can be — we even spoke about it at two major Agile events.
Yet I agree that it’s a rare occurrence, and more importantly I agree that a lack of Product Vision is no scapegoat.
A weak Product Vision is in no way a mandate for sloppy engineering.
Agile or broken?
Indeed, modern engineering practices allow for a fantastic amount of flexibility.
The frontier is thin between an Agile business that constantly adapts to the market and a broken organization that behaves as if it had no head. The devil is in the detail.
Whatever your situation, always do great work. Don’t let you fool by a questionable environment. Be awesome, always.
Just quit if awesome is not an option.
Liked this article? Show it!
Please clap 👏 and share the article! It is because of you that I put my heart and soul into writing.
And follow me on my blog to be notified when I publish new articles!
Thank you so much!