Your AMS Journey: Selection to Adoption – Step 5: Discovery

Take The Needed Time

Contemplate taking the necessary time to go through a deep and thorough discovery. Rushing a discovery will lead to an implementation that will be incomplete and potentially fail.

Imagine not spending time going through the architectural plans when you want to build a house. Moving rooms around after the build is impossible.

Share The Good With The Bad

During our discoveries, we frequently hear in great detail about all the failures of the existing AMS. We recommend that clients be comprehensive and share what works, as well as what does not. We want to ensure that we implement a product that alleviates the legacy system’s pain points and provides and maintains the functionality that has worked.

Core Team Is Key

The involvement of the core team is key to success. In our previous step of the process, we introduce the core team and highlight its key members.

The core team needs to provide the SI with the processes and pain points they face in each area and department of their association. They will be the ones signing off and accepting the various modules of the product implementation later. Their acceptance has a direct impact on adoption across the organization.

Seeing Is Believing

During the discovery meetings, the client should demonstrate the old system and processes to the systems integrator. In turn, the SI should demonstrate stock product functionality to the client.

The demonstrations can be short but will help the Core Team visualize the solution and buy-in quicker.

Solutions, Please!

As you go through the discovery, please ensure that the requirements are captured in-depth with adequate solutions. They could be stock product features or customizations that might be required to support your organization’s particular needs.

Document Everything & Sign Off

Having strong documentation of the required solutions is key to success, as they serve as the scope that drives the project’s acceptance criteria later on.

Ensure there is a sign-off of the relevant modules of discovery documentation by the appropriate department. This provides the opportunity for each department to own their piece of the implementation process. It also guarantees that each department actively participates in the implementation process and later champions the adoption within their own department.