Feedback fatigue is one of the most common reasons website design projects run late and over budget. It appears when a project keeps changing but stops improving: the important problems have been resolved, yet preferences, reversed decisions and fragmented comments continue to reopen the work.
Agencies can spot feedback fatigue early and prevent it with a clear structure: agree what counts as a round, collect feedback once and give every round a single purpose. This guide is for agencies and businesses that outsource website design in the UK and want each review to move the project forward.
What counts as a revision round?
A revision round is one consolidated set of feedback from everyone who has a say, submitted once and answered once.
Three emails from three people on Monday are not three rounds. They are one round that has not yet been consolidated. Agreeing on this definition at the start prevents many review problems before they begin.
Why a fourth round often stops helping
By the fourth round, the material problems have often been fixed. The remaining comments are more likely to reflect individual taste than a failure in the page's purpose or usability.
- Feedback shifts from ‘this stops people understanding’ to ‘I would like it a little different.’
- Reviewers compare the design with earlier versions instead of the agreed goal.
- Settled decisions are reopened.
- Tired reviewers provide vaguer, more hesitant comments.
Three signs of feedback fatigue
| Signal | What it looks like |
|---|---|
| Circling | Someone asks to restore an idea from an earlier version. |
| Shrinking | Comments become smaller but arrive more frequently. |
| Contradicting | New feedback reverses something requested or approved in an earlier round. |
Use the project's own feedback data
Open the feedback from a recent project and classify every comment as a problem, preference or reversal. This creates a simple evidence base from the agency's own clients rather than relying on an arbitrary industry rule.
| Round | Problems | Preferences | Reversals |
|---|---|---|---|
| 1 | |||
| 2 | |||
| 3 | |||
| 4 |
Watch which column grows. If preferences and reversals overtake genuine problems by round three, the review process is leaking time.
A practical three-round structure
Healthy review rounds become progressively narrower. Each one should answer a different question.
| Round | Focus | Question to answer |
|---|---|---|
| 1. Wide | Direction, structure and message | Is this saying the right thing to the right people? |
| 2. Narrow | Layout, copy and detail inside the agreed direction | Does each part do its job? |
| 3. Tiny | Polish, typos, spacing and sign-off | Is it ready to approve? |
A clean sign-off also improves the Figma handover because developers receive one approved version instead of several competing states. Feedback that belongs to a later round can go on a parking list, so it is not lost and does not derail the current decision.
Turn scattered comments into one useful round
- One collector: a single client-side owner gathers comments from every stakeholder.
- One place: use a shared document or Figma comments instead of forwarded emails and chat messages.
- One decision: when two stakeholders disagree, ask the client to choose rather than making the design team guess.
- Reasons, not fixes: ‘the pricing feels hidden’ is more useful than ‘make the pricing bigger.’
- One deadline: state when consolidated feedback is due and when the next version will arrive.
- One written reply: record what changed, what did not change and why.
To keep your launch date safe, we collect all feedback once per round. It saves your team from reviewing the same page three times.
Set expectations before the first mockup
Feedback fatigue is much easier to prevent than to repair. Put the process in the kickoff conversation and proposal before anyone sees the first mockup.
- We work in three rounds: wide, narrow and tiny.
- Please send your team's feedback once, in one place.
- If your team disagrees, we will ask you to choose so the design does not drift.
Framed constructively, these are not rules designed to protect the agency. They protect the client's launch date and keep decisions visible.
When a fourth round is completely reasonable
More rounds can be the right decision when the business facts have changed. A product change, new legal wording, updated brand guidelines or a genuinely new stakeholder requirement may justify a formal change request. The guide to stopping website scope creep explains how to assess that change without allowing it to enter the project invisibly.
A new feeling is different from a new fact. ‘I am not sure about it now’ should lead to a conversation about the page goal before it triggers another full design round.
Do unlimited revisions remove the need for structure?
No. Oncreation's plans include revisions while a plan is active, and the six-month plan includes unlimited rounds. Unlimited rounds change who carries the cost of additional iterations; they do not change whether those iterations improve the work.
An active plan still has a defined delivery window and one priority at a time. Clear, combined feedback achieves more inside that window, while scattered feedback uses the same time less effectively. Agencies can still set appropriate round limits with their own clients.
A quick feedback-fatigue check
- Has anyone asked to go back to an earlier version?
- Did feedback arrive from several people in several places on the same day?
- Are comments becoming smaller but more frequent?
- Does any feedback contradict something already approved?
- Does opening the client's feedback now create a sense of dread?
| Yes answers | Recommended response |
|---|---|
| 0–1 | The project is healthy. Keep the review rounds tidy. |
| 2–3 | Tighten the process, starting with one collector and one deadline. |
| 4–5 | Pause and reset the project around its goal, remaining obstacle and final decision-maker. |
A short reset call can use three questions: What is this page supposed to do? What is still stopping it? Who makes the final decision?
Questions agencies ask
How many revision rounds should a website proposal include?
Three rounds—wide, narrow and tiny—are a practical starting point. The appropriate number can change with project size, but the proposal should always define what counts as one round.
Should an agency charge for extra revision rounds?
Decide this before the project begins. New business facts can become a documented change request. Preference loops should begin with a conversation before more production time is authorised.
What if client feedback arrives in drips?
Use a defined collection window. Comments that arrive after the deadline wait for the next round. Dripped feedback is how one revision round quietly becomes six.
Is limiting revisions rude?
Not when the purpose is to protect the launch date and decision quality. Most clients value knowing how reviews and approvals will work.
What if the revision limit was never agreed?
Ideally, the round structure is written into the kickoff and proposal. If that opportunity has passed, pause for a reset conversation and agree the remaining decisions, approver and review process in writing.
What should a business agree before outsourcing website design?
Agree what counts as a revision round, who consolidates feedback, who approves the work and how the final files will be handed over. A dependable agency should confirm those points before the first mockup.
A useful round ends with a decision
The goal is not fewer rounds for the agency's convenience. The goal is a review process in which something is decided every time. When that happens, the website moves forward and the agency and client remain on the same side of the table.
Turn the guidance into a dependable delivery system.
Oncreation works behind agencies on website structure, custom UI, development, QA and launch—with the agency remaining in control of its client relationship.
