
PRODUCT DESIGNER
PRODUCT DESIGNER
WHAT IF
WE DIDN'T?
WHAT IF
WE DIDN'T?
I design complex enterprise products by questioning what needs to be there in the first place.




PRODUCT DESIGNER
WHAT IF
WE DIDN'T?
I design complex enterprise products by questioning what needs to be there in the first place.


SELECTED WORK
SELECTED WORK
SELECTED WORK
BNP Paribas
BNP Paribas
Ongoing
Ongoing
Complex banking configurations easier to understand and manage.
Complex banking configurations easier to understand and manage.
beFundr.
beFundr.
Pre-launch
Pre-launch
Crowdfunding experience connecting campaign creation, funding, and community governance.
Crowdfunding experience connecting campaign creation, funding, and community governance.
Cloud Storage
Cloud Storage
UX Research & Redesign
UX Research & Redesign
A redesign shaped by what users struggled to find, understand and complete.
A redesign shaped by what users struggled to find, understand and complete.
RFI Instrumental
RFI Instrumental
Live
Live
Clear navigation, consistent interactions, and responsive design.
Clear navigation, consistent interactions, and responsive design.
BNP Paribas
BNP Paribas
Complex banking configurations easier to understand and manage.
Ongoing
Ongoing
Cloud Storage
Cloud Storage
A redesign shaped by what users struggled to find and understand.
UX Research & Redesign
UX Research & Redesign
ABOUT
ABOUT
ABOUT
I MAKE COMPLICATED THINGS FEEL NATURAL
I MAKE COMPLICATED THINGS FEEL NATURAL
Psychology taught me to question behavior. Art direction taught me to question what we show. Product Design gave me a reason to question both.
My work involves navigating business rules, challenging requirements, and building reusable design systems. I collaborate closely with researchers, product teams, and developers to turn complex requirements into experiences people can understand and use.
Psychology taught me to question behavior. Art direction taught me to question what we show. Product Design gave me a reason to question both.
My work involves navigating business rules, challenging requirements, and building reusable design systems. I collaborate closely with researchers, product teams, and developers to turn complex requirements into experiences people can understand and use.
Psychology taught me to question behavior. Art direction taught me to question what we show. Product Design gave me a reason to question both.
My work involves navigating business rules, challenging requirements, and building reusable design systems. I collaborate closely with researchers, product teams, and developers to turn complex requirements into experiences people can understand and use.




A LITTLE PERSPECTIVE FROM THE OTHER SIDE
A LITTLE PERSPECTIVE FROM THE OTHER SIDE
A LITTLE PERSPECTIVE FROM THE OTHER SIDE
Bringing her screens to life was easy because she truly understands how to work as a team, and she always cares about how her designs translate into code.
Bringing her screens to life was easy because she truly understands how to work as a team, and she always cares about how her designs translate into code.
Bringing her screens to life was easy because she truly understands how to work as a team, and she always cares about how her designs translate into code.
Caick Andrade
Caick Andrade
Caick Andrade
Software Engineer, CROMG
Software Engineer, CROMG
Software Engineer, CROMG


MORE WORK
MORE WORK
MORE WORK
Different projects, different problems. Here’s what else I’ve been working on.
Different projects, different problems. Here’s what else I’ve been working on.
Different projects, different problems. Here’s what else I’ve been working on.
Award winner
AutoDAO

Case studies
More projects
AutoDAO
AutoDAO
Award winner
Award winner
A CLOSER LOOK
A CLOSER LOOK
A CLOSER LOOK
The decisions, constraints, and trade-offs behind two projects in more detail.
The decisions, constraints, and trade-offs behind two projects in more detail.
The decisions, constraints, and trade-offs behind two projects in more detail.
01/ BNP PARIBAS · ENTERPRISE BANKING
01/ BNP PARIBAS · ENTERPRISE BANKING
01/ BNP PARIBAS · ENTERPRISE BANKING
ONE CHANGE,
MULTIPLE CONSEQUENCES
ONE CHANGE,
MULTIPLE CONSEQUENCES
Systems thinking
Systems thinking
Systems thinking
Complex workflows
Complex workflows
Complex workflows
Business rules
Business rules
Business rules
Conceptual illustrations. No proprietary interfaces or client data shown. The design challenges and decisions described reflect my work.
Conceptual illustrations. No proprietary interfaces or client data shown. The design challenges and decisions described reflect my work.
Conceptual illustrations. No proprietary interfaces or client data shown. The design challenges and decisions described reflect my work.
ROLE
ROLE
ROLE
UX/UI Designer
UX/UI Designer
UX/UI Designer
STATUS
STATUS
STATUS
Ongoing project
Ongoing project
Ongoing project
FOCUS
FOCUS
FOCUS
Information architecture · Interaction design · Business rules
Information architecture · Interaction design · Business rules
Information architecture · Interaction design · Business rules
How do you make configuration manageable when every decision depends on what happens elsewhere?
How do you make configuration manageable when every decision depends on what happens elsewhere?
How do you make configuration manageable when every decision depends on what happens elsewhere?
Administrators manage payment methods across entities, sites and countries. What they can configure depends on eligibility rules, and a change can affect multiple sites. The challenge was to make those dependencies understandable without exposing users to unnecessary complexity.
Administrators manage payment methods across entities, sites and countries. What they can configure depends on eligibility rules, and a change can affect multiple sites. The challenge was to make those dependencies understandable without exposing users to unnecessary complexity.
Administrators manage payment methods across entities, sites and countries. What they can configure depends on eligibility rules, and a change can affect multiple sites. The challenge was to make those dependencies understandable without exposing users to unnecessary complexity.

