I think the core of the problem is about developing good metrics for evaluating your performance that are less vague than “satisfaction of all stakeholders”.
When you are a computer programmer you can make predictions about:
Whether your code will pass your tests
Whether there will be a request to change something about your code when it’s peer-reviewed
Whether your code will break the built
Whether after your code gets live, some business relevant metric will change.
There’s the old Drucker maxim of “What’s measured gets improved.” If you do a bigger project than it’s useful to make metrics together with other stakeholders that measure whether the product is successful.
When it comes to social interaction, I sometimes make predictions whether a person will hang out with me when I request that we meet. I could do the same for other request where I want another person to do something.
I think the core of the problem is about developing good metrics for evaluating your performance that are less vague than “satisfaction of all stakeholders”.
When you are a computer programmer you can make predictions about:
Whether your code will pass your tests
Whether there will be a request to change something about your code when it’s peer-reviewed
Whether your code will break the built
Whether after your code gets live, some business relevant metric will change.
There’s the old Drucker maxim of “What’s measured gets improved.” If you do a bigger project than it’s useful to make metrics together with other stakeholders that measure whether the product is successful.
When it comes to social interaction, I sometimes make predictions whether a person will hang out with me when I request that we meet. I could do the same for other request where I want another person to do something.