What is POC? Why a Software Proof of Concept (POC) Is Better than an RFI?
Last updated: November 15, 2022 Read in fullscreen view
Recommended for you
- 01 Aug 2024
The Standish Group report 83.9% of IT projects partially or completely fail 1336 - 02 Nov 2021 What is Terms of Reference (ToR)? 1284
- 05 Jul 2020 What is Sustaining Software Engineering? 1038
- 03 Apr 2022 Microsoft Solutions Framework (MSF) 1033
- 18 Oct 2021 Key Elements to Ramping Up a Large Team 991
- 20 Mar 2022 What is a Multi-Model Database? Pros and Cons? 918
- 03 Jul 2022 What is the difference between Project Proposal and Software Requirements Specification (SRS) in software engineering? 859
- 22 Sep 2022 Why is it important to have a “single point of contact (SPoC)” on an IT project? 750
- 13 Apr 2024 Lessons on Teamwork and Leadership from Chinese story book "Journey to the West" 740
- 20 Jul 2022 Software Myths and Realities 666
- 02 May 2022 What Is RAID in Project Management? (With Pros and Cons) 615
- 14 Jun 2022 Example and Excel template of a RACI chart in Software Development 581
- 06 Mar 2021 4 things you need to do before getting an accurate quote for your software development 557
- 18 Dec 2023 The Cone of Uncertainty in Scrum & Requirement Definition 556
- 13 Jan 2020 Quiz: Test your understanding project cost management 533
- 01 Sep 2022 Facts Chart: Why Do Software Projects Fail? 500
- 30 Jan 2022 What Does a Sustaining Engineer Do? 471
- 27 Jan 2020 Should a project manager push developers to work more hours due to mistakes of manager schedule setting? 401
- 16 Apr 2021 Insightful Business Technology Consulting at TIGO 354
- 13 Nov 2021 What Is Bleeding Edge Technology? Are bleeding edge technologies cheaper? 345
- 07 Jul 2021 The 5 Levels of IT Help Desk Support 342
- 07 Jul 2022 Managing Project Execution Terms 336
- 03 Jan 2023 Organizing your agile teams? Think about M.A.T (Mastery, Autonomy, Purpose) 330
- 12 Aug 2022 What is End-to-end project management? 329
- 17 Oct 2021 Does Fast Tracking increase project cost? 313
- 26 Sep 2024 Successful Project Management Techniques You Need to Look Out For 304
- 10 Apr 2024 The Parking Lot Method: Unlocking a Simple Secret to Supercharge Your Productivity 303
- 01 Mar 2023 What is Unit Testing? Pros and cons of Unit Testing? 301
- 09 May 2022 Build one to throw away vs Second-system effect: What are differences? 280
- 01 May 2023 CTO Interview Questions 279
- 06 Jun 2022 Change Management at the Project Level 275
- 03 Nov 2022 Top questions and answers you must know before ask for software outsourcing 253
- 22 May 2022 What are common mistakes that new or inexperienced managers make? 236
- 01 Aug 2022 Is planning "set it and forget it" or "set it and check it"? 236
- 15 May 2022 20 Common Mistakes Made by New or Inexperienced Project Managers 230
- 07 Aug 2022 Things to Consider When Choosing a Technology Partner 226
- 10 Apr 2021 RFP vs POC: Why the proof of concept is replacing the request for proposal 225
- 20 Nov 2022 Software Requirements Are A Communication Problem 219
- 25 Apr 2021 What is outstaffing? 216
- 02 Nov 2022 Difference between Change Management and Project Management 196
- 08 Nov 2022 4 tips for meeting tough deadlines when outsourcing projects to software vendor 193
- 02 Dec 2021 3 Ways to Avoid Scope Creep in IT Consulting 185
- 02 Jun 2024 Reviving Ancient Wisdom: The Spiritual Side of Project Management 184
- 09 Feb 2023 The Challenge of Fixed-Bid Software Projects 180
- 31 Dec 2021 What is a Data Pipeline? 175
- 24 Nov 2023 The project management paradox: Achieving MORE by doing LESS 174
- 09 Mar 2022 Consultant Implementation Pricing 168
- 10 May 2022 Levels of Teamwork 166
- 07 Oct 2022 Digital Transformation: Become a Technology Powerhouse 164
- 10 Apr 2022 What is predictive analytics? Why it matters? 158
- 09 Jan 2022 How to Bridge the Gap Between Business and IT? 150
- 16 Feb 2021 Choose Outsourcing for Your Non Disclosure Agreement (NDA) 143
- 07 Dec 2023 12 project management myths to avoid 139
- 30 Nov 2023 Project Managers, Focus on Outcomes — Not Deliverables 139
- 01 Mar 2023 How do you deal with disputes and conflicts that may arise during a software consulting project? 137
- 23 Jun 2024 Best Practices for Managing Project Escalations 126
- 21 Jun 2024 Dead Horses and the Escalation of Commitment 121
- 01 Mar 2024 10 Project Management Myths 107
- 05 Jun 2023 Fractional, Part-Time (virtual) or Interim CTO: Who Will Cover Your Business Needs? 94
- 10 Jul 2025 Building AI-Driven Knowledge Graphs from Unstructured Data 89
- 17 Mar 2025 IT Consultants in Digital Transformation 48
What is POC?
A proof of concept (POC) is an increasingly common method to select the best supply chain software vendor for your company, yet many supply chain practitioners still lean on the traditional RFI (request for information) tool. Software selection is risky. A poor choice can cost an organization millions of dollars as they limp along on a product that doesn’t fit their business or help them solve their core challenges.
A proof of concept (POC) is a demonstration of a product, service or solution in a sales context. A POC should demonstrate that the product or concept will fulfill customer requirements while also providing a compelling business case for adoption.
This post will examine why the RFI has become an outdated tool for software selection and look at how a software POC can help your organization choose the best supply chain planning solution by aligning directly to your business challenges. (Note: the same challenges apply for RFP (request for proposal) and RFQ (request for quotation methods, but for simplicity, we’ll just refer to RFI in this article.)
Seven Ways RFIs Fall Short
The premise behind the RFI is simple: Create a list of software requirements and choose or shortlist the vendor that checks the most boxes. Unfortunately, anyone who has ever been through the RFI process knows it’s not that easy. Here are some of the most common issues with RFIs:
Emphasizes features over objectives.
RFIs start by assuming everyone knows which features will help the organization meet its business objectives. Scratch that. An RFI assumes everyone knows what the business objectives are. If you’ve been through a supply chain project before, you know that’s not always the case.
Loooong list of requirements.
If multiple teams are involved in creating the RFI – and in a supply chain project they usually are – this indiscriminate list of requirements can grow very long very fast. The problem is, that long list probably included features not required to address your business challenges–and may omit the capability you really need.
No prioritization.
Narrowing down an RFI into something usable can involve intense negotiations as business leads battle over which features are “must-haves.” To avoid conflict – and get home in time for dinner – people give in. Eventually, the RFI ends up top heavy with far more features in the must-have column than not.
Too generic.
Since creating an RFI from scratch can take hundreds of hours, many software selection teams start with pre-built RFIs or one borrowed from another organization. No two supply chains are exactly alike, so why assume every organization has the same requirements?
In the same way, using an RFI as a way to “narrow the field” of potential planning vendors may overlook–or eliminate–your best-fit solution. Solid online research and structured interviews with potential vendors are a better way to accomplish that initial shortlisting exercise.
Blind spots.
An RFI can leave the organization with a blind spot as the team focuses on what they know. For example, an SOP may define how forecasting is done in the organization; therefore, the RFI focuses on features that enable that approach. There may be a better way to approach forecasting, but it’s not captured in the RFI because no one has any experience with it.
Focus on the wrong metric.
RFIs also assume the organization is focusing on the right metrics. Using forecasting as an example again, supply chain RFIs often emphasize forecast accuracy. In volatile supply chain environments, forecasts are inherently inaccurate. The longer the forecast horizon, the more inaccurate they are. In supply chain optimization, forecasts should be seen as a tool, not an end point.
A well-structured proof of concept can generate stakeholder buy-in far better than even the most extensive features checklist.”
— Henrik Sufke, Global VP, SC Planning – Ecolab
#7 Poor use of resources. As noted above, creating an RFI from scratch can take hundreds of hours. Evaluating responses can take almost as long and result in very few distinguishing factors between vendors. One of the reasons for this is that filling out an RFI is an exercise in creative writing for most vendors. They’re looking to check as many boxes as they can, so they can make it to the next round. Loosely interpreting the definition of a feature works to their advantage.
A POC Test Drive: A Better Way to Evaluate Supply Chain Software
Many supply chain professionals are skeptical of RFIs. They want to see evidence that the software works as described and will deliver on its promises. Henrik Sufke, Global VP, SC Planning – Ecolab, recently explained to me why a POC was the preferred choice for his company. “A well-structured proof of concept can generate stakeholder buy-in far better than even the most extensive features checklist.”
Explore more on these topics
Guest Blogging: The Definitive Guide
Top Trending Topics
Share This
Recently Updated News