Countries
Countries
Countries
Sites
Sites
Sites
Payment methods
Payment methods
Payment methods
Entity
Entity
Entity
THE SYSTEM
THE SYSTEM
A payment method isn't just a checkbox.
A payment method isn't just a checkbox.
A payment method isn't just a checkbox.
Which payment methods are available depends on the entity, its eligible sites and country-specific rules. Some methods may already be configured for only part of those sites. Administrators need to understand these existing states before making changes that affect the wider configuration.
Which payment methods are available depends on the entity, its eligible sites and country-specific rules. Some methods may already be configured for only part of those sites. Administrators need to understand these existing states before making changes that affect the wider configuration.
Which payment methods are available depends on the entity, its eligible sites and country-specific rules. Some methods may already be configured for only part of those sites. Administrators need to understand these existing states before making changes that affect the wider configuration.
Which methods are enabled?
Which methods are enabled?

Where can they be used?
Where can they be used?

Entity
Entity
Payment methods
Payment methods
Eligible sites
Eligible sites
Countries
Countries

What's already configured?
What's already configured?

What's available in each country?
What's available in each country?
Which methods are enabled?
Entity
Payment methods


Where can they be used? What's available there?
Eligible sites
Countries


THE DESIGN DECISION
THE DESIGN DECISION
THE DESIGN DECISION
Fewer steps. Clearer consequences.
Fewer steps. Clearer consequences.
Fewer steps. Clearer consequences.
An earlier version of the flow included a separate step for selecting sites. Once the business rules were clarified with Product, I revised the interaction flow to remove that unnecessary step and make the scope of each change explicit before confirmation.
An earlier version of the flow included a separate step for selecting sites. Once the business rules were clarified with Product, I revised the interaction flow to remove that unnecessary step and make the scope of each change explicit before confirmation.
An earlier version of the flow included a separate step for selecting sites. Once the business rules were clarified with Product, I revised the interaction flow to remove that unnecessary step and make the scope of each change explicit before confirmation.
EXPLORATION
EXPLORATION
EXPLORATION
Superseded
Superseded
Superseded
Select payment methods
Select payment methods
Select payment methods
Select eligible sites
Select eligible sites
Select eligible sites
Review changes
Review changes
Review changes
A site-selection step implied flexibility that the business rule didn't support.
A site-selection step implied flexibility that the business rule didn't support.
A site-selection step implied flexibility that the business rule didn't support.
REVISED DESIGN
REVISED DESIGN
REVISED DESIGN
Current direction
Current direction
Current direction
Configure payment methods
Configure payment methods
Configure payment methods
Explain that changes apply to all eligible sites
Explain that changes apply to all eligible sites
Explain that changes apply to all eligible sites
Review and confirm
Review and confirm
Review and confirm
Make the scope and consequences explicit
Make the scope and consequences explicit
Make the scope and consequences explicit
Site-selection is removed. The interface communicates the fixed scope instead of offering a choice.
Site-selection is removed. The interface communicates the fixed scope instead of offering a choice.
Site-selection is removed. The interface communicates the fixed scope instead of offering a choice.
Removing site selection made the flow shorter, but it also made the scope of each action more important to communicate. Rather than adding another configuration step, we kept that information within the flow so administrators could understand what would change before confirming.
Removing site selection made the flow shorter, but it also made the scope of each action more important to communicate. Rather than adding another configuration step, we kept that information within the flow so administrators could understand what would change before confirming.
Removing site selection made the flow shorter, but it also made the scope of each action more important to communicate. Rather than adding another configuration step, we kept that information within the flow so administrators could understand what would change before confirming.
DESIGN FOR REAL WORLD SCENARIOS
DESIGN FOR REAL WORLD SCENARIOS
DESIGN FOR REAL WORLD SCENARIOS
Existing states, different consequences.
Existing states, different consequences.
Existing states, different consequences.
A payment method may already be active for some eligible sites but not others. The interface needs to communicate that existing state without suggesting that administrators can select individual sites when making changes. It also needs to make the consequences clear before confirmation.
A payment method may already be active for some eligible sites but not others. The interface needs to communicate that existing state without suggesting that administrators can select individual sites when making changes. It also needs to make the consequences clear before confirmation.
A payment method may already be active for some eligible sites but not others. The interface needs to communicate that existing state without suggesting that administrators can select individual sites when making changes. It also needs to make the consequences clear before confirmation.
Understanding an existing configuration
Understanding an existing configuration
Understanding an existing configuration
A payment method may already be enabled for only some eligible sites. Showing that existing state helps administrators understand the starting point, while making it clear that any new change applies to all eligible sites.
A payment method may already be enabled for only some eligible sites. Showing that existing state helps administrators understand the starting point, while making it clear that any new change applies to all eligible sites.
A payment method may already be enabled for only some eligible sites. Showing that existing state helps administrators understand the starting point, while making it clear that any new change applies to all eligible sites.
SEPA Direct Debit
Partially enabled
Enabled for 2 of 4 eligible sites
Paris HQ, France
Lyon, France
Brussels, Belgium
Madrid, Spain
SEPA Direct Debit
SEPA Direct Debit
Partially enabled
Enabled for 2 of 4 eligible sites
Enabled for 2 of 4 eligible sites
Partially enabled
Paris HQ, France
Paris HQ, France
Enabled
Lyon, France
Lyon, France
Enabled
Brussels, Belgium
Brussels, Belgium
Disabled
Madrid, Spain
Madrid, Spain
Disabled
Before confirming a change
Before confirming a change
Before confirming a change
Before confirmation, administrators can review which eligible sites are affected by a change. The list provides visibility into the scope of the action, not a way to select individual sites.
Before confirmation, administrators can review which eligible sites are affected by a change. The list provides visibility into the scope of the action, not a way to select individual sites.
Before confirmation, administrators can review which eligible sites are affected by a change. The list provides visibility into the scope of the action, not a way to select individual sites.
Review changes
Review changes
Review changes
You're about to disable SEPA Direct Debit.
You're about to disable SEPA Direct Debit.
You're about to disable SEPA Direct Debit.
This change applies to all eligible sites.
This change applies to all eligible sites.
This change applies to all eligible sites.
Eligible sites
Eligible sites
Eligible sites
Paris HQ · Lyon · Brussels · Madrid
Paris HQ · Lyon · Brussels · Madrid
Paris HQ · Lyon · Brussels · Madrid
Cancel
Cancel
Cancel
Confirm
Confirm
Confirm
THE TAKEAWAY
THE TAKEAWAY
THE TAKEAWAY
THE GOAL WASN'T TO SIMPLIFY THE RULES.
IT WAS TO MAKE THEM MANAGEABLE.
THE GOAL WASN'T TO SIMPLIFY THE RULES.
IT WAS TO MAKE THEM MANAGEABLE.
THE GOAL WASN'T TO SIMPLIFY THE RULES. IT WAS TO MAKE THEM MANAGEABLE.
The business rules weren't ours to change, but the interaction flow was. By removing a choice the system couldn't support, we made the configuration more faithful to how it really works.
The business rules weren't ours to change, but the interaction flow was. By removing a choice the system couldn't support, we made the configuration more faithful to how it really works.
The business rules weren't ours to change, but the interaction flow was. By removing a choice the system couldn't support, we made the configuration more faithful to how it really works.
02/ FLEX ACADEMY
02/ FLEX ACADEMY
02/ FLEX ACADEMY
SAME PRODUCT,
DIFFERENT STARTING POINTS
SAME PRODUCT,
DIFFERENT STARTING POINTS
Product Strategy
Product Strategy
User journeys
User journeys
Conversion design
Conversion design
ROLE
ROLE
ROLE
Product Designer
Product Designer
Product Designer
TYPE
TYPE
TYPE
Design challenge
Design challenge
Design challenge
SCOPE
SCOPE
SCOPE
Homepage architecture · Forms & scheduling
Homepage architecture · Forms & scheduling
Homepage architecture · Forms & scheduling
How do you design one experience for people who aren't looking for the same thing?
How do you design one experience for people who aren't looking for the same thing?
How do you design one experience for people who aren't looking for the same thing?
Flex Academy helps people launch and grow short-term rental businesses through education and mentorship. With newcomers and experienced operators looking for different things, the challenge was to create two clear paths while giving priority to those just getting started.
Flex Academy helps people launch and grow short-term rental businesses through education and mentorship. With newcomers and experienced operators looking for different things, the challenge was to create two clear paths while giving priority to those just getting started.
Flex Academy helps people launch and grow short-term rental businesses through education and mentorship. With newcomers and experienced operators looking for different things, the challenge was to create two clear paths while giving priority to those just getting started.
Product strategy
User journeys
Conversion design



TWO AUDIENCES, ONE PRIORITY
TWO AUDIENCES, ONE PRIORITY
TWO AUDIENCES, ONE PRIORITY
Different goals = Different questions
Different goals = Different questions
Different goals = Different questions
I prioritized Launch as the primary journey, giving newcomers a clearer entry point while keeping Scale accessible for more experienced operators. That decision shaped the homepage hierarchy and the conversion paths for each audience.
I prioritized Launch as the primary journey, giving newcomers a clearer entry point while keeping Scale accessible for more experienced operators. That decision shaped the homepage hierarchy and the conversion paths for each audience.
I prioritized Launch as the primary journey, giving newcomers a clearer entry point while keeping Scale accessible for more experienced operators. That decision shaped the homepage hierarchy and the conversion paths for each audience.
Primary focus
Primary focus
Primary focus
LAUNCH
LAUNCH
LAUNCH
Preparing to start a business
Preparing to start a business
Preparing to start a business
Needs orientation and confidence
Explores what's possible
Looks for practical guidance
-> Next step: free webinar
-> Next step: free webinar
-> Next step: free webinar
Secondary path
Secondary path
Secondary path
SCALE
SCALE
Growing an existing business
Growing an existing business
Growing an existing business
Needs advanced, relevant content
Looks for strategic support
Wants expert guidance
-> Next step: strategy call
-> Next step: strategy call
-> Next step: strategy call
DIFFERENT JOURNEYS
DIFFERENT JOURNEYS
DIFFERENT JOURNEYS
Tailored paths from first visit to meaningful action.
Tailored paths from first visit to meaningful action.
Tailored paths from first visit to meaningful action.
For Launch, I kept registration short: the essentials needed to attend a free webinar. For Scale, I designed a qualification step before scheduling a strategy call, so the conversation could start with relevant context.
For Launch, I kept registration short: the essentials needed to attend a free webinar. For Scale, I designed a qualification step before scheduling a strategy call, so the conversation could start with relevant context.
For Launch, I kept registration short: the essentials needed to attend a free webinar. For Scale, I designed a qualification step before scheduling a strategy call, so the conversation could start with relevant context.
LAUNCH JOURNEY
LAUNCH JOURNEY
LAUNCH JOURNEY
Landing page
Landing page
Landing page
Value and orientation
Value and orientation
Value and orientation
Webinar registration
Webinar registration
Webinar registration
Simple form
Simple form
Simple form
Confirmation
Confirmation
Confirmation
Details + add to calendar
Details + add to calendar
Details + add to calendar






SCALE JOURNEY
SCALE JOURNEY
SCALE JOURNEY
Landing page
Landing page
Landing page
Relevant messaging
Relevant messaging
Relevant messaging
Qualification
Qualification
Qualification
A few key questions
A few key questions
A few key questions
Calendar
Calendar
Calendar
Choose a time
Choose a time
Choose a time
Confirmation
Confirmation
Confirmation
Details + next steps
Details + next steps
Details + next steps





THE TAKEAWAY
THE TAKEAWAY
THE TAKEAWAY
THE GOAL WASN'T TO GIVE EVERYONE THE SAME EXPERIENCE.
IT WAS TO GIVE EACH AUDIENCE THE RIGHT NEXT STEP.
THE GOAL WASN'T TO GIVE EVERYONE THE SAME EXPERIENCE. IT WAS TO GIVE EACH AUDIENCE THE RIGHT NEXT STEP.
THE GOAL WASN'T TO GIVE EVERYONE THE SAME EXPERIENCE. IT WAS TO GIVE EACH AUDIENCE THE RIGHT NEXT STEP.
The homepage established the priority. Each journey then offered a different next step: a low-commitment webinar for newcomers, and a more qualified conversation for experienced operators.
The homepage established the priority. Each journey then offered a different next step: a low-commitment webinar for newcomers, and a more qualified conversation for experienced operators.
The homepage established the priority. Each journey then offered a different next step: a low-commitment webinar for newcomers, and a more qualified conversation for experienced operators.
CONTACT
CONTACT
CONTACT
GOT SOMETHING WORTH QUESTIONING?
GOT SOMETHING WORTH QUESTIONING?
I'm always interested in complex problems and the people trying to solve them.
I'm always interested in complex problems and the people trying to solve them.
I'm always interested in complex problems and the people trying to solve them.
© 2026 Nathalia Andrade · Designed with intention. Questioned along the way.
© 2026 Nathalia Andrade · Designed with intention. Questioned along the way.
© 2026 Nathalia Andrade · Designed with intention. Questioned along the way.







