This week I’m declaring my independence from having to write a new KJR entry. Don’t worry, not forever. Just this week, when I’m taking advantage of the KJR Reruns Policy, which states that:

  • Whenever I want I can substitute a re-run for a new column, and …
  • Whenever I substitute a re-run for a new column, you’re free to not read it (which freedom, of course, you also enjoy for new postings).

But I think you should read (or re-read?) this one. It’s from two decades ago, titled, “Battling to achieve strategic change,” and is just as relevant today as it was back then.

I hope you enjoy it and find it useful as you battle to achieve strategic change.


# # #

Maybe it’s just semantics.

A bunch of readers commented on my recent column asserting that CIOs and CTOs should spend most of their energy dealing with strategic and tactical matters, delegating infrastructure, (which I equated to the military concept of logistics), to others.

Among the comments: “Amateurs talk strategy, professionals discuss logistics.” This correspondent, along with quite a few others, mentioned a number of examples in which bad logistics lost battles. I agree: Bad logistics can lose battles, as when the Spanish Armada literally ran out of ammunition fighting the British fleet, which was able to re-supply since the entire engagement was fought in the English Channel. But this misses the point. Of course bad logistics can lose battles. That doesn’t mean great logistics can win them.

The lesson for you: Bad infrastructure can make even the best applications unavailable. Great infrastructure is invisible. Do you want to be invisible unless there’s a problem? I didn’t think so. Delegate infrastructure; focus your attention on strategy and tactics.

Or maybe on “Operations” in its military sense. IS Survivalist Ralph Hitchens informs me that military theorists have added this as a fourth level of military planning.

Above it all is the non-military concept of “policy.” “We’re going to stamp out terrorism,” is an example — a national goal which military action can help advance. “Strategy” determines the overall objectives of military action and identifies the major campaigns that should be fought to achieve them so as to help achieve policy. “Operations” decides which battles to fight and how to deploy forces to fight them to win campaigns.

Organizing business change has significant similarities. Enterprise-scale change corresponds to the strategic level of planning. Call the organized effort of achieving strategic change a “program.” Since “operations” would inevitably be confused with running a data center, let’s call the next-lower level of change “business outcomes” and call the organized effort of achieving them “initiatives.”

Then there’s tactics — the specific plan of action military officers create to win battles. What might that correspond to in IT terms?

Tactics corresponds to projects, in more ways than one. In terms of military action, it’s hard to be sure if you’re really achieving your strategy, or even if you’re attaining your operational goals. Likewise in business. Whether the topic is combat or project management, you can be very sure if you’ve won the battle.

It’s up to someone else to win the war.