ed tech app | feature

EMBIBE LIVE Classes Batching & Monetisation
of Student App

Employer

Embibe

My Role

Research, product design, design systems, user-testing.

Contribution

Solo designer worked with VP product, Teaching Faculty

Timeline

May '23 - Aug '23
4 months

Feature name
Playing Video
Payment Information
Accessed Premium content
outcomes

Projected to generate ₹1Cr* every 4 months, providing interactive learning and personalized feedback for exam success.

* If 5,000 out of 10,000 (current) active viewers Sign up, ₹2,000/course = ₹1Cr in 4 months

BACKGROUND

Streamlining Live Classes and creation of sellable courses

The monetization of the EMBIBE Student App evolved from class batching (Requirement V1) to sellable courses (Requirement V3), creating a structured, personalized, and goal-driven learning experience.

Requirement V1

Batch Allocation Through Performance Assessment

Assessment-based batch allotment based on skill test results
Based on the result of the Skill Test
- Beginner: Basic level classes
- Performer: Intermediate level classes
- Achiever: Advanced level classes
Requirement V2

Existing Standalone Classes into Subject and Exam Batches

Integrating existing live class experience
Grouping live classes into subject or exam-based cohorts
Requirement V3

Turning Batches into Purchasable Subject and Exam Courses

Turning batches into sellable courses
Optimizing user experience for better course purchases and conversions
problems

Live Classes feature was unable to fully deliver its intended value.

The low continuing registration to the Live classes and low overall Pre and Post Class activities completion owing to the issues

Embibe users face difficulty enrolling in multiple classes, as they are required to register for each class separately, leading to a fragmented experience.

The overall completion rate of users for Pre and Post-class activities is low, impacting the effectiveness of the learning journey and reducing engagement with class materials.

UX RESEARCH

Validating our decisions

Convincing stakeholders, securing buy-in, and evaluating solutions.

Cocreation Workshop

  • Stakeholder agreement for a revised Requirment.
  • Competitor Analysis to arrive at new approach

Usability Testing

  • Identify motivations for using live classes.
  • Understand barriers to live class adoption, focusing on drop-offs and new users.
  • Analyze awareness and compare ed-tech platforms.
  • Investigate gaps in existing platforms and explore user experiences.
Solution

Timeline based Live class courses

Highlights

Simplify decision making

Precisely state the value that the student would get by purchasing the Course. To give them enough pointers of the impact the course would provide to accomplish their Exam Goals.

live_tv
Minimum of 5 offerings, for each and every Goal Exam
devices_other
Carefully Researched to meet students expectations
vibration
A Syllabus timeline broken down for students
Highlights

Optimising for Monetisation

Designed features like payment gateways and access management, ensuring that students can purchase and access their course materials without any friction.

Import:

.docx

.xlsx

.odt

Export:

.pdf

.pptx

.rtf

.webp

final designs

Seamless Experience

Key Flows

The video player view was designed based on insights gathered from competitor analysis of MOOC course providers.

Search & Filter
About & Syllabus
Buying Course

Notifications

I also worked on the notifications for the student app, which was part of a different project scope. However, in the context of Live Class batching, the notifications are as follows:

  • Class has begun reminder
  • Class cancelled
  • Class rescheduled

Content Player view

Users can interact with different content, and the hero part of the screen would contextually display different CTAs relevant to the content interacted with, namely:

  • Videos
  • Practice
  • Test
  • Notes
  • Live Class

Edge Cases

To address various edge cases in the video player view, solutions were designed to inform and educate users about specific conditions.

Project status

In development

The project has received approval from all stakeholders and is now in the development phase after design debriefing was done to core product dev team.