Sunday, 08 July 2012 00:00

Stop All IT Projects!

Rate this item
(0 votes)

Again, I was chided for saying there are no Information Technology projects. This time, the excuse was that the company built software. I countered my antagonist by asking if the same group that built their software also maintained the account system, workstations, email, and network. "No, that is a separate group." He was missing that his company's production group was not IT. Information Technology is the support group... and yes, they should not be doing anything that fails to directly affect getting product out the door or reducing costs. Every project's goal must be to deliver to the operational needs of the company—selling product—not to the whims and desires of the IT group. If a project fails to address the needs of the customer (directly or indirectly), then it should never see a penny of funding. This seems such an elementary concept, but it is routinely violated by techno-bigots trying to implement the latest toy or tool.

The Almighty Customer

Companies make money by producing a product or service. Duh. Whether the organization is a multinational corporation or a small non-profit, improving how they function requires initiatives. These projects may work directly on a production line's capabilities, implementing new state-of-the-art materials, indirectly affecting the product by enhancing the infrastructure to reduce internal costs or increase capabilities, or any number of other topics—as long as they benefit the business. Regardless, a business case must be present that improves the top line or bottom line. Adding IT resources to a project does not make it an IT project.

Imagine to upgrade software project (service patches, database optimization, break/fix are not projects). If the business is not fully engaged with the change, trouble is on the horizon. For example, the IT group has a strong business case to upgrade from Office 2003 (losing support) to Office 2010 or Office 365, but the business has to assess the impact to their productivity. Initially, it will plummet. Over time it will recover and may actually get better (I have yet to see any productivity increase from this specific upgrade). The business has little desire for the pain. Hence, an information technology group supplies the resources, the guidance on what needs to be done, and the business owns the project of implementing it based on their perceived value. This job is selling IT's roadmap. If the business does not upgrade and they are caught not having support it is their problem, not IT's.

Connecting to the Business

Want to read more?

Strategy, alignment, communication of goals is not easy. Our Vision To Value white paper talks about focusing your team on the key strategic corporate goals and ensuring everyone in your organization knows the direction.

To help, CIOs need to get their group closer to the business. There are a number of techniques for them to do this. It requires confident and mature teams—not in the individual-contributors, but in IT leadership—from the CIO down to the first level management. The CIO needs to look at him or herself as a facilitator. It needs to be someone thinking less about his or her fiefdom and more about providing resources to the business. The resources are in three areas:

  1. People capable of turning business initiatives into reality. The classical approach of housing IT's delivery resources away from the business will save on moving costs and make it easier for functional managers, but it will destroy the teams ability to understand what the customer needs (not what they want, but what they need). Embed IT resources in project teams and collocate them with the business team. This improves project delivery and customer relations by merging the two teams into one.
    Implementing a distributed team does, however, require strong IT leadership. Directing and coordinating a dispersed group of technical people and ensuring they get the proper care and feeding to grow and flourish is hard work. The benefit is that resources resident with the business have a thorough understanding of the business's issues and propose better solutions.
  2. Utilities that allow the business to its job. The operative word is "utilities." Servers, telephony, networks, and COTS applications as we all know are about as unique to our companies as electricity. The goal should be to find companies that provide these utilities and hire them.
  3. Visionaries creating a cost-effective technology roadmap. Provide the architects and governance to enable the business to adapt rapidly to the future. In a highly distributed organization, where your teams report to business managers rather than in to an IT group, aligning them to a common roadmap is difficult. The architects must be more than technical wizards; they need the ability to sell their ideas to the IT executives, the business executives, and a distributed implementation team.

Distributing Your Team

Stop all IT projects and make them business projects. Their existence simply perpetuates the old myths of business silos. Technology is ubiquitous in the business and so should the IT group to support it. IT is no longer a mysterious and arcane subject practiced in computer rooms. It can be boiled down to simple tools for manipulating data for the end user to get the answer they need. Distributing the technical resources to help the business do its job is the next logical step.

