Who should help design a workflow that sends work to another department?
When one department speeds up its own work, the team receiving it can end up with a harder job. Ask the people on the receiving end what they need before you call the process improved, and agree on a return route and an acceptance standard.
This one is my own application of the summit's process discussion, so it's my take and not a speaker's. Improvement should reach the person who needs the work, past the boundary of the team reporting the saving.
Walk through a real example together. Find out which information they rely on, what they check and which omissions send the work back, and include the timing of the transfer and the format they can really use.
Show the proposed AI assisted output early. Waiting until the workflow is built is how you find out that a missing field or an ambiguous summary stops the receiving team from acting.
Agree on an acceptance standard and a return route, so a recipient can explain why an item isn't ready without recreating the whole assignment. Then measure completion at the shared endpoint, where the receiving team can act on the work, and not at the moment the producing team sends the file.
What to try this week
Ask the receiving team to look at the AI assisted output now, while it's still a draft, and tell you what's missing for them to act on it.