Signal clearly when you’re done with a request before moving on

Close collaborative loops explicitly — send a brief "done" signal so the other person’s attention residue also closes.

Why it works

Collaborative work generates residue in both parties. When a collaborator sends a request and receives no closure signal, they carry an open loop ("did they receive it? Have they started? Will they need me?"). Clear closure signals — a brief completion message, a status update — close the loop for both parties simultaneously, reducing the system-wide residue load and the resulting follow-up messages that generate further interruptions.

How to do it

1. When completing a collaborative task, send a brief, explicit closure message: "Done — here’s what I found/decided/produced."
2. For longer-running work, send brief progress updates at natural stopping points rather than only at completion.
3. When handing off work, include a clear "what’s done, what’s next, what I need" note rather than a status meeting.
4. Respond to completed requests with explicit acknowledgment so the sender can close their loop.

Evidence

Loop closure in collaborative contexts reduces the frequency of follow-up messages and the uncertainty that generates interruptions. This applies the same Zeigarnik mechanism at the team level: ambiguous status keeps the loop active; explicit closure releases it. (mechanistic)

Closure signals can become overhead if overdone — brief, informative messages are the goal, not elaborate status updates for simple tasks.

Common mistake

Completing the task but not sending a closure signal — which leaves the requester carrying an open loop and likely to interrupt you with a follow-up "did you finish that?" check.