It sounds very attractive to developers, and I myself was a huge fan of this way of thinking for a long time. Sadly real life teams are never even close to this. And there are reasons for that, which we might like or not. But they have to be accepted. For instance most project leaders are not good developers nor good managers. And they don't really want to advertise that fact, because just like us they believe that anybody actually cares. So they get even worse by not tracking relevant metrics and instead focus (not by coincidence but by cunning) on metrics that are painful for developers, like current_open_bugs, or open_features_that_nobody_understands_and_that_where_discussed_with_nobody. They do that because it increases pressure on developers, hooks them with their desire to become better, and they provide automatic goals that can never be achieved. And these are the desired outcomes for the project leaders. Because if everybody is under time pressure, you don't need to worry that someone might steal your job, if everybody already feels bad about themselves they will not criticize you openly (and are motivated to work harder), and if there are always automatic goals you don't need to think about new goals all the time.

What is interesting to me is that nobody puts these people actively at the top of the projects. It's more like they grow to these positions naturally. But now that they are there, you can't really apply the logic from the presentation to convince them. Insted you might even give them the impression that they don't apply enough pressure yet because you are criticising their job.