Real-Time State Communication

Transforming
the Entry Point

From a Static CTA to a Dynamic System

From a Static CTA to a Dynamic System

Client

Complori

Industry

EdTech

Category

Web App

Role

Product designer

Location

Berlin, DE

Timeline

2024

This project is a UX case study focused on redesigning The Entry Experience around the platform’s most critical touchpoint — the ‘Join Live Class’ action. It covers the process from initial research and problem definition through solution design, validation, and measurable impact.

PROJECT OVERVIEW

PROJECT OVERVIEW

The Product

Complori, an EdTech platform providing live programming courses for kids.

The Challenge

The "Join Live Class" button — the platform's most critical touchpoint—was static, hard to find, and disconnected from real-time class status. This led to high student anxiety, late attendance, and a massive manual workload for Customer Support.

DISCOVERY & RESEARCH

Initial Observation

Initial Observation

During the initial research phase, I conducted a comprehensive product audit, including a deep dive into core user flows and key interaction scenarios. Early observations highlighted UX issues with the core action ‘Join Live Class,’ (1) particularly in navigation and information hierarchy. These issues significantly reduced interface clarity, usability, and the overall user experience.

Initial UX Hypotheses

  • Low discoverability of primary actions: Key CTAs are not immediately visible, reducing engagement [ 1 ].

  • Non-intuitive element placement leads to confusion and interaction friction.

  • Fragmented information architecture: Lesson details are dispersed, increasing cognitive load and hindering task completion [ 3-6 ].

Research Methods

Research Methods

What started as a design audit revealed patterns that pointed to a broader systemic issue. Since I didn’t have the luxury of running a full research study, I took a hypothesis-driven approach and triangulated lightweight signals from:

  • Behavioral Data Analysis

  • Targeted survey of newcomers

  • Customer support ticket analysis

  • Stakeholder insights

(CS, operations, coaches)

PROBLEM DEFENITION

PROBLEM DEFENITION

Key Problems

Key Problems

From research, I synthesized four key themes: discoverability, system feedback, trust, and operational scalability. Based on the synthesis, I identified three core problems:

  • CTA is hard to find

→ delayed class entry

  • No real-time class status

→ uncertainty & support reliance

  • Communication gaps

→ low trust & frustration

  • Manual operations → slow response & poor scalability

IDEATION

Placement Alternatives

Placement Alternatives

To make the entry point more visible, I had the idea to move the main action into the user’s natural flow of attention. Instead of placing it in the side navigation — where it can easily stay in the periphery — the goal was to make sure newcomers never miss their first class. I explored several alternative core action placements. Each option has its own pros, risks, and trade-offs.

Alternative 01

"Hero" Banner

Alternative 02

Contextual Card Replacement

Alternative 03

Global Sticky Footer

Global Sticky Footer

Global Sticky Footer

Alternative 04

Right Sidebar

Right Sidebar

Right Sidebar

DESIGN EVOLUTION

Iterating the Join Experience from low visibility to Actionable Countdown

Iterating the Join Experience from low visibility to Actionable Countdown

An iterative approach allowed me to move from quick improvements to more informed decisions. I started with quick visibility improvements—enhancing contrast and making the Entry Point more prominent. This was a fast, low-effort way to improve discoverability. Next, I introduced a dynamic status indicator—a countdown timer that updated the button state in real time. To reinforce urgency, the timer changed color when users were late.

While this iteration improved on-time attendance and reduced support inquiries, it still lacked sufficient visibility. Building on these insights, I prioritized solutions based on their impact on on-time attendance and implementation complexity. Two concepts emerged as the strongest candidates. We validated this direction through an A/B test.

A/B TESTING & VALIDATION

Finding the Optimal Entry Point

Finding the Optimal Entry Point

Experiment Overview: To identify the most effective placement for the entry point, we conducted a 14-day A/B test with a segment of newcomers. The goal was to find the right balance between maximum visibility and interface clarity.

Variant A:

Global Sticky Footer

