Enrico Galati

UX/UI Designer

Technology becomes simple when you start from people.

How I work

I do the research and the design myself: what I learn from interviews and tests becomes the interface, and only what the data confirms stays.

Naplesopen to roles across EuropeItalian native, English C1/C2

CV (PDF)

Work

IUCLIDTripLoopAlidays for Creators

See the work

PathOpen

ECHA, Helsinki — Product Management2026
POLI.design — UX and UI Design2025
Suor Orsola — Psychology, cognitive ergonomics, 110/110 cum laude2024
Re:Lab — Interaction Engineering, automotive HMI2023

Contact

enrico.galati96@gmail.com LinkedIn

Work 01 · ECHA / IUCLID

ECHA, Helsinki · March–August 2026

IUCLID

I planned and ran the consultation with the people who use IUCLID: six months, from the questions to the findings.

IUCLID is the database the European Chemicals Agency uses for regulatory dossiers. Version 6 brought it to a maturity where real improvements can be built on top, and that is where the consultation comes from: finding where it can grow, starting from the work people actually do. On the other side of the table were national authorities, industry, technical experts, EU and OECD partners and ECHA’s own staff. Remote interviews, in English, from twenty minutes to an hour.

RoleTrainee, Product Management

TeamUnit H1, IUCLID team

MethodSurvey, semi-structured interviews

ConstraintsUnder NDA

154survey responses

29interviews

6stakeholder types

The survey and the interviews were both needed.

People answer a questionnaire one way and describe their own work another way. The questionnaire measures where IUCLID stands today, the interviews bring out what is missing for the people who open it every morning. The survey ran on EU Survey. I wrote the interview guide, the questionnaire and the supporting material.

I anonymised every interview by hand, one at a time.

Transcripts from Teams, manual anonymisation for GDPR, then content analysis and thematic analysis. AI proposed the patterns, I checked them against the transcripts: on anonymised data only, and never through a platform without consent. In Power BI I built a star schema that cross-references the survey figures with the ones drawn from the interviews. Before ECHA I had never opened Power BI.

The hardest part was the calendar.

Every interview needed a colleague alongside me for the technical questions I could not answer, and their diaries changed the plan every week. The second difficulty was running the interviews naturally. At first they were not. I learned to handle both one-to-one and group sessions.

A job planned until the end of October, finished by the end of August.

This was not part of my research. 24 languages, over 500 phrases each to reformat by hand into a template. I proposed handing them to AI: one day tuning the prompt, 83% accuracy, three days of human correction. The AI could not write a slash, so I used XQX as a placeholder, a sequence that does not exist in any of the 24 languages.

The findings come out in the official report and will guide IUCLID’s development.

I presented the work to the team and it landed well. On the content of the research, until publication, I cannot say more.

“He successfully planned and managed this complex project, engaging with a wide range of stakeholders.”

Mark Roberts, Regulatory Officer, ECHA · my team leader

Next project

TripLoopOpen

Work 02 · TripLoop

POLI.design × Alidays · May–June 2025

TripLoop

UI for a business-travel platform: bookings, budget, transport and disruptions in one place. We designed it like a station.

Another group on the master’s course had designed the UX, again on an Alidays brief, so the research was not ours. The three of us designed the interface. Alidays and the tutors rated the work well.

RoleUI design

I handledColour, ticket card, micro-animations

ReferenceSwiss Style, the Swiss metro

Four services, four colours.

Train#4A90E2

Plane#F5A623

Hotel#70C216

Events#7E00AA

The four colours come from the Swiss metro. Swiss Style uses bright tones you can read from a distance, which is what a station needs: knowing where to go without stopping to read. They do the same job here, the colour arrives before the label. Manrope across the whole interface.

The only card drawn from scratch is a ticket. Whole for the trips ahead, torn for the archived ones.

Group outdoor activityTenerife, Canary Islands, Spain9–14 April52 participants

