Assign outcome ownership and acceptance at a handoff between two teams.
Reading tools
Please sign in to use all the tools
Once you sign in, the reading tools are yours: larger or smaller text, typeface, line spacing, focus mode, highlighting and bold, and notes saved to your account and gathered in My study.
Processes often cross teams that each see only part of the journey. A map saying ‘intake sends to delivery’ does not identify who checks whether the request is usable, who accepts the handoff, or who acts if it is rejected. A proposed process owner follows the end-to-end outcome, its criteria and failures; an activity performer completes a particular step. Ownership does not mean performing every task or automatically having authority over every team. Agree on actual decision rights. At each handoff record the item transferred, its acceptance condition, sender, receiver, time and rejection path. This permits investigation of a failed transfer in a case record rather than relying on a vague complaint about collaboration.
A simple responsibility matrix can show who performs, who is accountable, who is consulted and who is informed. Do not populate every cell with everyone. Give each important decision a clear accountable role and identify who can accept its output. Naming two team leads as jointly accountable without a tie-breaking route hides the disagreement. Making the process owner the performer of every step obscures that role's cross-team view. Decide who can return a request and when. Arbitrary returns lengthen the journey, while accepting defective inputs can move the defect to a more costly stage. Compare those consequences and set a specific acceptance condition.
Test the matrix with an awkward case. When a request with missing data is assigned near closing time, does the receiver contact its originator, return it to intake, or hold it with a reason and deadline? The rule needs escalation and a record of who acts next. Being informed is not the same as giving approval: telling a requester about a delay does not authorise delivery staff to bypass a safety or budget condition. After redesigning roles, update the procedure, case states, access rights and training together. A well-formatted matrix without a way to execute its decisions will not clear a single waiting request.
Lesson summary
Process ownership and cross-team handoffs: apply the method to case evidence and check the result and its limits.