04Busuu
Public summary · Sensitive details withheld
Turning learner insight into shared product direction.
Product principles translated existing learner insight into a coherent direction, helping several teams move from vision towards delivery together.
- My role
- Lead Product Designer
- Industry
- Education technology
- Focus
- Product strategy, Vision to delivery
- Scope
- Global consumer learning experience
The short version
The case in three moves.
- Challenge
- Existing learner insight pointed to opportunities that individual product optimisations could not address in isolation.
- Leadership
- I translated the evidence into product principles and coordinated design across several teams to make the direction actionable.
- Outcome
- The principles created a shared language for prioritisation and helped teams bring a more coherent experience into delivery.
01 / Insight
Look beyond the next optimisation.
Existing research showed related points of friction across the learner journey. Progress could feel slow, lesson experiences needed more variety and learners had limited opportunities to practise with other people.
I translated that evidence into a small set of product principles. They connected learner needs to product choices and gave leadership a way to discuss the experience as a whole rather than treating each symptom separately.
02 / Strategy
Give the experience a structure and a point of view.
The direction brought together structured learning, tailored revision and opportunities to learn with others. Culture became the connecting idea, giving lessons, progress and celebration a more distinctive role within different learning journeys.
The principles were specific enough to guide prioritisation without becoming a fixed specification. Teams could use them to make coherent decisions while continuing to learn through delivery.
03 / Delivery
Move from a future concept to a coordinated first step.
Working with Brand, Product and Learning Design, I developed the concept into a prioritised first release. Several teams owned related parts of the journey, so design leadership needed to connect their decisions and make dependencies visible.
Regular design sessions surfaced opportunities to collaborate and protected consistency. Teams tested changes that could disrupt established learner behaviour, using the findings to refine the release before it reached customers.
04 / Learning
Use the release to evolve the vision.
The first release translated a broad direction into something teams could build, observe and improve. Early signals informed the next round of decisions, while live-product usability work helped test whether the longer-term vision still reflected real learner behaviour.
The important outcome was not a finished future-state concept. It was a shared direction that remained useful when teams encountered the constraints and evidence of delivery.