reph

Templates · Design

Design critique notes template

Structured feedback on a design review

Start with this template →Sign in

Opens on reph with the template ready to start. No account needed; sign in to keep your document.

Use it when

You are running or attending a design review and want feedback captured by area and priority, with decisions that stick

Who it's for

DesignerProduct manager

Filled example

The template filled in for a made-up company, so you can see what good looks like.

Design critique: Refund flow, concept round

Author: Maya Torres · Date: 13 October 2026

Design under review

Link: Billing Figma file, page "Refunds v2 concepts" · Stage: early concept

Goals of the critique

Direction is still open. We are choosing between concept A (refund from the appointment) and concept B (refund from the payments list). Feedback on structure and flow is welcome; visual polish is out of scope this round.

Feedback

Area Observation Suggestion Priority
Entry point In concept B, receptionists must know the payment date to find it. Research showed they search by patient name. Lead with patient search in B, or go with A. Must fix
Partial refunds The amount field defaults to the full amount; a slip refunds everything. Default to empty and show the original amount beside the field. Must fix
Confirmation The final step says "Submit". Refunds cannot be undone with our provider. Name the action and amount: "Refund £45.00 to Visa 4421". Should fix
Owner limits The limit message appears only after the receptionist presses refund. Show the remaining limit on the first screen. Should fix
Receipt Email receipt option is hidden under "More". Fine for now; check in testing whether patients ask for it. Nit

What's working

  • Concept A's "Refund" action sitting next to the appointment matches how receptionists described the moment in research.
  • The step count (three screens) is right; nobody wanted fewer.
  • Keyboard flow through the amount and reason fields already works in the prototype.

Open questions

  • Do clinics with more than one card terminal need to choose a terminal? Jonas to ask three pilot clinics.
  • Should the refund reason be required? Ana to check what finance needs for reconciliation.

Decisions

  • Go with concept A as the primary path. Keep a refund action in the payments list for owners, using the same three screens.
  • Partial refund amount defaults to empty.

Next steps

The template

Show the blank template

Design critique notes

Author: [your name] · Date: [date]

Design under review

Link to the Figma/prototype, and the stage: early concept, refined, final before handoff. The stage sets how much structural feedback is still fair game.

Link: [prototype or file link] · Stage: [concept, design or polish]

Goals of the critique

What kind of feedback is being asked for. Is direction still open, or is this a polish pass? Say so, or reviewers will re-litigate the concept.

Feedback

One row per observation. Priority is must fix, should fix or nit, judged against the goals above.

Area Observation Suggestion Priority

What's working

Don't skip this. Specific praise is as calibrating as criticism, and tells the designer what not to change.

Open questions

Things nobody could answer in the room, each with who will find out.

Decisions

What was decided in the room, so it doesn't get re-argued next review.

Next steps

Owner and date on every line.

Questions

How do I set priority?
Must fix blocks the goal of this stage, should fix improves it, nit is taste and can wait
Who decides which feedback to act on?
The designer, using the goals of the critique, and the decision is recorded so it is not argued again
Should I critique the concept in a polish review?
Only if something blocks launch, otherwise note it for the next project

Fill it with your agent

Connect Claude to reph over MCP, then paste this. The draft arrives as suggestions you accept or reject section by section. How to connect Claude.

Find my reph doc "Design critique notes" with search_docs, then read it with read_doc. Turn the critique notes and transcript I paste into Feedback table rows (area, observation, suggestion, priority), naming who raised a point only if they agreed. Record decisions only where the room agreed. File it with suggest_edit, one replace_section op per section (heading line kept) so each can be accepted alone. Ask each open question (feedback that conflicts and needs the designer to choose) with add_comment quoting that section's heading line, then call request_review with a one-line summary.

Related templates

Start with this template →Sign in