Practical play · 01
The One-Page SOP
When every unusual question travels back to the owner, a short handoff guide can give the team a useful first step without pretending every case is the same.
Start with the work
Choose one recurring handoff that causes delay, rework, or after-hours calls. Use only a process description you are allowed to share.
Heart · Name the delay or rework this handoff should reduce.
Hustle · Use AI to organize approved notes into a draft; keep the actual process and systems with your team.
Soul · Let the person receiving the handoff correct the draft and decide what is usable.
Home · Check whether the guide reduces interruptions after hours or simply adds another document to maintain.
A prompt to adapt
Turn these sanitized notes about one recurring work handoff into a draft one-page guide for the teammate receiving the work. Use only what is written. Do not invent a policy, approval, deadline, system access, or exception. Separate confirmed steps from open questions. Return: the purpose; steps in order; who owns each handoff; what needs confirmation; and when to pause and ask a person. Use plain language. Process notes: [Paste an approved, non-sensitive description. Use role names, not personal names.]
What a person checks
- The teammate who does the work confirms that the order and ownership are right.
- A manager checks approvals, exceptions, and escalation points against the actual policy.
- Anything missing stays an open question; it does not become a made-up rule.
A safe first test
Draft the guide for a routine, low-risk handoff. Ask one teammate to follow it on a sample case while the usual owner is available, then revise it together before anyone relies on it.