strategy deployment

Matrices help prompt, organize, and efficiently display information. When the design is standardized, such as with (most) strategy deployment x-matrices, they facilitate a quick, universal grasp of the individual fields and their relationship with other fields. For example, a seasoned user can glance at an x-matrix and discern the small handful of breakthrough objectives, the associated annual (meaning this year’s) measurable targets, the corresponding annual improvement priorities, and their targets and means.

I remember, years ago, watching my oldest child struggle in his attempt to loosen a bolt. This was one of those all too few, brief, and shining child-rearing moments where I could easily and quickly share some trusty words of wisdom. “Righty tighty, lefty loosey.” I’m pretty sure that my son’s response was somewhere in the vicinity of, “Huh?” Not the effect that I was looking for necessarily. …Nevertheless, I’m going to try to apply the same advice, but to a different subject (totally without threaded parts). Strategy deployment (a.k.a. policy deployment, hoshin kanri, etc.). Huh?

First things first, as they say. It's hard to argue with such simple wisdom. That notion applies to strategy deployment, a.k.a.