Brew Dunnit? 🍺🕵️ An Oktoberfest Whodunit Where the Ingredients Are the Suspects
Somebody dry hopped the lager. 😱 A crisp Munich Helles showed up to Oktoberfest smelling like a California IPA, the Brewmeister is FURIOUS, and you’ve been called in from HR to find out who did it. 👉 Brew Dunnit? 🍺🕵️ The lineup 🌿 Hops: the obvious suspect, and very defensive about it 🌾 Malt: sweet, a little too eager, brought you a pretzel 🥔 Yeast: smug, has an alibi, and is NOT a potato 💧 Water: will not talk. At all. 👀 Leo the Intern: nobody ever suspects the intern Why a whodunit? The big idea in brewing isn’t just what goes in, it’s when. Hops in the boil add bitterness. Hops after fermentation add aroma. That one timing concept is what cracks the case, so learners can’t solve it without actually understanding the brewing process. Every interrogation teaches something real (lager vs ale, IBU, what malt does, why Helles is pale) and drops a clue on the evidence board. The accusation stays locked until you’ve questioned all five suspects, and wrong guesses get a very offended rebuttal. Malt is still hurt about the pretzel. 🥨 How I built it 🛠️ One Rise 360 Code Block, uploaded as a zip file 🎨 Characters created with Articulate AI image generation, all in the same interrogation room for a consistent look 💾 Progress saves with local storage, so you can leave and come back to your case ♿ Keyboard friendly, screen reader labels, and big readable text My favorite part? Water. Three questions, zero answers, and then it slides you the most important clue in the whole case. 💧😎 Would love to hear who you accused first! 👇Welcome to The Dugout
It is the 46th minute of a World Cup Final. The score is level. Your team is tired. The opponent likes to keep the ball. And the second half is about to begin. In this short challenge, you are not just learning about football. You are stepping into the role of head coach. You will make three tactical decisions. Each choice changes the match. Some decisions may create momentum. Others may protect your team. Some may work beautifully in one situation and fail in another. That is the point. Football is not only about knowing the rules. It is about reading the moment, making a call, and learning from what happens next. This experience was built using custom code blocks in Rise to create a more interactive, decision-based flow. Ready? Step into the dugout.Simple Solution = Best Solution for Customer Interaction (ELH Challenge #538)
Problem For this portion of my customer service eLearning module, I wanted to create an immersive experience that would help the learner practice the decision-making process and the approved scripting they must adhere to. Solution (my journey) I wanted to try my hand at using Rise360’s AI Assistant for a CSR-to-customer interaction. But my attempt did not produce what I was looking for. So… Why not try to “vibe” it? I switched over to Vibe Coding. I figured something “new” and “fresh” would liven up this customer service training module. I abandoned it after 12 attempts. I got close to a viable solution, but still had a ways to go. I returned to AI Assistant, used the proper format it needed, and tweaked the remainder of my scenario without using the avatar setting. Lessons Learned For a while, I was stuck in my head with the idea of “new and fresh.” But 10 out of 10 times, the simplest solution you build is likely the best possible one. Don’t underestimate simplicity. Finally, sometimes using a tool you touch daily can blind you to its potential in a new way. That’s what my final solution is – Rise360’s native scenario builder without the typical avatars I’ve used in the past. Conclusion Though we have access to “new shiny” tools and “AI on the brain,” tried-and-true tools and techniques will never go out of style. We ought to continually revisit the tried-and-true to be reminded how cool they are. 😉 Click here to experience the demo I built. 👀 It also includes more details of the great learning experience I had. 📝 Disclaimer: my demo doesn't strictly adhere to the challenge's parameters (a scenario instead of learning objectives), but I thought this would be a good place to share this learning experience with the community.
