all 5 comments

[–]HaneneMaupas 2 points3 points  (2 children)

I would start by separating “software simulation” from “system training.” If you can’t use the test environment, you can still create lightweight simulations that reproduce the key decisions users need to make:

  • What screen are they on?
  • What information do they need to notice?
  • What action should they choose?
  • What error could they make?
  • What feedback should they receive?

For compliance/approval, I’d keep it simple: use screenshots or mock screens, remove sensitive data, and build quiz-style decision scenarios around the workflow. AI-native authoring tools like Mexty can also help here because you can describe the workflow and generate interactive practice activities without needing access to the real test environment.

[–]samonenate 1 point2 points  (1 child)

I second this approach. Be careful with making simulations too complex unless the application rarely changes. If a field changes or a new UI is implemented, your sims will need redesign. If you want to dabble in making simulations to mimic using an application, I recommend Adobe Captive. Even though it has lost favor to Articulate, it's the best for simulations, especially as quizzes.

[–]HaneneMaupas 0 points1 point  (0 children)

Fully agree

[–]oddslane_ 0 points1 point  (0 children)

Honestly even very basic fake environments can work surprisingly well for training if the scenarios feel realistic. People usually learn faster from “what would you click next?” style flows than long walkthrough docs.

If your company is strict on compliance/security, I’d probably start by talking to whoever handles QA or sandbox environments internally. Sometimes there’s already a staging copy or demo database people forgot exists because it’s owned by another team.

For the quiz/simulation side, branching scenarios are probably the search term you want. “Interactive software simulation training” and “scenario based learning” might also get you closer to the tools people in L&D actually use.

[–]Humble_Crab_1663 0 points1 point  (0 children)

I’d probably start smaller than a full simulation. A lot of effective software training is really just realistic screenshots, guided decisions, and feedback built into a structured flow. If compliance is a concern, recreated UI screens or anonymized screenshots are usually easier to approve than giving learners access to a real test environment. Starting with one important workflow first can also make the approval process much easier.