Decoding vague feedback into a concrete revision plan
"Make the logo pop." "It needs more wow." "I'll know it when I see it." Ambiguous feedback is the tax on client work, and guessing wrong burns a revision round you may not be paid for. Feeding the raw comments to AI to sort them into concrete, actionable changes — and to surface the questions you still need answered — turns a vague email into a plan before you touch the file.
You are a design project manager. I'll paste raw client feedback on a {{deliverable}}. Turn it into an actionable revision plan. Client feedback (verbatim): {{client_feedback}} The current design and its rationale (so you can interpret the feedback against it): {{design_context}} Produce: 1. A table with columns: Feedback (their words) | Likely concrete meaning | Specific change to try | Confidence (high/medium/low). 2. A short list of clarifying questions for anything low-confidence or contradictory — the questions I must ask before making changes. 3. A flag for any feedback that conflicts with the agreed brief goals, so I can raise it rather than silently follow it. Constraints: - Do not present a guess about the client's intent as fact. When feedback is ambiguous, mark it low confidence and put it in the questions list. - Do not invent feedback I didn't paste, and do not soften or drop any comment. - Keep interpretations tied to the design context I gave you.
Fill in your details and the prompt updates live — then copy.
| Feedback | Likely meaning | Change to try | Confidence | | "Make it pop more" | More contrast or focal emphasis, not necessarily brighter | Increase icon-to-wordmark size contrast; test a warmer accent | Low | | "Blue feels corporate" | Navy reads cold for a craft brand | Try a warmer navy or a cream-forward version | Medium | | "Feel more 'us'" | Undefined — needs input | Hold until clarified | Low | Questions to ask: What does "pop" look like to you — can you point to a logo that pops? When you say "more us," which of your values is missing? Is "too plain" about the icon, the type, or the color? Brief conflict flag: a brighter color may work against the agreed "premium, not loud" goal — worth raising before changing it.
The full workflow
- Paste the feedback exactly as written, including the offhand and contradictory bits
- Run the prompt, then send the clarifying questions before opening the design file
- Raise any brief-conflict flags with the client instead of quietly complying
- Log the agreed changes so the revision round has a defined, signed-off scope
Watch out for
Treat the AI's interpretations as hypotheses, not answers. Acting on a confident-sounding guess about what a client 'really meant' is how you burn an unpaid revision round — send the clarifying questions first.
Keep pasted feedback free of confidential context. The comments alone are usually fine, but strip any attached internal plans, customer data, or unreleased material before it goes into a consumer tool.
Where this comes from
Every use case on this site is grounded in real reports from working graphic designers — not invented by us.