When an interior design collaboration goes wrong — and how to prevent it
Design projects rarely fail on the drawings. Five typical breaking points — decisions, communication, money, time, technical content — and how to avoid them.

Design projects rarely fail on the drawings. Far more often they fail on the collaboration: something was not said in time, something never made it onto paper, or two people used the same word for two different things.
This piece walks through five typical breaking points. Not to put you off, but because every one of them is preventable — and the prevention is nearly always the same: say things out loud before they turn into decisions.
Key takeaways
- The most common cause is not a bad design but an unstated expectation.
- There are five recurring breaking points: uncertain decisions, communication, money, time and technical content.
- The same thing guards against all of them: a written process, fixed decision points, and honest feedback in the uncomfortable moments too.
- If a project is already slipping, the fastest way forward is a re-planned schedule, not blame.
1. When we do not know what we want either
It is completely normal not to have a finished picture in your head at the start. The trouble comes not from that, but from leaving it unsaid — because then the designer believes you are confirming decisions while you are still looking for the direction.
In that case it is best to let the designer lead the concept stage: ask for two or three markedly different directions and choose between them. Reacting to finished proposals is far easier than describing what you want from nothing.
When the idea and the space do not match
Sometimes you hold on to a material or a colour that will not work in that particular space — too little daylight, the wrong orientation, or a finish that will not take the wear. The designer's job here is neither to give in nor to wave it away, but to explain why it does not work and to offer an alternative that produces the same feeling.
If the space cannot reach the intended result under the client's excessive control, it is better to say so early than to face it at the end.
2. The communication gap
The most common concrete cause. It works in both directions.
From the client: if you do not say that something is wrong, the designer reads it as approval. If the budget is never stated, every proposal may come with materials you cannot afford.
From the designer: failing to report decisions and progress leaves the client outside the process — and being left out turns into mistrust.
The answer is not more email but a transparent process: from the outset it should be clear how many stages the project has, where the decision points are, and what happens if a decision slips. Our piece on the design process sets out exactly that itinerary.
3. The money nobody mentioned in time
Budget tension almost always comes from the same place: the figure was never discussed at the start, or only in the broadest terms.
If the designer does not know the budget, they cannot propose realistic materials and furniture. If the client cannot see the fee structure, every extra invoice is a surprise. Both are avoided by putting the order of magnitude on the table at the first meeting — not to the last forint, but precisely enough for the proposals to be realistic.
4. Time, which runs out on both sides
Delay is rarely one-sided.
On the designer's side, the worst case is a commissioned project parked because a more attractive one came along. That is the quickest way to lose trust.
On the client's side, the mirror image is having no time for decisions: the designer waits for feedback and cannot move without it. Projects stall not from a lack of ideas but from a lack of decisions.
What helps: the schedule should carry named decision deadlines for both parties, and it should state what happens when one slips — not as a penalty, but so the consequence is predictable.
5. The technical content that does not come together on site
Every project has a moment when a material is unavailable, a dimension does not work out, or an idea fails in practice. That is not a fault; it is the nature of the work.
The question is what happens next. With detailed documentation, finding an alternative is a decision. Without it, somebody improvises on site — and improvisation rarely fits the concept.
That is what makes detailed documentation worth its cost: not for the paper, but because in unexpected situations it provides the reference point.
When disagreement turns personal
Creative work comes with disagreement — that in itself is healthy. It becomes a problem when the argument shifts onto the person. From that point it is no longer about the solution, and the project rarely ends well.
The shared goal is the handhold: the designer supports the client as a partner rather than performing a service against them. Keep that frame and most conflicts stay solvable.
A practical list for both sides
As a client:
- State the budget at the start, even if it feels awkward.
- If something is wrong, say so immediately — late feedback costs more.
- Leave time for decisions, and ask for calendar deadlines.
- If you are unsure, ask for comparable options rather than a single solution.
As a designer:
- Describe the process at the first meeting, not along the way.
- Keep the fee structure transparent and name additional work in advance.
- Do not take on more than you have capacity for.
- Deliver bad news on time — delayed bad news is twice the size.
If it is already slipping
When a project has stalled, the fastest route is not finding someone to blame but sitting down together and recording three things: where the work stands now, what is missing to move on, and by when each party commits to it. Most stalled projects can be restarted with an honest hour of conversation.
With us that itinerary is part of the process: fixed decision points, a written schedule, and consultation that remains available after the drawings are handed over. If you would like to see how that works in practice, take a look at our design service, or come to an informal consultation.
