Podcast | 9

Getting the Blueprint Right: Best Practices for RPA Process Requirements

Time: 19:16
Transform NOW Podcast with Khatina Brunson of Blue Prism

Can't see this content? That's probably related to your cookie preferences. 

When you're configuring your automation, you need a blueprint because a blueprint will tell you what you're building. Once you've decided which process you want to automate, you also need a process to follow. And when you create requirements for automated processes, you'll want to generate a requirements document for future reference.

So if the process is so important, what are the best practices for RPA process requirements?

On this episode of Generation Digital Workforce, Khatina Brunson, customer success manager at Blue Prism, discusses how companies can implement best practices for RPA processes.

Here's what we talked with Khatina about:

  • Preliminary steps to start the process
  • What makes a good requirements document for automation
  • How to capture the details (the level of detail is more intense than most people are used to)
  • What to avoid when building requirements

To ensure that you never miss an episode of Transform NOW, subscribe on Apple Podcasts, Google Podcasts, Spotify, or wherever you listen to podcasts.


The Latest From Blue Prism

Free the People

Becoming an agile enterprise means operating as a seamless mix of digital workers, human workers, and systems dynamically automating processes everywhere from the back office to the customer experience. You can do this with Blue Prism's intelligent digital workers that are versatile, autonomous, self-organizing, and secure. As a result, you gain better insight and control over the work, create new and transformative ways to operate, and empower people to focus on work that truly matters.

Get Started Free Trial

©2021 Blue Prism Limited. “Blue Prism”, the “Blue Prism” logo and Prism device are either trademarks or registered trademarks of Blue Prism Limited and its affiliates. All Rights Reserved.