Jae Yoon

Based in Snohomish, WA

Product design.
Global leadership.
Hands-on craft.

I lead a global organization spanning design, research, analytics, and technical writing, drawing on twenty years of experience in enterprise B2B software.

Emailjaeyoon@me.com Phone702.292.7790 SocialLinkedIn

Organization design & leadership

Building a Global Team

Integrating a global team at Lytx across design, research, analytics, and technical writing, with shared practices that support collaboration and growth.

My work connects people across the US, India, and Israel through hiring, mentorship, shared research practices, and working software as the prototyping standard.

Team growth
3 → 15+
Global organization
US / India / Israel
Current role
Sr. Director
Product Experience & Insights

01 / Global team

Integrating teams across locations.

I hired every current designer on the team and grew the organization from 3 to 15+ across the US, India, and Israel. Shared ownership, clear expectations, and common practices supported integration across locations.

I established the Bangalore team in person and connected it to the wider organization through hiring, mentorship, and critique practices that supported the growing global team.

Hiring
Build the team around product judgment, craft, and collaboration.
Development
Support designers through mentorship and critique.
Global practice
Make ownership and expectations explicit across locations.
Team members gathered around a table at an outdoor restaurant.
View team photo
Earlier organization structure Historical artifact

This earlier map shows how design worked across product and engineering groups. It documents a previous structure; the current team scope is summarized above.

Historical Lytx product development map showing design, product, scrum, and engineering roles across product groups.

Earlier product-development organization map.

View full-size organization map

02 / Hiring

Make the hiring bar explicit.

I built a structured approach to evaluating designers. The scorecard makes the discussion specific: how a candidate understands the user, frames the problem, develops a solution, and responds to questions.

Design judgment
Connect the business case to an end-to-end user journey.
User empathy
Explain how a person would use the system and where difficulties arise.
Communication
Present a clear rationale and respond constructively to feedback.

The scorecard and exercise shown here are examples from my earlier hiring process.

View the interview exercise ↗
UX presentation scorecard with rating criteria for design thinking, user empathy, presentation, and communication.

A shared scorecard for evaluating design thinking and communication.

Read the full scorecard

03 / Team practices

Connecting people through shared practices.

The handbook gave the global team a shared reference for product coverage, roles, and expectations. Onboarding guides helped new designers join the team with a common understanding of its processes and context.

Recorded walkthroughs and asynchronous communication connected work across locations. Alongside mentorship and critique, these materials helped integrate new colleagues into the team’s day-to-day practice.

Ownership
Document who covers each product area and what each role contributes.
Onboarding
Give new designers a structured introduction to the organization.
Shared practice
Keep research guidance, design standards, and team knowledge accessible.
Historical UX handbook showing a product ownership matrix and written responsibilities for product and visual designers.

The earlier handbook paired product ownership with explicit role expectations.

Read the handbook example
How new designers joined the team Onboarding example
Onboarding presentation with a Welcome to the team opening slide.

An onboarding guide from the earlier team practice.

View the onboarding example

04 / Research

Bring customer context into product decisions.

My research practice combined direct observation, usability testing, and a shared repository. Fieldwork provided context for how customers operated; the repository organized findings so product partners could revisit the evidence behind design decisions.

These earlier artifacts show the shared research foundation that preceded the broader Product Experience & Insights organization.

People observing a fleet operations workstation with six monitors.

Field observation in a customer’s operating environment.

View field research photo
Dovetail repository with research projects covering safety, coaching, self-service insights, and DVIR.

Research organized by product area and customer problem.

Explore the repository example

UX artifacts / Supporting work

Directing the work across product areas.

I directed the development of personas and end-to-end workflow maps across safety, fleet operations, compliance, and installation. I guided the team’s work and personally created selected artifacts. The collection covers both customer roles and the operational handoffs around the software.

Compliance manager: Daily auditing work, unassigned driving, reporting, and support for drivers.

Persona

Compliance manager

A role-specific view of auditing, reporting, and driver support extends the research coverage beyond the primary coach and fleet manager.

From order to installation: Company onboarding, fulfillment, shipment, installation, and device management, alongside open questions and UI explorations.

Service journey · March 2023

From order to installation

The service journey connects account setup, shipping, installation, and device management. Open questions and interface explorations make dependencies across roles visible.

05 / Integration

Bringing four disciplines together.

I led the enterprise migration from Amplitude and WalkMe, owning vendor evaluation and the selection of Pendo. Through that transition, Data Analytics and Technical Writing came under my leadership.

Integrating these functions brought four disciplines into one organization. Product design and customer research now sit alongside behavioral analytics and the information customers use to understand the product.

Design
Product strategy, interaction design, and prototyping.
Research
Customer context, user needs, and evaluation.
Analytics
Product behavior and adoption insights.
Technical writing
Product documentation and customer understanding.

06 / Practice today

Set working software as the standard.

I established near-working software as the team’s prototyping standard, moving beyond static handoffs. That approach is influencing how Design, Product Management, and Engineering build together.

My own hands-on product work demonstrates the interaction detail this approach makes possible. I am also implementing an enterprise AI toolchain across design, research, analytics, and technical writing while maintaining ongoing delivery commitments.

Related platform workNext-generation Lytx UI ↗