You do not need a research lab. You need five users a week and the discipline to actually talk to them.
Where design teams go wrong
Design dysfunction almost always shows up the same way. The team is busy. Files are everywhere. Stakeholders cannot find the latest version. Decisions are made and unmade weekly. The work looks fine in isolation, but the product as a whole has lost coherence. This is rarely a talent problem. It is almost always a systems problem.
- No source of truth for design decisions.
- Critique that happens too late, when sunk cost is too high.
- Engineering not in the room when key decisions are being made.
What good looks like in practice
Strong design teams share a few habits. They write things down. They critique kindly but specifically. They version their work as deliberately as engineers version their code. They treat the design system not as a deliverable but as a living constraint that earns its keep daily.
- A weekly design review with a fixed agenda and time-box.
- Design tokens, not pixel values, as the unit of decision-making.
- Engineering partnership from week one, not handoff at week eight.
Restraint is not the absence of decisions. It is the result of a hundred of them, made in private.
The taste question
Taste is the unfair advantage. It cannot be bought, only built — through deliberate exposure, ruthless editing, and the courage to delete work you spent twenty hours on because it is not good enough. Teams that take this seriously compound. Teams that do not eventually look like everyone else.
Where this leaves us
If you have read this far, you probably already know whether this thinking maps to your situation or not. We are not interested in convincing you. We are interested in working with the small number of teams who arrive at conclusions like these on their own and then need a partner who can help them act.
If that is you — for design work or anything adjacent — come and talk to us. The first conversation is always on us, and it always goes somewhere useful.
Written by Sneha Iyer for the Lilizon Journal. Published 2025-12-05. Filed under Design.