4 ms·
> the McKinsey framework only measures effort or output, not outcomes and impact Measuring outcome and impact gets messy when the developers aren’t the ones de
by Aurornis 3y ago
> the McKinsey framework only measures effort or output, not outcomes and impact
Measuring outcome and impact gets messy when the developers aren’t the ones deciding what to work on.
I had a VP of Engineering who was all about measuring impact and ignoring everything else. He was also adamant that product people decided what we work on, while engineers decided how it was implemented.
This created an environment where your fate was determined almost entirely by what product team you got assigned to. If your product managers wanted you to implement a feature nobody wanted, it didn’t matter how well you did. You weren’t going to be able to show positive impact if nobody used it.
Impact is only a good measure when you let people make their own decisions.
- vinay_ys 3y agoUgh. A quintessential engineering mind is always curious, critiquing and questioning everything and will always want to know the why of the what and ask why not an alternate what. Such a mind be motivated by a higher purpose – finding meaning in larger impact of their work. Only such minds can be creative and persistent to solve the hardest problems to create outstanding product experiences. All it takes to destroy such a mindset is to tell them to shut-up, not to ask so many questions, and to do as they are told.