As a shared workflow expands across teams, make responsibility for drafts, source checks and the next decision explicit enough for a new reader to understand the entire handoff.

Describe the responsibility attached to the work

Imagine a fictional shared workflow in which one person prepares a project summary and another reviews it before a decision. As more people take part, the handoff needs to say what each step is responsible for. A familiar job title may help readers understand a context, but it does not by itself explain which source was checked or who decides whether the proposed next step is appropriate.

Begin by naming the work rather than inventing a role hierarchy. In this exercise, preparing the draft means collecting the relevant synthetic notes and writing a summary limited to them. Checking the draft means comparing its statements with those notes and identifying unsupported interpretations. Deciding the next step means considering the unresolved question in the context of the original request. These responsibilities can be discussed separately even if one person performs more than one of them.

Make the output of each responsibility visible. The preparer can leave a draft with source references and a short account of uncertainty. The reviewer can identify which statements need revision and why. The next decision can remain open if a necessary condition has not been established. A handoff that records these distinctions is easier to inspect than a general statement that the work has been handled.

Now vary the fictional example by passing the draft to someone who did not attend the earlier discussion. Ask whether the written record explains the purpose of the summary, the scope of the source check and the decision still required. If the reader must infer those details from names or titles, the handoff is missing context. Add the relevant responsibility directly rather than assuming that everyone shares the same understanding.

A change in responsibility also deserves an explicit note. If another person takes over a review, identify what has already been examined and what remains open. Do not imply that a previous decision covers new material automatically. The goal of the exercise is to make the work understandable across a transition, including the possibility that the next reader needs to ask for clarification before proceeding.

Finally, compare the handoff with the original request. Check whether preparation, source review and decision-making have stayed within the intended task. The note should make it possible to see where judgment entered the process and where further input is needed. This does not establish an organizational design or report a staffing decision. It gives readers a concrete way to discuss responsibility in a fictional workflow.

About the responsibility exercise

Original illustrative material. No appointment, employee biography, organizational structure or business result is claimed.

The people and workflow in this article are unnamed and fictional. No real employee, appointment, reporting relationship or customer is represented. The guide focuses on describing work clearly enough that another reader can understand a handoff.

When practising with synthetic material, keep the responsibilities specific to the example. A readable note can help expose an ambiguity, but it does not replace the decisions required in a real organization or demonstrate an observed business outcome.

Continue exploring

Use the original evaluation and prompting guides to practise connecting a draft to its sources and making the next review question explicit.