The Do’s and Don’ts of the Intelligent Automation Journey

The Do’s and Don’ts of the Intelligent Automation Journey

  • Pawan Jadhav
  • March 11, 2020
Category: Intelligent Automation,Healthcare,Robotic Process Automation

In our final post of our Intelligent Automation (IA) blog series, we’ll examine the key tactics and pitfalls of implementing an IA strategy. If you haven’t already, check out last week’s post on the timeline of your IA journey, as well.

Intelligent Automation has a wide-reaching impact across organizations and it’s critical that we treat it this way to ensure the following is avoided at any cost. Here are the “Do’s” and “Don’ts” of implementing IA in your business environment:

RPA

Don’t

1. Take a Tactical Approach to Implementation

This approach may give some initial benefits but will get bogged down, due to the lack of adoption across the organization.

Instead…

Treat this initiative strategically with top management commitment, vision and assigned budget. The intention should be to eventually create a Digital Operating Model COE that embodies intelligent automation and its related components.

Don’t

2. Choose the Wrong Processes

If the wrong processes are chosen, there is an increased risk of failure and discontinuation of the program. Moreover, it will lead to low return on investment.

Instead…

Choose the right processes to help garner support from the larger organization. Follow very structured demand generation, demand management and process assessment methodologies to ensure the team is focused on automating the right processes.

Don’t

3. Ignore Smart Change Management Practices

Resisting change is a natural reaction when you do not involve people affected by the change and lead to lack of cultural adoption within the organization.

Instead...

Remember that the key to success is following smart, proven change management practices. A few practices to review are indicated by Harvard Business School professor Dr. Kotter, in his 8 step process to manage change. Additionally, McKinsey proposed their 7S framework created by Tom Peters and Bob Waterman in the 1970s.

Don’t

4. Force-Fit One Type of Technology

You may be very excited by the new kid on the block – Robotic Process Automation (RPA). Yet, should you use this to automate anything and everything? Obviously not.

Instead…

Stay attuned with the Digital Operating Model (coupled with your processes assessment results) to identify what technologies should be introduced (and in what order) to solve your problems. Sometimes just reengineering a process may solve most of your challenges.

Don’t

5. Establish Incorrect Expectations of Your Timeline

These technologies can deliver faster results but consider multiple factors before forming an opinion or expectation about how quickly results will be delivered.

Instead…

Consider a few factors, including team readiness, cultural adoption, dependence on other technologies (imaging, workflow, other conflicting initiatives, system/application upgrades, etc.), maturity of the organization, security/risk/compliance, resource capacity, and more. Also, consider conducting a workshop with various departments to get better understand bottlenecks and opportunities to consolidate and eliminate. In turn, you will better understand expected results. 

I hope this step-by-step guide to strategically and thoughtfully implementing an Intelligent Automation process in your organization was informative, helpful and ultimately, effective. To understand how Lateetud can walk with you along the IA journey, reach out to Andrew Spada. Also, visit www.lateetud.com/resource to see what’s possible.

ina
Ina
(Online)