This reminds me of Strengthsfinder[1], that came out of Gallup as the result of a lengthy study. Basically it said that loads of time and effort is wasted by m

This reminds me of Strengthsfinder[1], that came out of Gallup as the result of a lengthy study. Basically it said that loads of time and effort is wasted by managers trying to fix the flaws of individuals. The alternative, they argue, is focusing on building teams where the members bring complementary strengths to the table, and then working on how to make the most of an individual's strength in relation to the context of the group. Let's optimise the throughput of the team instead of maximizing the resource use of individuals. Just because you maximize the the amount of code written by each individual doesn't mean that you've optimized the throughput of the team: sometimes the opposite is true. They're orthogonal concerns, but they're treated as if the former magically creates there latter. [1]: http://strengths.gallup.com/110440/About-StrengthsFinder-20.aspx http://strengths.gallup.com/110440/About-StrengthsFinder-20....