Usage Data
- Understand when usage drops occur.
- Understand the correlation between campaigns and app usage.
Creating a continuous learning experience beyond campaigns.

Sparted is a mobile Learning Experience Platform for corporate training, built around gamified micro-learning campaigns: around 3 minutes a day for 5 to 10 days. Outside these periods, no other activities were available.
Activity analysis across all client platforms to compare usage during and between campaigns.
Mixpanel data analysis across all client platforms showed that the app was barely used between campaigns
I used this project to introduce user research at Sparted. The goal was to go beyond usage data and better understand the constraints, motivations and barriers affecting the two profiles at the heart of the experience.
Frontline staff — salespeople, technicians and workers — are often too busy to devote much time to learning.
Some players feel they do not have enough information before answering campaign questions.
Incorrect answers lead to a low ranking, which can in turn reduce the motivation to continue.
Micro-learning sits alongside many other activities. Content creation is one task among many and rarely their priority.
They need simple tools, do little configuration and rely heavily on support when the tool becomes complex.
The idea: offer a format very different from campaigns, always available, with no time limit, scoring or leaderboard.
A library of short content that players can consult to find information and review topics before campaigns.
Bring bite-sized knowledge together in recognisable, always-accessible learning paths to deliver ongoing value between campaigns.
Let players revisit topics, reinforce their knowledge and feel better prepared for future campaigns.
Quick, familiar browsing designed for frontline constraints and micro-learning.
The first exploration brought editing as close as possible to the final output: a strong “what you see is what you get” approach. With the Product Manager and Engineering team, we weighed this ambition against development complexity and the capacity of a small tech team. We reduced the scope to deliver a simpler first version while preserving the essential principles of creating a course.


Together with the Engineering team, we prioritised reusing existing components to reduce development effort, avoid duplication and maintain a consistent experience. Where needed, we adapted them to the new use case. We created new components only when an adaptation would have changed their original behaviour too much.
Customisable icon
New states: Loading and Locked.
Creating a course remained time-consuming for teams whose main job was not content production. We therefore developed native generative AI: creators describe their needs in a prompt, receive a structured first draft, then iterate with AI to refine it.

Comparison of average activity rates across two observed periods.
10 Courses created · 116 Courses started · 930 bite-sized knowledge items read
Videos, images and creation assistance enable new use cases.