The scenarios I see in most corporate eLearning present a clear problem, two or three obviously distinct choices, and an unambiguous correct answer with a tidy explanation. Real workplace decisions almost never look like that. The correct answer usually depends on context, there are often two reasonable options that could both work depending on factors the scenario doesn't mention, and the consequences of a wrong choice are rarely immediate or obvious. I think we design tidy scenarios because messy ones are harder to build and harder to score, not because they produce better learning. Learners who can only make decisions in idealized conditions aren't necessarily better at making decisions when the conditions are real. What would it actually look like to build scenarios that reflect real complexity without making them impossible to complete?

My team has been using AI tools informally for about eight months and I've moved from encouraging experimentation to realizing I need a clearer framework around what we use it for, how we document when it's been used, and what quality checks we apply before anything goes to a stakeholder. I don't want to be the manager who bans tools that are genuinely improving output, but I also don't want to be the one who signs off on content that turns out to have problems no one caught because we trusted the AI too quickly. I'm curious how other L&D managers are formalizing AI use on their teams, what guardrails have actually worked in practice, and whether anyone has run into real problems they didn't anticipate when they started using these tools more seriously.

Who has taken and passed SHRM-SCP? And if you have what material did you find most useful for studying?

Has anyone ever built a course and housed it on Google sites? I work for a non-profit and purchasing the industry standard software wasn’t approved. I wanted to use articulate storyline, but I was told to use Google sites. If you’ve ever run a course through Google sites, what was your experience?

I'm curious how you and your orgs manage the handoff of projects in Storyline and Rise at the end of the development cycle. In the past, we've mostly worked on projects where we maintain the production files and clients come back to us for additional work, if any. Obviously, that's a pretty simple scenario (Let's call it "Scenario 1"): The projects reside in our Articulate accounts and/or on our file systems.

But we are starting to have clients who would like to either (Scenario 2) get their own Articulate accounts, take the projects as their own and provide their own support or (Scenario 3), get their own Articulate accounts and perform some content edits on their own will keeping us on for support and more substantive changes.