Every design leader I have watched fail has failed in the same way, and it was never on craft or taste. They failed because they believed the function they led was the point.
It isn't. Design exists to move the business. So does engineering, so does marketing, so does the function you happen to run. That sentence gets read as cynicism by people who have never had to defend a headcount, and as obvious by anyone who has. It is neither. It is the single most useful thing I know about doing this job, and almost nobody says it out loud to the people who most need to hear it.
I want to make the case properly, because the version of this argument you usually encounter is a bad one.
The bad version
The bad version says design should stop whining, learn to read a P&L, and do what it's told. That version produces order-takers. It produces teams that ship whatever the loudest stakeholder asked for, that never say no, and that get cut first in a downturn because they made themselves interchangeable with a contractor.
Subordinate does not mean servile. A cardiologist is subordinate to the patient's survival. That doesn't make them a technician. It makes them accountable to something other than their own preferences.
The leaders who insist design deserves a seat at the table almost never get one. The leaders who understand they are there to move the business get handed the table.
What accepting it actually buys you
When I joined Honor, we were building for two customers at once: the families who needed home care, and the Care Pros who delivered it (our term for the caregivers, and the naming was not incidental). Those are different products with different economics, and the temptation was to treat the caregiver-facing tools as a moral obligation, the right thing to do, funded out of goodwill.
That framing would have killed them in the first budget crunch. The argument that survived was economic: better tools meant Care Pros stayed, retention drove supply, supply drove the marketplace, and the marketplace was the company. Higher pay and better software weren't charity; they were the business model. Same work, same values, completely different durability, because it was tied to something the company could not cut without cutting itself.
At Lyft the transition was from a car-based rideshare app to something multimodal: bikes, scooters, transit, eventually autonomous. You can frame that as a design opportunity, and it is a gorgeous one. But the reason it got resourced is that a rider who uses three modes is worth more than a rider who uses one, and the company needed a defensible position in cities that were turning hostile to cars. The design work was better because it was pointed at that, not despite it.
At Grammarly, moving from a browser extension to native Mac and Windows applications looked like an interface project and was really a distribution question wearing an interface costume. Where does writing actually happen, and can we be there? Answering it required roughly seventy new people in under two years, which is a hiring problem, an onboarding problem, and a culture problem long before it is a design problem.
The test
Here is how you find out where you stand. Take the thing your team is proudest of this quarter and finish this sentence without using the words quality, craft, consistency, or experience:
We did this, which caused ______, which the company needed because ______.
If you can't complete it, that work is undefended. It may still be excellent. It may still be the right thing. But it is undefended, and undefended work is the first thing to go, not because your executives are philistines but because they are allocating finite money against claims that are defended.
Most design leaders I've interviewed cannot complete that sentence about their own best work. They can talk beautifully about process, but they struggle to name the mechanism.
Where the line actually is
So what do you refuse?
You refuse the thing that wins this quarter and costs you the next four. Dark patterns are the obvious case, but they're rare enough to be a distraction. The common case is duller: the shortcut that adds a permanent maintenance burden, the feature that serves the loudest customer and confuses the other thirty thousand, the reorg that looks efficient on a slide and severs the one relationship that was making delivery work.
Notice that all of those refusals are also business arguments, which I feel is the whole point. You are not invoking a separate authority called "design." You are saying: this trade is bad on the terms you already accept, and here is the mechanism. That argument can be won. "This isn't good design" cannot, because it asks your CFO to defer to a taste they do not share and cannot audit.
The hard cases are the ones where you're right and you lose anyway, and I'm not sure there is a technique for those. I have lost plenty. What I've learned is to lose in a way that leaves the argument standing: write it down, name the mechanism, date it. Half the time the company comes back to it in nine months. The other half you were wrong, and you have a record of how.
Why nobody says this to you
Because the conference-talk version is more flattering. There is a whole genre of design-leadership content built on the premise that the discipline is chronically undervalued and the fix is more advocacy. It sells well. It is also, in my experience, close to backwards. The undervaluing is real, but it is a symptom. The cause is that the function keeps making its case in a language the business does not price.
I don't think you should love this. I think you should notice that the people who internalized it early got more scope, protected more of their teams through cuts, and (this is the part that surprised me) shipped better work. Constraint that comes from a real mechanism is more generative than constraint that comes from someone's preference.
Subordinate to the business is the whole job, not a smaller one. The craft is what you do with it.
Where I took this too far
I have been arguing for this frame for years, so I should say where applying it made me worse at the job.
There was a stretch, somewhere in the middle of my time running larger organizations, when I could complete the mechanism sentence about everything and had stopped asking whether the work was any good. Every project had a defensible commercial story, every review ended with a metric, and the quality of the thing we were actually shipping had drifted somewhere I was no longer looking. Nobody flagged it, because the numbers were fine and I had trained the room to speak to me in numbers.
The people who noticed were the designers, and what they did was stop bringing me the work they cared about, on the correct reading that I would ask what it was for and they would not have an answer I would accept. That is a real cost and I did not see it for a couple of quarters.
What I would say to a younger version of me: the mechanism is how you defend the work, and it is a poor instrument for choosing it. Some of what a design organization should be doing has no commercial story available yet, and a leader who requires one at the point of commitment will systematically kill the early version of everything that later turns out to matter. The discipline is to hold both, which is harder than either, and to be explicit with your team about which mode a given conversation is in.
Subordinate to the business is still the whole job. It is a claim about accountability, and I spent a period treating it as a claim about taste.
I've led design and product at Honor, Lyft, Grammarly and Pitch, and today I build at Noord. The counter-argument I take most seriously: in companies with very short time horizons, "the business" is a bad proxy for anything worth building, and a leader who optimizes for it faithfully will build something worthless. I think that's a reason to choose your company carefully, not a reason to reject the frame. But it's the objection I'd raise if I were reading this.
© 2026 Renato Valdés-Olmos