Verified against ChatGPT · 2026-08-13
Sequence a reorg communication plan so nobody hears their new reality from a rumor first
Builds a phased communication plan for a team reorganization that sequences who hears what and when, specifically to prevent the common failure where affected people learn their fate secondhand before the official announcement.
The prompt
Ready to copy — highlighted parts are example details you can swap.
Build a phased communication plan for Merging the Support and Success teams into one Customer Experience org under a single new director., sequenced specifically so no one directly affected hears about their situation secondhand before they hear it from someone who should have told them directly. WHO IS AFFECTED AND HOW 12 Support agents and 8 Success managers; two of the current team leads will no longer have direct reports and move into individual contributor senior roles. TIMELINE CONSTRAINTS New org needs to be announced company-wide within 10 business days due to an already-scheduled all-hands. WHAT CANNOT BE SHARED YET AND WHY The new director hasn't been formally offered the role yet, so their name can't be confirmed until that's signed. BIGGEST LEAK OR RUMOR RISK One of the affected team leads already suspects something is happening because of recent closed-door meetings and has been asking pointed questions. STAGE 1 — WHO NEEDS TO KNOW BEFORE ANYONE ELSE List, in strict order, exactly who is told first, second, third — this is not a simultaneous announcement; identify every person whose role changes and make sure each one is told directly by their own manager before any broader announcement goes out, since the single worst version of this rollout is someone learning their team is being dissolved from a company-wide email rather than from their manager first. STAGE 2 — MANAGER ENABLEMENT Before Stage 1 conversations happen, managers delivering the direct news need a short script and an FAQ of the hardest questions their specific reports are likely to ask, tailored to what's actually changing for that group, not a generic "here's how to talk about change" doc. STAGE 3 — BROADER ANNOUNCEMENT Draft the wider announcement (team meeting or company-wide as appropriate) that comes only after Stage 1 is fully complete, and explicitly state within the plan the minimum time gap required between Stage 1 completing and Stage 3 going out. STAGE 4 — LEAK CONTINGENCY Given the stated leak risk, write a short contingency: what happens to the sequencing if word starts spreading before Stage 1 is complete — name the specific trigger for accelerating the timeline and what gets compressed or skipped if that trigger happens. WHAT NOT TO DO Do not write vague talking points that avoid stating what's actually changing — people experiencing a reorg can tell immediately when language is being managed rather than informative, and vagueness in this specific context reads as either bad news being hidden or the plan not actually being finalized, both of which are worse than a clear, direct statement of what's changing and what isn't yet decided. OUTPUT FORMAT 1. Stage 1 order of who's told, by whom, and roughly when. 2. Stage 2 manager script and FAQ. 3. Stage 3 broader announcement draft, with the required minimum gap after Stage 1 stated explicitly. 4. Stage 4 leak contingency plan.
Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
The single most damaging and common failure in reorg rollouts is sequencing, not content — people can generally handle difficult news about their role changing, but they cannot forgive hearing it secondhand or from a company-wide email before their own manager told them directly, and that failure mode is purely about order and timing, which is exactly why this prompt forces a strict, explicit ordering of who's told first rather than treating communication as a single document to draft. Requiring the manager-enablement stage to happen before the direct conversations, with a script and FAQ tailored to the specific group's actual likely questions rather than a generic change-communication template, matters because a manager delivering news they haven't been prepared to handle will improvise under pressure and often either overpromise ("nothing will really change" when things clearly will) or underdeliver information the report actually needs, and GPT-5.1 can produce a genuinely tailored FAQ here because the specific changes were stated as input, rather than falling back to generic change-management talking points that don't address what this particular group will actually ask. Explicitly requiring a stated minimum time gap between Stage 1 completing and the broader announcement forces a concrete commitment that prevents the common real-world failure where Stage 1 conversations and the broader announcement get compressed together under time pressure, collapsing the very sequencing the plan exists to protect. The leak-contingency stage exists because reorg plans are frequently disrupted by exactly the risk described in the input — someone already suspects something — and a plan without an explicit contingency for that leaves whoever is running the rollout without a pre-decided answer when it happens, forcing an improvised decision about whether to accelerate under exactly the kind of time pressure that produces bad judgment calls. The explicit instruction against vague talking points matters because a model asked to write "communications for a sensitive reorg" will, without a direct counter-instruction, drift toward safe, non-specific corporate language, which in this specific context reads to affected employees as evasive rather than careful, undermining the trust the entire communication plan depends on.
What you get back
Stage 1 order: 1) the two current team leads losing direct reports, told individually by their VP, day 1 morning. 2) the 20 affected agents/managers, told by their current direct manager in 1:1s, day 1 afternoon through day 2 morning. Stage 2: manager script includes a direct line — 'Your role and team structure are changing; here's specifically what's different and what isn't decided yet' — plus an FAQ answering whether current reports change (yes, to the new director once confirmed) and whether compensation changes (no, confirm explicitly if true). Stage 3: company-wide announcement goes out no earlier than 24 hours after all Stage 1 conversations are confirmed complete. Stage 4: if the team lead who already suspects something asks directly before their scheduled Stage 1 conversation, the VP moves that one conversation up immediately rather than risk them hearing it from a peer first, compressing only that individual's timing, not the whole sequence.
Verified against
ChatGPT GPT-5.1 · 2026-08-13
Changelog
- 2026-08-13 — Initial publish, verified against ChatGPT GPT-5.1.
Need this built into your business?
If a prompt isn't enough — what Scult builds, built and maintained for you — that's Scult's day job.
EXPLORE WHAT SCULT BUILDS
