Love how your testing strategies emphasize practice!
I like to keep a very minimal set of lecture notes which I call my "Timing Notes." They consist of a table with two time columns (how many minutes into class are we now; how much time should this chunk take?) and the section or activity for each chunk. I keep a few notes on that document for reminding myself of what to prep before class - opening websites / simulations to avoid wait time, or demos to prep, or notes for something specific I want to remember to say. Pretty much everything I do is otherwise centered in my slides like you demonstrate (bubbles like "let's do a worked example on the Doc Cam"). I find this leaves me with enough flexibility that I can improvise when needed, but have enough structure and assurance that I'll hit the key points.
One page fits 2-3 class sessions, and I annotate these with notes for the next iteration. I keep them in Google Docs and include a link to the day's slides. I can thus share my timing notes with other faculty and everything outside of the LMS comes along for the ride, so they can see a sense for what we do without an overwhelmingly long doc.
Your timing notes sound brilliant. Would you be willing to share an example with me so I can see how it works in practice? I'd love to implement something like that.
Love how your testing strategies emphasize practice!
I like to keep a very minimal set of lecture notes which I call my "Timing Notes." They consist of a table with two time columns (how many minutes into class are we now; how much time should this chunk take?) and the section or activity for each chunk. I keep a few notes on that document for reminding myself of what to prep before class - opening websites / simulations to avoid wait time, or demos to prep, or notes for something specific I want to remember to say. Pretty much everything I do is otherwise centered in my slides like you demonstrate (bubbles like "let's do a worked example on the Doc Cam"). I find this leaves me with enough flexibility that I can improvise when needed, but have enough structure and assurance that I'll hit the key points.
One page fits 2-3 class sessions, and I annotate these with notes for the next iteration. I keep them in Google Docs and include a link to the day's slides. I can thus share my timing notes with other faculty and everything outside of the LMS comes along for the ride, so they can see a sense for what we do without an overwhelmingly long doc.
Your timing notes sound brilliant. Would you be willing to share an example with me so I can see how it works in practice? I'd love to implement something like that.