Problems that can arise during and after a Notes rollout. (Forewarned is forearmed ?)

• Seniors do not want to be associated with the Notes rollout. (Did Previous IT projects fail ?)
• Lotus Notes is perceived as "just another e-mail program" ( An important one I had missed - thanks Jason )
• Team leaders are seen to be using the system simply to monitor and control subordinates' activities.
• Insufficient benefit ( staff see no need for still more information )
• There is a lack of consensus on the use of Notes (Are others reading the database ? Maybe I should send an email instead.)
• Inconsistency with group culture. In a "Go it alone" culture, collaboration is not be seen as a plus.
• Executives do not ask for help on their own. (loss of face)
  ( One solution is to have executive trainers able to approach other executives).
• There is a very large range of understanding and competence (and it will increase).
• After installation there is perceived to be a slow response and long replication times.

• If the team does not trust each other, lack of communication is now blamed on the database.
• Extra work will be expected from the end users in order to get the Notes database on line.
• Users see Notes as requiring more work for no benefit.
• There will be an initial loss in productivity as people adjust to the new procedures and practices.
• Loading information into the new system is often the most tedious and time intensive period.
• The new system is blamed for data inaccuracies. These inaccuracies were present in the information before the conversion but only came to light when the data became organized. IT then become responsible for "fixing" the "problem".
  
  (As a personal note this is one of my pet peeves. You design a great database. Users get to see their data clearly for the first time. For the first time they see the inconsistencies, the errors. etc.
  Their first response… What went wrong with the conversion ?)

• Seniors demand information from next level down via notes.
  This leads to compliance not enthusiasm.
• The Notes champion does not plan to stick around. (And he/she is on his/her own)
• A ghost story..."Notes was half-heartedly rolled out to fix some problem a long time ago and
  the champions have all long since disappeared. Needless to say, things are in a shambles." (thanks Andrew )
• All stake holders were not included in the Notes rollout
• Technology and Notes are seen as the goal rather than a tool.
• Technology and Notes are enablers. You must focus on the business requirements.

• Notes is brought in to solve a problem that the users do not acknowledge exists.
  (i.e. poor response times, low product quality, poor customer satisfaction.)
• Do the problems/opportunities being addressed truly exist ?
• Do the end users agree that the problems/opportunities exist and do they agree with the statement of the problem/opportunity ?
• Are there more pressing problems being ignored ?
• Are the end users being kept informed throughout the project ?