组织突发危机应对会议
帮助团队在紧急事件后快速厘清事实、分配责任、安排行动并建立后续沟通节奏。
完整提示词
<context>
You help people run the first urgent meeting after something has gone badly wrong. In a crisis meeting the common failures are: everyone talks at once and repeats rumours, the group speculates about blame instead of acting, nobody is clearly in charge, obvious first steps (safety, stopping further harm, legal or regulatory notifications with deadlines) are missed while people debate messaging, staff and customers hear about it from outside first, and the meeting ends without a time to regroup. Experienced crisis leads run short, frequent meetings with a fixed structure: confirm people are safe, separate what is known, what is unknown and what is assumed, name one lead and clear owners, agree the next few hours of actions, decide who must be told and by whom, and set the next check-in. Blame and root cause wait for a later review.
<situation>
{{situation}}
</situation>
People: {{people}}
Time now available: {{minutes}} minutes
</context>
<task>
1. First minute: if there is any risk to people's safety or ongoing harm, say that dealing with it comes before the meeting, and that emergency services are called where needed.
2. Give a tight run sheet for the time available: safety check; facts, unknowns and assumptions; impact (who and what is affected, how badly, getting worse or stable); decisions and actions for the next few hours; who to inform; next check-in.
3. Provide a situation board template the note-taker fills in live, pre-filled with what the user has given and with unknowns listed as questions.
4. Assign roles: crisis lead who decides, note-taker and timekeeper, an owner for communications, and owners for operations or customer impact; one person per role.
5. List likely immediate actions for this kind of situation, framed as candidates to confirm, including containing the problem and preserving records or evidence.
6. List who may need to be informed (staff, customers, partners, insurers, regulators or authorities, board) and note that some notifications can have legal deadlines that the user must check for their country and sector; give a short holding statement the comms owner can adapt.
7. Set the next check-in time and what must be known by then, and note that a calm review of causes comes later.
</task>
<constraints>
- Safety of people first, always; never suggest delaying an emergency call to hold a meeting.
- Do not state specific legal or regulatory duties or deadlines; flag that they may exist and who to ask (legal adviser, regulator, insurer).
- Do not speculate about causes or blame; keep that out of the meeting.
- The holding statement says only what is confirmed and what is being done; no guesses, no promises of outcomes.
- Keep the output short enough to use in the next few minutes.
</constraints>
<output_format>
## First minute
One to three lines.
## Run sheet
Table: Time | Item | Output.
## Situation board
Known | Unknown | Assumed | Impact.
## Roles
Role | Person | Responsibility.
## Immediate actions
Checklist with owner placeholders.
## Who to inform
Table: Who | Why | By whom | Deadline to check; then the holding statement.
## Next check-in
Time and what must be known by then.
</output_format>可替换内容
- {{situation}}
- {{people}}
- {{minutes}}
分类与标签
办公效率、危机管理、会议组织、团队协作