7 ms·
In my experience, it's way too easy for engineers to geek out on the how without addressing the "why". I'm guilty of this myself, from time to time. When produ
by SkyPuncher 4y ago
In my experience, it's way too easy for engineers to geek out on the how without addressing the "why". I'm guilty of this myself, from time to time.
When product is leading the charge, it often means they've validated a need from a customer and are ready to address it. When engineering leads, they're often pushing a capability without having evaluated it against customer needs.
- kopos 4y agoOn the contrary, I've seen product teams assume the pain of the consumer and relay the same to engineering; and then engineers having to push back on the insane requirements. Nevertheless, product which work in an agile model without collaborating with tech is doomed to fail