RPA Bot Editor

Migration Assistant

What is RPA?

Automation Anywhere offers Robotic Process Automation (RPA) which automates manual processes with software robots that can learn, mimic, and then execute rules-based business processes.

What does Migration Assistant do?

Before Migration Assistant, customers had significant challenges with migrating their bots from our Windows-based application to the new cloud platform, A360. My team and I created the Migration Assistant, embedded in the Bot Editor, to enable easy and fast migration reviews.

My roles

  • Project lead

  • UI/UX Design

  • System design

  • User testing

My team

  • UX Designer (2)

  • Product Manager (2)

  • Lead Engineer (1)

  • UX Writer (1)

Timeline

12 Weeks | Started Oct 2020

Identify problems

It’s very complex and time consuming to review hundreds and thousands of migrated bots.

After Bot migration, the Bot Developer has difficulty understanding the bot structure changes. They find it hard to fix critical errors and have their bots working properly in A360.

creates, manages and deploys bots.

Bot Developer:

Open a migrated bot in A360

Review Bot Scanner Report to understand critical changes/errors

Test bots

Fix critical errors in Bot Editor

Repeat until all bots working properly

Bots working properly in A360

Pain point

Pain point

Review migrated bots

How Might We

Then I asked, “How do I want to make it better?” and “What do I want to achieve?”

My next step was working with the team to come up with HMW questions to frame our thinking around the problems that eventually became our principles.

01

Easily educate users about migration changes and new offerings in the Bot Editor?

03

Streamline the experience so users can easily make the necessary changes in a bot for it to run without issues?

05

Improve the relationship between the user and the product so that the user feels more comfortable with and trusting of Automation Anywhere?

04

Empower users to feel more confident in their skills so they can work faster?

02

Guide users so they know what needs to be done after migrating a bot?

Explore inspirations

Many products use modals, flyouts and windows to help their users understand features in their platforms.

I focused my research on how other products handle user onboarding and guidance as this aligned with the experience I aimed to improve.

Face challenges

We had to consider some limitations with the Bot Editor.

  • The new feature would be integrated into the Bot Editor, the primary workspace for our users.

    However, the editor had a very condensed workspace so the feature had to be designed accordingly.

  • Our solution had to accommodate large scales. A bot can have hundreds or thousands of different changes and errors after migration.

Explore ideas

I kept in mind the dual goals of providing helpful information but also respecting limited real estate while brainstorming.

We eventually picked the floating window because it was the most flexible without consuming additional space in the Bot Editor.

Encounter more challenges

As we developed the design, we faced many technical constraints and limitations.

Tackle the issues

Users had difficulties with prioritizing the migration review from high to low severity as well as identifying changes and errors in the Bot Scanner Report.

To sort migration changes, we organized them into 3 different groups:

  • Action required items

    -> Critical changes that need the user's input (Validation errors)

  • Review required items

    -> Changes that Automation Anywhere wants users to know about (Information)

  • Reviewed items

    -> Dismissed items, “Mark as reviewed” by users go into this group

Evolution of the window

The original idea was to include an X of Y counter on the details page to indicate positioning.

However, combining the counter with the ability to dismiss items from the list would create some confusion.

  • When you see the counter showing “1 of 25” and dismiss it, what number should appear next?

    “1 of 24” or “2 of 25”?

  • When you dismiss an item, which group is the item in? Still in the “Action required” or “Reviewed” because it’s dismissed?

Problem

  • We redesigned the entire bottom navigation, and removed the counter to simplify the navigation behavior.

  • The “Dismiss” button was renamed to “Mark as reviewed” which is more clear to users.

Solution

  • Items marked as reviewed stay in the “Action required” group until the users go back to the main list or close the window.

Introduce the feature

In order to educate users about the feature, we created a modal window that appears when they open a newly migrated bot.

We worked with our visual design lead to refine the final design.

  • Too much content in a small space.

    It makes users get distracted.

  • Needed to involve our brand team to get new illustrations, and it required too much effort and time within the timeline.

  • Required extra work for front and back end Eng teams to create a native modal, and they didn’t have bandwidth in the given timeline.

Initial version

  • Simplified the content and design so users would be able to stay focused on the modal.

  • Used a modal which Pendo provides to reduce workload for teams and meet the timeline.

Final version

  • Pulled metrics from Pendo to see how users engage with our Migration Assistant.

Final copy and visual design by Hector Jamie

Final design

What final design looks like

Evolve into a sustainable design

Creating this window design opened up opportunities for UX improvement across the product.

I re-used the window component and created the ‘Error Assistant’ and ‘Advanced Search’. Later on, these were merged to become the ‘Assistant’.

Advanced Search

Error Assistant

Assistant - all in one window

Measuring success

We reduced CS inquiries related to migration issues by 84% as of Q2 2022.

Plus, the Assistant window has become an essential feature for the automation development as it evolves.

© 2025 by Hanmaro Kim | Hanmarodesign.com

In this project, I’m showcasing my skills with a focus on...

  • Problem solving

  • Creating an extensive design

  • Collaboration with cross-functional teams

  • Working within technical constraints

Results

  • Successfully reduced bot migration issues by 84% in Q2 2022.

  • Repurposed the Migration Assistant to support additional features, eventually evolving into the Bot Assistant.