Minwal is our simulation delivery methodology: who leads the session, how trainees practice, and when practice becomes proof.
In Arabic, a minwal is the loom beam cloth is woven on. The word also means: the method. We weave every session on the same loom: four delivery modes, two purposes per mode, one session arc. The methodology ships with every project, and we train your operators on it.
The Session Arc
The mode changes from session to session. The arc does not: prime, then experience, then debrief.
Before the headset: we set the goal, explain the controls, and fix the competency threshold.
The heart of the session. One of the four delivery modes runs here, and Miqyas records every attempt.
After the headset: we read performance from Miqyas, not from memory. Where did the trainee hesitate, and how long did decisions take?
Our debrief is a data reading, not an impressions round.
Axis One · How the session runs
The modes step down from full support to full independence: the trainer performs, then we perform together, then you perform alone.
The trainer wears the headset and performs on screen for the group. Trainees see the expert's path before carrying the load themselves.
When it's chosen: First exposure to a new experience, a complex procedure, or a large group with few devices.
Guidance
One trainee performs while a peer follows on screen and evaluates, then they swap. One device trains two people.
When it's chosen: Consolidating a skill after the demonstration, and keeping everyone active when devices are few.
Guidance
Everyone inside one experience that demands role coordination under pressure. These skills are about other people, so they cannot be mastered alone.
When it's chosen: Resuscitation teams, critical incident management, and professional team communication.
Guidance
Each trainee runs the experience alone, repeating until they reach the competency threshold.
When it's chosen: Building individual mastery documented in the mastery report, and scaling to large numbers.
Guidance
Axis Two · Why it runs
The same mode runs once for learning and once for proof. The difference is declared before the session, not left to an operator's mood.
Feedback during performance, unlimited attempts, and safe error. Here the skill is built before it is tested.
A proctored session performed once, without prompting. Miqyas becomes the score sheet, and the session ends in a mastery report.
The Governing Principle
We fix each experience's valid modes at design time, so the choice is never left to operator judgment. The experience arrives with its operating method.
Its nature locks it to one mode. A team-coordination drill is about coordination itself, so it runs collaboratively only.
It climbs the whole ladder with the trainee: guided for beginners, then dyad, then independent, then a certification session.
It fits some modes and not others. A narrative awareness experience runs guided or independent; collaboration adds nothing.
The Integration
The same Miqyas works inside all four modes: it records attempts, reads performance as it happens, and produces the mastery report. Explore the Miqyas system →
In the demo we run a real experience in front of you, switch the delivery mode as you watch, and you see how Miqyas reads performance in each one.
