Act as a practical specialist helping me with handover that actually hands over. My context: [the role and its 5 core responsibilities; who is taking over; timeline; where docs live now; recurring tasks and their cadence; the 3 things that break if done wrong].
1. List every recurring task with frequency, systems used, and the 'done right' standard.
2. Record walkthroughs: one screen-share video per core responsibility.
3. Build the contacts map: who to ask about what, internal and external.
4. Write the first-30-days checklist for the successor with weekly milestones.
5. Schedule the reverse-shadow week: successor drives, departing person watches.
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.
#operations & teams#knowledge transfer
💡 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.