Onboarding and credentialing pipeline
Cut onboarding time-to-productivity from 90+ days to roughly half by standardizing intake, automating ticketing, and running a clear cadence.
Context
This work focused on the post-accept phase: credentialing and enrollment to access and training to ready to see patients.
Baseline cycle time was often 90+ days, driven by credentialing workflows and document-heavy back-and-forth.
Status lived in email threads, which created rework, missed handoffs, and unpredictable timelines.
What I owned
- Mapped the end-to-end flow with clear stages, owners, inputs, and blocker definitions.
- Implemented a single provider-level JIRA ticket that moved across departments instead of spawning disconnected requests.
- Used automation for routing and nudges to reduce manual follow-ups.
- Ran weekly pipeline calls to clear blockers plus monthly leadership updates for visibility.
- Led a search for external credentialing partners under cost and headcount constraints.
- Built operational artifacts such as SOPs, process maps, and a dashboard for aging and accountability.
Constraints and complexity
- Credentialing timelines dominated total cycle time and were not fully controlled internally.
- Document-heavy workflows created repeated asks and preventable handoff errors.
- Cost and headcount constraints limited brute-force solutions.
- Multiple departments needed shared definitions to avoid local optimization.
Results
- Reduced onboarding time-to-productivity from 90+ days to roughly half based on pipeline tracking.
- Introduced a single source of truth showing aging, blockers, and accountability across departments.
- Reduced document back-and-forth and handoff errors by keeping work in one routed ticket.
What I learned
- If work is not visible, it is not manageable.
- A single source of truth beats perfect documentation scattered across inboxes.
- Cadence is a product feature when multiple teams share a pipeline.