Portrait of Leonardo Bressan on a balcony in New York

Product UX/UI Designer & AI builder

I design human insight into business impact.

Hi, I'm Leonardo, a product designer with 5 years of experience between Italy and New York. I work where user needs meet business goals: I turn complex, data-heavy problems into clear products, stay in the build from Figma to shipped front-end, and measure whether the numbers move.

Selected work About me

(01) Selected work

Products I've shaped, end to end.

01UX/UI Mobile App

Ares

An electrotherapy companion that guides people through electrode placement and treatment choice, built for older and non-technical users.

−47%setup time, from about 5 minutes

View case study

02Medical tech

I-Tech

One compact touch screen connecting the compression boots and the control unit, designed for patients at home and practitioners in clinics, to IEC 62366.

+32%patients using the device correctly, start to finish

View case study

03AI/ML platform

Clyra

An AI platform that links datasets without shared keys, fills missing values, evaluates models and publishes them as APIs, so teams ship models without a data-engineering bottleneck.

−85%time from raw data to a live API, from 2–4 months to about 2 weeks

View case study

04In-house software UX/UI

Aston Martin

Designed Masters Console, the platform that ran Masters in Conversation at Q New York, and the event around it, for the launch of 007: Road to a Million.

1M+campaign impressions across partner channels

View case study

05UX/UI Mobile & desktop app

Arvic

An AI-native platform that predicts injury risk. I turned dense training, load and recovery data into a daily decision tool across iOS, Android and web.

50%+daily active usage in a 150+ athlete pilot

View case study

06UX/UI Mobile App

TripUp

From brief to a working prototype in four days for a multi-billion-dollar company: deciding, splitting and settling group travel in one flow.

4 daysfrom brief to a working, deployed prototype

View case study

Ares

(02) How I think

I'm a product designer who sits where user needs and business goals meet. Across health, fintech, automotive and AI, I've learned that the best interface is the one that makes a hard decision feel obvious, and that a good design is only finished when it ships and the numbers move.

01
People before pixels
Every product starts with one question: what does this person actually need? Screens come after.
02
Outcomes over output
I design toward a metric the business cares about, and I measure whether we moved it.
03
Stay in the build
I prototype in real code with AI tools, so there's no gap between the idea and the working product.

(03) Interaction patterns

Interaction patterns.

Small interaction decisions. Better product experiences.

A · Everything at once
Injury dashboard
Injury risk23%
HRV58 ms
Resting HR52 bpm
Sleep7h 42m
Training loadHigh
SorenessCalves
Six numbers compete; none says what to do today.
B · Progressive disclosure
Low risk
−5 pts vs yesterday
Today
Keep the intensity, trim the volume by 10%.
What's driving it?
Achilles15%Optimal
Shin splint43%Moderate
Training load HighSleep 7h 42m
Next 7 days
13141516171819
B · Progressive disclosure
Low risk
−5 pts vs yesterday
Today
Keep the intensity, trim the volume by 10%.
What's driving it?
Achilles15%Optimal
Shin splint43%Moderate
Training load HighSleep 7h 42m
Next 7 days
13141516171819
01Arvic
Progressive Disclosure
Challenge
Athletes make one decision every morning, but wearables hand them dozens of numbers.
Why this pattern
The risk and today's advice come first; what drives it is one tap away, so the screen stays calm without hiding the evidence.
Instead of
A dashboard with every metric at once: athletes need one decision, not twenty numbers.
Also in
- Arvic desktop the whole squad first, then one athlete in depth
- Aston Martin one data set, each role sees only its own items
See it in Arvic
1. 1Connect
2. 2Body area
3. 3Placement
4. 4Session
02Ares
Guided Flow
Challenge
Older and non-technical patients run electrotherapy at home, alone, with no one to ask.
Why this pattern
One clear action at a time, where, then how, then how much, so each step asks only for what it needs.
Instead of
A control panel with every setting on one screen, the way hardware remotes work.
Also in
- TripUp add an expense: scan the receipt, then split it item by item
See it in Ares
1. 1Primary: what the device is doing
2. 2Supporting: time left, cycle phase
3. 3Action: one large pause
03I-Tech
Information Hierarchy
Challenge
Practitioners read the screen from across the room; patients use it alone the first time.
Why this pattern
What the device is doing gets the most space, time stays in view, and pause is the one large control.
Instead of
Every value at the same weight, which forces a close read from across the room.
Also in
- Arvic one large ring with the verdict, the detail below it
- Ares the session dial: intensity at the centre, pause and stop beside it
See it in I-Tech
Settle up3 open2 open
Your payment
JoYou → Jo€178.00PayPaid ✓
Group plan
JoMia → Jo€409.77
JoNic → Jo€93.46
Paid · the plan updates for everyone
1. 1Action
2. 2Response
3. 3New state
04TripUp
System Feedback
Challenge
Money in a group creates doubt: did my payment go through, and what is still owed?
Why this pattern
Each payment confirms on the spot and redraws the plan for everyone, so nobody pays a stale amount.
Instead of
A silent update that leaves the group asking in the chat who has paid.
Also in
- I-Tech a warning stops the session and says what to check
See it in TripUp

