[Hasu]

> I really don't understand how asking to see data and talk in facts, rather than opinions, is a bad thing? This take seems to be implying the "design process" is just a giant, strictly qualitative "appeal to authority" fallacy and anyone who doesn't "get it" is some kind of naive rube?

I don't think you're quite understanding the context when this happens and why it's a sign of a weak manager.

The team is discussing a new design. A disagreement comes up: what should the text on this button say? Both sides seem to have good arguments, but the manager doesn't know how to pick between them. What to do?

"Do we have any data on this? Maybe we should run an A/B test?"

But no A/B test is needed: this is text on a button that doesn't have a meaningful conversion rate, it's just about clarity. The data we gather will not be useful. The problem is the manager didn't want to be seen as picking sides or playing favorites, or just doesn't understand what's happening, so they moved their own responsibility to an "objective, external measurement" to avoid making a decision.

Generally, "data-driven" is a buzzword that means "we manipulate statistics to do what we wanted to do anyway".

[ajuc]

It's the old joke about tossing a coin so you can realize what you root for, just in real life.