The task is finished. Why is the next team still waiting?

A team can complete its own task and still leave the next team unable to work. The sender says the request was submitted. The receiver says the request was incomplete. Both descriptions can be accurate.

To investigate cross-functional handoffs, examine the transfer as its own piece of work. Define what must arrive, who accepts it and what happens when it is not usable.

Download the handoff worksheet.

For each handoff, record the sending role, receiving role, item or information transferred, required fields, delivery channel and acceptance condition. “Send to operations” is not a complete definition.

Then name who handles missing information and who can resolve an exception. The person who sends a record is not necessarily the person accountable for its completeness.

Ask the sender when they believed the work was complete. Ask the receiver when they could actually begin. Compare the input, timestamps where available and any clarification messages.

Do not assume a different account means someone performed badly. The teams may be using different completion rules, working from different records or operating under an undocumented exception.

The process discovery questions help gather the accounts without prematurely deciding which one is correct.

Missing input: A required field or document is absent.

Unclear recipient: The work goes to a group inbox with no agreed accepting owner.

Different definitions of done: The sender completed a local task but not the receiving team's prerequisites.

Unspecified exception route: A nonstandard case waits because nobody knows who decides.

No return path: Rejected or incomplete work has no clear route back for correction.

These are diagnostic categories, not a claim that every business has all five.

Illustrative: Sales sends an accepted quote. Fulfillment needs the delivery address, item configuration and approved date. Finance still needs billing details. An account record exists, but no shared rule determines when the order is ready.

An initial improvement may be to define a complete release packet and a receiving owner. Before adding automation, establish how exceptions will be handled and who may approve changes.

The quote-to-order workflow example develops this scenario in more detail.

Hands-on processing time and waiting time answer different questions. Where reliable records exist, examine how often a handoff is returned, how long work waits and which information is most often missing. Label estimates and sample periods clearly.

A department's local completion count can look healthy while the end-to-end workflow still stalls. That is a reason to inspect the boundary, not a reason to disregard the team's own measures.

Record a proposed acceptance condition, responsible owner, exception route and review date. Have the appropriate people confirm the change. A map can document a proposed policy, but it cannot approve one by itself.

Use the roles and tasks worksheet for ownership detail and the operations audit checklist for the broader review.

Private participant responses allow each side of the handoff to explain its work. An advisor can compare those accounts, inspect the linked tasks and identify questions for follow-up. The map should show unresolved boundaries rather than hide them behind a single arrow.

Discuss process discovery and mapping for one cross-team workflow.