Transforming Language Education with English Quest

Overview

Problem

Teachers encountered difficulties in navigating the app, conducting classes, and effectively engaging students.

Outcome

Time spent to reach the lesson page decreased by 80% and allowing them to focus more on classroom instruction by designing new auto teach feature.

Client

English Quest

A teacher app that schools' teachers use to teach international quality english speaking lessons in person in school.

info

Role

Product Designer

Team

1 Product Manager & 2 Product Designers

Timeline

12 weeks
Old App UI
research

Understanding the
Problem

Conducted in-depth user interviews with school teachers to gain qualitative insights into their experiences and challenges. This direct engagement provided valuable feedback to better understand user needs and expectations.

In addition, analyzed Play Store reviews to identify recurring themes and potential areas for improvement. Complementing this, a detailed survey was designed and executed as a quantitative analysis to uncover common pain points and gather actionable data for informed decision-making.

Key Findings

Major insights and findings

Gathered all informations collected through various methods and categorised to find patterns.

After combing everything through, three main
insights were revealed.

1
User Interface Challenges

The onboarding process and bottom navigation menu confused users, making it challenging to navigate and use the app effectively.

2
Navigation Issues

Accessing lesson pages and completing attendance were overly complex, causing frustration and reducing overall app usability for teachers.

3
Impact on User Engagement

App complexity hindered teacher focus and failed to engage students, resulting in decreased interest and ineffective classroom interactions.

Opportunity
How might we simplify the app experience for teachers, enabling them to conduct classes effortlessly and without confusion?
Proto-persona

Understanding our user

Now it was time to think about who we were
designing for.

Our user is a primary school teacher who needs a simple way to conduct and manage classes. This allows them to focus on engaging with their students rather than being distracted by complex app features.

Bio

Latha is a primary school teacher, has 15 years of experience fostering her students' growth. Although passionate and hardworking, she often feels overwhelmed by technology and prefers straightforward tools to complement her traditional teaching methods effectively.

Attittudes

  • Thinks apps are difficult when conducting class.

  • Uses voice amplifier for teaching.

  • Using mobile distract students attention.

Latha

40

Female

Hyderabad, India

Needs

  • Effortless method for teaching vocabulary.

  • Keep students motivated through out the period.

  • A place to store lesson progress and class data.

Pain Points

  • The app is confusing and taking time to reach a lesson page.

  • Difficult to pay attention to students while using the app.

User Stories

Explaining our user’s
perspective

Next, we needed to understand what features were most valuable for Latha. We chose to write user stories, as they clearly describe where the pain occurs.

Keeping Latha’s needs in mind, we decided on three key user stories to further develop.

1

"I want to easily log in to the app so that it helps me start the class quickly without delays.”

Designing a simplified login process that collects information quickly will make onboarding easy & start using the app efficiently.

2

“I want to access the lessons to be taught today with minimal effort so that I can focus more on teaching”

By organizing the home page with today's lessons prominently, users can access their teaching materials quickly and effortlessly.

3

“I want a different method of teaching so that I can make students more interested and engaged in the lessons”

Relaunching the auto teach feature with new capabilities like auto appreciation will help to attain student’s attention and interest throughout the period.

Sketching

Building out the experience

Looking at our user stories, I took on the
responsibility to draw up both the low and mid-
fidelity wireframes before transitioning to the
computer to help with efficiency.

I focused on three core features.

1
Seamless Onboarding

A quick and simple login process ensures users can start using the app without delays or confusion.

2
Organized Home Screen

A clean dashboard displays today's lessons, schedules, and essential tools, reducing navigation effort for teachers.

3
Enhanced Auto Teach

An upgraded Auto Teach feature offers engaging, interactive lesson methods to captivate students and simplify teaching.

Solution 1

Easy Onboarding & Profile Selection

Users can quickly log in by providing minimal information, ensuring a fast and hassle-free onboarding experience.

Solution 2

Organized Navigation & Main Screens

Users can easily view and access lessons, schedules, and tools, simplifying their daily teaching tasks.

Solution 3

Enhanced Auto Teach
(Auto Teach v3)

Teachers can deliver engaging, interactive lessons with the upgraded Auto Teach feature including auto appreciation.

Retrospective

Final thoughts & takeaways

1
Pushing Boundaries

Designing an app for primary school teachers was initially a daunting challenge, especially as I had to deeply empathize with the struggles of non-tech-savvy users. Understanding their needs and creating feasible solutions required stepping out of my comfort zone.

This project pushed me to think critically, conduct thorough user research, and prioritize simplicity without compromising functionality. It was a rewarding experience that not only improved my design skills but also deepened my appreciation for creating user-centered solutions.

2
Communication is key

What challenges do teachers face while using the app? How can we simplify their experience? What features will have the most impact? How do we ensure the design aligns with user needs and expectations?

Things that made sense to me weren’t always clear to others on the team, and vice versa. By maintaining open and frequent communication, we were able to align our understanding, address potential roadblocks early, and ensure the project stayed on track.

3
More is more..?

When we began, I didn’t fully grasp the realistic expectations of the different roles involved. How much time do developers need to implement the designs? How should the design adapt to meet teachers' real-world needs?Working closely with all stakeholders—teachers, developers, and product managers—not only added immense value but also resulted in a more thoughtful and effective solution for our users.

Open to interesting challenges and opportunities!
Think I might be a great addition to your team? Let's find out!
Simply drop me a mail.
naseebpkn@gmail.com ↗