We’re experiencing a technical revolution of epic proportions. New technologies are flooding the markets and it’s very easy to get overwhelmed. We’ve used Proof-of-Concept with some of these solutions, and I thought it would be helpful to identify when a Proof of Concept is a useful.
Does the Solution Effect the Vast Majority of Employees?
Will the Solution Provide an Opportunity to Change HOW We Do Business?
Will People Outside of Our Information Technology Team Be Part of the Decision Making Process?
Does the Solution Provide a Return on Investment?
Will the Solution Impact People and Organizations Outside of Our Company?
Are there Design and Layout Considerations that Effect How the Solution is Used?
Do You Need Access to Specialists or Specialized Knowledge to Effectively Explore a Solution?
Does your Internal Team have the Knowledge and/or Time to Explore a Solution Internally?
Will the Solution be in Place for 5 Years or More?
Will a Proof of Concept Reveal Usage and Design for the Full Implementation?
If you find you’re answering yes to most of these questions, I recommend that you explore the use of a Proof-of-Concept. Many resellers have special programs and include a suite of services that are much more cost effective than purchasing their services ad hoc.
Tim Krueger, PEI