(04) Collaborations

Brands, startups and teams I've designed with, across Italy and New York.

(05) Impact

Design that moves numbers.

−0%

Less time to set up a session, from about 5 minutes

Ares · Medical device

0%+

Daily active usage during the pilot

Arvic · AI health platform

+0%

Patients using the device correctly, from connecting the boots to the treatment

I-Tech · Medical device

0M+

Campaign impressions across partner channels

Aston Martin · Brand platform

(06) Method

Business first. People always.

An entrepreneurial, proactive mind: I always look for how to do it better, and where to innovate.

Good product design is a bet on value. I make that bet explicit, so every screen traces back to a user need and a business outcome.

Business Revenue, retention, cost to serve. Which number has to move?
People The human being at the centre of everything. I get to know the people who will use the product before designing for them.
Technology Data, constraints, effort. What can we ship and learn from soon?

From bet to measurable outcome

01
Frame the bet
“What outcome moves the business?”
Before any pixel, I align with stakeholders on the goal, the metric that proves it and the constraints we can't ignore. A clear bet turns opinions into decisions.
- Problem statement
- North-star KPI
02
Understand people
“What do users actually need?”
Interviews, analytics and competitive scans show where the real friction is. I map jobs-to-be-done so the team designs for behaviour, not assumptions.
- Research insights
- JTBD map
03
Prioritise for impact
“Where is the biggest win for the least effort?”
With PM and engineering I size opportunities by impact and effort, then cut the MVP to the smallest thing that can prove the bet.
- Impact/effort matrix
- MVP scope
04
Design & build
“How fast can we learn from something real?”
Flows and systems in Figma, design tokens generated from the file with AI and checked against the code, then a working front-end with Claude Code. Real prototypes give real feedback, and engineering gets an unambiguous handoff.
- Design system
- Design tokens
- Coded prototype
05
Ship & measure
“Did it work, and what's next?”
Usability tests, pilots and KPIs close the loop. What we learn feeds the next bet, so the product compounds instead of drifting.
- Usability results
- KPI dashboard

(07) Beyond the handoff

Designed in Figma. Shipped in code.

AI is part of my workflow from start to finish. I take my own designs to a working front-end, so teams test real products with real users, and engineering gets something unambiguous to build on.

TripUp.fig: Home

iPhone 15 · Home

TripCard · 360 × 489

▾ TripCard
· Image / Lisbon
· Title
· Glass / Summary
· Button / Primary

TripCard.tsx

<TripCard
  city="Lisbon"
  dates="19 – 24 Aug"
  spent={1847.30}
  friends={4}
  onOpen={diveIn}
/>

// tokens straight from Figma
--radius-card: 28px;
--glass-blur: 24px;
--brand-teal: #12b3a3;

(08) About

Curious by default.

I'm never quite done with a product. I keep looking for the better way: a new pattern, a new tool, a new business model, tested with real people and shipped when it works.

More about me

(08) Contact

Let's build something people use and businesses need.

bressanleonardo@hotmail.com

I design human insight into business impact.

Products I've shaped, end to end.

Ares