Design Leadership · Head of Design

Leading design across a global, remote-first portfolio, and proving it scales.

As Head of Design at Scalable Path, I set UX/UI strategy across many client products, built the systems that kept quality consistent, and grew a distributed team.

Years
2017 – 2023
Role
Head of Design
UX/UI strategy · systems · team
Company
Remote-first · global
San Francisco-based
The Problem

Consistent, high-quality design at scale, without a co-located team.

A remote-first company serving a wide range of client products needed design that held a high bar across many industries and time zones, with a distributed team and no shared room to do it in.

The Solution

Treat design as a system and a practice, not a series of one-offs.

Shared design systems, clear strategy per engagement, and a mentored team operating on common standards.

01
Design strategy per engagement
Aligned design work to each client’s business goals.
02
Scalable design systems
Consistency across products without reinventing each time.
03
Team mentorship
Grew a distributed team and raised the craft bar.
04
Embedded in agile
User-centered thinking woven into cross-functional workflows with PMs and engineers.
Background

Scalable Path placed designers and engineers into client work across a broad range of industries, all remote-first and global. As Head of Design I owned the design bar across that whole portfolio, setting strategy on individual engagements while building the systems and standards that kept quality consistent no matter who was on the project or what time zone they were in.

This was years before remote-first was the default, and the lessons map directly onto how the best AI-native teams operate now.

Research

I oversaw end-to-end research across engagements.

Interviews, surveys, usability tests, and synthesis that fed design decisions. The constant was making research portable, a way of understanding users that held up across very different products and a distributed team, rather than living in one person’s head.

The Approach

Leading design remotely, before it was the norm, meant systems and clear standards were the only way a distributed team could move fast without drifting apart.

Design Systems

The core of the role was systems. I built and implemented scalable design systems that let a distributed team produce consistent, high-quality work across many products without reinventing the basics each time. A system is what lets people who aren’t in the same room, or the same country, ship work that feels like it came from one team. That’s the discipline that makes remote design actually scale, and it’s exactly what a founding designer installs on day one.

Leadership

I mentored and grew a distributed team, raising the craft bar and building the shared standards that kept it there. The goal was a practice that didn’t depend on me being in the room: designers operating on common principles, giving each other feedback, and holding the line on quality across engagements. Leading remotely taught me that clear standards and good systems are what keep a distributed team moving fast without drifting apart.

Results

A working model for leading design remotely, before it was the norm.

I raised the design bar on every engagement and proved a working model for leading design remotely across time zones and industries, directly relevant to today’s remote-first, AI-native teams.

+ Optional
Add any real figures you’re comfortable with: team size grown, number of products or clients touched, tenure, or a client outcome.
Final Thoughts
What I learned
Leading design remotely, before it was the norm, taught me that systems and clear standards are what let a distributed team move fast without drifting apart.
Most proud of
Building a design practice that held a high bar across many products, and a team that didn’t need me in the room to keep it there.
Next project →
Odaptos
Like what you see?

Let’s build something together.

felipe@felipelebrun.com
© 2026 Felipe RestrepoLinkedIn ↗Behance ↗Remote · Colombia / France · EN · FR · ES