Read 7646 times

Related items

  • Comparing Organizational Change Management Models

    A few weeks ago, I set out to write a post on the comparison of various organizational change management (OCM) methodologies and realized that would be a disservice to my readers. It would simply drag you down the path of implementation while failing to focus you on building the foundation. The pressure was too much and I have relented to numerous requests on making that comparison. The caveat is that juxtaposing these models is not comparing different varieties of oranges or even apples and oranges; we are surely comparing the peel to the fruit they contain. Hence, comparing methodologies like Kotter's model (the peel), Prosci's ADKAR (the core), and General Electric's Change Acceleration Process (the whole fruit) need a different approach.

  • The Executive-Project Manager Gap

    It was such an innocuous question, "Working on an article; what is the biggest problem you see with project governance at orgs? Can you comment?" Can I comment? Really? That is like cheese to a mouse. Where could I start—bureaucracy, draconian process, poor executive sponsorship, disengaged leaders? Plenty of fodder, because they all lead to project failure. I fired off, "Creating an over bureaucratic morass stifling innovation & implementing process instead of cultivating leaders." Then the maelstrom started and it went directly to the gap between the executives and projects managers. Naomi Caietti, Robert Kelly and I had a great conversation. Most of the thread is below.

  • Disband Your PMO

    After nearly 30 years of project work, I struggle to understand the role of a project management office (PMO). Even though, I have written of the pros and cons, and read a plethora of articles, opinions, and how-to guides little has been done to convince me that the PMO is reducing project failure. It seems to be nothing more than a tool to fill a void in leadership? Even the acronym, which is so widely thrown around, has little meaning as the "P" has no less than four meanings. It is an executive's crutch for their lack of understanding in how projects work. These, like other, unattended holes in the corporate accountability create opportunities for new and greater bureaucracies and empires that further obfuscate accountability.

  • The Catch-22 of Organizational Change Management

    "Kotter, ADKAR, or CAP which methodology should we be using to build our approach to improving project adoption?" I hear this question repeatedly from people trying to implement an organizational change management (OCM) program. The problem is that is the wrong question. Take a perfunctory peek at any of the models and you will see that in the quest for an answer people have mistakenly jumped over the first few steps and they head down the road of failure. It is a Catch-22; unless you already have an OCM process in place, you will most likely fail at implementing it. Putting one in place, however, is a change—one of the most difficult cultural transformations your company will undertake. As a result, people jump to the solution stage, which is well down the change management process path (which, they did not know, ironically, since there was no procedure in place).

  • Project Inception - Designing Organizations For Success

    Buy it now!

    A failing project’s fate is destined long before assigning a project manager. Its doom is sealed from the time the customer envisions the idea. Traditionally, project inception is defined as when the customer comes to a solution provider (internal or external to their organization) asking for a product or service. In actuality inception is much earlier. It starts when someone says, “Wouldn’t be neat if I could...” From that point forward the customer’s exceptions are set, changed, and reset as the process of discovery refines the concept. The customer’s ideas change from what they want to what they need, while continually constrained and formed by the realities of an ever-changing business environment. Although people cite unrealistic expectations as major problem during inception, the constant change in expectations causes the real issue—misalignment. For project managers to make a significant difference in a project’s success, they must use a new paradig.

Leave a comment

More Info on Project Recovery


Please send me more information on fixing a failing project.

Made with BreezingForms for Joomla!® by Crosstec

Rescue The Problem Project

Internationally acclaimed

Image of RPP

For a signed and personalized copy in the US visit the our eCommerce website.

Amazon logo
Buy it in the United States Buy it in Canada Buy it in the United Kingdom
Buy it in Ireland Buy it in Germany Buy it in France
Buy it in Italy Buy it in the PRC
Buy it in Japan
Book sellers worldwide.

Upcoming Events

Other's References