Product Mission
From UX execution to product design
The framework
4 years on a B2B SaaS product
4 years on a B2B SaaS document management product. Initially a UX designer role: translating needs into interfaces, handling user feedback, delivering mockups that match specs.
UX Design: solving visible problems
Improving the product from user feedback
The first years, the daily work: analyzing user feedback, identifying the real need behind the request, proposing solutions that fit within the constraints of a live product. No blank page, continuous improvement.
The turning point
When UX missions become product missions
The organization's needs evolved: purely UX missions were no longer enough. UX designer roles shifted toward product design missions, with a broader upstream scope. The title followed: it was no longer about designing screens, but framing topics, cross-referencing usage data by industry, and facilitating ideation sessions with architects and stakeholders.
Product Design: framing the right problems
Identifying the right problems before designing
For the past 5 months, the title has changed but the transition was already underway. The role is no longer about designing screens but about framing topics upstream: which problems to solve, for whom, in what order. Discovery, ideation, prioritization.
The Deezer and Leboncoin concepts were born from the same instinct as this evolution on the mission. The difference: here it's with the constraints of a live product (technical debt, compatibility, roadmap), there it's starting from a blank page.
Design System
Deploying a design system and ensuring its adoption