Categorized | Business

The Seven Deadly Sins of IWMS Implementation

1. Lack of realistic expectations

The first deadly sin is the most important one. Lacking realistic expectations is devastating for all projects. Don’t think that one project will save the world. It simply will not. If you embark on a journey with unrealistic expectations, you are preparing yourself for misery. Only projects with realistic expectations can lead to the desired outcome.

2. Lack of specific outcome

Success can only be measured against actual results. This however is impossible to do if the outcome of an IWMS implementation is not correctly specified. If you want to successfully implement an Integrated Workplace Management System, it is imperative that you clearly specify the outcome.

3. Lack of commitment

Without solid commitment IWMS implementations fail. Period. You need to ensure that both the project team and the project sponsors stay engaged with the project during the entire project. Most projects are initiated with a lot of enthusiasm and energy, however during the project this energy diminishes significantly. Only IWMS implementation projects with a committed project team and committed support from senior management can lead to the desired outcome.

4. Lack of planning

Once the IWMS implementation project has been started don’t stop planning. This will get you in trouble. Squandering your time in the beginning of the implementation project will lead to stress and dissatisfied IWMS implementations. Therefore you should aggressively guard the project planning in the beginning of the project.

5. Lack of quality

The lack of quality of ensures that you have to do re-work, which this puts your IWMS implementation project under pressure. Whatever you do; do it right the first time; every time.

6. Lack of communication

Your IWMS implementation project will not be run in a vacuum nor in your head. Communication with project stakeholders is extremely important. Don’t count on people’s mind-reading capabilities, but communicate. Be clear your communications. Listen carefully.

7. Lack of authority

Without the proper authority, IWMS implementation projects will run out of time and budget. The decision-making process will be unnecessary lengthy and complex which will have a very negative effect on the project outcome. Therefore you need to ensure you have the appropriate authority available within the project, or by external senior management support.

Related Posts

  1. Justifying your IWMS implementation
  2. 31 Days to Improve your IWMS Implementation
  3. IWMS Implementation: Don’t bite off more than you can chew
  4. Debate: Is an IWMS implementation successful when completed within time and budget?
  5. What IWMS Vendors Don’t Tell You About Successful IWMS Implementations

4 Responses to “The Seven Deadly Sins of IWMS Implementation”

  1. Joe Valeri says:

    A close runner up would be lack of follow through. Making sure client staff are trained well up front and then through a proactive support approach after go-live will increase the system uptake and the likelihood of long term success.

    Joe Valeri
    Lucernex Technologies
    http://www.lucernex.com

  2. Steven,

    I would add that most executives who implement IWMS technology are clearly committed to indelible organizational change and bring deep knowledge of their needs, internal systems and processes. However, many organizations lack internal expertise and experience in the successful implementation of IWMS technology to achieve their vision.

    Partnering with IWMS vendors and their service providers in the implementation of IWMS technology provides customers with deep process knowledge, industry-specific expertise and experience gained from the implementation of hundreds of successful projects to increases the value of a customer’s IWMS investment.

    John Clark
    TRIRIGA Inc.
    http://www.tririga.com

Trackbacks/Pingbacks

  1. [...] The last phase of the design-thinking process is the implementation of the product or service. (Avoid these Seven Deadly Implementation Mistakes). [...]


Leave a Reply