Most prompts fail because they’re vague about intent and audience. The READ model anchors every prompt to four parts so outputs are clearer and more usable in real change delivery

1) Understand a Change Quickly (Discovery / CIA starter)
R: Act as a Business Change Manager.
E: Produce a concise “what/why/who/when” summary of this change.
A: Project team and stakeholders.
D: 3–4 bullets; list impacted groups; note top risks/questions.
Input: [Paste brief or notes]
Human Check: Validate impacts and risks with SMEs; remove duplication

2) Cluster Impacts by Theme
R: Business Change Manager.
E: Group draft impacts by theme and severity.
A: Change team.
D: Themes = People, Process, Tech, Data/Policy; severity Low/Med/High.
Input: [Paste first‑pass impacts]
Human Check: Align themes with programme taxonomy.

3) Stakeholder Segmentation (Power–Interest)
R: Business Change Manager.
E: Segment stakeholders by role, interest, and power.
A: Engagement workstream.
D: Table: Name/Role • Power • Interest • Engagement Priority.
Input: [Paste stakeholder list/roles]
Human Check: Adjust for real influence, not title.

4) Segment Engagement Notes (per group)
R: Business Change Manager.
E: Draft objectives, core messages, cadence, and channel per segment.
A: Engagement & comms.
D: Keep to bullets; avoid jargon; tone supportive.
Input: [Paste segments or audience summary]
Human Check: Tune tone and frequency to local culture.

5) Message Map (Change Comms)
R: BC Manager & comms partner.
E: Create a message map for [initiative].
A: [Specify audience: frontline / managers / execs].
D: Table: Audience • Core message • Why it matters • What’s changing • CTA • Channel • Tone.
Input: [Paste change summary]
Human Check: Verify actions/dates; remove jargon.

6) Two‑Tone Announcement (Leaders vs Frontline)
R: BC Manager.
E: Draft 2 versions of the same announcement.
A: (1) Senior leaders/managers; (2) Frontline teams.
D: Leaders ~200 words; Frontline ≤120 words; plain English.
Input: [Paste the announcement content]
Human Check: Facts, tone, named support contact

7) Adoption Risks (Top 5)
R: BC Manager.
E: Extract and rate top 5 adoption risks with early mitigations.
A: Delivery leads.
D: Likelihood/Impact; mitigation in one line each.
Input: [Paste discovery notes]
Human Check: Validate L/I with project leads

8) Day‑1 Hypercare Plan (Go‑Live)
R: BC Manager with Service Ops lens.
E: Draft a day‑1 hypercare plan.
A: Support & change leads.
D: Hours, channels, triage flow, escalation, reporting cadence.
Input: [Paste support model context]
Human Check: Confirm with Service/Support owner

9) Training Objectives (from process change)
R: Learning designer with BC context.
E: Convert process change into 4–6 learning objectives.
A: Learners; managers.
D: Action verbs (Bloom’s); add assessment ideas.
Input: [Paste process change notes]
Human Check: Objectives are measurable and relevant

10) FAQs from SME Notes
R: BC Manager & editor.
E: Turn SME notes into a short FAQ.
A: Frontline & managers.
D: Group by topic; flag any answers needing policy approval.
Input: [Paste SME notes]
Human Check: Verify answers; secure approvals before publishing.

Add Human Check at the end: what you will verify, tailor, or remove before sharing.