<b>MYTH: "Faster handoffs mean a faster team."</b>

<b>MYTH: "Faster handoffs mean a faster team."</b>
The correction: a fast handoff with no definition-of-done just moves the rework downstream. Speed at the seam is where work goes to die.

<b>SOP: Clean handoff gate</b>
Run this whenever work passes from one person or team to the next.

Stage 1 — Sender packs
— ☐ State the definition-of-done you're claiming is met. (Owner: sender)
— ☐ Attach the inputs the receiver needs; no "ping me for the link." (Owner: sender)
— ☐ List anything knowingly incomplete. (Owner: sender)

Stage 2 — Receiver checks
— ☐ Confirm the done-criteria against the actual deliverable. (Owner: receiver)
— ☐ Accept or bounce within one working day; silence is not acceptance. (Owner: receiver)

Stage 3 — Log
— ☐ Record acceptance time so the seam is measurable. (Owner: receiver)

Owner: sender then receiver. Trigger: work crosses a team boundary. Done-when: receiver explicitly accepts against criteria.

Save this. Run it every time.

—
Продолжение про outreach scripts — @UGCOpsManual