Architect Your Automation Strike Teams – Forbes

Hand touching a plasma ball with smooth magenta-blue flames

Emerging technologies such as robotic process automation (RPA), virtual agents, and machine learning these are those invisible robots described in the recently published Forrester book,Invisible Robots in the Quiet of the Night: How AI and Automation Will Restructure the Workforce. Invisible robots have rocketed automation to a top spot among enterprise initiatives, yet firms are dragging organizational and governance issues along as an afterthought.

To address these gaps, automation strike teams are emerging. So, what are they? Strike teams replace the automation center or center of excellence concept. This well-worn phrasing or description has two drawbacks when applied to todays automation initiatives: First, the term center implies more control (and, hence, bureaucracy and tardiness) than automation initiatives can withstand that are inherently federated, distributed, and centered in the business; and secondly, the term center implies a single instance, whereas we are seeing multiple strike teams forming that may specialize in a domain for example, operations (for RPA) or conversational intelligence for B2E or B2C use cases.

Strike teams are a reaction to these realities:

What The Automation Strike Team Does

Automation strike teams address the growing federation of business and traditional technology management expertise. Many organizations will have more than one, and each team may specialize in business or technology domains. Here is a summary of what they do:

This post was written by Vice President, Principal Analyst Craig Le Clair, and originally appeared here.

Read the original here:

Architect Your Automation Strike Teams - Forbes