Improving the course details page to make actions clearer to users
- 1 Introduction
- 2 JTBD
- 3 Requirement Specifications
- 3.1 <User chooses to enroll into the course> Overview
- 3.2 < User chooses to enroll into the course - Overall Process Workflow>
- 3.3 <User chooses to enroll into the course> Story Overview
- 3.3.1 <Main Scenario>
- 3.3.2 <Alternate Scenario 1>
- 3.3.3 Exception Scenarios
- 3.3.4 JIRA Ticket ID
- 3.4 <User story 2 - User can start/resume the course> Overview
- 3.4.1 <Main Scenario>
- 3.4.2 <Alternate Scenario 1>
- 3.4.3 Exception Scenarios
- 3.4.4 JIRA Ticket ID
- 3.5 Localization Requirements
- 3.6 Telemetry Requirements
- 3.7 Non-Functional Requirements
- 3.8 Impact on other Products/Solutions
- 3.9 Impact on Existing Users/Data
- 3.10 Key Metrics
Introduction
By tracking the courses funnel on the mobile app, we realise that out of the 100% clicking on a specific course card, only 12% are clicking on enroll. Out of that, only 7% are completing the enrollment after signing in. These are fairly dismal numbers. While we see an increase in the numbers when the state makes courses mandatory, it isn't close to ideal.
Post enroling, % of users starting the course, and resuming the course after starting is fairly dismal. Field research seems to prove that this is an issue with the intuitiveness of the page. Users are unable to understand what action to perform next when they look at the details page. This PRD tackles that.
JTBD
Jobs To Be Done: As the State who is launching a course for teachers, I want teachers to be able to enrol into the course easily, so that I can ensure they have taken the course in order to upskill themselves.
User Personas: Government School Teacher
System or Environment: At home or in school using their mobile phone
Requirement Specifications
This section consists of requirement specifications for specific use cases in the User JTBD. The requirements for each use case are elaborated in detail through sub-sections for:
Use case overview
Overall process workflow
Associated user stories
Non-functional requirements
Localization requirements
Telemetry requirements
Dependencies
Impact on other products
Impact on existing data
<User chooses to enroll into the course> Overview
< User chooses to enroll into the course - Overall Process Workflow>
The state will launch courses by issuing QR codes on a circular. These circulars will be made available to teachers in schools via the circular. Teachers are expected to scan the QR code, enrol and take the course. On completion of the course, they will be provided with a certificate.
<User chooses to enroll into the course> Story Overview
This story covers the details that a user should be shown in order to prompt them to enroll into the course.
<Main Scenario>
Srl. No. | User Action | Expected Result |
|---|---|---|
1 | A user scans the QR code for a course (which has only one batch) and lands on the course TOC page | They should be shown the course name, org name with a prominent CTA to enrol into the course (with a date by which they need to do so, if that batch has an enrolment end date) They will be shown the description of the course, the metadata (medium, class, subject) and legal info (Author, Published on DIKSHA by, Licence terms and Copyright) They have the choice to see the TOC by clicking on a separate tab. |
2 | A user opts to look at the TOC instead of the course details and clicks on any of the content pieces on the TOC page | They are prompted to enroll to continue looking at the content. |
3 | The user chooses to enroll | They are taken to the sign in page (if they haven't signed in already) OR They are taken to the TOC page after being enrolled into the course (if signed in) |
<Alternate Scenario 1>
Srl. No. | User Action | Expected Result |
|---|---|---|
1 | A user is viewing the TOC page of a course which has multiple batches (upcoming and ongoing) | The user is shown the TOC page (as above) with an additional detail of the number of batches available (it is not clickable) ordered by most recent They are not shown the message to register by x date under the CTA to enroll |
2 | The user chooses to enroll | They are first shown a list of batches, and asked which one they'd like to enroll into (same screen as today) When they enroll into the course, they are asked to sign in/up (if they haven't already) OR they are taken to the TOC page after being enrolled if they've signed in |
3 | A user is viewing the TOC page of a course with multiple batches (some expired, and some ongoing/upcoming) and they choose to enroll | They are only shown ongoing and upcoming batches. They are not shown details of expired batches. |
Exception Scenarios
Srl. No. | Error / Exception | Expected Handling |
|---|---|---|
1 | The user has scanned the QR code of a course with expired batches | The user is shown a message on the same page that the course isn't currently active, and to come back later. |
JIRA Ticket ID
<User story 2 - User can start/resume the course> Overview
This story covers the details that a user should be shown in order to start the course and complete it, once they have enrolled into it.
<Main Scenario>
Srl. No. | User Action | Expected Result |
|---|---|---|
1 | A user has enrolled into a course and is on the TOC page | They are shown the name of the course, the organisation and the course contents by default They are shown a prominent CTA to start the course, and the detail of by when they need to complete the course (if the batch has an end date) |
2 | The user chooses to start the course | The first content of the course is played |
3 | The user revisits the course after watching some of it earlier | On the course details page, the user is shown a CTA to watch the next piece of content |
4 | The user selects the option watch the next piece of content | If the user was mid way through watching a piece of content, the same content will be played again OR If the user completed the previous content, they are played the next content |
5 | The user goes back to the course details page | They see their progress in terms of how many content pieces they have completed, and how many are pending They can also see which content or unit is completed at a TOC level |
6 | The user completes the course and is on the course details page | They are shown a message that they have completed the course They can still continue to play content using the TOC, but they have no other prominent CTAs |
<Alternate Scenario 1>
Srl. No. | User Action | Expected Result |
|---|---|---|
1 | A user clicks on a content from the TOC instead of clicking on the CTA | The specific piece of content is played for the user The TOC and their progress is updated accordingly |
Exception Scenarios
Srl. No. | Error / Exception | Expected Handling |
|---|---|---|
1 | The batch that the user has enrolled in has expired, and the user comes to the TOC page | They see a message while the course has ended, they can continue to take the course - but their progress is locked. |
JIRA Ticket ID
Localization Requirements
UI Element | Description | Language(s)/ Locales Required |
|---|---|---|
CTAs | Register for course Start watching Continue watching Watch next | All languages supported by mobile app today |
Labels | Register by <x> batches available Course contents Course details | All languages supported by mobile app today |
Telemetry Requirements
Note: None of the context info should be captured in edata.extravalues as that field can't be indexed in DRUID.
Event Name | Description | Purpose |
|---|---|---|
Enroll into course | The user clicks on Register for Course This should capture context details about the specific course the user tried to enroll into | This is to track the number of users who show intent to register for the course as part of the courses funnel |
Register for batch | The user chooses to register for specific batch if there is more than one batch This should capture context details about the course and the batch the user has chosen | This is to track behavior on a page where the user is offered more than one batch |
Enrollment complete | Users who haven't signed in to SunbirdEd are forced to do so once they enrol Owing to this, we need to find out the number of users who actually completed the enrolment process | This is to compute the enrolment index, which is one of the TPD solution success metrics |
Start course/Resume Course/Continue Course | Users who click on Start Course/Resume Course/Continue Course This should capture context details about the specific course the user has started/resumed/continued These are 3 different INTERACT events | This is to track the number of users who have started/continued/completed the course as part of the funnel |
Clicks course module | Users who click on any module on the TOC page | This is to track the number of users who click on the modules/sub-modules of a course |
Clicks couse content from TOC | Users who click on any content on the TOC page | This is to track the number of users who click on content from the TOC page |
Non-Functional Requirements
Performance / Responsiveness Requirements | Load/Volume Requirements | Security / Privacy Requirements |
|---|---|---|
Impact on other Products/Solutions
Product/Solution Impacted | Impact Description |
|---|---|
Impact on Existing Users/Data
User/Data Impacted | Impact Description |
|---|---|
Key Metrics
Srl. No. | Metric | Purpose of Metric |
|---|---|---|