Give feedback someone can act on
QUICK REFERENCE
Useful feedback connects an observation to a purpose. Instead of asking someone to “make it better”, point to the specific part, explain what the reader or user needs and describe the decision you want to resolve. Leave room for the person doing the work to suggest the right fix.
When to use this
Use this when reviewing a draft, slide, page or creative deliverable. It is particularly helpful when several reviewers have different preferences.
Know these three terms
Observation
Something you can point to in the work.
Impact
Why that detail matters to the intended reader or task.
Request
The change or decision you want considered; it may still need discussion.
A practical way to do it
Start with the agreed purpose
Identify the audience and intended action before judging the execution. A dense slide may be suitable as a reference sheet and unsuitable for a short spoken presentation. The intended use changes the feedback.
Describe the visible issue
Name the section or element and explain the difficulty. Keep preferences separate from requirements. “I prefer blue” and “the link is hard to distinguish” are different types of feedback and should not be presented as equivalent evidence.
Consolidate before sending
Combine duplicate comments and highlight contradictions. Ask the decision-maker to resolve incompatible requests. Send one coherent review when possible, with important corrections separated from optional ideas.
At a glance
| Loose comment | More actionable feedback | What remains open |
|---|---|---|
| Too much text | The opening asks readers to remember six points before finding the action. | Which two points are essential here? |
| Make it modern | The brief does not define what “modern” means. | Which reference or user need should guide the change? |
| Move everything up | The first action sits below a long introduction. | Can the introduction be shortened without losing its purpose? |
A small example
Fictional example: two reviewers ask for a shorter page and more explanatory detail. The consolidated feedback keeps the short introduction, suggests placing the extra explanation in a clearly labelled section and asks the owner to choose which information must be visible first. It records a trade-off rather than pretending both requests are automatically compatible.
Copy this working template
Use the fields directly in your own notes. AI is optional; check any AI-prepared version against your facts.
Part of the work:
Purpose or user action:
What I observed:
Why it matters:
Required correction or optional suggestion:
Decision / clarification needed:
How we will check the revision:Check before moving on
- The comment points to a specific part of the work.
- An observation is not being confused with a personal preference.
- Required corrections are separate from optional exploration.
- Conflicting reviewer requests have an owner for the decision.
Common questions
Should I prescribe the exact solution?
Specify it when a confirmed requirement demands it. Otherwise explain the problem and invite a proposal. A reviewer can identify a real issue without already knowing the best implementation.
What if I only know that something feels wrong?
Describe where you hesitate, what you expected and what made the task difficult. That is more useful than inventing a technical diagnosis. Ask the person doing the work to help investigate the cause.
Continue with your task
Browse the other quick references below.
