← All work

Branch · 2025 to 2026

From design function to product experience organization.

Evolving a design-centered team into a multi-disciplinary product organization spanning design, content, documentation, research, product education, customer community, and AI-enabled experience quality. Six pillars. One North Star. A measurable maturity model.

NORTH STAR 01 DESIGN 02 CONTENT 03 DOCS 04 RESEARCH 05 COMMUNITY 06 AI ONE NORTH STAR

Role

Sr. Director, Product Experience

Duration

Multi-quarter

Team

~15-person org scope

Outcome

Operating model adopted

The North Star

Make the product easier to understand, easier to adopt, and harder to leave.

Customer-centric. Business-relevant. Not design-centric. This framing was the unlock. It connects directly to usability, adoption, retention, customer confidence, product clarity, education, trust, and experience quality.

The problem

Growing scope, no shared operating model.

The Product Experience function already extended beyond traditional product design. The team owned product design, UX research, product content, technical documentation, design systems, customer programs, in-product education, product quality, and emerging AI experience patterns.

But without a clear strategy, that breadth looked like a collection of responsibilities rather than a coherent function. The company was entering a major product transformation across modernization, AI, analytics, and customer migration. Design could no longer operate as a downstream service function making screens after decisions were already made.

PX needed to become a strategic product partner with a defined scope, a shared operating model, and measurable outcomes.

The framework

Six pillars under one North Star.

Pillar 01

Experience Quality.

UX quality, interaction patterns, design review, usability, accessibility, visual consistency, cross-product coherence. How PX protects the customer from organizational fragmentation.

Pillar 02

Experience Platform & Delivery.

Design system, component governance, design-engineering partnership, UI infrastructure, delivery standards. Where PX moves from craft to infrastructure.

Pillar 03

Content & Clarity.

Product content, UX writing, technical documentation, help content, in-product language. Customers cannot adopt what they cannot understand.

Pillar 04

Research & Insights.

UX research, usability testing, VOC synthesis, customer visits, feedback loops into product strategy. PX helps the company make better product decisions by making customer signal easier to see and act on.

Pillar 05

Product Mastery & Community.

Customer education, advisory programs, community-led learning, adoption support. Product mastery is part of product experience. It is how customers become confident, capable, and loyal.

Pillar 06

AI & Intelligence.

AI product patterns, AI-powered insights, product voice for AI, research and tooling acceleration. AI changes how customers understand, trust, and interact with the product.

The operating model shift

Before

Design makes the product usable.

Function defined by craft boundary. Design as downstream service. Screens after decisions.

After

Product Experience makes the product understandable, adoptable, scalable, and trustworthy.

Function defined by customer outcomes. PX as strategic product partner. The connective tissue between strategy, quality, and adoption.

Maturity targets board

Measurable as a business function, not just visible as a craft.

Six pillars. Six headline targets. Aggregate function metrics underneath. Designed so the function can be evaluated like any other strategic capability, not just admired as craft.

PX maturity · 2026 targets

06 pillars · 8 targets

01

Design

System adoption

90 %

02

Content

Voice consistency

90 %

03

Docs

Review cadence

90 days

04

Research

Velocity vs baseline

3 ×

05

Community

Internal certification

90 %

06

AI

Task automation

40 %

Aggregate metrics

UX quality

≥ 8.5

Cycle time

−25%

Evaluable

Yes

2026 maturity targets, not realized outcomes. The strategy was designed to make Product Experience measurable as a business function.

What made this executive

Defining a function, not leading work inside one.

Function design

Architecting the role of PX itself.

Most design leadership work is leading projects inside an existing function. This was defining what the function does. Defining its scope, its outcomes, and its place in the broader product org.

Cross-functional integration

Connecting disciplines into one system.

Design, content, research, documentation, education, community, and AI all under one strategic identity. The team got a shared language for priorities and tradeoffs.

"One system, six pillars."

Measurement maturity

Targets, not just intentions.

Every pillar had measurable targets. Design system adoption percentage. UX quality score. Research cadence. Content consistency. Internal product certification. AI task automation. PX could be evaluated like any strategic capability.

The meta-point

Product Experience can't be defined by discipline boundaries.
It's defined by customer outcomes.

Understanding. Adoption. Confidence. Loyalty. That gave the team a stronger strategic identity, and the company a clearer way to invest in product quality. The work that most differentiates a Sr. Director from a VP isn't choosing a process framework. It's defining the function itself.