I’ve worked on over a thousand individual IT projects. Some have been small, others have involved international VPN systems with QOS for VoIP, and the relocation of an entire production datacenter with over 100 servers.
In all these projects, the smaller ones are more prone to failure and delays. One would think that smaller, less complicated projects would be easier. Here’s a brief analysis of why that’s not the case. If you’re a business owner, read this very carefully.
Projects that have a total budget of under $10,000 I classify as “microprojects.” At most, there should only be TWO people on these projects. Of those two people, one has to be the decision maker - and the decision maker is the person who can spend money. Any more people and these projects will cost more in wasted meetings and miscommuncation than they will ever bring in value to the company. If you can’t afford to spend $10,000 with no more than a one-hour planning meeting then you need to focus on making more money.
Projects that spend more than $10,000 but less than $100,000 are small projects. They typically involve less than six systems and are easily completed in under one week’s time. These projects comprise the bulk of IT consulting work and they’re the MOST prone to failure.
Projects of this magnitude generally involve management and have more than one stakeholder - it is generally an entire department or possibly two departments. The project involves phases, a multi-week project schedule, and generally is undertaken to realize some concrete gain, or return on investment.
Despite these critical factors, rarely is the requisite planning done in order to ensure success. From a technical stand point, projects of this magnitude can be engineered in under a month - usually in one week. The failure is almost always on the part of management to engage the pre-planning process.
To management, $10,000 on a line-item represents their quarterly bonus. Subsequently, management engages “micro” projects in an attempt to make themselves usefull(less) by shaving that magic $100 from some significant (but misunderstood) line-item.
However, a $100,000 project is usually what small businesses spend on such trivial things as petty cash, professional service fees, or energy and transportation costs. To management, $100,000 for a project is something they see every day. As such, they don’t think about that project as much, and mentally disengage from the pre-planning process.
Having done this, management won’t respond thoughtfully to questions like “How long can these services be down?”, “Which departments or ongoing client projects require these services during the proposed transition?”, “If we have to modify the schedule, what are the high priority services and how do you define high priority?”
Management is *always* going to be taken by surprise on small IT projects - not because they’re complex, but because management won’t make decisions about the project because the cost seems small in the grand scheme of the business. However, management will take a very, VERY keen interest when the accounting server goes down during the weekend upgrade and it won’t come back up - or when half the sales people stand to lose their last 3 years of email history.
At that point, management can do little or nothing. So the point here? Get involved on the front-end, during pre-planning. Yes, plough through the technobabble. LISTEN to your people. LISTEN to your consultants. Spit back what they say as you heard it until you get what they’re saying.
If you, as a business manager, won’t be engaged during pre-planning, then you forfeit your right to stand over the shoulders of your IT people shouting “JUST GET IT FIXED!”