Process / 04

How projects actually run.

A clear build process keeps your stakeholders aligned and makes approvals painless. Here's what a typical engagement looks like from kickoff to LMS delivery.

Scroll · Five phases
01 Engagement flow
Each phase ends with a demo or a deliverable you can show your CFO, not a status update buried in email.

Five phases. Real milestones.

01
Phase 01 · ~1–2 weeks

Discovery.

Define the win. We scope the training goal, audience, constraints, and what "success" actually looks like to your auditors.

  • Training goal, audience, constraints, and success criteria.
  • Devices, LMS needs, and deployment environment.
  • Source materials: SOPs, JHAs, checklists, photos, floor plans.
  • Stakeholder map and decision rights matrix.
02
Phase 02 · ~2–3 weeks

Design.

Storyboard the experience. Scenario flow, decision points, assessment checkpoints, and the UI/UX learners actually touch.

  • Scenario flow, decision points, and assessment checkpoints.
  • UI/UX prompts, indicators, real-time feedback.
  • Content review with subject-matter experts for accuracy and policy alignment.
  • Approval sign-off before a single asset gets modeled.
03
Phase 03 · ~4–8 weeks

Build.

Iterate quickly. Prototype, alpha, beta; each one shippable and demoable, not a blackbox waiting on a big reveal.

  • Prototype → alpha → beta milestones with real demos.
  • Performance tuning for standalone headsets.
  • Accessibility and comfort options where applicable.
  • Weekly playable builds. No mystery-meat dev cycles.
04
Phase 04 · ~1–2 weeks

Validate.

Pilot with real users. We run the experience through actual learners and refine where the friction shows up.

  • Pilot runs with target learners on real devices.
  • Collect structured feedback and identify confusion points.
  • Refine scoring, timing, prompts, and overall clarity.
  • Instructor handoff session + train-the-trainer.
05
Phase 05 · Ongoing

Deploy.

Ship and support. SCORM/xAPI packages or standalone builds, plus the support window your IT team needs to feel safe.

  • LMS packages (SCORM/xAPI) or standalone builds.
  • Optional kiosk mode for instructor-led labs.
  • Maintenance windows for content updates and device changes.
  • Documentation, runbooks, and admin training included.
02 Typical timeline
Realistic numbers, not a sales pitch. Larger or multi-site rollouts run longer.

What to expect.

From kickoff to pilot
0wk
Typical single-module engagement timeline.
Demo cadence
0d
Weekly playable builds during the Build phase.
Stakeholder touchpoints
0↑
One per phase, with clear deliverables.
Approval gates
0
Storyboard, alpha, and final acceptance.
Ready when you are

Start with discovery.

An hour-long call is usually enough to scope a first module. Bring a procedure, a hazard, or an audit finding, and we'll come back with a plan.

Book discovery → Browse services