VersionControl - FINALfinal v6.7.3 THIS ONE I SWEAR TO GOD


Problem: Version control in text-based projects can be a nightmare. Almost anyone can edit a Word doc, which means everyone does. There is no cost associated with producing an additional draft, so it doesn’t matter if it takes seven versions or fifty-eight. Of course there are costs in time and cognitive load but those are too abstract to feel finite.

Additionally, aside from the deadline, there is no concrete endpoint. Numbers go to infinity. Plus one.

What if instead of numbers, we use city names?

Use Case
I use this The Canada Protocol when working on a project where loss of momentum is catastrophic. Book writing, for example, is exciting at the beginning and at the end. What comes between is a slog. In such a project, each new city represents a significant update in the draft, rather than small changes to a chapter or adding additional material.

The concept can easily be adapted for other projects with long horizons - SAP S/4HANA changeover, a significant product update or even a store opening.

Why it works

  • Numbers are an open system. Geographical points are closed. After Gander it’s the Atlantic Ocean, which means unless you fancy a long, cold swim, the project is over.

  • A visual record of progress is a huge boost to momentum. And in those low-motivation moments in the middle when it seems like the project will never end, it is helpful to see that eventually you’ll get to Gander and everything will be fine.

  • The map gives team members something concrete for discussions - we reach Halifax in three days, what do I have to finish by then?

  • A journey is an easy narrative and maps are a recognizable format, so the cognitive load for adoptation is low.

Let’s try it

I’m very curious how this framework can be adapted for other types of projects. I’m working on creating some materials to support workshops.

In the meantime, drop me a line if you’d like to walk the model through.