How To Avoid Runaway IT Projects
That Empty Your Wallet
Even though YOUR business isn't a McDonald's with a billion-dollar IT budget, chances are you've had at least one failed IT project that derailed, emptying your wallet and leaving you with nothing other than a grudge. And if you haven't had that happen yet, chances are, as you grow, you will. So how do you avoid going down a rabbit hole of spending on an IT project? Here are five key strategies to keep you on tack:
- Begin with the end in mind. The clearer you are on what "success" is for the project, the more likely you are to achieve it. Take the time to sit down with your executive team and decide exactly what the new system LOOKS like (including the interface, if you're developing one), how it performs, what it does and how it works.
- IT projects need to be driven by an executive who understands the business need and outcome, NOT the IT department. If you and your executive team aren't going to be heavily involved with the process, decisions and management of the project, don't start it.
- Think in smaller, "bite-sized" projects. One of the problems with the McDonald's project was that it was so complex, affected multiple business systems and had such an enormous scope, it was almost guaranteed to fail. If you have a major system to build or overhaul, break it into smaller, manageable chunks so that problems are contained and costs controlled.
- Manage the project hours. Scope creep is the biggest challenge to keeping your project on time and on budget. If your project starts to take on a life of its own and goes over your budgeted time frarale and your budget by more than 10%, it's time to start re-evaluating what's going on. Excessive overtime is a red flag that the project was not thought through properly, that you have the wrong team working on it or that it's being grossly mismanaged. Don't ignore it.
- Missed milestones are a red flag. While it's normal to miss a few milestones by a small margin, your IT team should not be allowed to consistently miss key milestones in the project. We recommend setting clearly defined milestones every two weeks or monthly versus monthly or quarterly. This allows you to keep a tighter control on the budget and deliverables.