How Software Implementations fails:

Quarantine – Session III

Sharpen the Skill set

As said "Knowledge is Power"...

Since don’t have much of choices in this time, this is important for our sanity.   Not necessary that everything work for every people, but some things work for some people so point it and hit the target.

Finding what works well is most important element to keep the mind in a straight line and keeping ourselves cool is certainly required.

How Software Implementations fails:

Why does a software implementation often frustrate or struggles? Find whom to be blamed? At the end without any choice project owner will take the fault for failure before he/she realize the root cause.

Right implementation partner:

There will be a huge gap between Salespersons promises and technical/functional people deliverable. Software which expected to ease the operation of a process will work entirely opposite. Following this software and software vendor alone is not a primary problem, too many must be listed.

Hasty decisions:

Without enough research or getting the reviews and finding the level of customization allowed in that software. If decision maker keeps ignoring the inputs/feedback of other team members. Though made a research to pick the solution it’s always better get feedback before decision and move forward.

Integrator:

The first and foremost promise of vendor “integration is just plug and play we have multiple connectors” which will connect and talk to any software. Ensure this before establishing business commitments.

Bringing Legacy Data:

Managing data migration tons and tons of areas to be concentrated, analysis the legacy system properly, decide what to brought in and what not to.  Analyse the excess feature in new software and try to get aligned to it at the max don’t try to take the same junk to new software too, rather if it’s business critical.

Incorrect data transfer:

There are cases where people do not want to spend time cleaning up the data before the transfer. This leads to redundant master data in new implementation also. It’s important to stay in control during the on-boarding phase and know the product and its behaviour.

Unclear requirement:

It is good to keep in mind that software implementation has multiple stages, divide the information into easy steps which is understandable. Collecting requirement through single side approach will push to pit. Always ensure both Bottom up, Top down and multi-dimensional approach in requirement collection.

Underestimations:

During implementation customer is going to use new software, considering customers learning time by comparing his/her flexibility in legacy system. If software vendor fails here, then implementation failed.

Enforcing new features:

Always make references and teach how to use each of the features available in new system. It’s good to follow up the customer and provide the benefits how the software will improve their business using the new functionalities in that software. Or else this will decrease the usage of application.

Lack of communication:

Failing to setup effective communication channels and participative environment will end at lack of ideas, process flows, lack of visualization and absence of interaction between functional and developers.

Failing to Visualize:

This is the major reason for implementation failure, lack of foresight about the process and technical achievable.

Plans are just a plan:

This need to have a logical sequence of tasks, to be a good plan it needs to identify all the requirements and the people who are going to work on. Until reaching a good plan, really do not know when the project will end, or it will hike the cost of implementation.

Customization:

There should be always an eye to be kept in this aspect, while development futuristic thought process should provide some 15 to 25% of customization option, since at any business process may get changed for future requirements.

Lack of Quality Testing

Most projects, the importance given to coding isn't given to testing. Testing calls for a greater integrity and role in the entire software development. Casual testing, testing under non-real time environments contribute to testing failures.

Lack of Periodic Assessment:

Company which fails to do periodic assessment on implementation has more chances for fail.

Too many reasons can be listed beyond this but, finally, concluding this by saying technology should work for business not the vice-versa. If the implementation is healthy it provides the sensory input for MIS-Management Information system and helps management to respond. And implementer should think it as best investment and enjoy ROI – Return on Investment.

Abinath Sivasankaran