Overview
Redesigned four disconnected learning products into one unified platform, Pathfinder.
My Role
UX, User Research, UI, Design Strategy
Team
Timeline
2024 Q1–Q2
Pathfinder Community page, initial launch. The central hub connecting forums, challenges, missions, developer resources, and Academy.
Impact
What this work led to.
Enterprise teams
Adopted Mission Control. Designed the assessment, mission pages, and 90-day planning experience.
Persona paths
Automation Lead, Pro Developer, Citizen Developer
Cert growth
185 → 271/mo
Mission Control walkthrough
6 min
Problem
Why this project started.
Automation Anywhere had five separate learning products. Community, University, Missions, Bot Games, and Bot Store. Each had its own login, its own look, and its own navigation. Nothing connected them.
- No clear starting point — learners didn't know where to begin
- University sorted content by topic, not by role or skill level
- No guided paths for different experience levels or personas
- Certification completions dropping every month
Certification completions per month
Advanced + Master certifications, Feb–Jul 2024
Certification completions were one signal that the experience wasn't working. After launching role-based learning paths, completions recovered to 271 per month.
Heard directly from the community
Forum posts asking for a starting point appeared weekly. No clear entry path existed.
No filtering by role or skill level. A citizen developer got the same path as a pro engineer.
Completed training, no badge, no next step. Progress wasn't acknowledged anywhere.
scroll to see all →
Process
How we approached it.
Competitive research
Looked at a few competitors for inspiration and identified gap areas that were missing from the platform, features and patterns worth bringing in.
Assessment and mission design
Refined the assessment questions to better reflect where users were in their automation journey. Based on the results, the system assigned relevant missions and generated a personalised 90-day plan.
Role based learning paths
Introduced three distinct learning paths built around the core personas — Automation Lead, Pro Developer, and Citizen Developer. Each path gave users a clear starting point and a structured progression tailored to their role.
Certification redesign
Redesigned the certification pages with clear structure across three levels. Essentials, Advanced, and Masters each got their own page with exam details, prep course links, and a clear path forward.
Unified navigation
Built a single navigation across Community, University, Mission Control, and Bot Store. One consistent header and one identity across all five products so users could move between them without losing context.
Engagement and growth
Redesigned Bot Games challenges, certifications, and leaderboards to drive participation. Created LinkedIn ready banners and assets to help users share achievements and expand the platform's reach organically.
Solution
What we shipped.
Mission Control launch
Introduced a new program hub for enterprise automation teams. Teams assess their current maturity across five pillars and get assigned to focused missions with a 90-day plan to accelerate their program growth.
Role based journeys and university redesign
Redesigned the university experience around three distinct roles. Bite sized courses replaced long form content, giving learners a faster and more focused path to certification based on where they were in their journey.
Design system
Following a theme throughout.
Extended the existing design system library with new components built specifically for the Pathfinder experience. Badges, certification cards, mission banners, leaderboard patterns, and navigation elements.
Reflections
Few fun learnings.
On working in sprints
A 15-day release cycle meant proposing ideas, prototyping quickly, and collaborating with marketing simultaneously. Challenging and energising at the same time.
On wearing multiple hats
This was the first project that required handling both UX and visual design simultaneously, working as the sole designer embedded in a cross-functional team. A chance to explore unfamiliar territory before being moved to a higher priority project.
On working on a customer-facing product
First time working on a product where actual community discussions and learning happen. The stakes felt different, real users, real conversations, real impact.
On learning from people
Some of the most valuable lessons came from working alongside different teams and the Director of Community, Larkin. The product knowledge and community insight shaped every design decision.
Get in touch to know more.
The highlights are here. The good stuff is in the conversation.
Next Case Study
AI Agent Studio →