As with any project, but especially with process automation (there is a reason the word process is in there first) you need to identify a need, establish a goal then build and work from a plan. Otherwise you’ll simply wind up with automated chaos and a lot of angry people.

By Forrester Research  – Let’s just say that one measure of the hype that surrounds any emerging technology is the amount of new (and largely superfluous) jargon that it generates.

he market for robotic process automation (RPA) has been in hyper-growth for a while now. RPA and its extension into intelligent automation (IA) is an important market because it forms the tip of the spear for broader enterprise automation. We’ve previously estimated that IA technologies will release $134 billion in labor value by 2022. Meanwhile, the hype surrounding them is incessant, with vendors and pundits racing each other to create new words to describe capabilities. Often, these terms end up muddying the waters and confusing buyers. Lost amid the clamor is rational, pragmatic advice around how to succeed with RPA.

Research from Forrester shows that just 52% of enterprises have progressed their RPA initiatives beyond their first 10 bots. What gives? Just as with any other new enterprise technology, automation is a program that needs to be nurtured. Building your first bot may seem simple, but scaling an organization-wide RPA program is a whole different ball game. Read On: