TrueStory Africa Work with us

141 · Insights · Guides

How to give feedback on a design draft without starting again

For communications teams reviewing reports, posters and social graphics who want better results in fewer rounds.

  • Published17 November 2026
  • Reading time7 min
  • ByTrueStory Africa
  • Sources5
  • Facts checked27 October 2026

Why good drafts get thrown away

Most design projects that "start again" did not fail at the drawing stage. They failed at the review. A senior colleague sees the draft late, dislikes the colour, and the team abandons work that met the brief.

Good feedback on a design draft avoids this. It keeps what works, names what does not, and gives the designer enough information to fix it in one round. It is a skill, and like any skill it improves with a simple method.

The aim of a review is not to approve or reject. It is to ask two questions: what are we really trying to do here, and how close is this draft to doing it? Everything in your feedback should help answer them.

It also helps to remember what stage the draft is at. A first concept is meant to test a direction, so comments on exact wording or image crops can wait. A final layout is meant to be checked line by line, so it is too late to question the whole idea unless something is seriously wrong.

Review against the brief, not your taste

Before you open the file, reread the design brief. Remind yourself who the audience is, what the piece must achieve and where it will be seen. Then look at the draft through that lens.

  • Will the intended reader understand the main message in a few seconds?
  • Is the most important information the most visible?
  • Does it work at the real size: on a phone, a roll-up banner or an A4 page?
  • Does it follow the brand and any donor visibility rules?

If you find yourself writing "I don't like the green", ask whether the green stops the piece doing its job. If it does not, it is a preference. Say so, or leave it out.

Tell the designer what the problem is and why it matters, and let them find the solution.

Key point

Describe problems, not solutions

The most useful design feedback explains what is not working and why. AIGA Baltimore's guide to design critique advises explaining why you like something, using specific examples from the design, and, when something is not working, explaining why or offering suggestions on how it can be improved.1

Compare two comments on a report cover:

  • Weak: "Make the title bigger and red."
  • Useful: "From across the room, the title gets lost behind the photograph. The ministry needs to read it on the display stand."

The second gives the designer the real problem. They may enlarge the title, change the crop or add a darker band. They have the skills to choose. Comment on the work, not the person. The same guide suggests limiting the word "you" so the critique is about the design and not the designer: "the headline competes with the logo" lands better than "you put the logo in the wrong place".1

Say what works, too. Specific praise tells the designer what to protect in the next round.

Separate fixed rules from preferences

Some comments are not open to debate. Mark them clearly so they are fixed first.

  • Accuracy: wrong figures, names, titles or dates
  • Brand and partner rules: logo order, clear space, required statements. EU-funded work, for example, must show the EU emblem with a funding statement such as "Funded by the European Union", and the two must not be separated.2
  • Accessibility: text that is too small or too faint to read
  • Legal and ethics: missing consent, photo credits or safeguarding concerns

Accessibility is often treated as taste, but it can be checked. The W3C's WCAG standard asks for a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text, which it defines as at least 18 point, or 14 point bold.3 A contrast checker settles the question in seconds.

Everything else is a preference. Label it as one: "Optional: could we try a warmer photo here?"

Related service

Strategic communications

Media relations, key messages and spokesperson preparation that help your organisation speak clearly when it matters.

One voice, one round, one document

The quickest way to start again is to send five people's comments separately. The designer receives contradictions and has to guess who decides.

Collect all comments in one place, such as comments on a shared PDF or a single numbered list. Resolve disagreements inside your team before you send anything. One person, the project owner, sends the final set and makes the call when views differ.

Tell reviewers in advance what kind of feedback you want and how to give it. The UK Department for Education's design guidance on content reviews advises giving reviewers the context of the piece, explaining the type of feedback you want, and telling them you are looking for honest feedback delivered in a constructive way.4 A structured critique with people from different roles can also surface issues one person would miss. One DfE team ran critiques with designers, researchers and managers, and found buttons that were too easy to select by mistake as well as unclear rules and messages.5

Bring senior reviewers in early. A director who sees the first concept is less likely to reject the final layout.

A feedback template you can copy

Use this structure for every round. Number each point so the designer can reply point by point.

  • Overall: Does the draft meet the brief? One or two sentences.
  • Keep: What works and must stay.
  • Must fix: Errors, brand rules, accessibility, consent. Page or slide number for each.
  • Problems to solve: What is not working and why, without prescribing the fix.
  • Optional ideas: Preferences, clearly labelled as optional.
  • Questions: Anything you need the designer to explain.
  • Decision owner and deadline: Who approves, and by when.

Before sending, check each comment against three tests. Is it specific? Does it explain why? Does it agree with the other comments?

Know when to stop

Agree the number of review rounds at the start. Each round should get smaller: the first deals with structure and concept, the second with detail, the last with proofreading only.

If a late comment would change the concept, ask whether it is worth the cost in time. Sometimes it is, for example when a figure is wrong. Often it is not. In our own practice, the drafts that turn out best are the ones reviewed early, by the right people, against a clear brief.

Do a final check on the finished file in its real setting: printed at size, or viewed on a phone. That is where the last small problems show up.

Questions people ask

How many rounds of design feedback are normal?

Many projects plan for two or three rounds: concept, detailed layout and final proof. Agree the number at the start so both sides can plan their time.

Should I send the designer my own sketch of the fix?

Only if it explains a problem more clearly than words can. Describe the problem first, and present any sketch as one possible answer, not an instruction.

What if two managers give opposite comments?

Resolve it inside your organisation before you send feedback. Name one decision owner for the project so the designer never has to choose between colleagues.

How do I give feedback on accessibility?

Point to the specific element and the standard, for example text contrast below the WCAG minimum of 4.5:1 for normal text.3 Contrast and text size can be measured, so they are fixes, not preferences.

Sources

Every numbered link in this article points to one of these sources. We checked each one in October 2026. Summaries of rules are for planning, not legal advice.

  1. 1

    AIGA Baltimore. How to give and receive a good design critique.

    Secondary sourcebaltimore.aiga.orgChecked 27 October 2026

  2. 2

    European Commission (International Partnerships). Communicating and raising EU visibility: Guidance for external actions.

    Official sourceinternational-partnerships.ec.europa.euChecked 27 October 2026

  3. 3

    W3C Web Accessibility Initiative. Understanding Success Criterion 1.4.3: Contrast (Minimum).

    Official sourcew3.orgChecked 27 October 2026

  4. 4

    UK Department for Education. Reviewing and checking content.

    Official sourcedesign.education.gov.ukChecked 27 October 2026

  5. 5

    UK Department for Education. Running design critiques to improve the service.

    Official sourcebecoming-a-teacher.design-history.education.gov.ukChecked 27 October 2026

Found a mistake? Email hello@truestoryafrica.com and we will correct it. How we check facts

Related service

Strategic communications

Media relations, key messages and spokesperson preparation that help your organisation speak clearly when it matters.

Let’s tell
the story well

Launching a policy, reporting to partners, hosting a summit or explaining a programme? We shape the message, find the human story and make it clear.

Download our company profilePDF · 42 pages · 6 MB

TrueStory Africa

presents

Real stories. Clear impact

Strategy & story
TrueStory Africa
Aerial
Fiston Nyirishema
Photography
Yuhi Irakiza Augustin
Laury Habyarimana
Video production
Hakizimana Shaban
Cinematography
Isaac Gisubizo
Benjamin Irihose
Writing
Aliane Karerangabo
Filmed in
Rwanda and across Africa
Consent
Kinyarwanda & English
Headquarters
KG 522 St, Kigali

Every photograph on this website was taken by TrueStory Africa, with consent.
No scenes were staged in the making of this website.

Share this