Simplified content creation so educators can focus on great learning, not the learning curve
Industry
EduTech
EduTech
My role
UX/UI Designer
UX/UI Designer
Year
2021
2021
Quitch is a mobile-first learning platform that helps educators engage students through gamified, bite-sized quizzes. The Educator Portal is where teachers create and schedule content — the quality of this content is key to student success.
As the in-house UX/UI designer, I led research, interface design, and design system improvements to streamline the content creation flow — helping time-poor educators feel confident and supported from their very first quiz.The Challenge
Educators found it difficult to get started with Quitch, often requiring live demos or support from the customer success team. This reliance on hands-on support slowed adoption and made it harder to scale. To support a product-led approach, the experience needed to be simpler, faster, and more self-guided.
Research ApproachI conducted remote usability testing with three educators new to the platform. Participants (aged 30s–50s) shared their screens while attempting to create a quiz for the first time. I focused on task completion and confidence levels, asking each to rate their experience from 0–10. The average rating was 4.7, validating my hypothesis that new users were struggling with the content editor without hands-on support.
Key Insights & Recommendations
Confusion around content visibility: Educators were unsure when or if their content had been made available to students. With multiple actions involved (toggling visibility, scheduling, and publishing) users felt anxious and uncertain.
Clarify system status: Make content states (draft/scheduled/published) more visible and reassuring.
Class structure setup created a bottleneck: The required setup of topics and class structure acted as a barrier. One user couldn’t progress to creating questions at all.
Streamline the path to quiz creation: Reduce upfront requirements and let users create questions earlier.
Visual clutter distracted from the core task: Non-essential settings and unclear layout made it harder to focus on building content.
Reduce visual noise: Prioritise essential elements and de-emphasise optional settings.
IdeationI used Crazy Eights to rapidly explore solutions for each recommendation — from quick fixes like placeholder text in the class setup, to future-facing ideas like AI-generated content from teaching materials.
To prioritise, I mapped each idea using an Effort vs Impact matrix. This helped identify several quick wins (e.g. clearer content type descriptions) to include in the first iteration. Higher—effort ideas like a question bank were parked due to team resourcing.
For this release, I focused on low-effort, high-impact changes to reduce friction and help educators get to content creation faster.
For this release, I focused on low-effort, high-impact changes to reduce friction and help educators get to content creation faster.
Note: AI-assisted content creation was just emerging in mainstream tools at the time. While promising, it was considered high-effort and out of scope for this iteration — though later implemented in a future release.
Wireframing and Protoyping
I wireframed a basic content creation flow covering question creation and scheduling. Through three rounds of user testing and team reviews, I made iterative improvements:
— Removed unnecessary steps (e.g. choosing their first question type)
— Refined UI text (e.g. 'Save' became 'Publish')
— Adding the scheduling function to individual questions and topics
A final clickable prototype in Figma was tested with current Quitch users to ensure the new interface still felt intuitive. Due to technical constraints, the question content itself was fixed for testing.
Final updates included:
— Combining questions and resources in one view
— Adding a persistent '+ Add' toolbar
— Displaying a placeholder question to remove extra steps
— Contextual hover interactions to reduce clutter
— Arrows in preview to flip through content
— Removed unnecessary steps (e.g. choosing their first question type)
— Refined UI text (e.g. 'Save' became 'Publish')
— Adding the scheduling function to individual questions and topics
A final clickable prototype in Figma was tested with current Quitch users to ensure the new interface still felt intuitive. Due to technical constraints, the question content itself was fixed for testing.
Final updates included:
— Combining questions and resources in one view
— Adding a persistent '+ Add' toolbar
— Displaying a placeholder question to remove extra steps
— Contextual hover interactions to reduce clutter
— Arrows in preview to flip through content
Visual Design
The interface was kept clean and minimal so the educator's content could shine. I leaned on our existing design system for colour and typography, while introducing new icons for content types.
New components included:
— The '+ Add' dropdown menu
— Question/resource UI elements (with states)
— Simplified preview view
— Updated settings panel
The layout was also responsive: the preview is hidden on smaller desktops to prioritise editing, and mobile users are directed to larger devices for content creation.
The interface was kept clean and minimal so the educator's content could shine. I leaned on our existing design system for colour and typography, while introducing new icons for content types.
New components included:
— The '+ Add' dropdown menu
— Question/resource UI elements (with states)
— Simplified preview view
— Updated settings panel
The layout was also responsive: the preview is hidden on smaller desktops to prioritise editing, and mobile users are directed to larger devices for content creation.
Beta Testing and Launch
We ran a beta testing phase, giving educators the option to opt-in to the new interface. This reduced anxiety around change and allowed them to switch back if needed. We coordinated the launch to avoid peak class setup times and supported it with a persistent feedback modal.
Key results:
— 71.5% of existing users opted into the new editor
— 62.96% of sessions were completed using the new content editor
We also observed sessions via Hotjar and received direct feedback:
We ran a beta testing phase, giving educators the option to opt-in to the new interface. This reduced anxiety around change and allowed them to switch back if needed. We coordinated the launch to avoid peak class setup times and supported it with a persistent feedback modal.
Key results:
— 71.5% of existing users opted into the new editor
— 62.96% of sessions were completed using the new content editor
We also observed sessions via Hotjar and received direct feedback:
“I appreciate the streamlined processes, redesigned interface, and new features. This will undoubtedly improve our content creation and delivery experience. The ability to preview questions is a particularly valuable addition.”
Iterations and Refinements
Default settings matter
We introduced a “Publish Now” option to simplify scheduling, but many users rushed through setup and unintentionally sent content before they were ready. To fix this, we changed the default to “Publish Later” and made scheduling options more prominent.
We introduced a “Publish Now” option to simplify scheduling, but many users rushed through setup and unintentionally sent content before they were ready. To fix this, we changed the default to “Publish Later” and made scheduling options more prominent.
Moving content was more important than expected
Users wanted to reorganise content frequently, and while drag-and-drop was preferred, we couldn’t ensure a smooth experience within current technical constraints. Instead, we implemented batch actions — allowing users to select and move multiple items at once.
Users wanted to reorganise content frequently, and while drag-and-drop was preferred, we couldn’t ensure a smooth experience within current technical constraints. Instead, we implemented batch actions — allowing users to select and move multiple items at once.
Formatting improves clarity and engagement
Educators wanted more control over how their content appeared. We introduced basic text formatting options — bold, italic, and underline — to help them emphasise key points and make content clearer and more engaging.
Educators wanted more control over how their content appeared. We introduced basic text formatting options — bold, italic, and underline — to help them emphasise key points and make content clearer and more engaging.
Final Design
Quick start guide
Introduced a persistent onboarding guide that highlights key actions. Skippable but always accessible, it gives educators support when and where they need it.
Introduced a persistent onboarding guide that highlights key actions. Skippable but always accessible, it gives educators support when and where they need it.
Streamlined publish flow
Removed the toggle-schedule-publish confusion by combining steps into a single, intuitive publishing action — making it easier for users to share content and reducing missed steps.
Removed the toggle-schedule-publish confusion by combining steps into a single, intuitive publishing action — making it easier for users to share content and reducing missed steps.
All-in-one editing screen
Enabled users to create and edit questions in a single view, eliminating the need to open/close modals and helping them move through tasks more efficiently.
Enabled users to create and edit questions in a single view, eliminating the need to open/close modals and helping them move through tasks more efficiently.
In-browser preview
Added a Preview mode so educators can see exactly how content appears to learners — improving content quality without requiring the mobile app.
Added a Preview mode so educators can see exactly how content appears to learners — improving content quality without requiring the mobile app.
Clear content states
Introduced clear labels for ‘Draft’, ‘Scheduled’, and ‘Sent’ — giving educators confidence in what their students can access and when.
Introduced clear labels for ‘Draft’, ‘Scheduled’, and ‘Sent’ — giving educators confidence in what their students can access and when.
Smarter defaults and tooltips
Placeholder content, question type descriptions, and contextual tips support learning and ease of use
Placeholder content, question type descriptions, and contextual tips support learning and ease of use
Impact
Enabled self sign-up
Quitch supported self sign-up for the first time — removing the need for manual onboarding and demos
Reduced support load
Fewer setup-related support tickets and onboarding requests
Increased user confidence
Preview, clearer content states, and a simplified UI helped educators feel in control
Faster onboarding
New users were able to create and preview content more quickly
Enabled self sign-up
Quitch supported self sign-up for the first time — removing the need for manual onboarding and demos
Reduced support load
Fewer setup-related support tickets and onboarding requests
Increased user confidence
Preview, clearer content states, and a simplified UI helped educators feel in control
Faster onboarding
New users were able to create and preview content more quickly