Ensure your team provides equal emphasis on other requirement topics/areas.
Increase the likelihood of a successful software acquisition outcome by understanding:
Why visualize?
Think of solution pieces as depicted in the following image.
The following map provides a typical overview of a solution's anatomy. As you can see, it's much broader than application-specific requirements.
Specify minimum and detailed requirements expected from your vendor.
You're evaluating and selecting software to run your business, and that decision has long-term implications.
Establish stringent requirements by specifying the key attributes you're seeking from your vendor partner.
Specify the application requirements that are expected to be delivered by your vendor.
Each application is different. Understand the core attributes and capabilities of your application.
Leading applications do share some key attributes and capabilities. Refer to the graphic for representative examples.
Specify application configurability needed.
Configurability is a crucial capability found in leading applications.
Software vendors must appeal to a broad range of diverse organizations, sometimes cross-industry.
Configurability allows organizations to tailor a software package to meet their needs without customizing the code.
The visual references examples of configurable capabilities found in today's leading software applications.
Describe the expected user interface and navigation required.
An easy-to-use, intuitive system will save cost and time over the long term and result in higher user satisfaction and engagement.
A good experience will incentivize users to optimize their application use, leveraging all functionality to deliver value to your business.
Articulate expected reporting and analytic capabilities.
Often overlooked in evaluation projects are the vendor's reporting and analytic capabilities.
Invest sufficient effort to identify and document your organization's reporting and analytic needs.
As the following graphic depicts, it's more than just reporting.
Remember to specify the required options for distributing reports, such as print, PDF, device, web, and screen display.
Partner with your technology and security teams to define software application-related security and access requirements.
Also, your security team should provide you with a technical security questionnaire to include in your RFP. That questionnaire covers critical security topics such as:
Your application may need to integrate with other existing applications and capabilities within your organization.
List each application and define its integration requirements and standards.
The application software you're evaluating and selecting operates on one or more technical platforms, such as hardware servers, database software, network software, and other technical-related software.
Partner with your IT team to include your organization's technical standards and requirements.
Request vendors to highlight areas of their solution that are inconsistent with your organization's technical standards. Those exceptions will require review by your internal IT partners.
Note: Solutions that are not in compliance with your organization's technical standards may result in:
This area is critical to support your organization's long-term use and benefits of the application.
Specify your requirements and expectations for vendor application support, such as:
Application Management and Support is more than just application support. Consider capabilities and services such as:
Ask the vendor to provide a catalog of their products and services with associated pricing.
That provides insight into the vendor's maturity, stability, and ability to weather an economic downturn.
Diversity of product and service is a crucial indicator of vendor long-term viability.
Identify any potential long-term requirements that your organization may require.
Even though those needs may not be required today, selecting a vendor who can support them may be a differentiating factor in your decision-making process.
Not all needs are created equally. Prioritize your needs.
Prioritizing needs can be an exercise in decision fatigue. So often, we want to include all needs, regardless of importance, into an RFP. It's our way to mitigate risks, errors on the safe side and ensure nothing is overlooked in our vendor assessment process.
Only include vital and important needs in your RFP. These are the differentiating needs that are crucial in your vendor decision process.