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.

Bob

# # #

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.

When I was a teenager, many households had to add a phone line because my fellow teens and I spent so much time talking to each other in the evenings.

Housewives stereotypically (we are talking about stereotypes) spent hours during the day gossiping with friends over the phone.

Now that we’re old enough that geezing is becoming a hobby, we know deep in our bones that the ETG (embedded technology generation, aka Generation Z, Digital Natives, or iGeneration) are unhealthily glued to their smartphone screens, which is leading to the deep and distressing decay of our society.

Because nothing encourages self-righteous indignation so much as guilty equivalence.

Meanwhile, in another part of Equivalencytown, back in the ’60s the youth of America expressed their distrust of the government by dressing funny and participating in protest marches. That’s in contrast to the Tea Party of the late ‘2000s, whose members (the same generation only older) expressed their distrust of the government by dressing funny and participating in protest marches.

And before you go there, don’t: The January 6th insurrectionists had no equivalency other than the dressing funny part. And anyway they have nothing to do with this week’s topic, which is about recruiting, hiring, leading, and promoting members of the ETG.

From what I’ve been reading, this is hard to do, because [insert negative ETG stereotype here].

Maybe I’m missing something. It’s entirely possible, because I’m not hiring anyone any more. On the other hand …

A favorite ETG stereotype is that its members are “entitled.” What do they feel they’re entitled to? Stuff they want but haven’t earned.

For example?

Here’s something. From what I’ve seen, heard of, read, and imagined your typical ETGers think they’re entitled to pleasant working conditions, supportive leadership, compensation for 100% of the time they’re on the clock, and the sense that what they do for a living contributes to something important.

Maybe this is unreasonable and entitled. On the other hand, the stats say about half of working adults have left at least one job because they figure getting away from their manager will improve their lives. It appears there’s a lot of entitlement going around.

Jumping to the punchline, you can expect lots of ETGers to prefer the gig economy and remote work to traditional employment, because it puts them in better control of their financial situation and working environment. Gig work is also, in their eyes, a more honest account of their relationship with their clients – arm’s length, transactional, and with loyalty limited to pay they receive.

Think of it as the level of patriotism you’d find in a mercenary army.

So if your workforce is underpopulated and you’re having trouble finding people, look to contractors whose responsibilities can be handled remotely as an alternative to traditional recruiting.

Meanwhile, to the extent a contractor/client relationship with your workforce isn’t a satisfactory solution, the supply side of the equation isn’t likely to improve very much, at least not in the short term. The math of it says f = c + r – d, where f, your future workforce population, is equal to c, the current population, plus r, the number of new workforce recruits, minus d, the number of defections.

Yes, I know, and I’m sorry (no, I’m not). I’ve asked you to wade through what really is the day-before-yesterday’s news: reducing undesired employee attrition by making sure you provide a great place to work is as good an investment in your organization as you’re likely to find.

It looks like, in this respect at least, the future is going to look a lot like the present only more so.

Bob’s last word: I was tempted to provide a bulleted list of concrete steps you can take to reduce undesired attrition. I decided against it, on the grounds that the KJR community doesn’t need one.

If you do need help getting to the starting gate, try this: start by removing everything that makes employees’ working environments unpleasant.

Bob’s sales pitch: It’s summer! Time for some light reading. And what could be lighter than the novel Dave Kaiser and I wrote … inspired by a true story! … about a woman who was killed by an elephant in Wisconsin Rapids, Wisconsin.

It’s titled The Moral Hazard of Lime Daquiris, and, no, it isn’t one of those business theories that’s packaged into a novel so as to slip the author’s ideas into a digestible form.

It’s just light reading. I’m pretty sure you’ll enjoy it.

Now playing on CIO.com: The Edison Ratio: What business and IT leaders get wrong about innovation.

They get (and brag about) their responsibility for the 1% inspiration but often miss the remaining 99% of what’s needed.