UX Design Lab
Discuss a project
  1. SignalsRecognize the problem.01 of 08: Signals. Recognize the problem.
  2. OutcomesWhat is different when the work is done.02 of 08: Outcomes. What is different when the work is done.
  3. ApproachAssess, align, implement, iterate.03 of 08: Approach. Assess, align, implement, iterate.
  4. ProofUnifying 70+ digital properties.04 of 08: Proof. Unifying 70+ digital properties.
  5. ServicesFocused ways in.05 of 08: Services. Focused ways in.
  6. EngagementScoped to the problem, not a package.06 of 08: Engagement. Scoped to the problem, not a package.
  7. PavelWho you work with.07 of 08: Pavel. Who you work with.
  8. ContactStart a conversation.08 of 08: Contact. Start a conversation.

Enterprise UX Transformation

Scale UX across teams

Connect product, research, design systems, accessibility, governance, capability, and delivery where organizational structure keeps producing the same failures.

Discuss the organization

Recognize the problem.

If two or more of these sound familiar, start here.

  1. S/01

    Similar UX problems appear across several product teams.

  2. S/02

    Business units solve the same problem independently.

  3. S/03

    Design quality depends on which team owns the work.

  4. S/04

    Research, accessibility, systems, and governance operate separately.

  5. S/05

    Technology modernization has not fixed delivery behavior.

  6. S/06

    UX leadership is missing from major transformation decisions.

What changes.

What is different when the work is done — things you can point to, not adjectives.

  1. Change 01

    Leadership has one map showing where work is duplicated across teams.

  2. Change 02

    Shared problems have common ownership and decision rules.

  3. Change 03

    Research, accessibility, design systems, and governance connect to the same delivery model.

  4. Change 04

    Major UX decisions have named accountability.

  5. Change 05

    Transformation work includes mechanisms for internal ownership after implementation.

How we work.

Assess. Align. Implement. Iterate. Applied to the work with the most at stake.

  1. Assess

    Map the operating model, products, capabilities, workflows, evidence, ownership, and repeated failure points.

  2. Align

    Identify high-leverage changes and establish shared priorities across leadership and delivery teams.

  3. Implement

    Change the appropriate operating model, governance, systems, workflows, capability, or delivery mechanism.

  4. Iterate

    Establish ownership, measurement, standards, and internal capability.

Proof.

Comparable work, with its provenance stated.

Proof · INSURANCE · Enterprise UX Transformation

Unifying 70+ digital properties.

Context

Work led by Pavel reframed a planned platform migration around the operating model behind delivery. The program reported 20% lower departmental cost, 60% less developer dependency, and more than 70 properties in one unified ecosystem.

Provenance

Operational redesign for a fragmented digital ecosystem — measured during the engagement.Read the case: Unifying 70+ digital properties. →
Service blueprint and dependency map showing duplicated effort, broken handoffs and rework across business units.
FIG. 07.1Service blueprint and dependency map exposing duplicated effort, broken handoffs and sources of rework.

What changed

20%
LOWER DEPARTMENTAL COST
60%
LESS DEVELOPER DEPENDENCY
70+
PROPERTIES IN ONE UNIFIED ECOSYSTEM

Business pattern

Technology modernization fails when the operating model that created the problem remains unchanged.

Pavel Bukengolts smiling and gesturing by a window overlooking a city skyline

Senior work stays senior.

You work directly with Pavel Bukengolts, UXDL founder and principal, on assessment, major decisions, and direction. Specialist collaborators join when the work requires additional expertise or capacity.

Recognition

  • ADPList 100

    Recognized among the top mentors on ADPList.

  • 2026 GNTC Tech Educator of the Year

    Finalist, Greater Nashville Technology Council.

  • UX Magazine contributor

    Published on product, accessibility and AI practice.

Bring the pattern that keeps repeating across the organization.

Bring the product, workflow, delivery problem, or decision. No polished brief required.

Prefer email? [email protected]

Project inquiry

All fields are required except timeline.