Okay, Design Documents. This is where your skills as a learning designer come in. You’ve had your content meeting with your academic. You’ll have a video, some big sheets of paper, or some photographs. This then needs to be turned into a meaningful design document that captures 2 things:
1. The precise TEXT of any on screen learning content
AND
2. The exact NARRATIVE of any word spoken
Whichever way you look at these you’ll need to write it. If you have captured video of your academic explaining their content this can be easier because you can use their style of presentation and even transcribe verbatim what they actually say.
Creating your design document is best done in some kind of template. I find it best to feature 4 key elements: Learning outcomes, content (the on-screen text/ narrative), media treatments and an ID column. The ID column helps you assign assets (video clips, images etc.) and keep all of the course easy to organise.
The column that takes most of the time is the content (the on-screen text/ narrative). You may find yourself stuck with the content (remember, you are dealing with a subject matter expert who may be the leader in their field). Don’t expect to grasp everything and certainly don’t wrestle with your understanding by spending a lot of your own time studying. Most courses are designed for a certain level of understanding (say, undergrad level). Your SME has to be able to communicate with this audience and if you can’t understand it - the learners (audience) won’t either. So, if need be, leave gaps and flag parts where your SME needs to do a bit of work clarifying the text. Remember, they’ll usually be immensely grateful that you are doing the hard work for them; a bit of editing won’t faze them.
When you do hand back your Design Document for your SME to check, make sure that this is an official “step”. they must “sign-off” the Design Document to permit it to go to the next stage of development. If they don’t, you may find yourself making painful and costly re-writes several weeks down the line.
Once the text/narrative is done the next thing to do is to gather or schedule the creation of your multimedia assets. There is a synergy between the text/narrative and what is happening on screen. You need to be able to visualize the end-user experience and know what is possible - this will sometimes influence how you develop the narrative.
Eventually you will come up with a list of CREATED and CURATED assets. Once the script is agreed, spend your time getting these produced, stored and organised. Use the ID component of the Design Document to marshall these assets. Once you have your text/ narrative and assets within your Design Document commence technical development. But, in my view, never-ever commence development until you have a bullet-proof Design Document.