Red flag No. 9: The go-live date is a weekend or holiday
Many project leaders plan go-live events for the weekend or holidays because of lower chances of service disruption to employees or customers. While laudable, these windows also tend to be the times when tech support is harder to reach. You may have your primary vendor onsite, but third-party tech support may be closed or on call (and not returning calls in a timely manner), and the same may be true of your team. Talking to your best database troubleshooter over the phone while he's on vacation with his family is never optimal.
Red flag No. 10: Expectations have not been set
When a new system is going in to replace an old system, it's helpful for everyone to understand the new expectations. How is the new system going to act? How are transactions and transaction times different? Who do end-users call if they have problems? How long is the go-live troubleshooting team going to be onsite? A new system will always frustrate people, but if you set realistic expectations and give people accelerated support options, problems tend to go away faster and you end up with more satisfied customers sooner.
Red flag No. 11: Skimp on training
I can't tell you how many project leaders will pilfer the training budget when faced with a budget overrun. Usually it is a smug, supersmart leader who claims the system is so easy that users don't really need all the training. If you hear, "Heck, we'll train every other person with half the classes and they can train each other," or "Our users are pretty good at figuring out things; they can figure this new system out in a few days," you know you're in for failure. It's not just users who need training, but project leaders, troubleshooters, and help-desk staff, too. Be ready to delay the project if appropriate training is not given.
Related articles at InfoWorld.com:
- Submit your IT tale for InfoWorld's Off the Record blog -- and get a $50 American Express gift cheque if we publish it
- 20 IT gotchas: How to avoid these common big blunders
- 12 "best practices" IT should avoid at all costs
- 10 hard truths IT must learn to accept
- 8 biggest myths about managing geeks
- The 9 most endangered species of IT
- 5 dysfunctional IT relationships -- and how to repair them
- Dirty IT jobs: Grime and punishment
- Stupid user tricks 6: IT idiocy loves company
- IT inferno: The nine circles of IT hell
- IT personality types: 8 profiles in geekdom
- Jackass IT: Stunts, idiocy, and hero hacks
- True tech confessions: Sinners and winners
- 7 IT superheroes -- and their fatal flaws
- A-Teams of IT: How to build your crack strike force
- 12 effective habits of indispensable IT pros
- IT turf wars: The most common feuds in tech
- IT admins gone wild: 5 rogues to watch out for
This story, "11 signs your IT project is doomed," was originally published at InfoWorld.com. Follow the latest developments in IT careers at InfoWorld.com. For the latest business technology news, follow InfoWorld.com on Twitter.