How to avoid the top five IT mistakes

How to avoid the top five IT mistakes

Summary: Before you say goodbye to summer and get back on the ball with IT projects you may want to refresh your memory with these words of wisdom from Nucleus Research (free report): The root cause for failed IT projects is not the technology but rather missteps in project management and planning.

SHARE:
TOPICS: CXO
2

Before you say goodbye to summer and get back on the ball with IT projects you may want to refresh your memory with these words of wisdom from Nucleus Research (free report): The root cause for failed IT projects is not the technology but rather missteps in project management and planning.

Taking the time to build a structured project strategy and a clear business case that can be used as a budgeting and planning tool can help you avoid the following most common pitfalls, according to the analyst firm:

 

  1. Too much customization--It takes more time and you will spend more on consulting, especially on an ongoing basis.   
  2. Skimping on training--Don't let seemingly intuitive applications fool you; have at least a quick tutorial. 
  3. Absentee management--Get higher-ups involved, but make sure they have a clear view of the plan and a personal interest.
  4. Freewheeling consultants—Check their references with the same diligence as when selecting a solution.
  5. Assuming you're finished—Strategic technology projects are never really finished

Topic: CXO

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.

Talkback

2 comments
Log in or register to join the discussion
  • Agree with most, though first is a sticky subject

    Not a bad summary of the most common mistakes. The first bullet regarding customization though is something of a quandry.

    There's a lot of business processes that just don't work if you try to take an out of the box product and make it do all the things you're hoping. So customization is inevitable. I guess it's all a question of when is it "too much".

    I'm a little surprised that "Assuming everything is secure" wasn't on there.
    Vraxx
  • With offshoring, #s 2-4 are nullified.

    #1 is becoming a nonissue because the industry is headed toward more universal standards, ironically (all MS-based likely so have fun, hackerz)

    #5 is irrelevant; offshoring never ends. Until the oil does. Fortunately.
    HypnoToad