It is one thing to describe the eXACT methodology in the abstract. It is another to see how it plays out on a real project. This post follows a project through each stage of the eXACT methodology, from the first client conversation through to a finished course.
To keep things clear, we will follow a hypothetical example based on our experience. A client commissioned a compliance course. Staff across several departments needed training on a new workplace policy within a tight timeframe.
Starting with eXplore
The initial brief seemed straightforward. The client needed a course explaining a new policy, completed by all staff within twelve weeks. Conversations with stakeholders during eXplore revealed more nuance. Different departments interacted with the policy in different ways. A previous attempt at training on a related topic had been bady recieved, since staff found it generic and irrelevant to their work.
This shaped our approach significantly. We agreed on a single core module covering the policy itself. We layered short department specific scenarios on top, rather than building one generic course. We also defined learning outcomes around more than just policy knowledge. Staff also needed to recognise when the policy applied to their own work.
Planning it out in Architect
The storyboard reflected this structure clearly. We mapped out the core module screen by screen. We also storyboarded each department specific scenario separately, using a consistent structure to keep development efficient once approved. The client reviewed the full storyboard before we began any build work. They asked us to refine two scenarios so they better reflected situations staff would actually encounter.
We made these changes at storyboard stage. That meant a matter of days, rather than rebuilding finished screens.
Building it in Create
The bespoke eLearning project needed branching scenarios tailored to different departments, so we built the course in Storyline. Scenario based interactions let learners make decisions and see realistic consequences. This suited the goal of practical application over simple knowledge recall. We built in accessibility considerations throughout, including keyboard operable interactions.
Confirming it worked in Test
Testing covered the following areas before launch.
- Functional testing of every scenario path and branch
- Screen reader testing across the core module and each scenario
- Content review against the original learning outcomes
- Device and browser testing to reflect how staff would access the course
- LMS test to ensure reporting
This stage caught a labelling issue on one scenario. It would have confused screen reader users. We also spotted a minor inconsistency in how one department used certain terminology. We resolved both issues before launch.
What the eXACT methodology delivered
The finished course launched on schedule. Client feedback showed noticeably higher engagement than the previous generic training attempt. None of this happened by accident. It happened because we followed the eXACT methodology closely, and each stage contributed something specific. eXplore uncovered the real problem. Test caught accessibility issues that would otherwise have gone unnoticed until learners encountered them directly.
