I had a thought-provoking comment this morning about yesterday's post about telecom organizational structures and cost allocation, from a gentleman named Mark, countering my contention that in telecom, efficiencies gained through distributing authority and control can more than pay for efficiencies lost through redundant departments and systems. Here are some excerpts:
"This bit about control gets over-played. Certain functions should be shared; it's a more efficient use of capital. The rub comes when managers won't do the hard work to understand the cost drivers; measure and accurately report them; and work across the table with their peers to jointly minimize, at the margin, all costs - not just the shared ones. Substituting organizational structure for good cost accounting practices is a smokescreen."
Mark makes a good point, that part of the job of a manager is to work together with other managers across departments and collaborate on cost reduction or new product development, and I don't think I gave that enough attention in yesterday's post.
I can certainly cite examples where, as a line of business leader I had to rely on colleagues to help make the right decisions for the business, and where that worked well. One particular area was where our business counted on an external department to do capacity planning and trunk installation in support of an application-layer service. I think it would be silly to insist that my application-layer business unit needs to have its own circuit deployment department.
On the other hand, I can point to examples where relying on a central, shared department did not work nearly as well. In one case, the same application-layer business unit relied on an external, shared IT department for all systems development. The IT department served business units covering the whole gamut of services, from colocation, to wavelengths, to high-bandwidth long-haul transport services, to Internet access, to application-layer services. The IT department faced the impossible task of fielding requests from all business units and from operations, and prioritizing those requests in the midst of a great deal of lobbying on the part of the requesters, while simultaneously trying to serve their mandate to implement all of these requests on common systems for each function (order entry, provisioning, inventory, billing, etc.). The IT department was funded with a budget that defined their capacity, and a resource allocation committee of highly-paid SVPs, VPs, and Directors would regularly meet for hours at a time to try to figure out how to allocate the limited IT capacity. Lots of time and energy, and money, was spent in those meetings.
Departments soon sprouted "program managers" whose primary function was to make sure that the IT group followed through on committee decisions to fund a particular project. More time and energy and money spent. The resource allocation committee sometimes changed their mind about priorities (suprise!) and the IT group was asked to change course, leaving half-finished projects and hoping to get back to them, someday. Definitely a sub-optimal arrangement, in my view.
Of course, many business unit leaders don't have the experience or time to understand all of the ins and outs of information technology, so it won't always make sense to give each business unit their own IT department. And some systems should be shared, and there should be some synergies by developing experts in certain systems and software and re-using those experts across multiple business units.
So, is there a good alternative to the resource-allocation approach? I can think of one potential solution: give each business unit their own budget, their own P&L, and allow each business unit to decide how much of their budget they want to spend by hiring the shared IT group to build a new wrinkle into the billing system, or develop some of the systems in support of a new product. If the central IT group is over-subscribed, they need to develop more capacity or outsource the project. Price competition can be introduced by allowing competitive bidding from external IT shops. Yes, you will get some proliferation of redundant systems that way, it is a trade-off, for sure, but you also get the benefit of freeing hostage business units to do what they think is right to meet their business goals.
There are other approaches as well. I only bring up this example of IT as an example of how shared functions can generate more "hard work" for managers than can be justified. In my experience, managers are often eager to "work across the table with their peers." They just aren't happy about it when it is clear that the organizational structure is creating a great deal of waste... waste that they will pay for when it comes back to them as an allocated cost on their P&L statement.