Why do design projects go wrong?
Almost never because of bad design. Usually because of misaligned expectations about what 'the right result' looks like, how many revisions are included, who makes decisions, and what happens when something doesn't land. These are expectation problems, not design problems. They're almost entirely preventable if the right conversations happen before the project starts.
How do you handle a client who keeps asking for changes?
First: is it in scope? If revision rounds are clearly defined in the contract and you're within them, process the feedback. If you're outside the defined rounds, this is a scope conversation — not a quality conversation. Second: is the feedback about the work or about moving goalposts? Feedback that changes the brief is different from feedback that improves the execution. The distinction matters for how you respond.
What's the most important thing to agree on before starting a design project?
Who makes the final decision. Not who gives feedback — who approves. In every design project with more than one stakeholder, you need to know which one has final authority. Presenting to a committee that needs to 'take it back to the board' doubles or triples revision rounds. Get the decision-maker in the room at the first presentation.
A studio spent six weeks on a brand identity for a new client. The brief was agreed. The strategy was signed off. The first concepts were presented — and the client loved them.
Then the client showed them to her husband. Her husband preferred different colours. Then she showed them to a business advisor who thought the logo should be more modern. Then her accountant weighed in.
Four months later, the project was still in revision. The studio had exceeded their included rounds by eight. The relationship had deteriorated. The final logo was a compromise that no one was fully satisfied with.
None of this was a design problem. It was an expectation and process problem — specifically, the failure to establish decision-making authority before the project started.
The Three Conversations That Prevent Most Problems
Managing design expectations isn't a single conversation — it's three, at specific stages.
Conversation 1: Before the contract
This conversation establishes whether the project is right for both parties. It covers:
What the client actually needs versus what they think they need. A client who says "I need a logo" may actually need a complete brand identity system. A client who says "I need a rebrand" may need a positioning review before any visual work makes sense. Understanding what's really needed prevents delivering the wrong solution correctly.
Who's making decisions. Ask directly: "When we present work, who needs to be in the room to make the final decision?" If the answer is "I'll need to check with my business partner / board / spouse," establish whether that person can attend the presentation or whether there's a single point of decision-making authority.
What success looks like to them. Not aesthetically — commercially. "How will you know this project worked?" If the client can't answer this, they don't have a clear brief, and the project is likely to be evaluated on personal taste rather than strategic fit.
See the brand brief guide for how to structure the pre-project brief document.
Conversation 2: At project kickoff
Once the contract is signed, the kickoff conversation establishes the working relationship. It covers:
The process, phase by phase. Walk through exactly what happens, in what order, what you'll deliver at each stage, and what you need from them. Many clients have never worked with a design studio before — they don't know that strategy approval happens before visual work, or that concepts are presented for a directional decision rather than detailed critique.
Feedback quality. Tell clients what useful feedback looks like: "This doesn't work because..." is useful. "I don't like it" is not. "My wife prefers a different colour" is feedback you can't act on. "The colour feels too dark for the approachable positioning we agreed on" is feedback that connects to the brief.
The revision structure. How many rounds are included. What "a round" means (all consolidated feedback from one submission, not one piece of feedback at a time). What happens if additional rounds are needed. This is not a punitive discussion — it's a logistics discussion that protects both parties.
Timelines and response expectations. Your turnaround commitment. Their turnaround commitment. What happens if either side is delayed.
Conversation 3: At each presentation
Before presenting any work, re-state the brief that the work responds to. "We're presenting based on the positioning we agreed — premium professional services, targeting senior partners in law firms, with a visual register that signals authority without feeling traditional." This frames the presentation correctly and connects the work to strategic decisions already made.
After presenting, ask for structured feedback: "What's working? What's not working? What would you want to change and why?" Structure the feedback conversation rather than leaving it open — unstructured feedback produces emotional responses rather than actionable direction.
Handling the Subjective Response
The most common expectation management challenge: the client's response is "I just don't love it."
This response is real and valid — but it's not actionable in its current form. The job is to translate it into something you can work with.
Questions that help:
- "What specifically feels off about it?"
- "Is it the direction as a whole, or specific elements?"
- "Does it feel wrong for the brand, or wrong for you personally?"
- "What would you need to see differently to feel it's right?"
The distinction between "this doesn't fit the brief" and "this doesn't match my personal preference" is important. If the work correctly executes the agreed brief and the client doesn't like it, the conversation is about the brief. If the work misses the brief, the conversation is about the execution.
Clients who say "I know it fits what we agreed but I still don't love it" are telling you the brief was wrong. That's a different problem — and an earlier one — than a design failure.
Scope Creep: What It Is and How to Handle It
Scope creep in design projects usually takes one of two forms:
Additional deliverables. The project was scoped for a logo and colour system. Halfway through, the client asks for social media templates, a presentation deck, and a brand manifesto document. These are additional services, not revisions.
Shifting brief. The project started as "premium positioning for enterprise clients" and evolved into "approachable and friendly for SMEs" by round three. This isn't revision — it's a new brief.
In both cases, the response is the same: acknowledge the request, note that it's outside the agreed scope, and offer a path to address it — usually a scope amendment with additional timeline and cost.
Handle this matter-of-factly, not defensively. "That's a great addition — it falls outside the current scope, so let me put together a quick proposal for the extra work" is more effective than a long explanation of why you can't do more work for free.
When the Client Is Wrong (and How to Say It)
Sometimes clients make choices that are wrong for their brand. They prefer the colour that contradicts their positioning. They select the logo direction that the research indicates will confuse their target audience. They insist on a tagline that means nothing outside their internal organisation.
Staying silent is not professional support — it's avoidance.
The right approach: state your professional recommendation clearly, explain the reasoning, and give the client the opportunity to decide. "I want to be direct with you — this colour direction feels misaligned with the premium positioning we're working toward. It reads as approachable rather than authoritative, which we discussed was wrong for your target client. I recommend direction A. If you feel strongly about B, I want to understand why, because I'd like to make sure we're not creating a problem for you down the line."
This is not overriding the client's authority. It's giving them the benefit of your professional judgment, which is what they're paying for. Clients who hire designers and override every recommendation aren't getting value from the engagement — they're getting execution they could have done more cheaply elsewhere.
If the client proceeds with the choice against your recommendation, document it. "Following our call, I understand you've decided to proceed with [X] despite my recommendation to the contrary. I want to confirm this in writing so we're both clear about the decision."
What to Do When a Project Breaks Down
Sometimes, despite the best expectation management, a project goes wrong. The relationship has deteriorated, the client is unhappy, the work isn't landing.
Before the relationship breaks completely, a reset conversation is possible. This conversation acknowledges that something has gone wrong in the process, identifies where the breakdown occurred, and proposes a path forward.
"I want to step back from the work for a moment and talk about the project itself. It feels like we've got into a cycle where the work keeps not hitting the mark, and I don't think that's a design quality issue — I think we need to revisit the brief and make sure we're working toward the same goal."
This conversation is difficult. It's also almost always more effective than continuing to produce rounds of work that aren't resolving the underlying problem.
If the reset conversation doesn't work, and the project truly cannot be resolved, it's better for both parties to end the engagement professionally — with a clear exit arrangement — than to continue a relationship that produces poor work and a mutual reputation problem.
The Simple Rule
Most design expectation problems come from assuming alignment rather than confirming it. The more explicit you are, earlier in the project, about process, scope, decision-making, and what happens at each stage — the fewer surprises emerge later.
Surprises in design projects are almost always more expensive than the conversation that would have prevented them.
Looking for a Studio That Runs Smooth Projects?
We bring structure and clarity to every brand project — clear process, honest communication, and work that's designed to your brief from the start.
Two rounds per phase is the industry standard that balances thoroughness with efficiency. One concept presentation, one revision based on feedback, one final refinement. More than three rounds in any phase usually indicates a brief or communication problem rather than a design quality problem.
Yes, always. State the number of rounds per phase, define what a 'round' means (consolidated written feedback, not rolling changes), and specify the rate for additional rounds. This isn't adversarial — it's professional. Clients who respect boundaries produce better working relationships than clients who assume unlimited revision.
Connect your feedback to the brief, not to your aesthetic preference. 'This doesn't feel like it matches the premium positioning we discussed' is useful feedback. 'I don't like the blue' is not. If you don't know how to articulate what's wrong, try describing what you want the audience to feel when they see the work — that gives the designer something to work with.
Showing work in progress to too many people. Every additional opinion is an additional voice the designer has to reconcile. Decide who has input before the project starts and limit presentations to those stakeholders. An approved internal group of two or three is manageable. A rolling list of everyone who's interested is not.
Before accepting or rejecting final work, identify specifically what isn't meeting your expectations — and whether it's a brief issue or an execution issue. If the work was delivered to brief and you've used your revision rounds, the conversation is about whether the brief was right. If the work doesn't execute the brief correctly, that's a legitimate quality issue to raise directly.