Project Overview

TeachGo is an end-to-end platform that streamlines private lesson management for teachers and families. It supports the full journey from helping parents find suitable instructors to booking, scheduling, payments, and rescheduling.

By centralizing these workflows into a single system, TeachGo reduces administrative overhead, improves communication, and delivers a more seamless and consistent experience for both teachers and families.

Project Type

End-to-End App Design

Duration

5 weeks · 2026

Scope

User Research, Feature Strategy, Interaction Design, Usability Testing, and Prototyping

Tools

Figma, FigJam

My Role

Solo UX/UI Designer

The Problem

Teachers

Managing payments and reminders is time-consuming and emotionally uncomfortable
Communication around tuition often feels awkward and repetitive
Scheduling and cancellations are handled manually across tools

Families

Finding the right teacher is time-consuming and unclear
Information is often scattered or based on word-of-mouth
Booking, payments, and communication lack consistency

There is an opportunity to create a unified platform that simplifies lesson management for teachers and helps parents efficiently find and evaluate suitable instructors.

User Research & Key Insights

Target Users

Teachers offering private lessons
Parents booking and managing lessons for their children
Students as secondary users

Insights From Competitor Analysis

Most existing platforms focus on either discovery or management, but rarely provide a seamless end-to-end experience.

Payment tools exist, but they do not address the emotional friction of tuition-related communication.

Communication between teachers and parents is often fragmented across multiple tools, leading to inefficiency and confusion.

Parents lack a clear and reliable way to compare teachers, making decision-making difficult.

Research Methods

I conducted user interviews with 8 participants, including both private lesson teachers and student parents, to understand their experiences and challenges from both perspectives. The findings were then synthesized using an affinity mapping process.

Key Insights from User Research

Teachers struggle to manage multiple students and tuition changes
Tracking lesson schedules, payments, and updates across different students can become overwhelming without a centralized system.
‍
Payment communication creates emotional friction for teachers
Many teachers feel uncomfortable reminding parents about unpaid tuition or discussing price increases, especially in one-on-one relationships where they are familiar with families.
‍
Parents need clearer pricing, reminders, and transparency
Unclear communication around lesson rates, schedules, and payments often leads to confusion and missed payments.
‍
Finding the right teacher is limited and inefficient
Parents often rely on word-of-mouth recommendations, making it difficult to explore options or compare teachers based on availability, pricing, or teaching style.
‍
Both teachers and parents rely on fragmented tools
Scheduling, communication, and payments are often managed across multiple platforms (text, spreadsheets, apps), leading to inefficiency and lack of consistency.
‍
Both sides want a centralized source of truth
Teachers and parents both expressed the need for a single platform to manage all lesson-related information in a clear and organized way.

Affinity Map

Personas

Two primary personas were created to ground the design in real user needs.

A private lesson teacher who manages multiple students and struggles to track schedules and payments.
A parent who wants a clear and reliable way to find well-qualified teachers, then manage their child's classes and tuition without relying on fragmented tools.

Project Goals

Based on the research findings, I defined key business and user goals to guide the design direction.

User flows

#1 Parent searches for a teacher and requests a lesson

This user flow supports parents in finding a suitable teacher without feeling overwhelmed. By offering clear search options and detailed teacher profiles, parents can confidently request a lesson that fits their child’s needs.

#2 Teacher Payment Management

This user flow is designed to reduce the emotional stress teachers experience when managing payments by allowing the system to handle reminders. It creates a more comfortable experience for teachers while keeping payment communication clear and respectful for parents.

Problem Solving Through Design

Low Fidelity

Early concepts were explored through low-fidelity wireframes and iteratively refined into more structured mid-fidelity designs.

Usability Testing

What Worked Well

Participants found the UI clean, friendly, and easy to follow
The overall structure felt approachable and intuitive
Navigation felt easy to understand

Challenges Identified

Teachers had difficulty finding tuition settings
Some buttons were expected to be clickable but were not
Pricing needed to be consistent across screens

Design Changes

Restructure navigation to surface tuition management more clearly
Improve interaction completeness for key actions
Standardize pricing across all user flows

Iterations

High-Fidelity

Final Prototype

View Prototype in Figma

The final prototype showcases a complete teacher workflow:

‍From login to sending payment reminders and tuition increase communications, designed to streamline key tasks and reduce both operational and emotional friction.

The final prototype showcases a complete family journey:

From onboarding to discovering suitable teachers and scheduling lessons, designed to simplify the search process and support more confident decision-making.

Outcomes & What I Learned

This project helped me practice designing for multiple user roles within one platform and balancing different needs across teachers and parents.

Key Takeaways

Information architecture must match users’ mental models.
Small interaction details strongly impact perceived usability and trust.
Early testing helps avoid bad assumptions and costly re-design.
This project helped me shift from designing for visual appeal to designing for real user needs.
I learned to simplify interfaces and focus on clarity instead of adding unnecessary features.

Next Steps

If I were to continue this project, I would:

Explore monetization and subscription models for teachers.
Expand and complete additional features to move the product closer to a real, production-ready app.
Continue testing and iterating based on real user feedback.

TeachGo

TeachGo is an all-in-one platform designed to simplify private lesson management for teachers and families.