So far I’ve given you a bit of an origin story for Agile Learning Design and spoken a little bit about the Design itself. The next thing I thought I’d do was lay out some principles for Agile Learning Design. This post is more manifesto than explanation — some of it definitely needs to be fleshed out and explained.
The Key Principles of Agile Learning design are:
Start the process off by understanding the constraints you are operating in – what’s the timeline for development, what’s the duration of the course, what’s the expected study time, what are the outcomes and how do we evidence that. Know your audience – their motivations, desires and skills and learn about their intents.
Design with intent and purpose. Know what you want in the course and design it in. Ask and map out the points of Wow and Joy and design for them. We get to define the whole experience, so don’t leave it up to chance.
From the outset ask big questions – like how do you want to change students? What will they remember in 5 years or 10 years after this course? We often remove this perspective from the design and get too bogged down in the details. Yet often the answers to these big questions contain little details, snippets of ideas that help to define what the course and the experience will be.
The shape of the course will emerge from the process, don’t seek to do it too early. The scope of the course provides the constraints and they will help guide decisions, but the shape of the course is malleable. Remember, it’s just text on the page — mutable and adaptable. Don’t force the course structure too early.
Content is content until it is something else. We use “content” as a container to get things out of the SMEs head. Write it all out to start and iterate through it. Begin with dot points, add paragraphs, add guiding comments and increase the fidelity over time. Text is mutable, it’s easy to transform into a HTML page, a video script or an interactive – but you can’t do any of that without knowing what the content is.
Snowball not waterfall. Map, plan and then add detail. The course is fluid until it’s built. Everything is just text on a page so it’s easy to change and manipulate. Move things around, don’t be afraid to change and adapt. As you go through you might edit out content, that’s ok. It’s as important to remove as it is to add.
As the Learning Designer the roles and responsibilities in the process need to adapt to the course, the discipline and the individuals you’re working with. Don’t define your role or pigeon-hole yourself. Be there to support and ask what needs to be done. Match the needs of the course. LDs can write, model, check and develop — so be comfortable with your expertise and with the fact that what you do may need to change. Your role is to shepherd the course through its development. The most adaptable thing is your relationship with the SME.
These principles have been developed from my experience and that of my team and the work we have been doing. They don’t really explain how or what the process and practice is – but they do at least define what we do and what guides our way of thinking. I hope to tackle some of the details in the next couple of posts.