When we delegate responsibility, we’re frequently told, we must also delegate commensurate authority. Otherwise, we can’t hold delegates accountable.

As with so many other what-we’re-frequently-told statements, it’s more plausible than accurate.

Start with the organizational chart. What it does is document operational delegation — how the CEO has delegated responsibility (and, in theory, authority) for everything that has to happen for the organization to succeed.

Imagine you’re Director of Sales for a company that sells a variety of widgets, gadgets, and doohickeys. The company’s strategic plan calls for a 20% year-over-year increase in Gadget sales. You’re responsible, so you ask your top Gadget sales reps what they need to hit the target.

“Fix the product,” they tell you. “Our gadgets are the worst in the industry.”

So you convene a Gadget Redesign Committee, which dutifully creates new-and-improved Gadget specifications. You bestow them to the Director of Gadget Engineering.

Who bestows them right back, because he, not you, is responsible for and has authority over gadget specifications.

His strategic target is a 10% increase in gadget manufacturing efficiency. Your designs would reduce it. And you’re invading his delegated-authority turf.


No matter how you draw the boxes and connecting lines, anything important that has to happen crosses organizational boundaries. Successful products, for example, require research-and-development, design, engineering, supply chain management, manufacturing, distribution, sales, marketing, and advertising, and I’m sure I missed a few others.

Which illustrates why, as pointed out last week, there’s no such thing as a perfect org chart.

One solution is to create cross-functional teams to address boundary-crossing responsibilities. These work well when pointed at problems that require collaboration among those competent at the different disciplines required for success at whatever it is that needs to be successful.

But cross-functional teams are less well suited to when the company needs to be competent at something, with “something” encompassing organizational capabilities like: Project management, architecture, process design and management, organizational change, and quality assurance, to name a few.

That’s where Centers of Excellence (CoE) and Communities of Practice (CoP) come into play. Both are boundary-spanning entities whose goal is to improve organizational competence at a specified discipline.

Where they differ: CoEs are official entities with assigned leadership, budgets, and goals. CoPs, in contrast, are, as the name implies, true communities — self-organized, with goals defined informally and by consensus, and with the time and effort required for their success donated by community members on top of their official responsibilities.

Compare a CoE to, say, a Project Management Office (PMO).

With a PMO, the CEO has delegated both responsibility and authority for improved project success. Having authority, the head of the PMO is in a position to define and enforce the use of the company-standard project management methodology.

But as the head of every other organization has the equally delegated authority to run their operation as they see fit, including how they manage projects, conflict is built into this arrangement, right down to its core.

The head of the Project Management CoE, in contrast, is responsible for improving project management practices with no enforcement authority. Lacking authority, the CoE has to make use of a more subtle toolkit, one that includes internal marketing, persuasion and influence, a curriculum with certifications along the way, and one-on-one selling to managers throughout the enterprise.

When you can’t dictate you have to communicate and deliver benefit.

How about CoPs? As self-organizing entities they have a lot in common with volunteer organizations outside a business setting: They depend on the enthusiasm, commitment, and evangelism of people deeply committed to the practice in question. Usually, they’re even more dependent on a highly skilled, even-more-committed, charismatic leader to hold everything together, especially as many volunteers, in the absence of financial compensation, expect payment in the form of ego gratification.

CoPs can and do provide a lot of value. But they’re an unreliable organizational solution, because expecting a CoP to happen on its own is just trusting to luck. If a useful one does form, encourage it. Just don’t rely on it.

Can’t execs drive the process? No, for a simple reason: The act of encouraging a handful of experts to form a CoP instantly transforms it into a CoE, by definition.

By all means support CoPs whenever they form. But as a reliable way to increase organizational competence, CoEs are the way to go.

One last thought: Imagine the company has chartered several CoEs. Some work better than others. Should you charter a Centers of Excellence Center of Excellence?

Repress the thought. That way lies madness. Or at a minimum, uncontrolled recursion.

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.