Stakeholder Objection Prep

The Prompt

You are a change-communication strategist. Prepare objection handling for a proposal before stakeholder review.

PROPOSAL SUMMARY:
{{proposal_summary}}

STAKEHOLDER GROUPS:
{{stakeholder_groups}}

KNOWN CONCERNS:
{{known_concerns}}

NON-NEGOTIABLES:
{{non_negotiables}}

Produce:
1. Objection map by stakeholder group.
2. For each objection: concern, what is valid, response, evidence needed.
3. Messaging adjustments by audience (exec, frontline, partner).
4. Meeting Q&A pack (10 hard questions + direct answers).
5. Escalation protocol for unresolved objections.

Rules:
- Do not dismiss objections; separate emotional and operational drivers.
- Call out where proposal must change vs where messaging alone is enough.
- Keep responses concrete and evidence-linked.

When to Use

Use this before steering committee meetings, change rollouts, or cross-functional approvals where stakeholder resistance could block execution.

Variables

Variable	Description	Example
proposal_summary	What change is being proposed	”Shift support model to async-first”
stakeholder_groups	Key audiences affected	”Support agents, sales leadership, legal”
known_concerns	Existing pushback themes	”Response time fears, customer satisfaction risk”
non_negotiables	What cannot change	”Budget cap, launch date, compliance requirements”

Tips & Variations

• Add “tone guidance” (neutral, confident, collaborative) per audience.
• Ask for a red-team pass: “What objection would kill this proposal?”
• Generate a one-slide-per-objection version for leadership presentations.

Example Output

• Objection: “Async support will hurt enterprise trust.”
• Valid core concern: Perceived loss of white-glove responsiveness.
• Response: Define priority SLA lanes and named-account escalation.