>For this number to be relevant at all, it needs context - among the general population, how what percentage suffer from burnout? It doesn't have to have a per

>For this number to be relevant at all, it needs context - among the general population, how what percentage suffer from burnout? It doesn't have to have a perfectly described population context. If you had a metric that established 60% of all developers had issue X and 60% of the general population also had issue X, it doesn't minimize the significance of issue X. It's still an issue, in this case preventable, and it still effects a relatively large number of people, so let's focus on that. Context is certainly useful though because if the issue is more widespread (or found isolated with high correlation), it helps us better understand the cause of the issue vs looking at some subset of the population and trying to guess the cause to fix it. If it's the population at large, maybe Agile or knowledge work isn't the cause of burnout, maybe it's something else. But we should still identify the issue and try to fix it.