I’ve watched consensus break down the same way across organizations of different sizes. The CMO has pipeline numbers. The head of product has activation and retention numbers. Design has brand perception and user research. Everyone is doing real work, producing real output, and nobody is quite accountable for the same outcome. The brief arrives with good intentions and the work gets done, but the metric doesn’t move. And in the post-mortem, everyone technically contributed and nobody quite owns what went wrong.
Consensus feels inclusive, but it doesn’t scale.
The larger the team, the more consensus becomes a tax on speed, accountability, and decision quality. Ownership blurs. Standards soften. Nobody is quite accountable because everyone technically agreed.
When design decisions cascade through AI-generated components and agent-built features, a bad consensus decision scales instantly. A weak call at the top becomes a thousand downstream executions of that same weak call. I wrote about how fast that execution got in Clarity Before Agent Action. Scale is why the call has to have an owner.
Scale requires clear decision-makers. Input and debate matter, but decisions need owners. If everyone owns it, no one does.
From advocacy to ownership
For a long time, design leadership meant advocating or fighting for the user. In 2026 it means being the bulwark protecting quality. Good design leaders keep making the case in terms of adoption and churn, so that design, no matter who is doing it, isn’t asking for a seat at the table. Its presence is mandatory.
Designers protected the brand while the business measured whether the brand converts. Designers wasted energy defending the user while the metric that decides whether the product survives is churn. When design was its own function competing for budget and influence, it usually became decorative: present at the table, but not accountable to the same outcomes as the people sitting next to it.
The strongest design leaders I’ve seen aren’t the ones who won the most arguments. They’re the ones who stopped having them, because they started owning the numbers that made the arguments unnecessary. That framing puts you in conversations about taste, results, and therefore strategy.
At Omny there is no room for advocacy. The outcome of a decision that changes the product, good or bad, belongs to design leadership. If an operator ignores an alert because the interface buried the critical signal in noise, that isn’t a UX problem. That’s a design accountability failure. Advocacy implies you’re trying to convince someone else to care. Ownership means the result is yours whether they understood you or implemented without question. When design leaders act like advocates instead of decision makers, they signal that design is optional. Your influence grows when your responsibility is unmistakable.
Process won’t save you
We had rigorous process at Omny when we shipped that initial workflow for a specific set of customers that other companies immediately wanted to change. We had design reviews, engineering QA, and stakeholder walkthroughs. We followed the book. Customers still abandoned the feature in five days.
Process didn’t save us. Going back to the operators and asking the harder question did. What decision did they actually need to make in the next 30 seconds? That question changed everything about the design, and it had nothing to do with process maturity.
The designers who never struggle to justify their salaries aren’t the ones with the most rigorous process. They’re the ones who diagnose the business problem before opening Figma or Cursor. They push back when the brief is solving for the wrong thing. That judgment, knowing when to challenge the direction rather than only execute it, is what separates designers who grow into leadership from designers who perfect their craft and wonder why they’re still waiting to be heard.
Maturity shows up in what teams ship, what they refuse to ship, and how they behave when trade-offs get real. Everything else is supporting obsolete organizational structures and a dying design process. I’ve seen immaculate processes produce timid work, and I’ve seen scrappy teams make brave calls under pressure.
Also in March: Design Leadership Has Evolved · Clarity Before Agent Action · Where the Capability Lives
Daniel Arevalo is Product Experience Lead at Omny Security. He builds AI-native tools and writes about design, product leadership, and what it means to direct systems that execute at a speed humans never had before.