Template
Design feedback board template
A design feedback board template for Looph: collect critique on mockups and prototypes, with tags for usability, visual, copy and accessibility issues.
Design and product teams collecting structured critique on in-progress work from stakeholders or users.
- Statuses
- 4
- Tags
- 4
- Things to ask for
- 4
- Setup steps
- 6
Use this template
Copy the setup, import the starter posts
Two ways to start from this template today: copy the checklist below into your setup notes, and import the starter CSV into a new board from the Posts page of your team area. The file holds this page's example posts, with each status mapped to Looph's built-in name so the importer accepts it; delete them before you share the board.
Columns: title, details, status. 3 example posts.
Setup checklist
Design feedback board template (looph.ing/templates/design-feedback-board) Statuses (the Statuses page in the team area): - Keep "Open" - Rename "Under review" to "Discussing" - Rename "Complete" to "Applied" - Rename "Rejected" to "Not applying" Hide Planned, In progress and Closed if no other board needs them. Statuses are shared by every board in a workspace, so a rename or a hidden status shows on all of them. Tags: - Usability - Visual design - Content/Copy - Accessibility Board description: Start with a link to the frame. Then say what you expected and what you saw instead, and your role. Ask for in the details: - One observation, as a title - A link to the frame - Expected versus seen - Their role Setup steps: 1. Create the board. Make it private if the designs are unreleased, adding reviewers by email or an outside partner's @domain, or public if you want feedback from your wider user community. 2. Paste the prompt above into the board description, so every post starts with the frame link. 3. Rename the statuses as listed and create the four tags. 4. Invite the designers and product people who will respond as members, who are free on every plan. 5. Merge overlapping feedback into one post; votes and comments from both carry over, so you see the full weight behind it. 6. Check that reviewers are notified on status changes, so moving a post to Applied tells them the change is ready to look at.
Templates aren't applied automatically yet: you set the board up yourself by following the steps on this page. One-click templates are coming soon.
Fit
When to use this template
A good fit when
You share mockups, prototypes or a staging build with stakeholders or test users, and their comments end up scattered across chat threads and meeting notes. A board gives each piece of feedback its own post, linked to the frame it is about, with a status and votes from other reviewers who agree.
Votes earn their place here: when five reviewers back the same usability problem, you know it is not one person's taste.
Pick something else when
Pixel-level comments on a single frame belong in your design tool's own commenting. Use the board for feedback that needs a decision and a record, such as whether to change a flow, a label or a pattern.
It does not replace usability testing. A board collects opinions and observations, not measured behaviour.
What's inside
Statuses, tags and what to ask for, and why each one is there
Looph has a fixed set of statuses that you can rename, recolour, reorder and hide, but not add to; each status below says which built-in one to use. Posts are a title plus details, so the last list is what to ask for in the details.
Statuses
- OpenBuilt-in status
- New feedback nobody on the design team has responded to yet.
- DiscussingRename Under review
- The team is weighing it, and comments are where reviewers make the case for or against. Keep constraints reviewers do not need to see, such as engineering cost, in internal notes.
- AppliedRename Complete
- The change is in the design. Link the updated frame in a comment so the reviewer can check it matches what they meant.
- Not applyingRename Rejected
- Considered and rejected, with the reason written down once. Otherwise the same critique returns in every review round.
Hide Planned, In progress and Closed if no other board needs them. Statuses are shared by every board in a workspace, so a rename or a hidden status shows on all of them.
What to ask for in the details
- One observation, as a title
- One observation per post, stated specifically. "The Continue button looks disabled" can be resolved; "checkout feels off" cannot.
- A link to the frame
- A URL to the exact frame or prototype screen. Without it, "the button is confusing" could mean any of forty buttons. Looph cannot make it required, so put it first in the board description.
- Expected versus seen
- What the reviewer expected and what they saw. Expectations are the part designers most need and reviewers most often leave out.
- Their role
- The post shows who wrote it; their role tells you how to read it. A note from your accessibility lead and one from a first-time user are both useful, for different reasons.
Custom fields and file attachments are coming soon. Until then, a post is a title plus up to 5,000 characters of details.
Suggested board description
Put a line like this in the board description, so people know what to include: “Start with a link to the frame. Then say what you expected and what you saw instead, and your role.”
Tags
- Usability
- Visual design
- Content/Copy
- Accessibility
The tags separate problems that go to different people; filter by one and assign those posts. Accessibility has its own tag so those issues are judged on their own terms, rather than outvoted by visual preferences.
Setup
Set it up in Looph
Each step in order, with the guide that covers it.
- 01
Create the board. Make it private if the designs are unreleased, adding reviewers by email or an outside partner's @domain, or public if you want feedback from your wider user community.
- 02
Paste the prompt above into the board description, so every post starts with the frame link.
- 03
Rename the statuses as listed and create the four tags.
- 04
Invite the designers and product people who will respond as members, who are free on every plan.
- 05
Merge overlapping feedback into one post; votes and comments from both carry over, so you see the full weight behind it.
- 06
Check that reviewers are notified on status changes, so moving a post to Applied tells them the change is ready to look at.
Illustrative examples
Example posts
Made-up posts that show what a useful entry on this board looks like. They are not from real customers.
Example · Visual design
Checkout: the Continue button looks disabled
Frame: Checkout / Step 2. The grey fill reads as inactive, and two of us waited for it to turn blue before clicking. Reviewer: support lead.
Discussing
Example · Accessibility
Sign-up errors are not announced by screen readers
Frame: Sign-up / Errors. With a screen reader running, submitting an invalid email gives no spoken feedback. Comment from the team: error text is now tied to the field.
Applied
Example · Content/Copy
"Workspace" and "Project" used for the same thing
Frames: Onboarding 1 to 4. The first two screens say workspace and the last two say project for the same object.
Open
Plan
Which plan it needs
Needs Starter. Unreleased designs usually call for a private board, which starts on Starter. A public design board works on Free if it is the only board you run, since Free includes 1 public board. Compare plans.
How the pieces work: Browser extension and Feedback boards. Teams running this workflow: White-labeled client feedback portals for agencies and Customer feedback management for SaaS product teams.
More templates
Other starting points
Public bug tracker board template
Teams that want bug reports separated from feature requests, with triage by impact that reporters can follow.Feature request board template
Product teams that need a single public place to collect and prioritize customer-driven feature ideas.Beta feedback board template
Teams running a private or invite-only beta that need structured, votable feedback before a general release.Internal IT request board template
Internal IT and operations teams that need a searchable, votable alternative to a ticketing spreadsheet.
Related
The features and reading behind this template
Start collecting feedback in five minutes
Free forever on one board, with unlimited members and a 14-day Business trial. No credit card, no sales call.
Unlimited members · Published prices · Cancel anytime