Hypothesis: A persistently visible panel at the bottom of the screen maximizes reach, as the entry point remains in view during scrolling and stays accessible across all pages of the learning platform.

Variant B:

Contextual Sidebar Widget

Hypothesis: Placing a prominent widget within the “utility zone” would associate the entry point with schedule-related information, creating a stronger and more logical context for interaction.

Key Metrics & Insights

Key Metrics & Insights

Context beat pure visibility

We tested two variations, and the difference went beyond placement. The sidebar countdown widget increased visual prominence and introduced clear status indicators—icons and color states—that made the experience instantly understandable. Users could immediately recognize whether a class was upcoming or live. Paired with its contextual placement near the schedule, this reduced cognitive load and improved performance across all key metrics.

FINAL SOLUTION

Dynamic Widget. States and Placement

Dynamic Widget. States and Placement

Once we validated the concept through A/B testing, I translated it into a final, production-ready component. We evolved the static ‘Join’ button into a dynamic, state-driven component.

Phase 1: Initial
Implementation
Phase 1: Initial Implementation

Waiting

A high-visibility widget with a countdown timer focuses attention & builds anticipation before the live class.

A high-visibility widget with a countdown timer focuses attention & builds anticipation before the live class.

Phase 1: Initial Implementation

Live

The state indicates that the class is live and visually communicates that users can join immediately.

The state indicates that the class is live and visually communicates that users can join immediately.

Phase 2: Operational Extensions

Notification

The widget notifies users of any class delays or cancellations, helping users stay informed and avoid confusion.

The widget notifies users of any class delays or cancellations, helping users stay informed and avoid confusion.

Previously, class-related actions were scattered across the interface, making it harder for users to locate the correct entry point. The redesign introduced a unified class overview, where the dynamic widget became the primary interaction point—bringing visibility, timing, and status into one place.

NOTIFICATION CONTROL CENTER

Closing the Loop

Closing the Loop

A beautiful UI is useless without effective management. Previously, notifications about lesson schedule changes could take up to 15 minutes, which is not ideal for real-time communication. To make the widget work in real time, we needed to give superpowers to operations and support.

Problem

Ops and CS had no direct way to communicate with students inside the platform. They had to use manual email/SMS/calls, which was slow and led to a "information lag".

Goal

Transform manual support tasks into a scalable, efficient communication system, where Admin and Ops actions are instantly reflected in the student UI to maintain trust during incidents

Communication Management
& Advanced Targeting

Communication Management
& Advanced Targeting

The Notification Control Center is designed for high-pressure situations—when a Coach doesn’t show up, or class is delayed or some temporary tech issue. In these moments, speed and accuracy are critical. I prioritize clarity, efficiency, and scalability, enabling teams to act quickly and without error.

History Management Hub

History Management Hub

This is another part of the interface designed to manage all published notifications and drafts in one place. It allows admins to efficiently view, search, and manage communication across the full lifecycle.

IMPACT & RESULTS

21%

21%

On-Time Attendance Rate
On-Time Attendance
On-Time Attendance Rate

-60%

-60%

Avg.Join Delay (Post-start latency)
Avg.Join Delay
Avg.Join Delay (Post-start latency)

36%

36%

CS tickets 

Volume (Class status)
CS tickets 

Volume
CS tickets 

Volume (Class status)

1 min

1min

Time-to-Notify (During accident)
Time-to-Notify
Time-to-Notify (During accident)

KEY INSIGHTS

From Interface to System

From Interface to System

Visibility alone doesn’t drive action. Users act when information is both visible and meaningful in context.

Real-time UX requires system thinking. A seamless interface depends on operational tools and data flow behind the scenes.

Clarity reduces cognitive load and builds trust. Clear status communication helps users make faster decisions and reduces anxiety.

This project was created as part of my work at Complori, an EdTech company. The presented material is a demonstration of my contribution to concept development and is not intended for commercial use. All rights belong to their respective owners.

© Oleksandra Zuieva, 2024-2025

Create a free website with Framer, the website builder loved by startups, designers and agencies.