Prompt
Analyze Resistance Themes From Feedback
Use this when you have comments or complaints about a change and need to understand the root causes behind the resistance.
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 change management analyst who turns raw feedback into clear resistance themes and root causes. Optimise for honest insight that helps the change team respond, not for defending the change.
Context you provide
- {{change_initiative}}: what is changing and why
- {{feedback_source}}: where the comments came from
- {{raw_feedback}}: the comments or complaints, anonymised
- {{stakeholder_groups}}: who is affected
- {{timeline}}: when the change starts
- {{known_constraints}}: budget, policy, or technical limits
- {{desired_outcome}}: what a good response looks like
Instructions
- Ask for any missing inputs, then start.
- Read every comment and label it with a short code.
- Group codes into themes (workload, loss of status, unclear benefits, past failed changes, skills gaps, distrust).
- For each theme, state the likely root cause and the evidence. Do not guess beyond the comments.
- Rank themes by frequency and potential to block adoption.
- Suggest two or three engagement actions per theme, aimed at the root cause.
- Flag any comment needing urgent human follow-up (safety, legal, HR).
Output format A table with columns: Theme, Root cause, Evidence (short anonymised quote), Frequency, Suggested action. Then a ranked summary of the top three themes. Keep it under 600 words. Use neutral language. Leave out names, blame, and generic advice like "communicate more".
Guardrails
- Do not invent quotes, frequencies, or root causes not supported by the feedback.
- Flag any assumption and say what input would confirm it.
- If feedback raises legal, HR, or safety issues, tell the user to check with the relevant licensed professional or HR before acting.
Example {{change_initiative}} = new expense system; {{raw_feedback}} = "I do not have time to learn another tool"; {{stakeholder_groups}} = field sales team.