[pdimitar]

With the risk of getting roasted, here are my top three impressions of the article:

(1) The guy is very deep in the management / higher-level business bubble and is extremely disconnected from the day-to-day work that enables his lifestyle. He seeks to optimize things that are mostly managerial / consultant lingo and don't have much connection to things in the real world. That's not 100% true of course but it mostly strikes me as such.

(2) Instead of de-formalizing the process he seeks to find more and more micro ways to measure people. This can probably work long-term, maybe, but many people have tried and failed many times in the past and I think it's arrogant to not take that into account in your supposed solution.

(3) He is not accounting for humans, like at all. I knew programmers that worked quietly for 3 weeks and then showed us all a gem that made us go "wowwwwww". In traditional systems like Scrum and any agile-based nonsense this is severely frowned upon. Truth is however, people are different and as long as you are happy with the average ($result / $month) of somebody then you should leave them the hell alone to find and optimize their own way of being productive.

---

The above is overly simplified and I am well aware there is a lot of nuance. But I didn't want to write a book so I settled for a condensed and partially inaccurate summary.