Overview
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.
Who I designed for

Laci
Parent decision-makers comparing options, needing clarity, trust, and predictable next steps.

Josef
Long-time expert who knows the system deeply but struggles with UI drift and lack of standardization.

Andrew
Buyer researching company online to assess credibility, clarity, and whether product answers their pain points.

Jan
Parent researching cabins, amenities, prices, and driving logistics; juggling seasonal availability and family needs.

Dana
Coordinates setup while keeping an active medical practice running. She repeats information across forms, returns lengthy fax packets, and schedules training around staff and patient demands.

Evan
An experienced musician who absorbed planning because somebody had to. He needs to maintain the tour without becoming the human lookup table for everyone else.

João
An adult looking for fitness or self-protection training; often skeptical and needs assurance before committing.

Priya
Daily user entering procedure data, relying on clarity, consistency, and speed under time pressure.

Claudia
Hospital staff user seeking training, docs, or cert materials; needs stable content and clear navigation.

Jordan
Individual wanting simplicity, clear booking flows, and trustworthy info; browses on mobile and books quickly.

Marcus
Delivers the same foundational lessons through five scheduled sessions per client. Calendar coordination and repeated instruction leave less time for difficult workflows and individual questions.

Riley
An experienced member who depends on the itinerary but doesn't maintain it. Reliable dates and changes matter because touring commitments intersect with work and family obligations.

Ron
The internal user who relies on tried and true workflows, less chaos, and predictable communication.

Scott
Spends too much time rebuilding redundant patterns and troubleshooting bugs caused by inconsistent markup.

Dan
Internal employee updating pages, syncing with devs, and needing stable IA and predictable site governance.

Steve
Internal user who needs consistent branding and a site within platform constraints without operational friction.

Elena
Collects, checks, and redistributes faxed enrollment materials. Duplicate questions, unnecessary return pages, and incomplete packets create repeated follow-up and manual routing.

Theo
A musician booking an early tour without an experienced road manager's accumulated knowledge. He needs the product to expose what's missing rather than assume that expertise already exists.
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.
Build
Process & Service Design
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.

Welcome Packet
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.



Onboarding Videos
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.
Instructional Design
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.



What changed for them

Laci
The site clarified programs and offered a transparent flow for onboarding. Messaging is now timely and consistent.

Josef
UI improvements did not require downtime nor slow or interfere with established, familiar user experience.

Andrew
Company web presence looks both mature and current. Clearer IA made product info easy to understand.

Jan
New listing layouts show key differences clearly, even links to nearby amenities. Cabin search can filter by preferences.

Dana
A coordinated onboarding path reduced repeated paperwork and clarified each next step. Self-paced videos and training let her prepare staff around the practice schedule and become operational sooner.

Evan
Can scan which dates still need attention without manually auditing every record.

João
Onboard sequences and ready content reduced anxiety by setting expectations with guided flows and clear next steps.

Priya
Even with a new look-and-feel, everything was in its familiar place with no difficult renderings or legibility.

Claudia
Training, docs, cert materials now live in stable locations. No more relearning how a site decided to rebuild itself.

Jordan
Simplified steps and cleaner UI removed avoidable friction. Calendars and real-time status made booking state easier to understand.

Marcus
Reusable lessons, quizzes, and sandbox exercises moved foundational instruction into self-service. Marcus could focus live support on questions, exceptions, and complex client workflows.

Riley
Can retrieve current tour details without routing the question through the planner.

Ron
The automated workflow eliminated repetitive outreach, improved reliability, and produced social media content faster.

Scott
Delegating front-end code ownership and reusing components from a single source of truth eliminated redundant effort.

Dan
By delegating ownership, devs no longer bottleneck updates or releases for even small content updates.

Steve
The CMS model made content edits easy and improved SEO. Less manual work is needed to book a guest.

Elena
Consolidated intake and clearer fax-back requirements reduced duplicate requests and unnecessary pages. More complete submissions moved through the organization with less manual follow-up.

Theo
Can see which information a show still requires instead of relying on experience they do not yet have.
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.

