The main topic of this post is the way that the project moved from idea to something more concrete.
This is post is an overview of the more technical considerations like lining up the course structure with the requirements of a range of curricula. Yes, it’s at least as much fun as it sounds……..
At the time of writing I plan two more posts: One looking at how the course went day by day and another on “Lessons Learned”.
The latter will try and answer the question “with what I now know having run this course, how should I have run it“.
Keeping it simple
As is often the way with development work many hours and days of work eventually boiled down to nice simple course specification document.
This set out all the traditional stuff like aims & objectives, risks and issues, and learning outcomes.
However it also gave guidance on the approach that I thought would be required to keep a class of 16-18 year old vocational students interested and engaged over a a five day course.
In this case the whole course specification took just 10 pages.
The “mother” test
I was pleased with the clarity and simplicity of the course specification. My rule of thumb is that if such a document is complex and hard to follow it probably hasn’t been thought through as well a it could have been.
The test I like to apply is “could my mother have understood this”.
This might seem like a bit of a strange idea. After all, what could a lady well into her 80s possibly know about what I am doing?
This is the point. Often such documents are read by busy people who may not have a detailed understanding of the topic.
The job of the writer is to make it as easy a possible for the reader to find and make sense of the information they need to make a decision.
The way I look at it is this: if my late mum (Hi Mum – I’m still thinking of you) could understand what I wrote then so could a busy Chief Exec.