WIPP field notes / Designers

Get design feedback on the decision, not just the surface

Give reviewers a task, audience and constraint so UI, typography and branding feedback goes beyond personal taste.

Choose another craft
Illustrative hierarchy study: two arrangements, one changed emphasis.

Start withOne screen or mark. A task and a constraint.

  1. Share contextStage, goal, constraint
  2. Ask one questionObservation before verdict
  3. Test one changeKeep the original; compare

Design feedback changes when a reviewer knows what the design is supposed to do. A beautiful UI may still obscure the next action; a distinctive logo may lose its shape at a small size. Show the task and the context before asking whether the screen or identity “works.”

WIPP can be a place to share images or video of a design in progress and explain your choices. It is not a substitute for testing with the intended users. Treat community comments as observations and hypotheses to investigate, especially when a UX decision affects accessibility or a critical task.

Write a compact brief before exporting a screen

Describe the audience, the action you want them to take and the limitation you cannot change. For a mobile checkout, that might be a first-time customer reviewing delivery details on a small screen. For branding, it might be an independent bookshop that needs a legible mark on receipts and outdoor signage.

Say which decision is open. If copy is provisional but navigation is under review, label the copy as provisional. Remove client names, internal metrics and customer information unless you have permission to share them. A practice brief is safer than exposing a confidential project.

  • UI: show the screen at a readable scale and explain what happens just before it.
  • UX: describe the user’s goal and where you think they may hesitate.
  • Branding: name the use case and show the mark in a relevant small-size or one-color context.

Compare alternatives that answer one question

A useful logo iteration compares a real variable, such as stroke weight or spacing, rather than presenting six unrelated directions. Label the alternatives A and B in the image itself so a comment remains understandable. Keep the surrounding context constant when possible.

For typography, show the headline, body text and a representative long line together. Ask about hierarchy or reading effort rather than which font is fashionable. A screenshot can reveal some issues, but it does not prove keyboard access, responsive behavior or screen-reader usability.

Request an observation before a recommendation

Ask a reviewer what they believe the primary action is before revealing your intended answer. If they point to the wrong element, you have evidence about hierarchy. If they understand the action but dislike the color, that is a different kind of feedback.

When someone recommends a change, ask which part of the brief it addresses. “Increase the spacing” is more useful when paired with “these two labels look like one control.” Keep suggestions that help the task; record disagreements without turning critique into a vote on your ability.

Close the loop with a testable change

Revise one choice and inspect the design in its intended context. Check a logo at receipt size, review text on a real phone, or walk through the flow with a person who has not seen it. Use appropriate accessibility checks rather than assuming visual approval means accessible design.

If you post an updated screenshot, explain which observation led to the change and what remains unresolved. This is a process note, not a promise that every comment will be implemented. When giving feedback yourself, refer to the brief and avoid replacing the creator’s goals with your own stylistic preferences.

Illustrative practice brief / Not a member project

Example description: choosing a booking-screen hierarchy

Practice brief: a first-time visitor needs to confirm a workshop date before booking. A and B use the same copy and spacing; only the date emphasis changes. What would you check first, and which action looks primary? The illustrations are placeholders. I would like feedback on hierarchy, not a new color palette.
Stage
Two practice booking-screen alternatives; illustrations are placeholders.
Goal
Help a first-time visitor confirm a workshop date before booking.
Ask
What would you check first, and which action looks primary?
Boundary
Hierarchy only, not a new color palette. Copy and spacing stay constant.

This is an illustrative brief, not a client result. Holding most variables constant helps a reviewer explain why one arrangement communicates the task more clearly.

Feedback prompts to adapt

Choose one question that fits the stage of your work. You do not need to ask all of them.

  • What do you think happens after selecting this button?

  • Which information would you need before taking the next step?

  • At this size, do any letters in the logo merge?

  • Where does the typography make the reading order ambiguous?

Put it into practice

A small next step on WIPP

Pick one screen or identity decision and include the brief beside it. Invite a narrow critique before spending time presenting every possible direction.

Posting requires signing in. Feedback is optional.