算法艺术创作
algorithmic-art
通过代码和可调参数创作生成艺术与交互式视觉效果。
66-crisis-playbook-global【设计与创意】Use when a brand faces a communications CRISIS or a campaign is failing in public — L1 to L5 severity classification, a first-four-hours process, response templates by type, an escalation matrix, a do-not-do list, holding statements, and a post-mortem. Trigger on 'PR crisis', 'crisis playbook', 'a complaint is going viral', 'bad reviews are spreading…
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
name: 66-crisis-playbook-global
description: "Use when a brand faces a communications CRISIS or a campaign is failing in public — L1 to L5 severity classification, a first-four-hours process, response templates by type, an escalation matrix, a do-not-do list, holding statements, and a post-mortem. Trigger on 'PR crisis', 'crisis playbook', 'a complaint is going viral', 'bad reviews are spreading', 'our content caused backlash', 'we are getting attacked online'. Also use when the user forwards an angry thread and asks what to do right now. Not for — monitoring before anything blows up, see 15-social-listening-global; diagnosing weak performance numbers, see 03-performance-eval-global; the routine post-campaign review, see 63-campaign-retrospective-global."
metadata:
version: 1.0.1
category: operations
license: MIT
triggers:
A crisis arrives without warning, so the playbook must exist before it is needed. Three ground rules: (1) do not react before you have facts — most crises look worse than they are in the first 30 minutes; (2) do not stay silent past 4 hours on a spreading crisis, because silence reads as admission; (3) handled well, a crisis builds trust; handled badly, it destroys it permanently.
Read the 15-social-listening-global report if available (early detection). Before doing anything, answer 4 questions:
If you do not have enough information: publish one short line confirming you are investigating and commit to a specific update time. Do not go silent, and do not respond to unverified claims.
| Level | Type | Example | Priority | Response window |
|---|---|---|---|---|
| L1 | Operational — campaign or system failure, severe KPI miss | Ads not delivering, landing page down, tracking broken | High | 2-4 hours |
| L2 | Content — inaccurate or misleading content published | Misleading caption, wrong figure, inappropriate image | High | 2-4 hours |
| L3 | Reputation — customer complaint spreading | Viral one-star review, exposé thread | Critical | 1-2 hours |
| L4 | Brand attack — coordinated | Mass fake reviews, competitor smear, brigading | Critical | Same day |
| L5 | Legal / compliance / data | Deceptive-advertising or undisclosed-endorsement complaint, personal data breach, IP infringement, platform enforcement action | Critical + counsel | Immediate |
In the first 2 hours: pull the full data set to find where the real number sits; diagnose the root cause (run 03-performance-eval-global); notify leadership with a hypothesis and actions; deploy the emergency fix.
Report template: "Campaign [X] is at [actual] against a target of [target]. Preliminary cause: [hypothesis]. In progress: [3 actions]. Next update at [time]."
Immediately: screenshot and archive the evidence BEFORE removing anything; take down the affected post (faster than apologizing on the broken post); notify the leader, do not self-handle.
Within 2-4 hours: establish what was wrong, who was affected, and the reach; draft the response and have the leader approve it before posting (run 62-marketing-review-global).
Response template: "We found that [content X] in our [date] post contained [an error / inaccurate information]. We have [removed / corrected] it and apologize for the confusion. The correct information is: [...]. Thanks to [the person who flagged it] for raising it."
Immediately: do NOT delete comments, do NOT argue in public, archive all evidence with timestamps.
Within 1-2 hours: verify whether the complaint is legitimate.
Note: in US and EU markets, review platforms are part of the crisis surface. Respond on the platform where the complaint lives, and never incentivize or suppress reviews to offset it — that is itself an FTC issue.
Archive evidence with timestamps; notify leadership immediately; weigh staying silent (a small-scale attack is amplified by responding) against speaking up (if it is spreading); never respond emotionally; report coordinated inauthentic behavior through the platform's own reporting flow; consult counsel if there are signs of defamation.
Stop every related campaign IMMEDIATELY. Notify leadership. Consult counsel before doing anything else, and make no public statement before legal input. Route by trigger:
| Trigger | First move |
|---|---|
| Claim challenged as deceptive, or an endorsement ran without disclosure | Pause the asset, pull the substantiation file and the creator contract, route to counsel. FTC exposure attaches to the advertiser, not only the creator |
| Personal data exposed or accessed without authorization | Notify your data protection lead or counsel the moment you become aware. Under GDPR a controller has a 72-hour duty to report a qualifying breach to the supervisory authority, and affected individuals must be told without undue delay where the risk is high. Do not wait for full facts to start the clock |
| California or other US state privacy complaint (CCPA/CPRA and equivalents) | Route to counsel; preserve the request and response record, do not respond ad hoc |
| Platform policy enforcement (account restricted, ads disapproved at scale, page unpublished) | Do not spin up backup accounts. File the platform appeal, document the disputed asset, and fix the underlying policy issue |
| Regulated category (health, finance, insurance, credit, crypto) | Any claim issue escalates straight to legal review before any response is drafted |
This playbook coordinates the response. It does not give legal advice, and it does not replace counsel on any of the triggers above.
| Level | Handled by | Who must know | Timeline |
|---|---|---|---|
| L1 | Media buyer + leader | Leadership same day | 2-4 hours |
| L2 | Content + leader | Leadership if reach > 10K | 2-4 hours |
| L3 | Leader | Leadership immediately | 1-2 hours |
| L4 | Leadership + leader | Board or executive team if needed | Same day |
| L5 | Leadership + counsel | Board or executive team, plus the data protection lead for any data incident | Immediate |
# Crisis Response — [Incident name] — [Date/time]
## 1. Initial assessment
| Item | Content |
|------|---------|
| Classification | L[1-5] — [type] |
| Origin | |
| Current scale | [estimated reach, number of channels] |
| Verified facts | |
| Unverified claims | |
## 2. Hour-by-hour response plan
| Time window | Action | Owner | Status |
|-------------|--------|-------|--------|
| 0-1h | | | |
| 1-4h | | | |
| 4-24h | | | |
| Day 2-7 | | | |
## 3. Messaging
Approved to say: [...]
Not to say: [...]
Single spokesperson: [...]
Channels used: [...]
## 4. Internal actions
| Task | Owner | Deadline |
|------|-------|----------|
## 5. Monitoring
| Metric | Before | After 24h | After 7 days |
|--------|--------|-----------|--------------|
| Sentiment | | | |
| Mention volume | | | |
| Inbox / complaints | | | |
After one week: write the post-mortem (what happened, how it was handled, the outcome), update this playbook with the new lessons, and run a team session so it does not repeat. If the crisis was campaign-related, fold it into 63-campaign-retrospective-global.
15-social-listening-global: early detection before it becomes a crisis, and sentiment tracking during and after.03-performance-eval-global: root-cause diagnosis for L1 operational crises.62-marketing-review-global: approve the response content before publishing.63-campaign-retrospective-global: extract systemic lessons once it is resolved.07-marketing-report-global: report the impact on monthly KPIs.