Helping teachers help students:
WeVideo for Classrooms
Industry: SaaS, EdTech, B2B, Enterprise
Platform: Responsive Web
Role: Product Designer, User Researcher
Team: 1 PM, 1 Junior Designer, 6 Engineers
Timeline: 6 months
Highlights
I led a redesign of WeVideo’s flagship product to focus on engagement and scalability for K-12 Education, creating a new design system and improving UX across the board.
Impact
Increased NPS score by +33 points with positive feedback from users
Recognition
Awarded “WeVideo hero” for significant contributions to the project
Background
WeVideo is a cloud-based video editing platform used across education, B2C, SMBs, and enterprises. While users were able to create and share professional-quality videos online, the decade-old product had become increasingly difficult to scale. Years of technical and UX debt made it hard to deliver a seamless, modern experience resulting in an increasing frustration for our users.
Problems
Users were asking for features we couldn’t integrate
The outdated codebase prevented us from delivering modern features users expected, many of which were already standard offering from our competitors.
The interface was inconsistent and disjointed
Lack of unified design patterns led to user cognitive load and confusion.
The product failed accessibility standards
With issues like low contrast, small text, and poor keyboard navigation, it made it unusable for some students and prevented adoption in districts with legal accessibility requirements.
Opportunity
To support growth and user satisfaction, we reimagined the video assignment experience for teachers and students, emphasizing simplicity, clarity, and accessibility. The design challenge was to create a tool that felt intuitive for students of all ages, while making it easier for educators to manage and assess video-based learning.
Business Goals
Engage and Inspire
Design a classroom-friendly tool that teachers love using.
Build for the Future
Establish a scalable design system and architecture that supports long-term growth and seamless evolution across our products.
Design for All
Make sure all teachers and students can fully participate by meeting WCAG AA accessibility standards. Improve usability for everyone, not just those with specific needs.
Scope based on Priority
As the lead designer for a complex, ambiguous project with limited time, I created a game plan for the designs and schedule based on the requirements for the MVP.
Research
After conducting multi-methodology research efforts including user interviews, I consolidated the analysis with recommendations, UX values, and UX priority ratings.
Main takeaways
Teachers often had to use time-consuming workarounds with the flagship product
Sales were sometimes lost because the product did not pass accessibility standards
Multi-Persona User Flows
During a team meeting, a disagreement among different stakeholders helped me identify a critical misalignment in who our users were. To create shared alignment, I proactively:
Led a Proto-persona workshop with nine cross-functional stakeholders, delivering actionable primary and secondary personas with just 90 minutes of collaboration and two hours of synthesis.
Transformed these insights into strategic, user-centered journey flows, ensuring design decisions were rooted in empathy and aligned with business goals
Limitations - I knew that the personas would need more time and research to validate, but we were no longer blocked by misalignment. I had also identified 2 other personas but again with time constraints, I made a plan to return to the Persona research post-launch.
Brainstorm sessions
I rapidly mapped out user flows to visualize the end-to-end experience, then drove collaborative brainstorming and fast-paced iterations to ensure the concept was cohesive, scalable, and aligned across the system.
Design Systems for Speed, Consistency, and Accessibility
To streamline workflows and scale design efficiently:
I created WeVideo’s first scalable design system.
The system reflected WeVideo’s brand values while driving consistency across platforms.
Every component was built with accessibility in mind, meeting WCAG standards to support inclusive design and faster development handoff.
Usability Testing
I identified key friction points early, rapidly prototyped a solution, and tested with our Education Ambassadors.
Main takeaways
Users skipped key steps we thought were intuitive, highlighting where clearer guidance or design cues were needed.
While users said the feature was useful, testing showed they struggled to find or use it. This highlighted the need for better discoverability.
A minor copy change and a repositioned button reduced task completion time by 40%, showing how small UX shifts can have a major impact.
After design updates with clearer next-step navigation, there was a 30% increase in task success rate
Before
After
Final Design
Impact
Increased NPS score by +33
After just six months, WeVideo Classroom was launched and received enthusiastic feedback and strong engagement from the Education Ambassador community. The initiative was recognized by C-suite leadership as an “exemplary project” that set a new benchmark for future company-wide efforts.
A completely new codebase, enabling support for the latest technologies, performance enhancements, and future feature scalability.
I drove the creation of a fully accessible, brand-new design system, collaborating closely with Accessible360. Their audit confirmed the product met industry standards for inclusive design, establishing a new accessibility baseline at WeVideo.
Learnings & Problem-Solving
Faced with ambiguity and tight deadlines, we operated in a lean, fast-paced environment, prioritizing high-impact solutions to keep momentum without losing sight of long-term quality.
When time zone and communication challenges arose with our engineering team in Romania, I introduced video demo walkthroughs for developer handoffs and feasibility questions. This approach dramatically decreased friction and increased team alignment.
With a fixed timeline, we had to critically evaluate the scope of our selected user journeys. We made strategic compromises, choosing to launch a beta with select users to validate assumptions and minimize risk before the full launch.