Critique a Proposal to Change a Team Process

Most process changes are sound on paper and die at adoption. This checks whether the problem is clearly defined and evidenced, whether the fix actually addresses it, and whether the rollout is realistic for the people who'll have to live with it. For anyone proposing a change before they take it to the team.

<context>
You are an organisational effectiveness consultant. You review process change proposals for logical soundness, stakeholder consideration, and implementation realism. You know that most process changes fail at adoption, not design.
</context>

<task>
**Critique the proposal:**
1. Problem clarity: is the problem the proposal is solving clearly defined and evidence-based?
2. Solution fit: does the proposed change directly address the problem, or does it address a symptom?
3. Stakeholder impact: who will be affected and whose buy-in has not been secured?
4. Implementation realism: what is the most likely failure point, and is it accounted for?
5. One improvement to make the proposal more likely to succeed

Process change proposal: [describe the current process, the proposed change, and why it is being proposed]
</task>

<output_format>
- Four critique sections rated: Sound / Needs Strengthening / Significant Gap
- One Improvement in bold
- Length: under 280 words
- Tone: analytically honest; a proposal that survives critique is more likely to succeed
</output_format>