I redesigned a month-long medical SaaS onboarding process across departments, cutting completion time in half. I then led its evolution from physical welcome materials and scheduled calls into reusable digital learning.
New medical practices bought cloud software but entered it through paper: contracts, HIPAA agreements, faxed enrollment forms, repeated departmental questions, and five scheduled training sessions — all required before support access unlocked. Typical onboarding took a month.
As Technical Writing Manager, I redesigned that journey as one cross-department service, cutting onboarding from four weeks to two. I then led its digital evolution: packet instructions became reusable videos, and the printed training program became modular LMS learning that activated clients automatically on completion.
Problem
A cloud-software company onboarded clients through paper, faxes, and phone calls
A newly enrolled medical practice faced signed software use agreements, financial contracts, HIPAA agreements, clinical details for EDI and integration setup, and five scheduled one-on-one training sessions built around a printed manual — all before staff could work independently. The materials represented sincere concierge intent, but they tied every client's progress to paper delivery, fax machines, and two people's calendars.
Departmental handoffs repeated information and delayed client progress
Enrollment, implementation, training, and sales each sent separate materials and routinely requested information the client had already provided elsewhere. Clients even faxed back pages containing no signatures or new information. And because so many tier-1 support calls were basic questions, support access was gated behind completing all five training sessions — meaning a busy practice's onboarding stretched to roughly a month, throttled by scheduling.
insight
Why was a heavily documented process still taking a month?
I inventoried every form, job aid, manual, script, and training asset, then used cross-department listening sessions to trace how information moved. The friction lived between artifacts: repeated data collection, manual transfers, scheduling dependencies, and local processes no individual team could see from inside its own workflow.
The delay came from service architecture, not a shortage of documentation
The company had optimized individual forms, manuals, and calls without redesigning the system around them. Some assets needed updating, others consolidation, and some elimination. Digitizing everything unchanged would only reproduce the same service failure in a new medium.
Jobs to be done: Practice staff need to complete setup and learning around an active workday, without repeating themselves to every department that touches their account.
Dana
Marcus
Elena
decision
Digitize everything at once, defend the paper, or stage the transition?
The audit showed that better documents alone would not eliminate duplicated requests, fax dependencies, or scheduled-training bottlenecks. I considered three approaches:
- Improve the print-and-phone model — refine manuals, contracts, job aids, and training scripts without changing delivery.
- Digitize departmental materials individually — add videos, PDFs, or point solutions while each department retained its own workflow.
- Redesign onboarding as one service, then digitize it — consolidate intake, convert repeatable guidance to media, and rebuild training as modular LMS content.
Design tension: Onboarding needed to become faster and more self-directed without removing expert support from practices adopting critical software.
I staged the transition, letting each win fund the next
I mapped the complete service, consolidated the physical experience into the GO!Pak, converted recurring guidance to video, rebuilt formal training for an LMS, and preserved human help for exceptions — with all updates tied to software releases. The measurable win from consolidation built the organizational confidence and budget for digital delivery. The tradeoff: paper and digital coexisted longer than I would recommend today.
Gallery
I mapped the service and removed duplicated work across departments
I zoomed out from my department's output and mapped the complete new-client experience across teams. Multiple departments expected fax-back forms with overlapping information, so I identified which fields each team actually needed, collected them once, and revised return instructions so clients stopped faxing pages nobody read. This phase alone cut typical onboarding from four weeks to two.
I consolidated startup materials into a coordinated concierge package
The GO!Pak consolidated startup aids, contracts, enrollment forms, and laminated instructions into one branded, sequenced welcome system, so clients could see what came next instead of guessing. Dynamic PDFs added structured entry, but the workflow still ended in printing, signing, and faxing — a meaningful transformation that also revealed how hard we were working to simulate digital behavior on paper.
I converted printed instructions to reusable digital media
I identified recurring guidance that needed neither an individualized conversation nor a physical artifact and converted it into short videos, which demonstrated software behavior better than dense instructions could. Clients could revisit guidance on demand, several departments could reference one maintained explanation, and print began its retreat to where it added distinct value.
Involving each department as on-screen talent gave them the opportunity to SME review our scripts.
The Building Blocks video marks the new client transition from onboarding to training.
EVOLUTION: The video-training model was extended to internal staff onboarding. This industry primer tutorial describes a medical patient's "user journey." Toward the end of the video, you can notice the narration becoming unpolished. We had not yet edited this draft's script for brevity or screen time.
I transformed printed training into structured, LMS-ready instruction
I led the conversion of Nuebie Notes and its five scheduled sessions into modular LMS learning: objectives, role-based paths, demonstrations, quizzes, and sandbox practice. Every asset was categorized Update, Consolidate, Standardize, or Sunset, and standards for terminology, scripting, and maintenance tied lessons to the software release cycle so training never lagged the product.
The LMS conversion replaced a monolithic printed manual with modular lessons, audience-specific pathways, assessments, sandbox practice, and content governance tied to the software release cycle.
Each tutorial combined task-based technical writing, a visual software demonstration, SME-reviewed procedure, and a reusable assessment or practice activity.
Delivery
I delivered the transformation in stages that built organizational confidence
The process redesign and GO!Pak created the first measurable win, helping fund reusable video and an enterprise LMS. Content then shipped incrementally alongside software releases. The final workflow also automated Support activation when curriculum completion was recorded, replacing a manual trainer handoff.
I turned a departmental project into a cross-company program
I brought requirements together across enrollment, training, sales, business development, product, and HR; secured leadership budget; helped select the LMS vendor; and managed writers and video producers through conversion. SMEs retained procedural review, while trainers remained available for exceptions and complex workflows.
Validation
I separated service outcomes from learning checks and production controls
The clearest measured result belongs to the process and GO!Pak phase: typical onboarding — measured from enrollment date to training completion — fell from roughly four weeks to two, often sooner. Later validation included departmental review, SME script review, quizzes, sandbox practice, and release checks, while readability and recording-time metrics improved production without being claimed as user outcomes. The project did not capture mature data on LMS completion rates, trainer capacity, or support volume — those would be the first instruments I'd add today.
IMPACT
I cut onboarding time in half and created the foundation for self-serve learning
The cross-department redesign reduced typical onboarding from approximately four weeks to two. The GO!Pak consolidated startup activity; videos moved recurring explanations beyond one-time paper delivery; and the LMS transformed a printed course into modular lessons, role-based paths, assessments, and practice. The infrastructure later supported employee education, while the Documentation department evolved into a broader Media function.
Dana
Marcus
Elena
REFLECTION
Better learning content began with redesigning the service around it
The project began with documentation but exposed a larger service problem: disconnected departments, repeated information, slow media, and calendar-dependent instruction. Redesigning those connections produced measurable improvement first; reusable video and LMS content then made delivery easier to maintain and scale.
What I'd do differently next time...
With today’s product perspective, I would challenge both the delivery model and the product problems creating so much instructional demand earlier.
- Replace fax workflows with digital intake.
- Make physical materials optional.
- Feed training friction back into product design.
- Measure learning and operational outcomes.
- Reserve trainers for high-value support.
The durable principle was to design the service before digitizing it, question whether every asset should survive, and reserve human expertise for situations requiring judgment. This project taught me to ask whether redundant instruction belongs in training at all or should be solved in the product.