With learning experience design (LXD), you are encouraged to create learning objectives that help learners change their behavior. I've talked about Terminal and Enabling learning objectives before but when I said those were the only two types of learning objectives, I was wrong. There aren't any.
After chatting with developers in your community and diving into how they learn, you'll have a pile of notes and data you can use to improve your marketing and DevRel efforts. What do you do with this data? Turn it into insights! One of the tools I use
In part 2 of the Uncovering your product's unique insight email series, I teased that having developer chats can help you design better developer experiences. How so? You can ask questions related to how people learn. By doing this, you can start to form a picture of how
There are 5 moments of learning need: 1. When you learn something for the first time 2. When you want to learn more, 3. When you try to apply and / or remember 4. When something goes wrong 5. When things change This has subtle power when you think about how
Continuing on this week's exercise of defining learning objectives for a hypothetical new Excalibur.js learning experience, yesterday I grouped the steps we laid out and asked if you had any ideas. Here are the groups again for reference: Group 1 * Explain what Actors are * Explain what Scenes
Yesterday we started to think about how to create enabling objectives from scratch using the Excalibur.js quickstart as an example. We came up with the following terminal objective: "Create your first game." The rough steps, in no particular order, that would be required to reach this objective
