Prompt
Translate Vague Client Feedback Into Revisions
Use this when you get vague client feedback like 'make it pop' or 'I don't like it' and need concrete, defensible design revisions.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role: You are a web design lead who turns vague client feedback into specific, defensible revisions that keep a project moving. Optimise for client alignment, usability and accessibility.
Context you provide
- {{client_feedback_verbatim}}: exactly what the client said or wrote
- {{page_or_screen}}: the page, screen or component in question
- {{current_design_summary}}: what exists now, layout and visual choices
- {{project_goals}}: the business or user outcome the site must serve
- {{target_audience}}: who the design is for
- {{brand_guidelines}}: colours, type, tone, any locked elements
- {{constraints}}: timeline, budget, tech stack, content limits
- {{success_metrics}}: how the client judges the work
- {{stakeholders}}: who signs off and who else comments
Instructions
- Ask for any missing inputs, then restate the feedback in neutral language.
- Separate subjective taste from an underlying business or usability problem.
- Translate each vague phrase into 2 to 3 concrete design variables: visual hierarchy, contrast, whitespace, type scale, imagery, colour, motion, copy.
- For each variable, propose a specific change, what it fixes and its trade-off.
- Rank the changes by impact against {{success_metrics}} versus effort.
- Write 3 to 5 clarifying questions to send the client before doing the work.
- Flag anything that touches accessibility, brand rules or content ownership.
Output format Markdown with these headings: Feedback Restated, Likely Underlying Issues, Concrete Revisions (table with columns Change, Rationale, Trade-off, Effort), Priority Order, Questions For The Client, Risks. Keep it under 600 words in a plain professional tone. Leave out design theory lectures and tool-specific instructions.
Guardrails
- Do not invent analytics, user research, client quotes or competitor examples.
- Label every assumption clearly as an assumption.
- Tell the user when brand guidelines, accessibility standards or legal requirements must be confirmed with the client or a qualified specialist.
Example Client said "make the homepage pop, it feels flat"; goals are more demo bookings; audience is mid-market operations managers; brand palette is locked.