Hi
Hi
Hi
quentin gillon
quentin gillon
quentin gillon
LEAD
product
designer
I design products to last,
and build them so they can evolve.
I design products to last,
and build them so they can evolve.
My four pillars
Over time, I’ve identified a few principles that guide me.
These four pillars sum up how I approach projects and teamwork.
1. Setting direction
I align design, product, and engineering around a shared goal
I step in and make the call when debates drag on and slow things down
I clarify the product direction when the vision is still blurry
I help teams grow and become more autonomous
2. Designing for engineering
I make design and engineering speak the same language
I surface constraints early
I make decisions and trade-offs explicit
I reduce back-and-forth and friction
3. Delivering over time
I shorten time to production
I keep quality stable over time
I make delivery reliable and predictable
I support growth without losing control
4. Owning complexity
I take on messy, sensitive, or less desirable topics
I clarify products with high business or functional complexity
I make critical but low-visibility tools usable
I never sacrifice usability for visuals — or the other way around
1. Setting direction
I align design, product, and engineering around a shared goal
I step in and make the call when debates drag on and slow things down
I clarify the product direction when the vision is still blurry
I help teams grow and become more autonomous
2. Designing for engineering
I make design and engineering speak the same language
I surface constraints early
I make decisions and trade-offs explicit
I reduce back-and-forth and friction
3. Delivering over time
I shorten time to production
I keep quality stable over time
I make delivery reliable and predictable
I support growth without losing control
4. Owning complexity
I take on messy, sensitive, or less desirable topics
I clarify products with high business or functional complexity
I make critical but low-visibility tools usable
I never sacrifice usability for visuals — or the other way around
1. Setting direction
I align design, product, and engineering around a shared goal
I step in and make the call when debates drag on and slow things down
I clarify the product direction when the vision is still blurry
I help teams grow and become more autonomous
2. Designing for engineering
I make design and engineering speak the same language
I surface constraints early
I make decisions and trade-offs explicit
I reduce back-and-forth and friction
3. Delivering over time
I shorten time to production
I keep quality stable over time
I make delivery reliable and predictable
I support growth without losing control
4. Owning complexity
I take on messy, sensitive, or less desirable topics
I clarify products with high business or functional complexity
I make critical but low-visibility tools usable
I never sacrifice usability for visuals — or the other way around
About
Hey! I’m Quentin — I’m a Lead Product Designer, mostly working on complex products, where clarity matters, structure is needed, and teams have to move forward together.
0
0
Aligned teams
0
0
Aligned teams
0
0
Aligned teams
0+
0+
Product projects
0+
0+
Product projects
0+
0+
Product projects
0+
0+
Years of experience
0+
0+
Years of experience
0+
0+
Years of experience
Call me:
Call me:
Call me:
Email :
Email :
Email :
featured case studies
These case studies are intentionally selected.
They reflect the systems, constraints, and decisions I typically work on at Lead / Senior level.
x0
x0
Front dev speed
x0
x0
Prototyping speed
x0
x0
New clients in 12 months
-0%
-0%
Navigation depth
0%
0%
Daily infra actions handled
x0
x0
Deployment frequency
FREQUENTLY ASKED QUESTIONS
I often get the same questions about my role, how I work, and how I collaborate with product and engineering teams.
Here are a few answers to give a better sense of how I approach projects.
1.
In which contexts are you most useful?
2.
How do you work with product and tech teams?
3.
How do you measure the impact of your work?
4.
What kind of environment do you work best in?
5.
What sets a Lead Product Designer apart from a Senior?
1.
In which contexts are you most useful?
2.
How do you work with product and tech teams?
3.
How do you measure the impact of your work?
4.
What kind of environment do you work best in?
5.
What sets a Lead Product Designer apart from a Senior?
1.
In which contexts are you most useful?
2.
How do you work with product and tech teams?
3.
How do you measure the impact of your work?
4.
What kind of environment do you work best in?
5.
What sets a Lead Product Designer apart from a Senior?
Hi
Hi
Hi
Let’s talk
If this resonates with your challenges or your context, we can talk about it. I enjoy discussing products and teams — especially when things get a bit complex.