As a designer, I’ve learned that tools can be inspiring at best, a siren's song at worst. Sometimes, just exploring a new app or platform sparks ideas for how I might enhance an activity or rethink a learning experience. That said, I try not to let the tool lead the design, which can be an easy trap to fall victim to. I've made that mistake before, and it takes a certain amount of restraint to not get starstruck by tool features and functions.
My process typically starts with determining the learning goals, which is a best practice in the industry. Before I open any software, I ask myself what the learner should be walking away with. What skills or knowledge should they build? And then I can think about the right tool for the job based on that outcome. This requires me to ask myself even more questions: Is Tool X helping learners engage with the lesson better? Will it help create a deeper connection to the concepts? Will it promote reflection and collaboration? Are there features that can promote engagement in unique ways?
These questions keep the focus on purpose over novelty and act as a speed bump for me, forcing me to slow down and think through what I'm looking to achieve. All said, I love shiny new toys - I think most IDs do - but we need to keep the learner experience top of mind. We use the tools, not the other way around.
Comments
Post a Comment