OPUS

One of OPUS' core value propositions is a money-back guarantee: Customers are refunded if their child/student does not show improvement. In order to measure and monitor student progress, OPUS tutees take a quiz at the end of every lesson. Previously, quiz scores were recorded in different Google Drive spreadsheets which became unwieldy to manage. Hence, we created a custom web app to give OPUS a better way to track and update student progress.

I began this project by identifying potential users/stakeholders and creating actionable requirements. Some of the most important ones are summarized below:

• Stakeholders: Admin/business owner, tutors, parents, students
• Parents can monitor their childrens' progress
• Tutors can record lesson information
• Admins can manage users including parents, tutors, students, and other admins
• Flag students who have "deproved"

Originally, an OPUS lead would find out about the company through a digital ad and schedule a consultation via phone call. During this call, an OPUS representative would discuss the lead's tuition needs and make arrangements for lesson scheduling.

I made some simple user journey sketches to explore how this OPUS lead/customer might interact with a web app as well as what screens I'd need to design.

A few wireframes for brainstorming certain screens:

I opted for a simple but modular design for OPUS after considering several factors:

• Small team size
• Small and "contained" market size
• Need for flexibility to accomodate changing requirements and product needs
• Limit unecessary technical complexity, added frameworks

The OPUS web app consists of a React frontend which interfaces with the Typescript backend/server via a REST API. The server handles all business logic while retrieving data from the PostgreSQL database. A few diagrams taken from the technical documentation: