Every project plan has a neat little box called client feedback, three days. Every project then discovers that feedback takes three weeks, arrives from six people, and contradicts itself. The timeline did not fail. The feedback process was never designed.
A feedback round is a scheduled window in which the client reviews the work and returns one consolidated set of comments by an agreed date. Note the three load bearing words: scheduled, consolidated, agreed. Remove any one and the round becomes a drift.
Why does feedback always take longer than planned?
Because nobody planned for how decisions actually get made on the client side. The plan assumes one person opens the file and replies. Reality is a chain of forwards, hallway opinions, and a director who is travelling.
The fix is to plan for the reality, not the fantasy. Ask who needs to see it, how long they genuinely need, and when they are unavailable. Then put that in the plan. A feedback date the client helped set is a date they will defend. This is the same decision latency problem I wrote about in why good marketing teams still miss deadlines.
What is design by committee, and why does it fail?
Design by committee is what happens when everyone with an opinion gets an equal vote on the work. It fails because opinions are not expertise, and a design that pleases six people excites no one.
Committees do not produce bold work. They produce safe work with all the edges sanded off, usually late. The alternative is not dictatorship. It is clarity about whose judgement counts and what everyone else is being consulted for.
How do you get one clear voice from the client side?
You ask for it by name, in writing, before the project starts. One person collects every internal opinion, resolves the contradictions, and delivers a single set of comments. That person is the feedback owner.
This only works if the feedback owner has real authority. If they have to check everything upstairs, you have added a delay, not removed one. And the team needs to know that comments arriving outside the round, from outside the owner, do not count until the next round.
What should feedback actually say?
Feedback should describe the problem, not prescribe the solution. Saying a design feels too corporate for the audience is useful. Telling the designer which font to use is the client doing the designer's job badly.
Vague feedback is the other killer. Comments like make it pop cannot be acted on, so they generate a guessing round, which generates another round. Teach your clients the magic sentence: what is not working, for whom, and why. If the team is well briefed, good feedback writes itself. See how to brief a creative team.
What is a feedback contract?
A feedback contract is a short written agreement about how feedback will work: how many rounds, who gives it, in what form, and by when. It sounds formal. It saves friendships.
Two rounds is the honest standard for most projects: one for direction, one for refinement. More than three rounds means something earlier failed, usually the brief or the first round's discipline. Put the number in writing at the start and the conversation about round four becomes very short.
Working with Avy
Running feedback well is unglamorous and absolutely decisive. It is the difference between a project that ships and a project that circles. I set up the feedback contract in week one of every engagement, before anyone needs it.
If your timelines keep dying in review, the problem is rarely the work. It is the process around the work. Book a call and tell me about your last feedback round. I will tell you where it broke.
Need someone to get your project over the line?
Project delivery support for brand, digital, and creative teams that need clearer direction and smoother progress.