Example
How to Talk to Your Instructional Designer
đŹ Speaking "ID": A Vibe-Coded Translation Guide
Weâve all heard themâthose classic stakeholder phrases that make every instructional designerâs eye twitch just a little bit. For this weekâs challenge, I wanted to tackle the "Don't Say This / Instead, Say This" script using a slightly different workflow.
đ ď¸ The Tech Behind the Scenes
Instead of building a traditional interaction, I went the Vibe Coding route. I used natural language to "vibe" the interaction into existence and then integrated it into a Rise 360 Microlearning.
It was a fun experiment in rapid development:
- The Goal: Create a sleek, visual way to show stakeholders a better script.
- The Method: Vibe Coding + Custom Blocks + Rise 360 Microlearning template.
- The Result: A modern, responsive interaction that feels custom but was built with a totally different logic than a standard drag-and-drop.
đ The Script
Inside the microlearning, you'll find a series of common stakeholder "red flags" paired with the professional, ID-approved versions weâd all love to hear instead. Itâs a little bit of humor, a little bit of storytelling, and a whole lot of workflow experimentation.
Check out the Vibe-Coded interaction below!
4 Replies
- CarolN21Community Member
Shannon, Your graphics pulled me in, but I wasn't sure how to navigate and move forward. What am I missing?
- Thomas_ShayonCommunity Member
Thanks so much for sharing your demo. I always appreciate your breakdown, explaining the "how" behind your demos. In this one, I thoroughly enjoyed the custom feedback and precise language used.
