Solution Decision


Prepare Gap Analysis

Understand where the solution will not meet your needs
  • Final Scope
  • Functional Decomposition
  • Data Model
  • Business Processes
  • Major Impacts and Solution Impacts
  • Completed Functionality Evaluation Document
  • Completed Data Modeling Worksheet
  • Completed Reports Evaluation Document
  • Completed Technical Evaluation Document
    1. Identify the gaps and note them in the Gap Analysis Document.
    2. Add actions required.
  • Gap Analysis Document

The intention of this step is not to identify where the system needs to be configured to meet your needs. It is to understand where something is missing, and will either have to be built, or you will have to get by without it.

The gap analysis also ignores any preparatory work that may have to be undertaken such as cleaning up data, or installing hardware. It is a document to list where the proposed solution does not meet our needs, and if we can make it meet our needs.

Split the document into business and technical gaps. Don't spend too much time deciding which box to put something in if it overlaps. Just make sure it is noted.

The Executive Overview gives a summary of the results. Not every gap will be analysed, and there may be options in some of them. That is to be expected. The document is indicative rather than definitive.

Give the Vendor an opportunity to review the document. They may be able to suggest another alternative or approach that will assist. It also adds credibility to the document. It avoids the situation where a Vendor can say to the company "But if you told me about that, I could have fixed it for you. Is that why we lost the sale?"

Gap Analysis A document to record the gap analysis

Return to the top