06Global
A shared discovery process for better decisions and releases.
A practical framework that clarified ownership, strengthened cross-functional collaboration and moved stakeholder input earlier.
- My role
- Lead Product Designer
- Industry
- Media & entertainment
- Focus
- Product discovery, Ways of working
- Scope
- Cross-functional product teams across Global Player
The short version
The case in three moves.
- Challenge
- Slow delivery still produced missed details, unclear ownership and solutions that reached stakeholders too late to be properly validated.
- Leadership
- I adapted a framework developed at Busuu, embedded it in Miro and Notion, and refined it with the teams using it.
- Outcome
- Teams reported clearer ownership, stronger collaboration, smoother handovers and more polished releases; adoption continued iteratively rather than through a forced big-bang change.
01 / Diagnosis
Slow did not mean considered.
Early releases and retrospectives exposed the same pattern: important details were missed, disciplines worked with limited collaboration, ownership was unclear and stakeholders saw solutions too late.
The underlying problem was not a lack of effort. Teams needed a shared structure for the work, the decisions and the moments where other perspectives should enter.
02 / Framework
Adapt the process to the organisation using it.
I brought in a discovery framework first developed at Busuu and worked with Global stakeholders to fit it around existing workflows. A flexible Miro template made the stages and tasks visible.
Usage exposed gaps, so the framework gained clearer roles, recommended tools and methods, and realistic expectations for time and collaboration. Notion task templates later translated the model into each designer’s day-to-day responsibilities.
03 / Adoption
Let useful behaviour create momentum.
Early adopters demonstrated the value to other teams. Rather than demand instant compliance, people could begin with the parts that solved their immediate problems and expand from there.
Feedback and observation continued to shape the templates. That flexibility helped the process become a team-owned foundation instead of another static document.
04 / Impact
Better alignment showed up in the releases.
Teams described clearer task ownership, closer cross-functional work and fewer handover bottlenecks. Stakeholders became involved early enough to challenge and validate direction, and releases became more polished and thoughtful.
The framework also gave design leadership better visibility of progress and the right moments to coach or unblock work.
