Participation depends on whether practice feels relevant and useful. Treat learner and trainer acceptance as part of the evaluation, not as something to solve after purchasing.
Choose a situation people recognise
Start with a difficult conversation or workflow the team genuinely encounters. Generic personas and unrealistic responses make it easy to dismiss the exercise. Ask experienced representatives to test the scenario before introducing it to the wider cohort.
Calibrate the difficulty and feedback
A scenario that is impossible, trivial or scored inconsistently will undermine trust. Review the criteria with trainers and test more than one valid way of handling the situation. Feedback should explain a specific behaviour and give the learner a practical next attempt.
Explain how the evidence will be used
Tell people what is practice, what is assessment and who will review the result. Provide a route to question an inaccurate score. Do not imply that a developmental exercise is confidential if managers can view it, or turn practice into an undisclosed performance decision.
Protect time for practice
Fit assignments into the actual working schedule and connect them to an upcoming task. Ask learners where they got stuck and trainers what administration it added. Completion alone can conceal frustration; review the experience alongside performance.
Make adoption a pilot criterion
Agree what useful participation looks like before rollout. In a Solidroad demo, test the feedback and repeat-attempt experience with your own team. Expand only when the scenarios are credible and the programme has an owner who can keep them current.
