In November I learned a valuealbe lesson. My wife and I were getting ready to run a 12K race in Vancouver, WA. The weather forecast called for high 30s to low 40s and rain the day of the race. It’s the Pacific Northwest so rain is always likely. I packed running clothes that I thought would be right for the race and the weather.

The day of the race we woke up to cloudy…but not rainy skies and tempatures in the mid to upper 40s. I decided that I would stick to my plan and wear what I brought. As you can see from the picture that included a rain proof jacket plus a cold weather long sleeve shirt and a running shirt. 

My wife warned me I would be to warm, but of course I didn’t listen to her advice (why should I, she runs faster and farther than I do). When we stepped outside the hotel I felt comfortable not to hot, not to cold. My wife on the other hand was a bit cold…huh….who’s laughing now?

The race started and not 3K in I started getting a good sweat going. My muscles loosened up and I found my stride. By the 6th Kilometer I was hurting. I was tired, soaking wet from sweat, as the rain jacket did what it was suppose to do and keep my heat in. I was dying to keep up with my wife (which is always my goal…I’ve yet to beat her in a race…2014 is my year though!)

My wife on the other hand was feeling great..she went from a bit cold to nice and warm and perfectly dressed for the race. Needless to say by the 8th Kilometer I was pealing off layers trying to cool down and get my energy back (with my wife running backwards a few steps ahead of me egging me on…..wish I was making that up).

I did finish…in a t-shirt and plenty warm.

Planning for the end not the beginning

As I was running this blog post starting rolling around in my head (I write a lot of blog posts while running….I need to get better at actually writing them down). I made a common mistake. I planned for the beginning of the run not the end of the run. It’s the same thing I see happen with technology plans or with laptop/tablet roll out programs.

All to often I see school districts plan and overplan for the beginning of the roll out or the impact the new technology might have and less time on what happens next.

It is the problem we all face with technology plans. We make a plan based on the data we have, we prepare to implement the plan and even when things (like the weather) around us change we stick to the plan thinking we have to. Technology moves way to fast to “stick to the plan”. Technology plans need to be simple, lightweight, and easily changeable. Otherwise you find yourself half way through trying to peel off layers and keep the momentum going.

We talk a lot in education about the “Backwards By Design” model of lesson planning. A method I used in the classroom, we still use in COETAIL and most other planning I do.

Yet I don’t find it much in creating technology plans.

What does learning look like in 3 years time? 

When creating plans with admin teams and school districts I like to start with this simple sentence. Not what technology does everyone have, not what do we need….but rather what does it look like. From there we talk about the skills that we hope student will learn. This isn’t a new notion. I wrote about this process in 2007 in this free PDF you can download from the front of my blog.

It’s a paper I still use today with teams. The tools have changed the idea of in sourcing to outsorcing has changed (unless you are in China…which is where I was when I wrote this…and it still applies) but the idea of starting with the question of “What do we want students to learn?” and working backwards from there is still an important one to start with.

What happens when you don’t start with the end in mind is something that I’m starting to see a lot of (and we’ll see if this holds true for 2014). It is the questions that is asked after every students has an iPad or a laptop or both.

Now what?

Getting the technology into the students’ hands really is the easiest part of the process. Rethinking learning, rethinking teaching, rethinking the classroom structure, the value of content vs process, are the really hard parts. They are the parts at the end of the plan that many times are overlooked because they aren’t tangelable. They aren’t shinny and new, but they are more important.

Refuel Stations

The only thing that saved me that last race was that about 9 Kilometers in when I was really struggling there was an refueling station. My wife pushed an energy gel pack in my hand and a cup of gatoraid. A half a kilometer later I felt it kick in, got my energy back and finished the race pretty strong (my time splits to the right thanks to runkeeper).

There is nothing wrong with using refueling stations. In technology plans these can be sending teachers to conferences, bringing in a consultant, or having a renewed technology focus. We need to be refueled in our passion and our beliefs of why we do what we do and where we expect this new learning to take us. Many times I get the sense that schools and districts feel like they have to go it alone as if asking for help is a sign of weakness or unpreparedness.

Building this into a technology plan and revisiting it helps. You don’t always know where you need a refueling stating. Is it 1 year in? Is it 3 years in? However having the option to have one is what matters. A team, much like a runner, can tell you when the refueling is needed. Be flexible, be open to opportunities and if someone pushes an energy gel pack in your hand…take it.

We make planning many times more difficult than it needs to be. It’s a pretty simple formula really. Start with the end in mind, be willing to adjust your plan when things change, use refueling stations and listen to your wife those around you.