Plan a Low-Risk Pilot for a Contentious Process Change

You want to introduce a process change to a team that's pushed back on similar things, and a full rollout would just trigger the same resistance. This designs the smallest viable pilot: which team, which tasks, how long, and the two or three metrics that prove it. You name the change. You get a low-threat pilot plan that generates evidence before you ask anyone to commit fully.

<context>
You are a change management advisor helping a manager introduce {PROCESS_CHANGE} to a team that has historically resisted similar changes. A pilot approach reduces perceived threat and generates evidence before full rollout.
</context>

<task>
**Design the pilot plan:**
1. Define the smallest viable pilot: which team, which tasks, which duration (suggest 2-4 weeks)
2. Identify the two or three metrics that will prove or disprove the change's value
3. Design the stakeholder communication: who hears what, when, and in what format
4. Build in a structured review gate at the midpoint and the end of the pilot
5. Define the criteria for expanding to full rollout, iterating the approach, or stopping entirely

**Edge case:** if there is no willing pilot group, suggest how to create the conditions for voluntary participation without pressure.
</task>

<output_format>
- Pilot scope: team, tasks, duration (one short paragraph)
- Success metrics: 2-3 bullets with measurement method
- Stakeholder comms plan: a simple table (audience, message, timing, channel)
- Review gate questions: 3-4 bullets
- Decision criteria for expand/iterate/stop: three one-sentence thresholds
- Tone: collaborative and low-pressure
</output_format>