Internal products & AI · Yeita
SKU PROJ-007 · Colorway: AI
My current role at Yeita: building products for employees, and exploring AI topics, notably by running the AI community. Status: ongoing.
Product builder · AI × UX · Yeita
You show up with a fuzzy problem, you leave with a usable product: framed, prototyped, tested. AI when it actually helps.
SKU PROJ-007 · Colorway: AI
My current role at Yeita: building products for employees, and exploring AI topics, notably by running the AI community. Status: ongoing.
SKU PROJ-001 · Colorway: Circular economy
A product team aligned through design and data: 2 days saved per release, feedback loops shortened by a full week.
SKU PROJ-002 · Colorway: Circular economy
Declaration and validation journeys redesigned: 10 minutes saved per declaration, 30 on internal validation.
SKU PROJ-003 · Colorway: E-mobility
First designer to work with Gireve: foundations laid (stakeholders, design system), then handed over for a 12-month mission.
SKU PROJ-004 · Colorway: Research
The design system behind the digital twin (machine learning applied to supply chains): foundations adopted down to novice profiles.
SKU PROJ-005 · Colorway: Insurance
The KYC reform on Secur'Axa: validation time halved thanks to OCR, for 10 million client records.
SKU PROJ-006 · Colorway: Banking
Three years of Open Banking: the Stellar design system rolled out to a dozen products, APIs for 5 international entities.
SKU PROJ-008 · Colorway: TBD
The next drop could be yours. A fuzzy problem is enough to get started: 15 minutes to talk it through.
Book a call ↗They trusted me
Design, product, data: the work happens at the intersection of all three, with one simple compass, the business and its users. Consultant at Yeita, where I also run the AI community.
Five years of product work in demanding environments: banking with BNP Paribas, insurance with AXA, research with CEA, e-mobility with Gireve, circular economy with Citeo. The more complex the industry, the more value there is to create.
The difference is made in dialogue. Marketing, PM, dev, data: these teams often ignore each other. When they understand each other, products ship faster and aim truer. That bridge is what I bring.
Not everything works. Here's what failed and what I took from it. The most useful part of this site.
On a new assignment, I calibrated my discovery on decision-makers. The real users were in the sales teams.
Since then: stakeholder mapping on day one, insights at the source. Every time.
Remote developers rebuilding my designs under different names. Double work, invisible in the rituals.
Since then: components named like the code, Storybook as the shared language. A design system is a contract, not a library.
The same trade-offs re-explained team by team, sprints lost re-validating settled decisions.
Since then: every decision documented, every team able to raise a flag early. Writing is a speed tool, not bureaucracy.
Want the full version of my limits?
Read the anti-CV →What I write, or where I show up.
I'm a consultant at Yeita. Let's talk, that's what the Calendly is for.
No. Prototyping, speccing, testing: yes. Production code is the developers' craft, and respecting it means not pretending.
As few as possible. A clickable prototype says more than a 40-page deck.
A tool, not a religion. It goes into the product when it solves a real usage problem. Otherwise, that gets said.
With an AI, openly: I build products with it, so I might as well build mine that way. Details on the Under the hood page.
A project, a question, an idea to challenge: write to me, I reply.
* Just kidding, I'm better organized than that.
You made it to the very bottom. Respect. One thing nobody guesses here: I know Bad Bunny's Baile Inolvidable by heart. Yes, all of it.