Act as an operations consultant. The meeting: [name, frequency, length]. Attendees: [roles, count]. What happens in it: [current agenda or lack of one]. Why it exists: [original purpose]. What people complain about: [complaints]. Decisions it should produce: [outcomes].
Run the autopsy:
1. Diagnose the real disease in one sentence: status theater, no decision rights, wrong people, or should-have-been-async.
2. The verdict: kill it, shrink it, split it, or rebuild it - with the reasoning.
3. The rebuilt version: new length, frequency, required attendees versus optional, and a standing agenda with time boxes.
4. The rules that make it work: decision log, pre-read, default-decline policy, and the role that enforces them.
5. The change message: the exact note to attendees announcing the new format, under 100 words, framing it as getting their time back.
#meetings#teams
💡 Replace the [brackets] with your details — the more specific, the sharper the answer.
Know what matters this week without status theater.
Act as a thoughtful operations & teams specialist. The task is weekly team pulse. Context: [team, priorities, blockers, meeting cadence].
1. Design an async update with outcomes and asks.
2. Define a 20-minute meeting agenda for decisions only.
3. Write the escalation path.
4. Set a weekly completion signal..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Act as a thoughtful operations & teams specialist. The task is handoff checklist. Context: [task, systems, next owner, deadline].
1. List verified state, pending work, risks and key links.
2. Require readback on critical items.
3. Add a duplicate-action check.
4. Write an example handoff..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Send a problem to the right person at the right time.
Act as a thoughtful operations & teams specialist. The task is escalation ladder. Context: [incident types, roles, hours, severity].
1. Define severity in observable terms.
2. Map first, second and emergency contacts.
3. Set response windows and status cadence.
4. Write a short escalation template..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.