Product design feedback rounds: how to run them so they end

Product design feedback rounds end when each round has one decision to make, one person who makes it, a date to make it by, and a clear status on every comment when it closes. Without those four things, rounds don't end; they blur into each other. Comments from round two turn up in round four, a new stakeholder reopens the colour, and nobody can say which version was agreed.

This guide is for industrial designers, product design studios and in-house teams who send designs to clients, product managers or a room full of stakeholders. It works with any tool. The aim is a process where "the last round" is a real thing.

#How do I run a feedback round that ends?

Treat each round as a small project with a start, an end and an outcome.

1. 1

   Name the decision for this round

   Write one sentence: "This round decides the overall form and proportions." or "This round decides the CMF (colour, material, finish) for the two hero colourways." Everything outside that sentence goes on a list for later.

2. 2

   Name who decides

   One person signs off each round. Others can comment, but the decider resolves conflicts between them. If you don't know who that is, ask before you send anything.

3. 3

   Set a deadline for feedback

   A date, not "when you get a chance". A few working days is common for a focused round; choose what suits the project and say it up front.

4. 4

   Send one version, clearly labelled

   "v3, form and proportions" in the file name, the subject line and on the model itself. Never two variants of the same version.

5. 5

   Ask for consolidated feedback

   One set of comments from the decider, with conflicts already settled. If you must take comments from several people, you consolidate them, and the decider settles the conflicts.

6. 6

   Answer every comment with a status

   Each comment ends up as done, in progress, won't do (with a reason), or moved to a later round. No comment is left without an answer.

7. 7

   Close the round in writing

   A short summary of what was decided, what changed and what's next. Then freeze that part of the design.

#Why do feedback rounds go on forever?

Usually for one of a few reasons, and each has a fix.

#How do I consolidate feedback from several stakeholders?

When five people review a design, you get five lists that overlap and disagree. Consolidating them is work, and it should be clear whose work it is.

The cleanest arrangement: the client consolidates, and you receive one list. If that's not realistic, do it yourself in three passes:

• Group comments by area of the product (handle, base, display, packaging), not by person.
• Merge duplicates. "The button is too small" from three people is one comment with three supporters.
• Flag conflicts and send them back to the decider as direct questions: "Marketing wants the logo larger; engineering says the boss underneath limits it to 22 mm. Which wins?"

Don't resolve a conflict between stakeholders by guessing. You'll be wrong for half of them, and the topic comes back next round.

#What should I write when I close a round?

A short summary that someone who wasn't there could read. Here's a template:

Round 3 (v3) closed - form and proportions

Decided:
- Overall height 182 mm, base diameter 96 mm
- Handle option B, with the softer radius
- Display moved 4 mm towards the front

Not changing (with reason):
- Thinner base: battery pack needs the current depth

Moved to round 4 (CMF):
- Colour of the trim ring
- Texture on the grip

Next: v4 for CMF review, feedback by Thursday.
From now on, form and proportions are fixed. Changes to
them will be treated as a change request.

The dimensions are an example. The structure is what matters: decided, not changing, moved, next, and what is now fixed.

#What does "freeze" mean in practice?

Freezing a decision means it won't be reopened without a reason and a cost. It doesn't mean nobody can ever change it; it means a change is a deliberate choice, not a stray comment.

In practice:

• Say what's frozen in the round summary, as above.
• When a frozen item comes up, answer it as a change request: what it affects, what it costs in time or money, and whether to go ahead.
• Keep the record of when it was frozen and by whom, so the conversation is about the change rather than about what was agreed.

#Where MeshMarkup helps

MeshMarkup handles the mechanics of a round for 3D models, so the process above is easier to stick to.

• Comments pinned to the spot. Reviewers open a link in their browser with no account and click the model where they mean, so "the edge" becomes a numbered note on that edge.
• Every note gets a status. You reply and set OPEN, IN PROGRESS, RESOLVED or WON'T FIX; the client sees Working on it and Fixed. Click internal to discuss a note with your team where the client can't see it. See notes, replies and statuses.
• A deadline that chases for you. Ask for feedback by in the Share menu shows the date at the top of the link, and if you add the reviewer under Their email, MeshMarkup reminds them in your name until they answer. See feedback-by dates and reminders.
• One link for several models. A project link opens every model in a project on one page and always shows the latest version of each.
• Rounds as versions. Upload v2 keeps the next round on the same model, with open notes carried across, and Report saves the round's notes and threads as a PDF, which can sit next to your written summary.
• A clear end. A Sign it off link (Solo plan and up) gives the decider an approve button for that exact version, and it won't go through while any note is still OPEN or IN PROGRESS. See client sign-off.

Everyone with a link to the same version sees the same notes, so stakeholders can reply to each other rather than to you separately.

#Questions

#How many feedback rounds should a product design project have?

There's no right number; it depends on the product and the stages you've agreed. What matters is that each round has a named decision, and that the number included is written into the agreement.

#What if the decider won't commit?

Ask a narrower question with a default: "If we don't hear by Thursday, we'll go ahead with option B." Then do what you said.

#Should every stakeholder see every round?

Not necessarily. Invite people to the rounds where their decision is being made, such as engineering for form and fit, and marketing for CMF, and send the others the round summary.

#What do I do with feedback that arrives after a round closes?

Thank them, and put it into the next round's list. If it reopens something frozen, treat it as a change request.