Helping Circus Street learners feel at home after a platform transition, without increasing support burden

MY ROLE ON THE PROJECT

I led product design from discovery to launch. My objective was to help Circus Street learners adapt to the Cloud Academy platform without increasing support requests or putting retention at risk.

I worked closely with Product, Engineering and Content stakeholders across the three organizations involved in the migration. Within that group, I was responsible for:

  • leading the UX strategy for the Course and Lesson pages

  • bringing together research, usage data and usability testing to find where the experience could be simplified

  • aligning competing stakeholder needs around a shared learner focused hierarchy

  • designing and prototyping the full experience

The biggest challenge was organizational alignment. The Course and Lesson pages had recently been redesigned, so most stakeholders expected a conservative refresh. The data showed that several highly visible sections were barely used by learners, even though they were considered important internally. I pushed for a more fundamental rethink that focused on reducing cognitive load, so learners could quickly find the information they needed.

A familiar platform was about to be replaced by a more complex expereince

At the end of 2023, QA Group began migrating learners from Circus Street to the Cloud Academy platform.

This created a significant UX challenge. Circus Street learners were used to a simpler and more intuitive experience that they genuinely liked. Cloud Academy offered richer functionality, but also introduced additional complexity and denser content structures.

A slightly dramatized summary of how early user testing with Circus Street learners went.

There was a real risk that learners would:

Associate the migration with a degraded experience
Disengage during the transition
Generate increased support requests

Improving usability wasn’t just a UX goal — it was critical to reducing migration friction and protecting retention during a high-risk transition.

We decided to improve the experience incrementally, starting with the core learning flows: Courses and Lessons.

The goal was a smooth adjustment to a complex platform, without overwhelming learners or, worse, a spike in churn

To better understand the problem, I combined internal stakeholder feedback across three organizations, behavioral analytics and usability testing on the existing pages.

The research consistently pointed to the same issue: learners felt overwhelmed.

Both the Course and Lesson pages had cluttered layouts, unclear hierarchies, and low-value content in prominent positions. For instance, author link only had 0.2% user engagement but was taking up a good amount of space. Useful elements like the syllabus or description were partly hidden or hard to scan, while actions like enrolling or rating were inconsistently placed.

Misleading UI elements and structural inconsistencies (highlighted with a red dot in the image) made the experience feel disjointed. Most importantly, Circus Street stakeholders and learners described the pages as very overwhelming.

Associate the migration with a degraded experience
Disengage during the transition
Generate increased support requests
Associate the migration with a degraded experience
Disengage during the transition
Generate increased support requests

Our stakeholder priorities were often conflicting.

Different teams had strong opinions about what information needed to remain highly visible, even when usage data suggested learners rarely interacted with it.

Some examples:

  • author links had very low engagement but was very important for Cloud Academy content stakeholders and users

  • some metadata sections were almost never used but important for Sales

  • learners were scrolling extensively just to find course structure and progress information

However, removing less used sections entirely wasn’t possible because they served internal stakeholder goals across multiple organizations.

This forced us to think less about removal and more about prioritization.

Our stakeholder priorities were often conflicting.

I rebuilt the page hierarchy around what learners actually came to do

Instead of continuing to layer improvements onto the existing structure, I redesigned the information hierarchy around the core learner tasks:

  • understanding course value quickly

  • finding course content faster

  • tracking progress easily

  • reducing distraction during learning

I rebuilt the page hierarchy around what learners actually came to do

The redesign simplified scanning by prioritizing the most important information higher on the page and moving secondary content into dedicated tabs.

This allowed us to:

  • preserve stakeholder-required content

  • reduce cognitive overload

  • create a more scalable structure for future content needs

The redesign simplified scanning by prioritizing the most important information higher on the page and moving secondary content into dedicated tabs.

Author information moved into a Credits tab that adapts to each course type

As briefly mention above, one of the most politically complex areas was instructor and author information.

Different organizations had different expectations:

  • some content rarely included author information

  • Cloud Academy content often relied on recognizable cloud experts

  • content teams wanted flexibility to support multiple contributors in the future

At the same time, learner engagement with author-related content was extremely low.

Rather than removing the section entirely, I proposed moving it into a dedicated “Credits” tab.

This created a compromise that:

  • reduced visual noise for learners

  • preserved stakeholder needs

  • supported future scalability

  • accommodated multiple content models

The system was intentionally designed to flex between:

  • no author information

  • a single author

  • multiple contributors

depending on the course type.

Completion states became easier to spot, and certificates appeared only once earned

User testing also showed that learners often missed completion states entirely.

Previously:

  • completed lessons only displayed a small “Complete” label

  • certificate information appeared early as an empty progress state

  • progress visibility lacked clarity

To improve this, I redesigned completion patterns by:

  • introducing clearer completion variants

  • allowing users to hide completed steps

  • delaying certificate visibility until content was fully completed

  • making achievement states more visually prominent

This made progress easier to understand while reducing unnecessary distractions earlier in the learning journey.

The migration launched without a rise in complaints or support requests

The migration launched without a significant increase in learner complaints or support requests, which we considered a major success given the scale of the transition.

The redesign helped reduce friction during onboarding to a more complex platform while preserving access to stakeholder-required content.

We also saw behavioral signals that learners were finding key information faster:

Tab engagement remained below 20%, suggesting secondary information no longer distracted from primary tasks
Tab engagement remained below 20%, suggesting secondary information no longer distracted from primary tasks
Scroll depth decreased by 25%, indicating learners could access important content earlier without excessive scanning

Internally, content teams also responded positively to the clearer structure and increased flexibility of the new system.

Most importantly, the migration felt less like a disruption and more like a natural evolution of the learning experience.

Check out more projects