This article needs a part two. It does a good job of pointing out the misalignment between user needs and organization needs, but fails to address why this misalignment exists.
The flow diagram assumes the naïve situation that this is a just a matter of awareness, education, or people becoming somehow a "better" person.
Whilst I don't have all answers, it's a complex problem set, allow me to speculate.
When you look at the type of products discussed, say a mouse, they are low margin products. Ultra quick time to market, yearly iterations, and hardly ever built to have a long time span.
That's not us though. We're "Good Corp". We do it properly. The mouse comes with a basic driver, no app needed. We do build an optional app for the lights. It's a native app, built from scratch. Smooth and fast. We build this app for 2 or 3 operating systems, natively. And we respect standards, the app can also control lights of devices from other manufacturers. Our enormous test lab tests every possible combination across operating systems and competing mouses, and will keep doing this as these underlying systems are constantly updated. Finally, we build our mouse to last, from better materials, and also design for repairability.
Our good corp mouse costs 120$.
The evil corp mouse costs 50$. It has the exact same features, just a lot of cutting corners, but functionality is comparable.
Which mouse will customers buy? Will they recognize quality? More importantly, will they pay for it? Or will they just go for the cheapest and tolerate the annoyances, and buy another one 3 years from now?
I think you know the answer. When the market does not reward quality, quality will not be delivered. There will be no magical moment where developers turn "good", they cant do good, because good is expensive, and nobody buys it.