How To Work With A Web Designer Without Endless Revisions

“It is not quite what we had in mind” is difficult feedback to act on, especially near the end of a website project.

A better working relationship starts earlier. Your designer needs to understand the business decisions behind the website, and you need to understand what you are being asked to approve.

You do not need to arrive with every answer. The aim is to make the important questions visible before they become expensive changes.

Bring The Business Context

Explain who the website is for and what you want those people to do. Share the questions customers ask, where the current website causes confusion and what your team struggles to update.

Bring examples rather than only adjectives. “Customers cannot tell which service includes installation” gives a designer more to work with than “We need a premium feel”.

Useful starting material includes:

• Your main audiences and services.
• Existing brochures, product information and brand guidance.
• Common sales and support questions.
• Pages or functions that must be retained.
• Known deadlines and who needs to approve the work.

Be open about gaps. If photography or copy still needs to be produced, that belongs in the plan.

Agree On The Problem Before The Appearance

The Design Council’s Double Diamond separates understanding and defining a problem from developing and testing solutions.

For a website project, that means checking the purpose and structure before debating the colour of a button.

Ask your designer to walk through a typical customer journey. Where does someone arrive? What do they need to understand? What might prevent them from enquiring?

A simple page outline can reveal missing information before a polished design makes everything feel settled.

Explain Why You Like A Reference

Reference websites can help, but “make it like this” leaves room for different interpretations.

Point out the specific quality you mean. Perhaps the product comparison is easy to read, the photography feels relevant or the enquiry process is straightforward.

Also identify what you do not want. You may like a site's visual style but dislike its long opening animation.

Use references to discuss principles, not to copy another company's branding or content.

Give Feedback In Terms Of The Reader

Try replacing a preference with the concern behind it.

Instead of “Make this section bigger”, explain that the service area is easy to miss and customers need it before requesting a quote. The designer can then suggest an appropriate solution.

Separate factual corrections, usability problems and personal preferences. All may be worth discussing, but they should not carry the same weight.

When possible, attach feedback to a specific page or section. A screenshot with a short explanation is more useful than a long message referring to “the thing near the bottom”.

Consolidate Decisions Without Hiding Disagreement

Choose someone to collect feedback and confirm the final direction. This prevents the designer from receiving contradictory instructions through separate conversations.

That person should not simply forward every comment. Discuss conflicts internally, or bring the unresolved decision to the designer with the business reasons on both sides.

Keep a record of what was approved and what is still open. If a decision changes, ask how it affects the scope and schedule before work continues.

Review Real Content And Real Tasks

Placeholder copy can make a design look tidier than the finished website. Review with representative headings, long product names and realistic amounts of text.

Ask to see mobile layouts and try important interactions. Can someone find a service, read the details and complete an enquiry? Can your own team update the information it owns?

Agree review points at the beginning, so questions are raised while there is still room to respond.

Make Handover Part Of The Conversation

Before launch, establish who will maintain the website, what training is needed and how outstanding issues will be recorded.

A useful handover lets your team perform its normal work, not just receive a folder of files.

The best collaboration combines your understanding of the business with the designer’s ability to turn that understanding into a usable website. Clear questions and timely decisions give both sides room to do their job well.