Quantization of work is so weird to me in the context of software engineering.
Most of the work I do happens passively as I think about some problem. Much of this thinking occurs outside of the traditional 9-5 window.
"Amount of time spent presiding over a work PC" doesn't count as a useful metric in my book. I prefer to measure the quality of work via outcomes and customer feedback. Meetings are an unhappy exception to all of this, but they are a necessary evil. Eliminate unnecessary meetings with prejudice - They will come back like zombies if they were really that important to the business.
Contributions still need to be mapped to outcomes, but that has nothing inherently to do with a time dimension. Non-contributors and relative performance should still be quite obvious to management, even if you can't say exactly how much time was spent by each participant.
Most of the work I do happens passively as I think about some problem. Much of this thinking occurs outside of the traditional 9-5 window.
"Amount of time spent presiding over a work PC" doesn't count as a useful metric in my book. I prefer to measure the quality of work via outcomes and customer feedback. Meetings are an unhappy exception to all of this, but they are a necessary evil. Eliminate unnecessary meetings with prejudice - They will come back like zombies if they were really that important to the business.
Contributions still need to be mapped to outcomes, but that has nothing inherently to do with a time dimension. Non-contributors and relative performance should still be quite obvious to management, even if you can't say exactly how much time was spent by each participant.