The Simulator: Run What-If Scenarios Before They Happen in Reality

Use AI to simulate stakeholder reactions, test risk responses, and pressure-test plans without real-world consequences. Catch problems in simulation, not production.

The Simulator: Run What-If Scenarios Before They Happen in Reality

Every project manager has experienced this: you present a plan, and a stakeholder raises an objection you didn't anticipate. Or a risk materializes that seemed unlikely. Or a decision has consequences you didn't foresee.

Simulation reduces these surprises.

Claude can role-play stakeholders, stress-test plans, and explore scenarios—giving you a practice environment where mistakes cost nothing and insights are invaluable.

The Value of Pre-Validation

Real-world validation is expensive:

Simulation-based validation catches problems early:

The time investment is minimal; the protection is substantial.

Stakeholder Simulation

Role-Playing Difficult Conversations

Prompt Pattern:

"Role-play as [Stakeholder Name], [their role].

Based on what I've told you about them:

  • Primary concern: [Their main worry]
  • Communication style: [Direct/Diplomatic/Data-driven/etc.]
  • Decision-making pattern: [How they typically decide]

I'm going to present [topic]. Respond as they would—including objections, questions, and concerns. Be realistic, not supportive."

Then present your topic and receive feedback from the stakeholder's perspective.

Anticipating Objections

"I need to present a budget increase request to the CFO. Based on typical CFO priorities (cost control, ROI, financial risk), what objections should I prepare for? For each objection, suggest how I should respond."

Testing Messaging

"I'm about to send this communication to the executive team:

[Paste your message]

Role-play as each executive reading this. What questions would they have? What concerns? What's unclear? What's missing?"

Risk Scenario Simulation

Pre-Mortem Analysis

"Let's run a pre-mortem. Assume this project has failed completely six months from now. Acting as a post-failure analyst, identify:

  • The most likely reasons for failure
  • Warning signs we should have noticed
  • Decisions that in hindsight were mistakes
  • External factors that could have derailed us

Be creative and thorough—the goal is to anticipate, not comfort."

Risk Response Testing

"Risk: [Describe a specific risk]

Our planned response is: [Describe mitigation]

Challenge this response:

  • What could go wrong with this mitigation?
  • What scenarios would it not address?
  • What secondary effects might it create?
  • What would a more robust response look like?"

Scenario Exploration

"Explore this scenario: Our key vendor declares bankruptcy mid-project.

Walk through:

  • Immediate impacts on project timeline and budget
  • Options for response
  • Stakeholder notifications required
  • Decision tree for next steps
  • How we could have prepared better"

Decision Simulation

Option Analysis

"I need to decide between three approaches:

Option A: [Description] Option B: [Description] Option C: [Description]

For each option, simulate the next 6 months:

  • What goes well?
  • What problems emerge?
  • What's the likely outcome?
  • What would I wish I had done differently?

Don't pick a winner—help me see the trade-offs."

Second-Order Effects

"We're about to implement this decision: [Describe decision]

Explore second and third-order effects:

  • What does this decision enable that wasn't possible before?
  • What does it constrain or make harder?
  • How might stakeholders respond to the downstream effects?
  • What unintended consequences should we monitor?"

Devil's Advocate Mode

"I've decided to [describe decision]. Play devil's advocate:

  • Make the strongest case against this decision
  • What am I not seeing?
  • What evidence would change my mind?
  • Who would disagree and why would they be right?

Push back hard—I need to stress-test this thinking."

Negotiation Practice

Difficult Conversation Rehearsal

"I need to have a difficult conversation with [Person] about [Topic].

The core issue is: [Describe] My goal is: [What I want to achieve] Their likely position is: [What they probably want]

Let's role-play this conversation. You play [Person]. Start with their opening statement, and I'll respond. After we complete the conversation, give me feedback on my approach."

Negotiation Scenario

"I'm negotiating [describe negotiation] with [describe counterparty].

My constraints: [What I can't give up] My flexibility: [Where I can compromise] Their likely constraints: [What they can't give up]

Simulate three rounds of negotiation. After each round, pause and explain:

  • What tactics they might use
  • How I should respond
  • What moves I should make"

Meeting Simulation

Presentation Dry Run

"I'm presenting this to the board tomorrow:

[Paste presentation content or talking points]

Simulate the Q&A session. Ask me challenging questions that board members typically ask. After I respond, give me feedback on my answers and suggest improvements."

Difficult Meeting Anticipation

"Tomorrow's meeting includes these attendees:

  • [Name 1]: [Role, known concerns]
  • [Name 2]: [Role, known concerns]
  • [Name 3]: [Role, known concerns]

Topic: [What we're discussing]

Predict how this meeting will go:

  • Where will conflict emerge?
  • What will be the sticking points?
  • What should I do to navigate these dynamics?
  • What's my best-case and worst-case outcome?"

Building Simulation Into Your Workflow

Before Major Decisions

Run this checklist:

  1. Devil's advocate analysis
  2. Second-order effects exploration
  3. Pre-mortem analysis
  4. Stakeholder reaction simulation

Before Difficult Communications

  1. Test messaging with stakeholder role-play
  2. Anticipate objections
  3. Refine based on feedback
  4. Prepare response frameworks

Before Important Meetings

  1. Simulate likely dynamics
  2. Practice difficult conversations
  3. Prepare for challenging questions
  4. Identify potential landmines

The Confidence Effect

Simulation builds confidence—not false confidence, but grounded confidence based on preparation.

When you've already explored how stakeholders might react, you're not surprised by their responses. When you've stress-tested your plan, you know where vulnerabilities exist. When you've practiced difficult conversations, the actual conversation feels familiar.

This preparation shows. Stakeholders sense when someone has thought deeply versus when they're improvising. Simulation enables that depth of preparation in a fraction of the traditional time.

Limitations to Acknowledge

Simulation has boundaries:

Claude doesn't know your stakeholders personally. Its role-play is based on patterns and your descriptions, not actual knowledge of individuals.

Real situations have nuances simulations miss. Use simulation to prepare, not to replace judgment in the moment.

Simulation can create false confidence if you assume you've covered everything. Stay humble and responsive.

The goal is better preparation, not prediction.


Ready to Transform Your Project Management Practice?

This article is part of a comprehensive guide to AI-powered project management. Learn how to save 10-15 hours per week, automate repetitive workflows, and build your own private AI command center.

Explore the Complete Book: Claude for Project Managers