Product owner · UX and applied AI · Paris
From user research to working software.
I defined the scope, chose the approach, set the delivery order and agreed with the team how to validate the result, starting from user research and prototypes. My experience covers B2B and B2C products.
Background in product design, and an MSc in Applied Data Science and AI.
Selected work
Four projects, two or three decisions each
For each one: the problem, what I contributed, the decisions that mattered, and where the work stands. Screens come from my own prototypes. Where a client's material is confidential, the case stays at the level of the approach.
AI workflow · Managing AI features
An AI feature is not finished at launch
How I manage AI features: a delivery loop and a reliability loop planned from the start, seven decisions for every feature, eight conditions before launch, and the same rules applied to my own work.
Read the AI workflow →Method
How I work
Documents go out before the meeting. The meeting is for deciding.
Yexit kickoff briefEvery open decision leaves the room with an owner and a date. The value can come later.
Yexit decision logFailure states are in scope from the start: offline, interrupted, declined, empty, denied.
Yexit prototypesIn a small team, the user test runs every week and the backlog comes out of it.
MindiiDocumentation describes what the code does. If the help text and the code disagree, the text says so.
Stellantis user guidesTrade-offs are made explicit as quality, time, cost and confidentiality, and decided in that light.
YexitWorking with me
Three things to count on, with the evidence
Range
Audiovisual production, then UX and product design in B2B SaaS, then product ownership, then an MSc in applied AI. At Yexit the same person wrote the user flows, the acceptance criteria and the editorial half of the model prompt. I can read a spec, a Figma file and a Python module, and write all three.
Work
The two Stellantis extensions were built alone in six months, alongside the MSc thesis, and each has its own user guide. At Yexit, the specification and UX guide gave the developers the flows and acceptance criteria to build from.
Patience
The Yexit family tree went through ten rounds of screenshots and ended as written rules: each connector has one meaning, and a fixed order settles conflicts. At Mindii, a user test ran every week for months, and its findings set what the team fixed next.
Contact