Classroom churn was terrible
Before I started on redesigning the EF Classroom, It had a problem:
15% percent of students never made it into the classroom!
Before I started on redesigning the EF Classroom, It had a problem:
15% percent of students never made it into the classroom!
Context: Group Lessons and Private lessons are an opportunity
for English students to apply what they have learned during self-study
with other students and with a certified EF English teacher.
In order to take an online English Group Lesson, students had to go through
four main steps:
The problem: when students were lined-up to enter the
classroom (queued for a teacher), not all of them were able to enter the
classroom right away. With a wait time of up to 10 minutes, 15% of all the students churned during this wait!
Why is this a problem? Not only are Group Lessons very beneficial to student's
English education, but EF also makes a fair share of their money from having
students complete Group (and Private) Lessons.
The hypothesis: students might churn less if we were more honest with them about what they were waiting for.
The execution: what needed to happen is a cross-team effort in order to:
After going over a few interactions in Sketch, I built a prototype in Framer in order to give the developers an idea of what I had in mind. In the spirit of speed, not all states were built into the prototype.
By showing a progress indicator like this, we were able to increase transparency with our students. The four backend steps required for students to make it into the classroom were now clear to them; they knew why they were waiting:
We A/B tested this idea by measuring student cohorts' "seat given" KPI before and after the change.
Check out the EF English Live classroom at: englishlive.ef.com
In a single sprint, we had reduced classroom churn by 14%.
Team: User Experience & Design @ EF Education First
(Shanghai, China)
Role: User Experience Designer