Gerard Mestres
2016-2026
I work across complex digital products, SaaS platforms, mobile applications and web experiences, often in projects where functional complexity needs to coexist with a strong and distinctive visual identity.
My work on products such as SiriusXM and NutreXS has involved designing extensive systems with multiple platforms, states, requirements and user needs.
001
Define
I start by understanding what the product needs to achieve, who it is for and the context in which it will be used. I look at the different user profiles involved, their needs and the problems the product needs to address, while also considering the business objectives behind it.
I analyse the existing landscape through competitor research, market positioning and relevant references to understand where the product sits and what opportunities exist to make it useful and distinctive.
From this, I define and prioritise the opportunities that will shape the product, bringing together user needs, business objectives and the context in which the product will operate.
The goal is to establish a clear foundation for the project, aligning product, design and stakeholders around what is being built and why.
002
Prioritise
Once the opportunities are defined, I translate them into the functionality and requirements needed to address them.
I work with the available resources and constraints to establish the scope of the product and prioritise what needs to be built first. Not every opportunity needs to become part of the initial product, so I distinguish between what is essential to achieve its objectives and what can be developed later.
This is where I define the MVP and the functionality that belongs within it, creating a clear direction for the product before moving into its structure and interface.
The result is a defined and prioritised scope that gives the design process a clear direction.
003
Structure
With the scope defined, I structure the product through information architecture.
I define its main areas, content hierarchy and the relationships between them, determining what belongs within each section and how the different levels of information are organised.
I then use this structure as the foundation for defining the different user flows. I map the paths users need to take to accomplish specific goals, including the decisions, alternative paths and states that need to be considered.
From there, I develop the wireframes to explore these structures through actual interfaces, identify structural issues and refine the experience before moving into visual design.
The aim is to establish a structure that makes the product understandable before deciding how it should look.
004
Design
Once the structure and flows are established, I develop the visual and interaction layer of the product.
This is where product design brings together the functional structure defined in the previous phases with the visual identity of the product.
I work across UX writing, visual direction, high-fidelity interface design and interactive prototyping, translating the product’s requirements into a coherent experience. The goal is to create an interface where clarity, usability and visual identity reinforce each other rather than compete.
I build the interface in Figma as a scalable system, using auto-layout, constraints, components, variants, styles, variables and tokens to create consistent patterns that can adapt across different screens, platforms and use cases. I design with implementation in mind, considering how components, layouts and interactions will translate into a working product and how they can be built consistently in development.
I also consider the states and behaviours required by each component and interaction, including responsive adaptations, empty and error states, loading states and other conditions that need to be represented in the final product.
005
Document
Once the design is defined, I document the information needed to take it into development. My focus is on the design handoff: making the intended behaviour, interactions, states and implementation details clear to the people building the product.
Depending on the project and the team involved, this can range from detailed component specifications and responsive behaviour to functional logic, interaction rules and specific edge cases that are not immediately visible from the screens themselves.
I use Figma as the main reference point, structuring components, styles, variables and tokens alongside the relevant specifications and notes. I also use AI to help structure and accelerate this documentation, particularly when a product involves a large number of screens, states or interdependent behaviours.
The level of documentation adapts to the needs of the project and the people involved, with the goal of making the transition from design to development as clear as possible.
006
Implement
∞
Collaborate
I collaborate with clients, product owners, developers and stakeholders throughout the entire process. Depending on the project and the team involved, I can work independently, take ownership of the design process or integrate into an existing product and design team.
I define and present the work, gather feedback and validate decisions as the project progresses. This means involving the people with the relevant knowledge at each stage, from product requirements and scope to information architecture, flows, visual design and implementation.
This continuous collaboration allows each phase to be validated as the project evolves, helping identify problems early, incorporate different perspectives and maintain a shared understanding of the product.