The organization had been buying this training from a vendor. That model produced a course, but not a program: no internal update control, no way to align content with how the organization actually operates, and an annual cost with no accruing asset. The mandate was to bring it in-house and serve two distinct needs at once — new employee onboarding and an annual refresh for the entire existing workforce.
The audience spanned four tiers, from all-staff through people managers to the facilities and security personnel who would deliver parts of it.
Replace a vendor-delivered program with an internally owned one that could be updated on the organization’s own timeline, delivered across departments with no shared calendar, and taught by facilitators who were not trainers.
The constraint that shaped the entire design: departments could not surrender a half-day, but they could give twenty minutes three times. Every delivery decision was made backward from that reality.
The program ran in two distinct phases. The first established the baseline requirement and initial documentation. The second — a focused reframe from September through December 2025 — rebuilt the needs analysis capture from the ground up and operated inside a widened, tiered stakeholder review structure.
The reframe was where the program got its spine. Working across more review layers meant requirements had to be traceable, not just agreed to in a room. I rebuilt the analysis documentation so every design decision could be tracked back to a validated need — which is also what made a single consolidated project plan possible.
One requirement did not survive that validation. A scheduling constraint had been carried into the design on the understanding that delivering during new employee orientation would displace an existing onboarding component. I checked it directly with the orientation facilitator. The constraint was not real, and a design option that had been ruled out was available again.
It is a small thing I think about often. Requirements captured secondhand harden fast, and by the time they reach design they are treated as facts. Going back to the source cost an afternoon and recovered a delivery pathway.
Led. Needs analysis and requirements validation, blended design across four modalities, facilitator enablement, delivery logistics, communications campaign, and the consolidated Training Analysis & Project Plan that became the program’s single source of truth when repeated stakeholder realignment created version confusion.
Four-Modality Blend
A self-paced digital core, a team-based practicum, small-group scenario walkthroughs, and a leadership briefing toolkit — each carrying the part of the objective the others could not reach.
Designed for Internal Update Control
Built so the organization could revise it without returning to a vendor. Content modularity was an ownership decision before it was an instructional one.
Facilitator Enablement
Session scripts with talking points, timing markers, and transition language — deliverable as-is by a first-time facilitator, adaptable by a confident one. Plus guides, calibration guidance, and train-the-trainer.
Delivery Logistics as Design
Scheduling architecture across departments with no shared calendar, facilitator load balancing, group sizing for genuine participation, and make-up pathways for shift coverage and contractors.
Audience-Differentiated Comms
All-staff, people managers, facilitators, and leadership each received messaging written for what they actually had to do — with reinforcement designed to survive past the completion spike.
One Source of Truth
When realignment produced competing versions of the requirements, I authored a consolidated Training Analysis & Project Plan. It unblocked the build and became the artifact the review structure ran on.
Training analysis & consolidated project plan · blended modality matrix · facilitator session scripts and guides · leadership briefing toolkit · communications sequencing plan
- Vendor-delivered training replaced with an internally owned, internally updatable program serving both onboarding and annual refresh
- Four coordinated modalities delivered against a twenty-minute departmental constraint rather than requiring a half-day release
- Non-trainer facilitators — facilities, security, and department managers — enabled to deliver consistently through scripts, guides, and calibration
- A single consolidated analysis and project plan resolved competing requirement versions and unblocked the build
- Organization-wide activation delivered as the program’s public launch moment
The design held up. What I would do differently is treat organizational adoption readiness as its own workstream — scoped at the front, with its own stakeholders and its own timeline — rather than assuming a well-designed program arrives ready to be adopted. Design quality and adoption are different problems, and only one of them is solved by the design.