For the people who own the trade-offs.
Summary: Design cost is not set by the design team. It is set by the conditions around it. A small number of operating disciplines hold that cost at its floor, and every deviation from them returns later as a surcharge that product and leadership pay without always seeing where it came from. This is about what those disciplines are, and why the cheapest version of design is the disciplined one.
At some point in almost every project, someone in a leadership position looks at the design timeline and asks a version of the same question: why does this take so long, and can we compress it?
It is a fair question. Design time is visible. It sits on the plan, it has a start and an end, and it looks like something you can negotiate. But that question hides a more important one that nobody asks out loud: what does it cost when design is not done properly?
Because that cost is real, it is often far larger than the design time itself, and it almost never appears on the line where leaders are looking.
Here is the part worth holding onto before the rest: the price of design is not fixed, and it is not set by the design team. It is a variable, and you control it. A small number of operating disciplines hold that price at its floor. Every time an organization deviates from them, it pays more. Not less design, not faster delivery. More cost, arriving later, charged to a different name.
When UX maturity in a company is low, that surcharge does not show up in one place. It scatters. You see quality issues, badly solved problems, badly defined problems, missed requirements, rework. Most of it surfaces somewhere inside the product development lifecycle, far from where it was created. You can hire the best designer on the market, but if you drop them into an environment where their hands are tied, the environment wins. Soft skills move the ceiling. They do not remove it. The ceiling is set by the system, not the person.
So this is not about why designers struggle to be visible. It is for the other side of the table, for product and leadership, and it is about something more useful: the disciplines that keep design cheap, and the exact cost of breaking each one.
Discipline I. – Someone owns the question
A good designer asks questions early. In the best case, relevant ones, the kind whose answers are not optional, because without them the work cannot move in the right direction. This is not friction. This is the work. Problem before solution, always.
The trouble starts with ownership. The larger the development team, the harder it becomes to identify who is actually responsible for answering a given question. And while that question sits unanswered, one of two things happens.
In the better case, design stops and waits. That looks like delay, and delay is expensive, but at least nothing wrong is being built. The money is burning, but not on the wrong thing.
In the worse case, the work moves forward anyway. There are designers who keep going without the answer, and product people who actively push them to. The decision gets made implicitly, by default, by whoever is moving fastest. This almost always ends in the same place: refinement. Rework. The cost of building on an assumption that turned out to be wrong, paid later, with interest.
So the first surcharge is not slow designers. It is unowned decisions. The bill is written the moment a critical question is left without an owner.
Discipline II. – Estimation is a risk decision, not a negotiation
A deadline is a framework. It is a real constraint, and good design estimation respects it. But respecting a constraint is not the same as letting product decide how long design takes.
Strong estimation starts from the timeline, then offers options inside it. Usually three. And here is the part that gets misunderstood: those three are not three versions of the same thing. Each one carries a different deadline, a different level of quality, and a different level of risk. The decision in front of the leader is not “which option is best.” It is “which risk am I willing to carry.”
This is where a quiet misunderstanding sits between design and the people approving the work. There is no such thing as two or three optimal solutions. If a leader expects three proposals on the same framework, with the same deadline and the same level of risk, they are not asking for options. They are asking to make an emotional decision and have it look like a strategic one.
Three proposals can be valid, but only when each serves a genuinely different purpose. This maps cleanly to Cynefin: the right response depends on whether the problem is complicated, complex, or chaotic, and those are not interchangeable. Three real options map to three different readings of the problem. Three pretty options map to nothing but preference.
It is also one of the cleaner ways to read a designer’s actual skill. A designer who arrives with three high-fidelity versions, without having challenged the business first, is telling you something about the thinking behind the work, or the absence of it. The surcharge here is subtle: you pay it in decisions made on taste instead of risk, and you keep paying it every time taste turns out to be wrong.
Discipline III. – Design is involved early
Late-stage involvement is still common, and for the business it is often the single most expensive pattern, especially when quality matters for the product.
What makes it dangerous is that leaders rarely see the cause. They are not in the room when design gets pulled in too late, after the direction is already set and the constraints are already locked. What reaches them is the symptom: the project is slipping. And in the worse version of that sentence, the project is slipping because of design.
That is how the surcharge gets misattributed. The cost was created upstream, when design was brought in after the decisions design should have helped shape. But it gets charged downstream, to the most visible name on the timeline. The damage is real, the blame is real, and both are pointed at the wrong cause.
Discipline IV. – The requirements exist before the work does
This one is quieter than the others, and one of the most expensive gaps a product organization can carry.
Functional requirements rarely get the attention they deserve. The pattern holds the way it holds everywhere: the stronger the people, the more documentation works as a framework rather than a rigid guideline. But that only holds with genuinely strong professionals in their field. Without that foundation, missing requirements become a recurring tax, paid in confusion, in misalignment, in things built twice.
And when design ends up writing the functional requirements that should already exist, which in low-maturity environments it often does, that is not generosity. It is the organization paying a senior rate to patch an upstream gap. The cost is not removed. It is moved, and made harder to see.
Why a senior hire does not lower the price on its own
The instinct, when design keeps generating this kind of cost, is to fix it with a hire. Bring in someone more senior who will finally make design work. Sometimes that helps. Often it does not, and the reason is the same reason the cost existed in the first place.
Influence and conditions do not arrive together automatically. In a more mature organization, a strong leader inherits clear ownership, sensible involvement, and a shared understanding of how design fits the wider lifecycle. In a less mature one, that same person inherits the questions without the authority to get them answered, the estimation conversations without the trust to hold the line, and the late involvement without the standing to change it. Maturity is a transformation, not a jump. You cannot shortcut it with a single name on an org chart.
This is why the cost is structural. A senior hire can raise the ceiling. They cannot, alone, rebuild the room.
Where this leaves the cost conversation
Put the four disciplines together and the logic is simple. Someone owns the question. Estimation is treated as a risk decision. Design is involved early. The requirements exist before the work does. Hold those, and design sits at its floor price: paid early, deliberately, in full view. Break any of them, and the cost does not disappear. It compounds, arrives late, and shows up disguised as something else. A stalled sprint. A refinement cycle. A slipped deadline. A blamed designer.
This is why what looks like a design problem is usually a system problem. The most expensive thing in a low-maturity environment is not the design work. It is everything the organization pays to compensate for not being ready for it.
So the real question was never how much design costs. The cost is coming either way. What leadership actually controls is how high it climbs, and that is a decision, made deliberately or made by default.
Design always sends a bill. The disciplined organization keeps it at the floor. Everyone else pays the surcharge, and rarely sees the line item.
More articles on Medium: https://medium.com/@attila.ando.aa
More articles on Linkedin: https://www.linkedin.com/in/attilaando/
