Rehearse three breach-disclosure strategies overnight.
Three response strategies run through Simulate. The proactive disclosure and customer compensation in strategy (b) result in net-positive brand recovery by day 20. Strategy (a), the minimal legal statement, festers into sustained negative narrative for 60 simulated days. The team pre-drafts strategy (b) before anything happens.
Run Simulate- 1
Describe the task
Simulate can rehearse a breach disclosure against a synthetic public before the breach is ever announced, running each candidate response strategy through weeks of agent reaction so you know which one recovers brand trust and which one festers. For a healthcare company, disclosure is a one-shot event with a narrow window; the difference between a strategy that breaks even by day 20 and one that bleeds for two months is decided the moment you speak.
The more honestly you draft the strategies, the more useful the rehearsal. Give Simulate each response option as real comms, describe the affected public accurately, and ask it to model recovery over time, not just first-day sentiment, and it will find the strategy whose trust curve actually crosses back into positive.
Rehearse three breach-disclosure strategies against our affected public, defined in affected-public.json (patients, families, and press). The three response strategies, drafted as real statements in response-drafts.md: - Strategy A: minimal legal statement, no compensation - Strategy B: proactive detailed disclosure with customer compensation - Strategy C: phased disclosure, hold detail until the investigation closes Run 60 simulated days of reaction for each. For every strategy, track the brand-trust curve day by day, the day it breaks even (if it does), and any sustained negative narrative. Rank by day-60 recovery and name the biggest risk of the winner.
- 2
Give Simulate context
In a Simulate workspace, point the run at an affected-public profile that reflects who actually bears the breach, patients whose records were exposed react very differently from the general public. Trust recovery depends on that composition, so the profile has to carry it.
Draft each response strategy as the actual statement you would publish, tone, level of detail, whether compensation is named. Simulate reads the statement itself; "we’ll be transparent" and a specific transparent statement produce very different curves.
Required contextEach response strategy written as the real statement you would issue, tone and detail includedAn affected-public profile, who was impacted, how directly, and how they currently regard youOptional contextA comparable industry breach and its public aftermath so the model calibrates recovery paceRegulatory disclosure constraints so no simulated strategy assumes something you legally cannot sayYour standing brand-trust baseline so recovery is measured against where you actually startresponse-drafts.mdaffected-public.jsonpeer-breach-aftermath.csv - 3
What Simulate creates
Simulate runs each disclosure strategy through 60 days of reaction and tracks brand trust as a curve rather than a snapshot. You get the day each strategy breaks even (or the fact that it never does), the strategies that harden into a sustained negative narrative, and a ranked recommendation you can pre-draft against.
From Simulate: Rehearsed 3 disclosure strategies over 60 days against affected-public.json.
Day 20Break-even under Strategy B60Days of festering under Strategy A3Strategies rehearsedNet-positive recovery1 strategyStrategy Break-even day Day-60 trust Biggest risk B: Proactive + compensation Day 20 Net positive Compensation cost, and a "buying silence" read if under-explained No recovery in window2 strategiesStrategy Break-even day Day-60 trust Failure mode C: Phased disclosure Not reached Slightly negative “What else are they holding?” builds each week A: Minimal legal statement Not reached Sustained negative Press fills the silence; narrative festers 60 days "Strategy B is the only one that crosses back into positive trust inside the window, it breaks even around day 20, while the minimal statement festers for the full 60. The one risk on B is the compensation reading as ‘buying silence’ if it isn’t framed as accountability. Want me to pre-draft the day-one B statement and hold it ready, or model how B holds up if the breach leaks before you announce?"
- 4
Follow-up prompts
Pre-draft the winning statement and hold it
The value of rehearsing early is having the right words ready before the clock starts. Have Simulate write the day-one Strategy B statement, tuned so the compensation reads as accountability rather than hush money, so it sits ready to publish.
Draft the day-one Strategy B statement: proactive disclosure plus compensation, framed so the compensation reads as accountability, not "buying silence." Keep it inside our regulatory disclosure constraints.
Model the "it leaks first" scenario
A disclosure plan assumes you speak first. Re-run Strategy B on the assumption the breach leaks to the press before you announce, and see whether the same statement still recovers or needs a different opening.
Re-run Strategy B assuming the breach leaks to a reporter 48 hours before we planned to disclose. Show me whether the trust curve still recovers and how the statement should change if we’re now reacting instead of leading.
- 5
Tips and troubleshooting
Read the curve, not the first day
Every disclosure looks bad on day one. The strategy that matters is the one whose trust line turns back up, so ask Simulate to model recovery over weeks. A first-day sentiment snapshot would have ranked all three as "negative" and hidden the only winner.
Rehearse the real statement
Simulate reacts to the words you would actually publish. Feed it a strategy label and it guesses; feed it the drafted statement, tone, detail, and whether compensation is named, and it catches the "buying silence" reading before your audience does.
Rehearse before you need to
The point of running this cold is to hold the winning statement ready. A disclosure written under real crisis pressure is worse than one rehearsed against a synthetic public weeks ahead, run it now, not on the day.
Ready to try it yourself?
Rehearse your disclosure strategies against a synthetic public today, and hold the statement that recovers trust ready before anything actually happens.
Run Simulate