Content Map
Many people associate content maps with mind maps, but not me. For me, a content map is a defined structure of a course or project based on client-furnished information and overall learning objectives. I would liken it to creating an outline for an essay. Remember how your high school English teacher always made you write out (and usually submit) that damn outline for your essay? It may have been annoying, but it was important. The same way content maps are important.
It’s a lot easier to modify the structure of a course in the design phase, when you’re mapping out your content and the structure of the entire course. Here, feedback can be provided, and you won’t have to go into each and every module to make modifications. Sure. It might seem like an unnecessary step, but in the long run, it will save you time.
A content map will typically include, but is not limited to, the following elements:
- High-level course objectives
- Timing per module
- Module information, including sub-modules and topics
- Assessment information (e.g. type of assessment items to use).
Some folks might call this design documentation, but it’s really just a small portion of the design documentation.
In the Defence sector, it was not uncommon to walk into a room and see a wall full of post-it notes. This industry referred to these walls as ‘Scalars’, which provided overall scaffolding for training programs. At the smaller scale, these scalars are really just enormous content maps.
If you haven’t started using content maps, you should make this documentation part of your development process, even if it’s not a deliverable and even if it’s written on a post-it or napkin. In the end, it’s going to guide you and keep your project structured, which stands to increase the overall effectiveness of the training you’re developing.