We’ve been involved in the design, development, and implementation support of enterprise-level software for over 20 years, which is why our team of experts puts together this 10-part series on evaluating Enterprise-level software. We’ll cover topics ranging from security, data collection and reporting requirements, implementation resources, pricing/cost models, and more, to ensure your next enterprise software deployment is a success. You can also download the entire Evaluating Enterprise-level Software whitepaper here.
____________
Last week we looked at the importance of having a centralized location for software administration. Does the solution you’re evaluating meet this requirement? Let’s move on to the implementation process, and the resources that the provider has to ensure a successful and smooth implementation.
If a well-managed project with clear objectives is a key driver of project success, then a close second would be a good start to the process itself. Nothing like hitting the ground running.
Just as projects without good leadership and clear objectives will most likely fail, projects that are not implemented well will likely struggle to meet your needs and eventually wither.
So, when considering an enterprise-level solution, ensure that the solution provider has a track record for implementing enterprise-level projects and can offer all the training, tools, and support (i.e. onboarding procedures, data upload templates, project reviews) needed to ensure your project will be a success from day one.
Some things to consider:
- Does the solution provider offer support for initial project implementation and configuration? Is technical support provided (free of charge) and can you submit support requests 24/7?
- What onboarding/project implementation resources are available (e.g. onboarding procedures and/or implementation guides, training material, initial data upload templates)?
- What support is offered by the solution provider (e.g. training, configuration, customization)?
- Does the solution provider offer ‘test’ or ‘sandbox’ environments for the initial rollout testing, new releases, user-testing, etc.?
Next week, we’ll be concluding our series on evaluating enterprise software by exploring the pricing and cost model of the solution.
