There’s no such thing as an IT project. There is, on the other hand, such a thing as There’s No Such Thing as an IT Project: A Handbook for Intentional Business Change. It’s now officially available for purchase (or will be tomorrow morning). Humility prevents my coauthor, Dave Kaiser, and me from telling you it’s the most important business book published this year.

It’s a good thing we’re so humble. Or maybe not, because if you have anything to do with making business change happen … intentional business change, that is … you need this book. And I hope you’ll forgive a bit of hard selling because if you want the organization to change you’ll want your peers and collaborators to understand what it is you’re doing and why.

What’s the book about? It’s about 180 pages long. It’s about eighteen bucks … a dime a page … if you want the Kindle edition, more if you want crushed trees smeared with ink, and if you do, consider buying it straight from our publisher (https://www.bkconnection.com/books/title/Theres-No-Such-Thing-as-an-IT-Project ).

It’s about the difference between “implementing software” and something useful coming of it.

It is, we think, comprehensive without being tedious; practical and pragmatic while still presenting big ideas; clear and concise without being humorless.

If you’re a long-time KJR reader you’re familiar with the mantra, for example from this ten-year-old evergreen from the archives – https://issurvivor.com/2009/12/07/someone-elses-problem/ .

Now, instead of having to root around in the archives to pull everything together you’ll find it all in one place.

That’s how KJR works. You get a concise account of a narrow slice of a big topic once a week, out of the goodness of my greedy little heart. You get a complete view of subjects that matter from the books I publish from time to time (look here if you want to know what else I’ve written over the years: https://www.amazon.com/Bob-Lewis/e/B001HMOX0I/ref=dp_byline_cont_ebooks_1 .) It’s one way you can support KJR — something readers ask from time to time.

If you like the ideas and need help making them real, give me a shout. https://issurvivor.com/contact/ . With many consultants you don’t really know what you’re getting into. I am, more or less, an open book.

Well, 12 open books, but who’s counting?

Oh … one more request. Books aren’t real until they have a bunch of Amazon reviews. So I’m asking you to write one — preferably after you’ve read the book (as a consultant I have a strong sense of sequence).

If you like the book, please say so and explain why. And if you hate it, please explain that in a review as well. I’m not trying to put my thumb on the scale — I like good reviews as much as the next author, but it’s more important for the book to be real.

And don’t worry. Unlike public radio, I’m not going to hold KJR hostage until enough of you have bought the book.

I might badger you about it from time to time, but I won’t fill more whole columns pleading with you and your fellow readers to satisfy my deep craving for attention. Dave and I hope you enjoy the book and, more important, find it useful. We won’t know, though, until we read your review.

What do self-driving cars have to do with IT governance?

As it turns out, quite a lot.

Start with (self-promotion alert #1) the phrase “IT governance.” As long-time (and, I hope, short-time) readers know, in KJR-land there’s no such thing as an IT project — an idea so important Dave Kaiser and I named our soon-to-be-available book after it.

You’d give a perfect self-driving car your destination and let it figure out whether the best solution is to drive you there, to fly … at which point it would book your tickets and drop you at the airport … or make some other arrangements. Self-driving car governance should be transportation governance, just as IT governance should be business change governance.

More important than even this is how badly many designers of all forms of corporate governance ignore one of the most basic elements of delegation.

The element in question is the difference between delegating goals and delegating tasks. You’ll find (self-promotion alert #2!) what you need on this subject in Leading IT: <Still> the Toughest Job in the World. Put simply, the most effective leaders only delegate tasks when they can’t trust the person they’re delegating to enough to delegate the goal and leave the details to the delegate.

Look at it from the perspective of a self-driving car’s owner, who, even if the current state of the art doesn’t include booking tickets for some other mode of transportation, should be able to enter the destination and let the car handle the rest.

Except that no self-driving car is reliable and adaptable enough to handle all the details without human supervision. Humans metaphorically delegate driving tasks to the car but … and this is the essential point … can’t trust the car to handle the job without oversight.

Take a look at business governance as usually practiced and you’ll find distrust is baked into the heart of it. Governance is all about controls. Some controls are useful — they make sure processes are … well … in control.

They’re fine. But then there’s the other kind — approvals, to make sure those who have a job to do lack the authority to screw it up by just doing it, by requiring one or more signatures first.

This doesn’t mean organizations should become free-for-alls. No, organizations should prescribe their processes and practices clearly enough, and educate their managers and supervisors enough that those responsible for doing stuff know when there’s a corporate recipe in place because, for example, legal and regulatory requirements don’t leave room for creativity.

They should prescribe processes and practices in detail when the company’s systems and process management would be messed up if everyone accomplished similar goals in radically different ways.

That’s all fine. What isn’t so fine is when what’s prescribed is, in self-driving car terms, turn-by-turn directions, each turn of which requires someone’s signature.

Because that’s what controls end up looking like — the need for outside approval of each step managers, supervisors, and employees need to take to get their jobs done.

Governance by controls, which is what we’re talking about, has three major disadvantages. The first: it slows things down, because each approval takes actual time, which incurs delays.

The second: It adds to the workload of already up-to-their-eyeballs-in-more-important-matters executives. This doesn’t have to be overly onerous, so long as the executives in question are willing to just rubber-stamp the decisions in question. But if they rubber-stamp everything, what’s point of requiring their signature?

The third disadvantage? It’s demoralizing. I worked with a company a number of years ago that wanted to revamp its capital approval process. Something my team learned along the way was that the smallest decisions required the most signatures (six), and each signatory except the last resented being second-guessed.

What we heard, over and over again, was the same complaint: “If the company doesn’t trust me to make a decision like this, why did they hire me?”

Which might (and, I hope, did) lead you to ask, if governance isn’t to operate through controls, what’s the superior alternative?

The self-promotion-opportunity #3 answer: As Scott Lee and I point out in The Cognitive Enterprise, culture is (or should be) the new governance.

That is, for self-driving cars, culture provides, metaphorically, the lane markers. Controls are the guardrails, something self-driving cars that stay in their lanes will never make contact with.

The parallel? Governance bodies should spend most of their time instituting a culture that makes most controls unnecessary.

Oh, and I hope I didn’t hurt your feelings by comparing you to a car.