Counter-argument: an hypothetical manager simply won't (and very often can't) get involved to a point where they can fix this situation. Worker A: Pushed the f

Counter-argument: an hypothetical manager simply won't (and very often can't) get involved to a point where they can fix this situation. Worker A: Pushed the feature in 2 hours. Worker B: Pushed the feature in 4 hours says he read the documentation. This can be be a signal that Worker B is more mature/senior and takes the time to do it well, but it can also just be that Worker A is better (and also read the documentation), was familiar with framework X already or another reason that has nothing to do with "not reading documentation". In that context the optimal manager behaviour is to do nothing, if Worker A was doing lower quality work it might show up at some point or Worker B might get more accustomed to framework X and do the tasks in 2 hours too. Which is all to say, you can't as a manager have that level of insight without personally looking at the work output and being familiar with framework X, which I'd argue might be within reach of a team lead for a somewhat reasonably scoped product, but will rarely be the case in practice.