How to Give Creators Useful Feedback

What matters most

Good required feedback is objective: a factual error, missing disclosure, unreadable mandatory text, wrong link, prohibited claim, unapproved asset, or absent deliverable. Good optional feedback presents an audience or performance hypothesis.

Explain the underlying need instead of writing the creator's line. 'The audience needs to understand this is available only in Canada' gives more room than replacing a paragraph without context.

Use timestamps, screenshots, copy excerpts, and one numbered list. Avoid vague notes such as make it pop, more premium, on brand, or not quite right unless the team defines the observable outcome.

A practical workflow

1. 01

   Collect stakeholder input and remove duplication or contradiction.

2. 02

   Classify each note as required, suggested, question, or new scope.

3. 03

   State location, issue, reason, evidence, and acceptable outcome.

4. 04

   Invite the creator's solution and answer questions quickly.

5. 05

   Confirm closure item by item and preserve the approved version.

Describe the problem, not the solution

The instinct in review is to write the fix: change this line to that line, move this section earlier, cut this joke. It feels efficient and it discards the reason you hired the person.

State what is wrong and why it matters instead, then let them solve it. The audience will not understand this is only available in one country is a problem, and the creator can solve it in their own voice in a way that fits their edit. Replacing their sentence with yours produces a piece with a visible seam where the brand copy starts, which viewers notice and discount.

The exception is where precision is the requirement: mandated legal wording, a specific claim boundary, an exact product name. Mark those as verbatim and explain that they are, so the creator understands the constraint is external rather than a preference dressed up as a rule.

Label required and suggested, every time

The single highest-value habit in review is marking each note as required or suggested. It costs a word per comment and it resolves most of the conflict that otherwise plays out over two rounds.

Without the label, every comment carries the implicit weight of the client, so creators treat all of them as instructions. They will implement a passing thought about the thumbnail with the same seriousness as a compliance requirement, and the content degrades under the accumulated weight of preferences nobody intended to mandate.

The labelling also disciplines the brand side. Working out whether a note is genuinely required often reveals that it is not, and that it should either be dropped or offered as a hypothesis about what might perform better. A suggestion the creator declines is a normal outcome, not a compliance failure.

Say what worked, because the next version depends on it

Feedback that lists only problems reliably makes the next version worse, and the mechanism is straightforward: the creator does not know which parts to protect, so they revise broadly and the thing that was working goes with everything else.

Naming what to keep is therefore functional rather than diplomatic. The opening is doing exactly what we needed, keep it, and this demonstration section is the strongest part is information the reviser needs in order to change the right things.

It also affects whether the relationship survives the campaign. Creators receive a great deal of undifferentiated correction, and being told specifically what worked is uncommon enough to be memorable. It costs two sentences and it is one of the cheapest things a brand can do to be worth working with again.

Common mistakes

• Sending every stakeholder comment without one decision owner.
• Giving a rewrite without explaining the factual or audience problem.
• Calling a new idea a correction covered by existing revisions.
• Using vague aesthetic language with no observable criterion.

Working checklist

• Feedback is consolidated and internally resolved.
• Required and optional notes are clearly different.
• Every note has location, reason, and outcome.
• The creator retains room to solve creative execution.
• Closure and approval are recorded.

Questions and answers

How quickly should feedback be returned?

Within the turnaround you committed to at onboarding, and consolidated into one response rather than trickled. Late feedback compresses production time rather than review time, so the cost lands on the part of the process that determines quality, and it is the behaviour creators most often cite when declining repeat work.

What if internal stakeholders disagree?

Resolve it before sending. Contradictory notes leave the creator arbitrating between people they do not know, and whichever way they choose, someone is dissatisfied and a further round follows. One owner consolidates, decides what is required, and sends a single coherent response with priorities attached.

How do you tell a creator the content is not good?

Specifically, against the brief, in terms of what the content needed to do and did not. Not quite there is not actionable and reads as a taste judgement. If the problem is genuinely subjective and no agreed criterion was missed, say that honestly, since it is a request rather than a correction and it may carry a cost.

Can you ask a creator to change the hook?

You can suggest it, and it should usually be a suggestion. The opening is where a creator's judgement about their own audience is most valuable and a brand's instinct is least reliable. If a hook creates a real problem, a claim, a safety issue, a misleading impression, name the problem and let them re-solve it.