Difficult and Resistant Stakeholder Management Strategy
Maps and creates personalized engagement plans for stakeholders who resist, sabotage, or hinder project progress.
Identify the most critical and resistant stakeholders, understand their real motivations, and create engagement strategies that transform resistance into support or at least neutrality.
At a glance
Access
Free prompt
Open to copy without upgrading.
Prompt objective
Identify the most critical and resistant stakeholders, understand their real motivations, and create engagement strategies that transform resistance into support or at least neutrality.
Real use case
TechBanking is implementing a new compliance system that will automate 30% of the back-office team's manual tasks. The operations director boycotts meetings, the middle-office manager claims the system will \\\\\\\\
Customize these fields first
Replace the placeholders with your own context before you run the prompt. That usually improves the first output more than adding more instructions later.
Prompt
Create a complete difficult stakeholder management strategy for the following project:\\\\\\\\n\\\\\\\\nProject: [PROJECT NAME]\\\\\\\\nDescription: [WHAT THE PROJECT DOES AND WHAT CHANGES IT CAUSES]\\\\\\\\nProblematic stakeholder 1: [NAME/TITLE — describe the behavior]\\\\\\\\nProblematic stakeholder 2: [NAME/TITLE — describe the behavior]\\\\\\\\nProblematic stakeholder 3: [NAME/TITLE — describe the behavior]\\\\\\\\nCurrent impact of resistance on the project: [DESCRIBE: delays, blockers, lack of information]\\\\\\\\nInfluence resources available to you: [ENGAGED SPONSOR? LEADERSHIP ACCESS? DATA?]\\\\\\\\n\\\\\\\\n## 1) Stakeholder Analysis — Power x Interest x Attitude Matrix\\\\\\\\nFor each listed stakeholder:\\\\\\\\n- Power of influence on the project (1-5)\\\\\\\\n- Interest in the outcome (1-5)\\\\\\\\n- Current attitude: Champion / Neutral / Resistant / Saboteur\\\\\\\\n- Desired position at end: what is acceptable?\\\\\\\\n\\\\\\\\n## 2) Resistance Diagnosis\\\\\\\\nFor each resistant stakeholder, analyze:\\\\\\\\n- **Fear**: What are they afraid of losing? (power, job, routine, prestige)\\\\\\\\n- **Non-understanding**: What do they not understand about the project?\\\\\\\\n- **Legitimate disagreement**: Are they right about anything?\\\\\\\\n- **History**: Previous projects that failed and created distrust\\\\\\\\n- **Hidden interests**: What do they want but not say?\\\\\\\\n- **Influencers**: Who does this person respect and listen to?\\\\\\\\n\\\\\\\\n## 3) Engagement Strategies by Profile\\\\\\\\n\\\\\\\\n**For the active Saboteur:**\\\\\\\\n- 1:1 meeting to genuinely listen (not to convince)\\\\\\\\n- Technique: Let them define what success looks like for them\\\\\\\\n- Offer a relevant role in the project (ownership creates commitment)\\\\\\\\n- Controlled escalation: when and how to involve the sponsor\\\\\\\\n- Document all requests and responses for PM protection\\\\\\\\n\\\\\\\\n**For the Passive Resister (doesn't respond, doesn't show up):**\\\\\\\\n- Change the communication channel (if email doesn't work, try in-person/phone)\\\\\\\\n- Reduce friction: shorter meetings, more specific questions\\\\\\\\n- Involve the stakeholder's direct manager to demand participation\\\\\\\\n- Create legitimate artificial urgency: \\\\\\\\
Open directly in an AI — the text is pre-filled:
How to use this prompt
- 1Replace the key placeholders first: PROJECT NAME, WHAT THE PROJECT DOES AND WHAT CHANGES IT CAUSES, NAME/TITLE — describe the behavior, DESCRIBE: delays, blockers, lack of information.
- 2Replace any bracketed placeholders like [this] with your own context.
- 3Add extra background information when you want more tailored results.
- 4Combine multiple prompts in one conversation when you need a richer output.
- 5Save your best-performing prompts so they are easy to reuse later.
Next best step
Open the guide first, then branch only if you still need more.
A guide for choosing prompts, tools, courses, and workflows without creating expensive tool sprawl.
If this prompt is close but not quite right, generate variants next. If the job is recurring, move into the course library after the guide.
Related prompts
View allWork Breakdown Structure (WBS) for Corporate IT Projects
Creates a project breakdown structure for technology initiatives.
Best for
Develop a complete WBS that decomposes complex IT deliverables into manageable work packages, facilitating estimation and responsibility assignment.
Master Schedule with Dependencies and Critical Path
Generates a detailed schedule with critical path analysis.
Best for
Build a master schedule that identifies the critical path, float, and interdependencies between activities to ensure on-time delivery.
Project Charter for Executive Approval
Charter template for formal project authorization.
Best for
Create a professional Project Charter that formalizes scope, objectives, assumptions, and constraints to secure sponsor approval and align stakeholder expectations.
Scope Management Plan with Change Control
Defines processes to manage scope and prevent scope creep.
Best for
Establish clear scope definition, validation, and control processes that prevent scope creep and ensure changes are formally evaluated.
Explore other prompt categories
Move sideways into adjacent libraries when the current category is not the full answer.
Free browsing stays open. Premium prompts unlock the reusable workflow layer.
Use the guides and role paths to validate the job first. Upgrade when you want the full prompt text, editable premium prompts, and the surrounding course paths in one place.
Free access
- Browse guides, role paths, and category pages.
- Preview prompts before you decide to upgrade.
- Find the right starting point without friction.
Membership access
- Unlock premium prompts and the full copy text.
- See more workflow paths and course connections.
- Keep the reusable templates in one place.
