HelloSiteWorks Websites. Branding. Beautiful details.Let’s talk Email us
Start a project
← Back to the journal
Mint paper fox pointing to one highlighted design card on a board of organised feedback beside a website mockup.
Original HelloSiteWorks concept illustration; the mockups are fictional.
HELLOSITEWORKS FIELD NOTES · Design

Make design feedback easier to use.

Point to the part that needs work, explain the practical concern and agree the priorities before the next revision begins.

4 min read · Practical ideas for a stronger first impression

The useful bits.

Anchor each comment to a real use and an exact version.

Explain the concern before suggesting a treatment.

Consolidate priorities and preserve the decisions that work.

Start with the job the design needs to do.

A design review is easier to follow when everyone is looking at the same problem. Before collecting opinions, restate who the piece is for, where it will appear and what the reader should understand or do. A small profile image and a printed welcome card ask different things of the same identity. Review the work in its intended setting.

Keep the agreed brief beside the draft. If the project needs to introduce a local service clearly, ask whether the business name, service and next step are easy to find. Personal preferences can still be useful, but connect them to that purpose. A request for a different colour needs context before someone can decide how to respond.

Point to one place and describe what happens.

Broad comments such as “make it stronger” leave room for several interpretations. Name the page, version and exact element instead. Describe what you notice at the size someone will actually see. The logo may look clear in a large presentation but become difficult to recognise inside a small profile circle. That observation gives the next revision a concrete starting point.

For a fictional repair shop, useful feedback might read: “On the mobile service page, the opening photo takes up most of the first screen. I cannot see the service heading without scrolling.” This describes the location and concern without pretending there is only one solution. It is an illustrative example, not a report about a customer website.

Separate the concern from a proposed fix.

You can suggest a solution while leaving space to test it. “Could we shorten the photo or move the heading?” is easier to discuss when it follows the reason for the change. The designer may find another way to make the heading visible. Keep the practical concern attached to the suggestion so it survives if the proposed treatment changes.

Be equally specific about what works. If a compact mark stays recognisable at small sizes, record that as a feature to preserve. A revision should carry successful decisions forward. Avoid reopening every colour, type choice and layout detail when the current review is meant to resolve one agreed issue.

Send one prioritised set of notes.

Gather comments from the people who need to approve the work, then resolve contradictions before sending the next round. One person may want a quieter layout while another asks for more content in the same space. That is a decision for the review group to discuss, rather than a puzzle the designer should have to solve from separate messages.

Sort the resulting notes into required corrections, questions and optional ideas. A wrong phone number belongs ahead of a preference for a different decorative shape. Identify the person who can settle open questions. Keep the original draft available and give the next revision a clear version name so comments do not become detached from the work they describe.

Close the loop before preparing the handoff.

When the revision arrives, compare it with the agreed notes in the same real setting. Check the corrected contact detail, the small mark or the mobile heading directly. Record what is resolved and describe any remaining concern precisely. If a change creates a new problem, explain the connection rather than starting an unrelated list of preferences.

Before calling the design approved, name the exact version and the uses that were checked. Keep unresolved production questions visible for the person responsible for confirming them. A short decision note can travel with the final files, giving the next person a dependable account of what was agreed and what still needs attention.

Keep a good idea going.

All field notes →
Websites · 4 min read

Choose website images with their placement in mind.

Review the picture inside its intended layout, with the real words and a phone view, before treating an attractive image as the right fit.

Read the field note
Design · 4 min read

Give each approved design variation a clear use.

Connect the variations in your identity set to real placements, then record where a new format still needs its own review.

Read the field note