- Whether to mention a pregnancy in a job interview
- A possible meeting protocol
- What are an end-user's responsibilities?
- Another take on opening PCs, or not
- Getting some process going
- Selling a more open environment to management
- Running an effective meeting
- Licensing rules for virtual machines
- The ROI of metrics
- Legal challenges to virtual machines
October 10, 2006 | Comments: (0)
Will central IT allow independence?
Dear Bob ...
1. Operational excellence
2. Product leadership
desktop systems that are the same everywhere, run servers that are the same
everywhere. Minimizing overall cost (or at least "first incurred cost") seems to
be a hallmark of this model.
intergalactic IT group that supports desktops and servers and the like. We work
for R&D researchers, and as such have to know a lot about their business,
have to offer customized services and products that change quickly due to the
nature of R&D. I'd say that we are in the "customer intimacy" service model.
to pull in all "embedded" computing. They claim that they know how to manage
different support models, but all we ever see is the "one size fits all" mantra
that the operational excellence service model is known for.
opinion on service models, and especially any history/advice you have on
organizations trying to blend service models.
- Being intergalactacized
Dear Warped ...
I'll take up the service models question in a future Keep the Joint Running. The other question you asked - is it possible for a central management group to support multiple service models - is worth some time and energy on its own.
The theoretical answer is of course. It is possible, in that nothing about it violates the laws of physics. It does, however, violate the laws of organizational dynamics, which means it's highly unlikely to happen in practice.
The reason is connected to how the person in charge defines success. Each service model is connected to a different definition - one reason among many that the many executives who tell their teams, "We're going to do all three!" invariably tear their organizations apart at the seams.
When central IT says it will successfully manage to multiple service models, it's saying it can accommodate different definitions of success in different parts of the company. There's no reason why not, except that it's so hard to explain as you go up the chain of command. "Well, yes, the IT group in Altoona does spend quite a bit more in desktop support than the one in Walla Walla, but that's okay because Altoona focuses on customer intimacy while Walla Walla focuses on operational excellence."
"Altoona can be as intimate with its customers as it wants, so long as it doesn't spend more than anyone else," is the likely response.
Clayton Christensen discusses this at some length in The Innovator's Dilemma, and concluded that it's the single most important reason great companies fail at innovation: They measure the success of the innovation using the same criteria as they measure their traditional business. The ones that succeed at innovating are the ones that take the team that's supposed to innovate and spin it off, viewing it more as a funded venture than a reporting business unit.
Which gets to the answer: If central IT views itself as a "holding company," it can manage multiple service models, but it will be tricky because it will have to figure out how to deal with each "business unit" on its own terms instead of on a single, shared set of criteria.
All in all, I wouldn't bet on it happening that way.
- Bob
Posted by Bob Lewis on October 10, 2006 08:35 PM
RATE THIS ARTICLE:
-

- COMMENTS
Inovation vrs on-going business is a problem far beyond IT. It is one of the reasons that so many consumer goods fail in generating new products. 3-M is a company that seems to have overcome and are able to continually generate new products.
In the gloablised 21st Century, all the corporations are operating in a "control-oriented" mode where maximizing the share-holder value attracts top-most priority. In such an organization, it is the finance execs who call the shots and who decide how the business should be run. And finance execs are focused on the top-line and the bottom line and don't care much about what comes between these two lines. Least of all on how customers' interests are best served.
The second factor at play is, organisations are structured in such a way that the management execs spend as little time per SBU that they possibly can afford to and still, exert as much control as they can. Such an approach will not work with an "innovation-centric" business model where the exec will have to learn the nuances of the individual businesses (this will maximize the time he spends in a business).
So, in a nutshell, large organizations are by design set-up for failure on the innovation front.
Posted by: Vasudevan at October 12, 2006 07:00 AMFor the last four years I have worked as local support for a company that has a central IT. In that time I have been allowed to do less and less, at this point I can't even restore a file from a backup or change a user's password. The old timers tell me that it is all a pendulum and shortly it will start to swing back the other way. In the mean time central IT has not added staff so they are now less responsive than ever. A file restore could take days as opposed to the minutes it took when I was able to do the work myself. All in all it is very frustrating. When I finally get up the courage to leave I will keep that in mind as I look for other opportunities.
Posted by: Tom at October 12, 2006 09:56 AMI also work in a company that is making it very difficult for the IT staff to get anything done. The problem is not that management has determined that this is the best way to run an IT organization. The problem is with Sarbanes-Oxley and the resulting audits. We don't have any choice but to put many controls and approvals in place. We need to maintain strict segregation of duties. Management would rather not run this way, and in non-SOX areas, things are not as bad. The problem in our organization is that all systems that have anything to do with a financial system need to conform to our auditor's definition of SOX compliance. This covers a fairly wide range of systems. Until the definition of SOX compliance changes to something more oriented toward productivity and less control and approval based, IT organizations in public companies will not be allowed to do anything other than tightly control major parts of its systems and infrastructure.
Posted by: George at October 12, 2006 06:36 PM|
Three books. Three ways to change the world, your life, or at least Bob Lewis' bank account. Leading IT: The Toughest Job in the World distills the world of IT leadership into eight learnable skills and gives you concrete, practical techniques for each one of them. Bare Bones Project Management: What you can't not do makes project management manageable, even for first-time project managers with no formal training in the discipline. ManagementSpeak: What managers say/What they mean … well, it won't help your career, and won't make you a better manager. Mostly, it will make you chuckle, guffaw, and maybe even chortle. Make friends - it's the perfect gift for anyone who has ever suffered through one of those meetings. Order your copies today! |
TOP STORIES
Hyperconnected users growingSteve Jobs to keynote WWDC
CSC settles kickbacks case
MS previews SMB software
What does HP-EDS really mean?
Mac Office 2008 SP1 released
HP buys EDS for $13.9 billion
Corporate IT spending slows
MS targets smartphone market
Sun to clarify JavaFX plan
ADDITIONAL RESOURCES

- Virtualization: A Step by Step Approach to Success
- Dialing up Agility with Business Transformation
- 5 Things You Need to Know About Storage Virtualization

- Is your smaller organization ready for High Availability?
- Is system maintenance doing more harm than good?
- Virtual Test Lab Automation: Manage development infrastructure