ongoing

Whole: trip ongoing.

Business trip 9–14 April 2025 Milan 6 people

Torn: trip archived.

The trip’s status sits in the shape of the object, so you neither remember it nor read it. Tearing is a gesture the user knows from the physical world. And a work trip is often team bonding too: the stub left in a pocket says that trip happened. Building it taught me Figma features I had not used.

Hover a service and it fills with its colour.

I handled the prototype’s micro-animations. Short, tied to the transport colour code, and built to recall a metro line: the button opens the way a route extends.

TripLoop dashboard with smart booking, trips in progress, notifications and calendar — 01The dashboard: quick booking by service, trips in progress, alerts on strikes and delays.

List of trips in progress with whole tickets, and of archived trips — 02Trips in progress and archived, with whole and torn tickets.

Detail of the trip to Naples with participants, budget and transport — 03The detail: participants, budget by service, transport.

Travel documents and the day’s timeline — 04Documents and timeline: every leg in its own colour.

Trip budget with costs and approvals per service — 05Budget: costs and CFO approvals for each service.

One user, no changes.

Gaze path over the dashboard during the eye-tracking test

Gaze path from booking to trips in progress

Eye-tracking test with one person. The equipment belonged to the course; I gave the tasks and asked the questions. We had predicted a precise order: the black new-experience button first, then quick booking by service, then the trips in progress and the past ones. The gaze followed that order, so we changed nothing. In my thesis I had designed a protocol around that same instrument, so I knew what to measure.

Next project

Alidays for CreatorsOpen

Work 03 · Alidays for Creators

POLI.design × Alidays · March–April 2025

Alidays
for Creators

A platform where travel creators pitch trips to Alidays and their followers book them.

A real brief from the tour operator partnered with the course. Collaborative work, everyone on everything; I led the research: netnography, participant sourcing, interviews.

RoleUX designer and UX researcher

Team4 UX/UI designers, 1 graphic designer

MethodNetnography, interviews, usability testing

95%of travel influencers have fewer than 100k followers

35%of consumers look for travel ideas on social media

60%use Instagram as their main channel

I was wrong.

I thought a tour operator and a travel creator had nothing in common. Netnography and interviews said otherwise, and I found the common ground in reviews: for anyone who lives off an audience, perception is worth as much as the product. The creator cannot afford to recommend a bad trip, Alidays lives on trips people remember. They sell the same thing, the credibility of whoever promises it will be memorable.

“We are at the mercy of the algorithm.”

The creator loses reach without posting constantly, and does not know the rules the algorithm rewards them by. Brands often pay in products, sometimes at ninety days. Travelling alone, they organise everything themselves. The platform gives them a scheduled collaboration, with dates and fees agreed before departure.

Silvia

30–35. She has a main job, travel blogging is the second one. Built as a course exercise, she stayed at the centre of the project.

“I’d like to focus on the quality of the content, but without consistency the algorithm cuts me out.”

Wants

Authentic, local destinations
Growing the community with real advice
Getting better at photo and video

Held back by

The algorithm, unless she posts constantly
Collaborations paid in products
The logistics of travelling alone

The creator proposes, then builds.

Two routes were open: a running conversation with an Alidays contact, or a proposal that travels on its own. We chose the second. The creator uploads the trip, an Alidays employee reviews it asynchronously, and the document changes many times before approval. Then the creator leaves on a trial trip, checks that it holds up, and only then does the package go on sale.

Why it pays for both.

Alidays gets packages it would not have built alone, and the creator’s followers booking them. The creator gets a pilot trip, covered in full or in part depending on the contract, and the content to publish on the way back.

We took the patterns from Notion, Airbnb and WeRoad.

Silvia comes to the product with deadlines and content to produce. Every new pattern she has to learn is time taken from her work, so we used patterns she already knows. WeRoad for the group trip, Airbnb for the stay, Notion for a document that keeps changing.