Rehearse stakeholder objections before a proposal meeting
Review a proposal through several stakeholder perspectives using known priorities and previous discussions. Use the simulated debate to uncover unanswered questions and improve the supporting evidence.
How this works
Review a proposal through several stakeholder perspectives using known priorities and previous discussions. Use the simulated debate to uncover unanswered questions and improve the supporting evidence. Use this before a proposal meeting to test whether the argument addresses known stakeholder priorities. The rehearsal should uncover evidence gaps and tradeoffs rather than pretend to predict people or secure their approval.
Translate documented responsibilities and prior statements into distinct review perspectives. Challenge the proposal from each perspective, record possible objections and improve the supporting evidence. Label all simulated reactions as hypotheses and confirm important concerns with real stakeholders through the normal process.
Before you start
Proposal draft
Obtain the decision requested, evidence and assumptions.
Stakeholder context
Use explicit priorities, responsibilities and relevant prior discussions.
Meeting goal
Define what the owner wants to decide or learn.
Prepare the inputs
- proposal
- Required
options, costs, benefits and risks
Separate estimates from measured facts.
- stakeholder_evidence
- Required
role, stated priority and source
Avoid personality or motive inference.
- decision_constraints
- Required
authority, resources and nonnegotiable requirements
Do not invent approval criteria.
- rehearsal_scope
- Required
perspectives and key questions
Keep the exercise focused on the proposal.
Implementation, step by step
Map the decision
- Identify the proposal's claims, assumptions and requested commitment.
- List evidence needed for the decision rather than for persuasion alone.
Checkpoint: The argument has a clear structure.
Build factual perspectives
- Summarize each role's documented concerns and responsibilities.
- Mark missing context instead of filling it with stereotypes.
Checkpoint: The simulated viewpoints have a defensible basis.
Generate objections
- Challenge cost, feasibility, operational impact and alternatives from those perspectives.
- Keep reactions explicitly hypothetical and avoid attributing them to actual people.
Checkpoint: The rehearsal produces useful questions.
Improve the proposal
- Find evidence or revise claims to address legitimate gaps.
- Retain unresolved tradeoffs instead of producing artificial consensus.
Checkpoint: The proposal becomes more reviewable.
Prepare meeting responses
- Draft concise responses and questions for real discussion.
- Distinguish known answers from matters requiring stakeholder input.
Checkpoint: The owner can enter the meeting prepared.
Decisions along the way
Objection depends on an unsupported assumption
Label it speculative and ask whether it matters.
Perspectives agree too easily
Test a meaningful counterexample rather than treating agreement as validation.
Response needs an unapproved promise
Replace it with an option or decision request.
What you will produce
proposal-rehearsal.md
MarkdownA clearly hypothetical preparation record.
Include: perspective · possible_objection · evidence · response · gap
proposal-revisions.md
MarkdownA focused set of improvements.
Include: claim · change · reason · remaining_question
Check the result
- Verify stakeholder context comes from explicit evidence.
- Confirm simulated opinions are never described as actual feedback.
- Check responses do not overstate facts or commitments.
- Ensure unresolved tradeoffs remain visible.
When something goes wrong
Assistant flatters the proposal
Ask for concrete failure conditions and contrary evidence.
Stakeholder context is outdated
Refresh it or use role-level questions only.
Rehearsal expands into personal judgments
Return to documented responsibilities and proposal facts.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Synthetic: rehearse an automation proposal.
Inputs
Operations previously requested reliable exception handling; finance requested a cost baseline. The proposal has a demo but no measured review cost.
Expected result
Synthetic result: simulate questions about failure recovery and total operating cost, add those evidence gaps to the proposal, and avoid claiming either stakeholder would approve.
Run a small pilot
Start small
Rehearse one proposal with a few documented perspectives.
Record the baseline
Record gaps found and changes useful in the real meeting.
Agree success criteria
Agree evidence quality and preparation usefulness before reuse.
Stop or revise
Stop treating simulated agreement as real consultation or approval.
Keep the scope clear
- Generated reactions are hypotheses about questions, not predictions of people.
- The exercise cannot authorize commitments or represent stakeholder consent.
Check before using
Treat simulated reactions as hypotheses. Confirm concerns with the real stakeholders; generated agreement does not establish approval.
Business activities
- Coordinate meetings and follow-ups
- Plan products and business changes
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Draft proposal · Authorized notes about stakeholder priorities and earlier discussions
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow