How Should Agencies Handle Conflicting Website Feedback From Multiple Stakeholders?

A practical way to turn competing comments into one decision before the next website revision starts.

By Charlie Boudreau10 minute read

Key Takeaways

  • Name one client decision owner before collecting feedback.
  • Let each stakeholder comment on the same identified page and version.
  • Separate factual corrections, preferences, strategic disagreements, and new scope.
  • Compare competing requests against the audience and goal in the approved brief.
  • Record the chosen direction, then revise and seek explicit approval of the new version.
Printed website mockup with competing orange and navy feedback notes pointing to the same headline and button
Different priorities can point at the same element. Editorial illustration, not a Jottrly interface.

What Should You Do When Stakeholders Disagree?

Quick answer: Gather the comments on the same version, identify the exact conflict, and ask the agreed decision owner to choose a direction based on the project goal. Record that decision before the designer makes a change. Then review the revised version and request a separate approval.

Imagine a website redesign where the sales lead wants a prominent “Book a Demo” button and the support lead wants the same space to say “View Help Center.” Both requests may be reasonable. The agency needs to know which visitor and outcome the page serves first. Editing the button twice will not answer that question.

The broader client feedback problems checklist covers conflicting comments as one of several review issues. Here is a process for handling that particular issue from intake through sign-off.

1. Name the Decision Owner Before Review Starts

Ask the client who can make the final call for this page or deliverable. It might be the marketing lead, founder, or project sponsor. The right person is the one authorized to resolve tradeoffs and confirm that the result meets the brief.

  • Decision owner: chooses the direction and approves the final version.
  • Contributors: provide audience, product, brand, legal, or operational input.
  • Agency lead: groups requests, explains consequences, and recommends an option.
  • Designer or developer: implements the confirmed direction and flags new implications.

Write the names and review deadline into the request. The client design approval process has a fuller sequence for review briefs, revisions, and sign-off.

2. Collect Every Comment on the Same Version

Tell stakeholders exactly which page and version they are reviewing. Ask them to point to the relevant element and describe the concern, intended outcome, and priority. A comment such as “This feels too salesy” needs a follow-up. “This headline promises a live demo, but this page is for self-service buyers” gives the team something to evaluate.

For a public webpage, Jottrly can capture a page from its URL and let reviewers pin comments to that captured snapshot. It is a fixed visual capture, so test menus, forms, and responsive behavior on the actual website. See the URL capture workflow for a focused website review process. For uploaded designs and PDFs, keep comments with the corresponding file and version.

A useful review request

“Please review the homepage, round 2, by Thursday. Focus on the hero message and primary action. Add one comment per issue and explain the visitor outcome you want. Jamie is the final decision owner and will resolve competing requests before we revise.”

3. Sort the Feedback Before You Start Revising

Not every disagreement needs the same response. Sort comments before scheduling design work. This prevents a factual correction from being treated like a brand preference, or a new feature request from slipping into a revision round.

Types of conflicting website feedback and recommended next steps
TypeExampleNext step
Factual correctionTwo teams give different product specifications.Verify the source of truth with the owner.
Audience or goalSales wants demos; support wants help clicks.Choose the page’s primary visitor action.
Creative preferenceOne person prefers a photo, another an illustration.Test each idea against the agreed brief.
New scopeA reviewer asks for a new calculator.Estimate effort and agree on scope first.
Functional issueA form fails on a phone.Reproduce and fix it on the actual site.

When a request adds work beyond the agreed deliverable, follow the design revision and scope process. A missed requirement in the approved brief is a correction, not automatically billable extra work.

4. Turn Two Opinions Into One Decision

Summarize each side in neutral language. Then explain how each option affects the page goal. Do not ask the designer to blend two requests just to make everyone feel heard. A hybrid works only when it actually serves the audience.

The four-part decision path
  1. 1Locate the conflictName the element, version, and two requested outcomes.
  2. 2Use the briefCheck the audience, purpose, and agreed success measure.
  3. 3Show the tradeoffRecommend an option and state what it prioritizes.
  4. 4Record the callGet a written decision before the next revision begins.

