How to Scale Your Proof of Concept

Introduction

You’ve been experimenting with a proof of concept in the Internet of Things (IoT), Robotic Process Automation (RPA), Machine Learning (ML), Artificial Intelligence (AI) and/or Blockchain space and you’ve unearthed some interesting use cases for your business. You’re excited because you’ve done the math and rolling out this new technology to the business could generate some very interesting savings (even if only longer term).

However, as with all new technology, your stakeholders are skeptical. They’ve been around the block a few times and have seen many “revolutionary technologies” die in the Gartner Hype Cycle’s Trough of Disillusionment (I don’t know about you but I love that name).

So how can you ensure your project isn’t dead on arrival? Do your homework. Have the answers ready for anyone wishing to poke holes in the feasibility of your proof of concept at scale. This means answering the fundamental question: “What are the impacts of scaling your proof of concept on People, Processes & Technology?” Although the “three legs of the ITIL stool” don’t directly apply to scaling up a proof of concept, they are interesting lenses to consider when evaluating the impacts of deploying at large.

To help in this endeavor, I’ve compiled the following list of questions you should ask yourself and your team along these three angles. These questions help fully bake the cost of scaling. In my opinion, everything starts with process so let’s start there…

Subscribe to Premium to read the rest.