Building a World-Class UX Organization at Alteryx

At Alteryx I built the UX team from 3 designers to a global multidisciplinary organization of 35 UX Designers, Product Designers, Researchers, Visual Designers, and UX Engineers. I also managed the Technical Writing team and helped set process and standards for product help documentation, in-product training content, and UI copy. Additionally, I managed the Telemetry & Insights team — a function that enabled UX and Product to make data-driven decisions and validate design assumptions with real behavioral evidence.

Through these teams I influenced decision-making across the company to drive meaningful improvements in product design, team process and structure, and overall product strategy.

Most UX organizations rely on research to understand what users say. I wanted Alteryx to also understand what users do — at scale, continuously, without scheduling a study. I created the Telemetry & Insights team specifically for this: a dedicated function within UX responsible for product instrumentation, behavioral analytics, and translating usage data into design and roadmap decisions.

This was genuinely unusual. Embedding a data analytics capability inside a design organization gave us a level of evidential confidence that most teams don't have access to. Design decisions weren't defended with intuition or anecdote — they were defended with data. Roadmap prioritization at the senior leadership level was regularly informed by what this team surfaced. It also changed the culture: when design brings data, the conversation changes.

One of the highest-leverage investments I led was a comprehensive redesign of Alteryx's trial and first-use experience. The telemetry data made the problem legible: too many users were hitting friction early, before they'd had a chance to experience the platform's value. The drop-off wasn't a product problem — it was an experience problem.

The redesign focused on reducing time-to-value, clearing the path from sign-up to meaningful first use, and building the kind of early confidence that converts trial users into advocates. The results were measurable: a 20% increase in trial-to-paid conversion and a 75% improvement in time-to-value.

I also led the Technical Writing team, which I repositioned as a product content function rather than a documentation function. The distinction matters: documentation lives outside the product; content design lives inside it. We established standards for in-product tooltips, empty states, error messaging, and onboarding tutorials — and integrated help documentation directly into product release cycles so that guidance was never an afterthought.