Yohann Kouma — Product Designer
Regulation, flow, and calculation impose their complexity.
Designing a product means choosing who carries it: the system, or the human.
Work
Case study 1 of 5
Rigor
Continuity
Discernment
Ground truth
Rigor means documenting failures and trusting the data: an untested assumption always ends up corrupting the business logic. That’s the prerequisite for continuity — a resilient product handles edge cases by default and protects the critical path, even as the system degrades. That robustness doesn’t get decreed in a PRD or in Figma — it demands discernment grounded in the field: when user research or analytics contradict the spec, usage wins, even if it means scrapping the iteration in progress. The goal was never to design happy paths. Every workaround a user invents is proof the product failed to absorb the cognitive load in their place.
About
Eleven years of product design in ecosystems where a mistake is expensive: insurtech, fintech, and health tech. Starting as a consultant on pricing and underwriting flows, my scope has steadily narrowed toward owning complex domains in-house — asset management, billing, regulatory compliance. The thread running through it is constant: absorbing business-rule complexity so the interface doesn’t have to. My territory is the invisible layer of the product, where financial flows meet the legal framework. The goal was never interface polish — it’s architectural robustness: structuring the system so it carries the weight of complexity instead of the user.
-
Doctolib
Product designer
-
Amundi
UX/UI designer
-
Axance
UX/UI Consultant
-
Gras Savoye/WTW
UX/UI Consultant