How to Review a Website Mockup with Multiple Stakeholders

More reviewers can bring useful knowledge to a website redesign, but an open invitation to “everyone” can create contradictory directions. Marketing may focus on campaign language, legal on claims, leadership on positioning and customers on usability. Give each person a defined lens, then route the combined feedback through one decision owner.

Assign a review role to each stakeholder

• Decision owner: resolves tradeoffs and gives final approval.
• Subject expert: checks factual details within a defined area.
• Brand reviewer: checks identity and messaging against approved guidance.
• Implementation reviewer: flags technical constraints or dependencies.
• Informed participant: receives updates but does not add another approval gate.

One person can hold multiple roles on a small project. The important part is making decision rights clear.

Give reviewers a shared frame

Send the same preview version, the brief, the review questions and the deadline. Explain whether the artifact is a static mockup, a prototype or a working build. Ask people to stay within their review lens and mark new requests separately.

Collect comments before discussing them

Let reviewers submit observations individually, then have the feedback owner combine duplicates and resolve conflicts. If two comments disagree, ask the owner to choose based on the brief or gather the missing evidence. A meeting can resolve a real decision; it should not be needed to discover which file everyone reviewed.

Use a decision table

Page / section	Comment	Review lens	Decision owner	Status
[page]	[observation and reason]	[role]	[name]	[open / accepted / deferred]

Keep the table focused. It is a decision record, not a transcript of every conversation.

Protect the review from endless reopening

After a decision is approved, record its scope and version. Reopen it when a requirement changes or new evidence affects the outcome. A late preference change can still be considered, but the team should assess its impact rather than treating the prior approval as if it never happened.

For a lightweight workflow, share one browser preview, define who can comment and ask one owner to consolidate input. The existing approval owner guide explains how to choose the final decision maker; the feedback consolidation guide covers the next step.

Give each review lens a useful question

• Marketing: Can the intended audience recognize the offer and next action?
• Legal or compliance: Are claims, disclosures and required information accurate and visible?
• Operations: Does the page reflect how the service is actually delivered?
• Technical: Are any layouts, content sources or interactions dependent on a system constraint?
• Leadership: Does the direction support the agreed business goal?

A role is not permission to comment on everything. It defines what knowledge the person contributes and helps the approval owner assess the note.

Resolve disagreement with a decision rule

When stakeholders conflict, identify what kind of conflict it is. A factual disagreement needs verification from the source owner. A brand question should be checked against the approved standards. A strategic disagreement needs the decision owner to choose a goal or request more evidence. A personal preference can be heard without automatically becoming a requirement.

Do not ask the designer to decide between two authorized client stakeholders. Return the question to the named owner, explain the tradeoff and pause only the work that depends on it.

Keep the review accessible to busy participants

Send a concise brief with the version, deadline, focus questions and method for submitting comments. Provide a short summary for participants who cannot attend a meeting, and give them the same visual reference. If a meeting is needed, share the consolidated comments first so time is spent resolving decisions rather than reading notes aloud.

After the meeting, send a decision summary with actions, owners and due dates. Mark which feedback was accepted, deferred or needs more information. The approval owner article can help the team define who has final sign-off.

Frequently asked questions

Should every stakeholder approve every page?

Only involve people whose expertise or authority is relevant to that decision. Keep visibility separate from veto power.

What if the decision owner disagrees with subject experts?

Clarify whether the disagreement concerns facts, risk or preference. Document the rationale and any follow-up needed before implementation.