Process
How projects run
A clear build process keeps your stakeholders aligned and makes approvals painless. Here’s what a typical engagement looks like.
1) Discovery
Define the win
- Training goal, audience, constraints, and success criteria
- Devices, LMS needs, and deployment environment
- Source materials: SOPs, JHAs, checklists, photos, floor plans
2) Design
Storyboard the experience
- Scenario flow, decision points, and assessment checkpoints
- UI/UX (prompts, indicators, feedback)
- Content review with SMEs for accuracy and policy alignment
3) Build
Iterate quickly
- Prototype → alpha → beta milestones
- Performance tuning for standalone headsets
- Accessibility and comfort options where applicable
4) Validate
Pilot with real users
- Run through with target learners
- Collect feedback and identify confusion points
- Refine scoring, timing, and clarity
5) Deploy
Ship + support
- LMS packages (SCORM/xAPI) or standalone builds
- Admin guides + trainer notes
- Maintenance options for updates and new modules
6) Scale
Build a library
- Standard templates for consistency
- Reusable environments and interaction systems
- Faster turnaround for new scenarios
What we need from you
To move fast
- Procedure steps + “non-negotiables” (what must be done, in what order)
- Photos or walkthrough video of the relevant area (even phone footage)
- Brand guidelines (logo, colors, any UI constraints)
- Any required quiz / competency checks for compliance