The myth of collaboration
Modern design culture loves collaboration.
Stand-ups, co-design sessions, endless Figma comments, open feedback loops.
We say we want alignment.
What we often get is confusion.
Everyone has a voice. But no one has authority.
We’ve mistaken participation for progress.
We’ve built cultures where everyone contributes, but no one decides.
It sounds democratic.
It feels inclusive.
But it often leads to stalled decisions, diluted ideas, and frustrating cycles of rework.
In one startup I worked with, the design team would hold weekly “alignment” sessions. Dozens of sticky notes. Everyone contributing. But decisions? They lingered for weeks. By the time they shipped, no one even remembered the rationale.
Because the real problem isn’t that people aren’t working together.
It’s that no one knows who’s supposed to make the call.
The real design bottleneck
“The worst decision a team can make is none at all.” – Julie Zhuo
It’s not the tooling. It’s not the meetings. It’s not even the speed of iteration.
It’s unclear ownership.
If you’ve ever been in a project where everything feels “nearly done” for weeks, this is probably why.
Decisions are slow because no one wants to overstep.
Feedback becomes passive-aggressive alignment theatre.
And great work gets watered down by compromise.
You can’t scale design if no one knows who’s in charge.
And without clarity, you start seeing those symptoms:
- Repeated rework with no obvious cause
- Circular conversations that always return to square one
- Frustrated stakeholders wondering why the design “still doesn’t feel right”
What systems can’t fix
Design systems have helped us scale execution.
We’ve standardised components, tokens, patterns. We’ve improved consistency.
But no system can make a judgment call.
No token can resolve competing opinions.
No component library can replace leadership.
Most design chaos isn’t visual. It’s structural.
I’ve seen beautifully documented systems break down entirely the moment two leads disagreed about a component’s purpose. The documentation was there. The tokens were there. The governance? Missing.
You can build the cleanest system in the world, but without governance, without a clear understanding of who decides what, it will break under pressure.
We’ve focused so much on aligning pixels that we forgot to align people.
The missing layer: decision logic
“Design systems are only as useful as the conversations they enable.” – Dan Mall
Design needs a human layer.
Not just a style guide, but a structure for decisions.
This is where design systems often fall short.
They document what to do, but not how decisions get made when there’s ambiguity.
Because there will always be ambiguity.
The missing layer is decision logic.
It’s not another file or template. It’s a cultural layer.
It answers questions like:
- Who has authority in which situations?
- When does feedback become direction?
- What happens when we disagree?
- How do we make sure decisions are traceable and consistent?
It’s not about top-down control.
It’s about shared clarity.
Without it, even small projects can spiral.
Design systems need interpreters
Reality Check:
If everyone’s still giving feedback after six rounds, and no one’s confident to ship, your team doesn’t have a design problem. It has a governance problem.
Systems don’t interpret themselves.
Someone always has to decide: does this pattern fit here? Do we break it? Do we evolve it?
That decision needs context.
It needs creative direction.
It needs someone who understands the nuance behind the rules.
And if no one is empowered to interpret, the system becomes rigid.
Or worse, ignored.
I once worked with a team that had a beautiful design system, but only one person on the team actually felt confident applying it. The rest? They were afraid to touch it. It had become sacred. Inflexible. And totally unhelpful.
Design systems only work when they’re animated by people who know when to apply them, when to flex them, and when to push beyond them.
That’s not documentation. That’s leadership.
What healthy decision-making looks like
Visual idea: Imagine a pyramid. At the base, you have tokens and components — the ‘what’. Above that, patterns and templates — the ‘how’. But at the top? Decision logic — the ‘why’. That top layer is the most fragile and the most powerful.
It’s worth saying: sometimes, you don’t need stronger opinions. You need stronger signals.
The fastest way to cut through ambiguity isn’t always a decision-maker. It’s real feedback from real users.
User testing grounds the conversation. It removes the guesswork. It shifts the weight from personal preference to actual evidence.
And when done early and often, it helps teams avoid circular debates entirely.
But even user insight needs someone to act on it. Someone who connects the dots, decides what matters most, and makes the call. That’s where decision logic and testing meet.
- Clear roles and flexible authority
Everyone should know who has the final say on any given decision. But it should shift based on context, not just hierarchy. - A shared definition of success
If the team doesn’t agree on what good looks like, decisions become subjective. Define it early. - Feedback is welcome, but directional input is owned
Open critique doesn’t mean equal weight. Make space for voices, but be clear whose voice is making the call. - Transparent decision trails
Write down why a choice was made. So when it gets questioned three months later, the logic is clear. - Creative friction, not creative confusion
Disagreement is healthy. Ambiguity about who decides is not. - Empowered interpreters
Train your team not just on the system, but on how to think with it. Systems are only as smart as the people applying them.
Final thoughts
Great design doesn’t come from perfect alignment.
It comes from clear, informed decisions.
If your system is breaking, if your team feels stuck, if your work is always “nearly there” but never quite landing, maybe it’s not the design that’s the problem.
Maybe it’s that no one knows who’s in charge.
Fix that first.
The rest tends to follow.
