Project Planning & Playbooks

Lesson Planning 

Live training benefits from traditional planning and outlining. I take a backwards design approach to adult education, focusing first on "what are the desired outcomes for learners?" and planning all activities with that goal in mind. 

This means that I start with my proof of learning, then scaffold all assessments, learning activities, and educational materials around what I expect my learners to be able to do by the end of the training. 

Documenting this process helps illuminate the educational experience for stakeholders and invites their input during design iterations. Clear, concise documentation also ensures the ability to scale and repeat, lessening wasted time and money for the business. 

Here, you can see a couple of simple examples of trainings that I have designed, including an activity that I put on to teach software engineers about the importance of accessible and inclusive design in software. 

Scalable Project Plans, Templates, SOPs

I believe that insight into your own practices is absolutely vital for a team. I make it a practice to always write operational procedures for my methodology, tooling, and projects. 

Imagine that you join a team, and content already exists. No one wrote down how it was made, and the creator has moved on to another company. Your only option is to either create new materials with potentially a different style entirely, or to attempt to reverse engineer what's been done. 

Sound fun? 

It isn't. I've done it. 

Documentation helps the business thrive. I've created plans for large, cross-functional projects that help guide each stakeholder and owner in the project. 

I've written internal playbooks for both tone and style, and technical guidance for complex systems use. 

I've developed templates for storyboards, project plans, communications, dashboards, videos, slide decks, and more. Templates are a gift to those around you, showing that you care enough about them to never ask someone to reinvent the wheel.