What’s your approach to POCs with software vendors? What factors do you consider when weighing whether to do a POC or pilot?

1.4k views1 Upvote3 Comments

Director of IT in Education, 501 - 1,000 employees
To make sure software is work well with the business context, stable, security.
Mostly first step is POC by IT team and second step recommend to user to do the POC as well, and if user agree and willing to use, lets consider the pilot test, 
The main success of software selection for organization is not about how software is good but its about how satisfy by the user and the top management as well, as software in the market is similar but some business function, user interface maybe not satisfied by them.
EXECUTIVE DIRECTOR SUPPLY CHAIN in Healthcare and Biotech, Self-employed
One of the main reasons we consider a POC is when there’s new technology and we're uncertain if that solution is the right one. A POC provides a testing ground to validate what that technology will do and whether it will prove the ROI or the business case as expected.

The other way we look at POCs is if we have an incumbent solution that we're not happy with. We may use a POC to pilot a potential new solution, especially if we're unsure whether the challenges we're having with the incumbent solution are an industry problem or an issue we’re having with our supplier. 

POCs make great opportunities, but we must keep in mind what happens beyond the POC and what are the terms of the POC. For example, if you're going to do a three month POC, how do you disengage? How do you shut it down? How do you ensure the billing gets turned off if there is a charge? What are the decision criteria before you go into the POC? That should be discussed and clarified ahead of time.
Co-Founder in Services (non-Government), 2 - 10 employees
Can you elaborate on the different between POC and Pilot in your view? I think some people may look differently 

Content you might like

Strongly agree6%




Strongly disagree0%

Unsure (explain in the comments)0%


1.2k views1 Upvote

CTO in Software, 201 - 500 employees
Without a doubt - Technical Debt! It's a ball and chain that creates an ever increasing drag on any organization, stifles innovation, and prevents transformation.
Read More Comments
44.9k views132 Upvotes322 Comments

Easy to use unified view of data30%

Good data cleansing and transformation capabilities44%

Real-time or near real-time data integration55%

Above average automation capabilities37%

Works with all our applications and systems41%

Data governance support25%

Ability to scale and adapt to new data sources25%

Affordability of the solution17%

Potential for cost optimization11%



2.2k views1 Upvote