How to Run a PoC (Proof of Concept) that Provides Real Value 2/2

This is the second part of the series “How to run a PoC (Proof of Concept) for valuable insights”. Here you can read the first part.


A proven strategy for planning and implementing the PoC is the following two steps:

I. Before running the PoC, the following questions should be considered:

  1. Have all necessary applications and access rights been reviewed?
  2. Are legal requirements met at all stages of the automation?
  3. How can known and unknown exceptions be handled?
  4. Is scaling possible? Under which circumstances?
  5. Which resources are needed in the future to ensure smooth automations (people, budget, time)?
  6. What are the company’s ambitions regarding their RPA journey?


II. Select the right processes for the PoC

The next step is to select a set of simple processes to be automated (the less, the better) which give answers to the questions mentioned above.

Many companies choose an “easy-and-fast-to-implement” process as their PoC. They do this because they want to present RPA as a magic silver bullet that easily automates every process and has outstanding benefits. The consequence of this will be a group of stakeholders with sky-high expectations, waiting to see benefits in just a few weeks. Does this sound realistic keeping the questions in mind? No, of course not.

Hence, a PoC that considers all the aspects indicated in step I helps the RPA team to present more realistic findings about the potential of RPA in their company. The realistic method gives stakeholders more valuable insights that allow pragmatic expectations. The risk of disappointment reduces vastly.

In summary: consider all factors when planning the PoC, and present the potential of RPA in a realistic manner to make sure that stakeholders’ assumptions remain realistic enough to be met.


Do you want to know more about RPA and the strategies around it? Follow our blog for many more interesting and valuable insights from our team and external RPA experts.