Example: “The sales and support teams have requested different hero actions. The approved brief describes this as a product evaluation page, so we recommend ‘Book a Demo’ as the primary action and a Help Center link lower on the page. Jamie, please confirm or choose a different direction before we update the design.”

That wording gives the client a real choice while making the agency’s recommendation clear. For examples of comments that identify a problem and outcome, see how to give useful design feedback.

Keep the Conversation With the Design

Pin each request to the relevant part of the work, discuss conflicting ideas in context, and keep the current version clear.

Explore the Product

5. Record Decisions Where the Team Can Find Them

Keep a short decision log for disagreements that affect content, design, or scope. It does not need to become a new meeting document. The record should be easy to find beside the relevant review.

Example decision log for a website redesign
Page and issueOptionsDecision and ownerStatus
Homepage hero actionBook a Demo / View Help CenterBook a Demo, confirmed by Jamie on Nov. 9Ready to revise
  • Link the decision to the page and version reviewed.
  • Name who chose the direction and when.
  • State the accepted change and any deferred idea.
  • Note whether a separate scope decision is needed.
  • Tell the team which comments can now be addressed.

Jottrly’s pinned annotations, threaded comments, version history, and open or resolved tracking can keep the discussion close to the work. The person responsible for the client decision still needs to confirm it. The product overview explains the review features, while how Jottrly works shows the wider workflow.

6. Revise Once, Then Ask for Approval

Send the confirmed decisions to the designer or developer as one coherent set. After the changes are made, ask the contributors to check only the affected areas and ask the decision owner to confirm the current version.

  • Before revision: resolve the direction, the review boundary, and any added scope.
  • After revision: summarize what changed and identify the new version.
  • For website captures: capture the updated page again because an earlier snapshot does not change with the website.
  • For functionality: test forms, navigation, and responsive behavior on the actual site.
  • For sign-off: request an explicit decision about the revised version.

Closing a comment only means that issue was handled. It does not approve the whole page. If a late stakeholder request reopens a settled choice, identify its effect on the schedule and scope before starting another round. The article on managing revisions without scope creep gives sample wording for that conversation.

Stakeholder Feedback Checklist

  • Identify one final decision owner.
  • Share the same named page and version with everyone.
  • Set the review goal, deadline, and requested decisions.
  • Ask for one issue and intended outcome per comment.
  • Group factual, strategic, preference, scope, and functional requests.
  • Summarize conflicts without taking sides prematurely.
  • Recommend an option against the agreed brief.
  • Record the client’s choice before revising.
  • Check the revised version and request explicit approval.

Give Every Review a Clear Decision

Bring website captures, pinned comments, revisions, and review status into one place while your team makes the final call.

Contact Jottrly

Frequently Asked Questions

Who should make the final call when client stakeholders disagree?

Choose one decision owner with authority to approve the work. Other stakeholders can contribute expertise, but the decision owner should confirm a single direction against the agreed brief before the agency revises the design.

Should designers combine two conflicting requests?

Only if the combined approach solves the underlying problem. A compromise that weakens both goals is not automatically better. Explain the tradeoff, propose a solution, and ask the decision owner to confirm it.

What if the CEO disagrees with the marketing manager?

Pause the affected change and ask the client team to resolve the priority internally. Show both options in terms of audience, goal, and tradeoff. Do not quietly treat a job title as a substitute for the agreed approval process.

How can we tell a correction from a new scope request?

Compare the request with the approved brief and deliverables. Fix an omitted agreed requirement as a correction. A new page, feature, audience, or creative direction may need a separate scope and schedule decision.

What if feedback arrives after the decision was made?

Identify the version and decision being reopened. Assess the effect on work already completed, timing, and cost, then ask the decision owner whether to start a new review round. Keep the earlier decision visible.

Can a visual feedback tool resolve stakeholder disagreements?

A tool can keep comments attached to the relevant design, preserve the discussion, and help track open issues and review status. The client team still needs a decision owner and a clear process for choosing between competing requests.

Does resolving all comments mean the website is approved?

No. Resolving a comment closes an individual issue. Ask the decision owner to review the revised version and explicitly approve it or request changes.