Connect a task to its next step without losing the context behind it.

Describe the handoff before connecting the steps

In a fictional planning exercise, one assistant helps a reader understand a project note and another prepares a draft update. The handoff between them is more than a transfer of text. The next step needs to know what question was asked, which source supports the interpretation and what the first step did not resolve. Without that context, a polished draft can make an incomplete understanding look settled.

Begin with a synthetic project note that names an activity and a condition that must be checked before it can proceed. Ask the first step to describe the condition and identify the relevant passage. Then ask what the next step would need in order to prepare a reviewable draft. Keep the exercise focused on the information that crosses the boundary, rather than assuming that a connection makes the whole task reliable.

Three parts of the handoff deserve separate attention. They can be recorded together, but each should answer a different question:

• Purpose: carry the reader’s requested outcome and the limits of the task, so the next step does not quietly expand the request.
• Evidence: carry the supporting passage and its scope, while marking assumptions and unresolved conditions as such.
• State: say whether the work is an interpretation, a draft awaiting review or a confirmed result; do not infer completion from the existence of a response.

Test the context that crosses the boundary

Original illustrative material. No integration, partnership, customer workflow or observed outcome is claimed.

Read the handoff as if you had not seen the first conversation. Can you explain why the proposed next step follows from the source? Can you identify what still needs a person’s decision? If the answer depends on details that appear only in the earlier exchange, add those details to the handoff or narrow the next step. The goal is to make the reasoning inspectable without requiring a reader to reconstruct hidden context.

Now change one condition in the fictional source. For example, the note might describe a different version of the activity or leave its timing unresolved. The next step should retain that difference in its draft. It should not reuse a previous interpretation simply because the new source looks similar. This variation helps reviewers discuss whether the handoff carries the specific condition that matters to the task.

Consider what happens when the second step cannot proceed. It may lack a necessary destination or encounter an unresolved choice. A useful response identifies that missing piece and returns a clear question for review. It does not need to invent a destination or treat a guess as an instruction. The reader should be able to distinguish a blocked draft from a completed change.

The same care applies when information returns from the next step. A response should describe what was prepared or confirmed and what remains uncertain. If the exercise only produces a draft, label it as a draft. If an outcome cannot be established from the available evidence, preserve that uncertainty. A summary of intended work is different from a record of completed work.

Keep the review proportional to the fictional task. A short note can be sufficient when it captures the question, source, proposed next step and unresolved decision clearly. More text is not automatically more useful. Remove repetition that obscures the relevant condition, but retain the details another reader needs to understand why the next step is being proposed.

End by comparing the original request with the final handoff. Check whether the requested outcome is still recognizable and whether any new assumption appeared along the way. The exercise is successful as a discussion tool when readers can point to those assumptions and decide what needs clarification. It does not establish the effectiveness of a connected system or the readiness of a real workflow.

About the connected-work exercise

The assistants, project note and handoff in this article are fictional. They illustrate questions a reader can ask about information moving between steps. No vendor relationship, deployed capability, customer result or employee statement is represented.

Use synthetic material when adapting the exercise. Describe the intended task and the review boundary explicitly, then examine whether the handoff preserves them. Any actual implementation would need its own requirements and verification beyond this educational example.

Continue exploring

The related guides offer original exercises for examining supporting sources and preparing a draft that another person can review.