Norbert Kucsera
Back to Case Studies

Case Study

Spark School — E-learning Platform

A unified learning platform that replaced fragmented school workflows with one scalable product for students, teachers, and content creators.

01

Context

Spark School is an early-stage startup building a digital learning ecosystem for students, teachers, and content creators.

Before this project, schools relied on a fragmented setup of 4–5 different platforms to manage courses, grading, attendance, and communication. This created operational overhead, data inconsistency, and a poor user experience across all roles.

The goal was to consolidate these workflows into a single scalable platform that could support both current operations and future international expansion.

02

Role

I was the sole UX designer on the project, leading the process end-to-end — from design sprint facilitation and user research to flow definition, interface design, testing, and iteration.

I worked closely with product and engineering, maintaining strong ownership over UX decisions while balancing technical constraints to ensure feasible and high-quality implementation.

03

Problem

The initial brief focused on building a unified platform, but the deeper issue was fragmentation.

Users were forced to switch between multiple tools to complete basic tasks, leading to inefficient workflows for school staff, loss of data consistency across platforms, increased operational costs, and poor alignment with Spark School’s specific educational model.

Additionally, the system needed to support multiple user types — students, teachers, and content creators — each with different expectations and interactions. That made consistency and clarity critical.

04

Process

I ran a design sprint to align stakeholders and understand the real workflows behind the system.

  • Conducted user interviews with teachers and content creators.
  • Reviewed and mapped the 5 existing platforms to identify overlaps and gaps.
  • Reframed flows based on user logic rather than system structure.
  • Iteratively tested and refined interaction patterns across user roles.

A key insight was that workflows that initially seemed complex or abstract internally were actually intuitive for users, as long as they matched their mental models.

Another critical learning was designing across roles: every action created by one user type, such as a content creator, needed to translate clearly and predictably for others, including teachers and students.

05

Key Decisions

  • Consolidated multi-platform workflows into a single system to reduce friction and eliminate tool-switching across daily tasks.
  • Designed role-aware interactions so content and actions remained consistent and understandable between students, teachers, and content creators.
  • Prioritized simplicity over feature parity instead of recreating every feature from the existing platforms.
  • Focused on intuitive, efficient flows tailored to real usage rather than internal system structure.

06

Outcome

The platform significantly improved operational efficiency by centralizing all core workflows into one system.

  • Reduced dependency on multiple external tools, lowering costs.
  • Enabled smoother daily operations for school staff.
  • Delivered a simpler and more intuitive experience for students.

Within roughly 2 years, the platform scaled successfully:

  • 16 countries
  • 167 schools
  • 12,100 users
  • 49,307 assignments created
  • 19,140 course pages created

Beyond metrics, the product established a scalable foundation that allowed Spark School to expand internationally and evolve its learning ecosystem.