GETTING RESULTS

PRAGMATIC STEPS OR UTOPIAN LEAPS ? HOW TO ENSURE THAT SOFTWARE DELIVERS
Technology alone does not create business value – what matters is how it’s used.
Realising that value requires the close participation of the business that will use the software.

Before implementation the envisioned benefits need to be clearly defined. Are they tangible and achievable ?
The key to success will then be to ensure that the barriers to change are removed, as your company will initially measure success as to how quick, how easily, how productively:
  • the system supports processes and organisational structures that will deliver tangible benefits
  • the benefits of the system and it´s usage are achieved as soon as possible after implementation
  • the system becomes an active part of your organisations day-to-day activities
Change will only be accepted in your organisation if it plays an active role in managing that change for itself.
Just as your activities need to be interwoven into the design of the system, so your organisation needs to associate change and system implementation as being a single activity.

Practical steps you can take are, for example:
  • immerse the software team in your business to observe operations and processes
  • take part in scenario testing, to fully  understand its application and impact on processes and users
  • train for the use of the new system to develop a deep understanding of the benefits it will deliver
  • prepare “how to…” guides on subjects that will support your team in delivering their business change.
A close cooperation will make acceptance, use of the system and benefit delivery to be a seamless experience.