Start at the handoffs
Map the journey from scheduling and registration through documentation, billing, and follow-up. For each handoff, write down the source system, required information, receiving team, and definition of completion. A task leaving one queue does not necessarily mean the next team can act on it.
Make exceptions visible
List the reasons work returns to an earlier stage: missing documentation, conflicting information, unclear ownership, or an unresolved payer response. Give each exception a named owner and an escalation path. Review a small sample of actual workflows with the people doing the work.
Choose one improvement
Select a repeatable handoff with measurable delays. Record its current cycle time and rework before making changes. Test a limited scope, review outputs with the receiving team, and expand only when the new process is reliable.