As visibility improved across the DEX ecosystem, a new challenge emerged.

General Availability deadlines were approaching while capabilities across onboarding, metadata management, routing services, validation, portal experiences, and future support functions were being defined simultaneously.

Teams were navigating shifting priorities, evolving organizational structures, and increasing delivery expectations while still determining what needed to be built.

Creating visibility had been the first step.

The next challenge was creating enough clarity to move forward.

To help teams navigate uncertainty, I introduced planning frameworks, facilitation practices, and roadmap structures that connected strategic objectives, capabilities, requirements, and release goals into a shared delivery model.

Focus Areas

Key Outcomes

Key Insight

As DEX matured, the challenge shifted from understanding the ecosystem to coordinating delivery across it.

Title of Artifact: Requirements artifact. Or roadmap. Something showing the need for structure.

Planning Capabilities, Not Backlogs

As delivery expectations increased, teams needed more than feature requests and backlog items. They needed a shared understanding of what capabilities were being created, why they mattered, and how they would mature over time.

Working closely with the Product Designer and UX Technical Writer, I facilitated planning sessions that transformed loosely defined ideas into structured service initiatives.

Together, we developed Service Capability Delivery Plans that connected:

These sessions became a mechanism for aligning product, design, engineering, and stakeholder groups while improving visibility into the work required to reach General Availability.

Critical Questions

Key Outcome

Service Capability Delivery Plans created a repeatable framework for translating organizational goals into executable work while improving alignment across rapidly evolving delivery efforts.

Service Capability Delivery Plans: Service Capability Delivery Plans used to define outcomes, ownership, dependencies, and implementation pathways for emerging DEX capabilities.

When a Feature Became a Service

Metadata Management Services (MMS) became one of the first capabilities to expose the operational complexity emerging beneath the DEX ecosystem.

Initially positioned as an administrative feature supporting the Portal, MMS quickly revealed dependencies across onboarding, permissions management, routing configuration, governance, and long-term operational ownership.

Working alongside the Product Designer, I helped define user flows, operational requirements, and delivery plans that supported the evolution of the MMS experience.

As the work progressed, a larger realization emerged that MMS was not simply a feature.

It was becoming the operational system responsible for managing how organizations, users, permissions, routing relationships, and data exchange configurations were established and maintained across the ecosystem.

MMS revealed that successful delivery required more than software functionality.

It required ownership models, onboarding processes, governance structures, support pathways, and operational accountability capable of sustaining the ecosystem after launch.

The conversation expanded beyond interface design into questions of:

Key Outcome

The MMS effort helped establish a shared understanding that successful delivery required more than software functionality—it required operational models capable of supporting the ecosystem after launch.

Metadata Management Service (MMS): An operational capability supporting onboarding, permissions management, routing configuration, and ecosystem governance across DEX.

From Delivery Tracking to Operational Readiness

As DEX moved closer to General Availability, delivery planning became less about tracking features and more about coordinating an increasingly complex service ecosystem.

Portal development, onboarding activities, metadata management, validation services, communications, and future operational support functions were progressing simultaneously—often with overlapping dependencies and competing priorities.

To maintain alignment, I managed roadmap structures that connected:

These artifacts created visibility into the broader effort while supporting prioritization, sequencing, and release readiness discussions.

Over time, planning conversations began to shift.

Questions evolved from:

What are we building?

to:

Those questions would ultimately shape the next phase of work.

Key Outcome

Roadmaps evolved from delivery tracking tools into coordination mechanisms that connected product development, operational planning, and organizational readiness ahead of General Availability.

Key Insight

By General Availability, the challenge was no longer simply delivering features. It was ensuring the operational systems, governance models, onboarding pathways, and ownership structures existed to support them.

As delivery planning matured, it became clear that launching DEX successfully would depend as much on onboarding and customer readiness as it would on platform capabilities.

DEX Roadmap Coordination: DEX roadmap coordination artifacts used to align capabilities, dependencies, release objectives, and operational readiness activities across the evolving ecosystem.

Discovering a Larger Operational Challenge

As Metadata Management Services (MMS) matured, it exposed a broader operational challenge. Questions that initially appeared technical quickly expanded into customer onboarding, permissions management, governance, and long-term service ownership.

While teams were successfully defining portal functionality, there was no shared understanding of how customers would be introduced to DEX, onboarded into the ecosystem, provisioned within the platform, and supported over time.

To better understand these relationships, I partnered with Program Onboarding stakeholders to facilitate discovery sessions focused on onboarding experiences, operational workflows, and future-state service needs.

Key Areas Explored

Key Insight

The deeper we explored onboarding, the clearer it became that DEX onboarding represented a service requiring coordination across multiple teams—not simply a sequence of portal tasks.

Artifact Title: DEX Onboarding Discovery & Operational Assessment

Reframing the Customer Support Perspective

One of the most important discoveries emerged through the Metadata Management Service (MMS) effort.

As MMS evolved from a portal capability into a broader operational service, new questions began surfacing around onboarding, permissions management, customer readiness, governance, and long-term support.

While much of the DEX initiative had been organized around platform capabilities, delivery milestones, and organizational structures, MMS revealed something larger:

Customers would require ongoing guidance long before and long after technology implementation.

To better understand these needs, I partnered with Program Onboarding stakeholders to examine how customers entered the ecosystem, navigated onboarding requirements, coordinated implementation activities, and received support over time.

Through these conversations, a clearer picture emerged: Program Onboarding was becoming more than an intake function.

The team was positioned to help customers understand DEX, identify the appropriate Data Senders, gather required onboarding information, coordinate implementation activities, and navigate the broader ecosystem.

As discussions shifted toward this evolving role, new questions began to surface:

Questions We Explored

The work revealed that successful onboarding depended not only on platform capabilities, but also on understanding the needs, responsibilities, and constraints of the people tasked with implementation.

Key Insight

The onboarding experience had largely been designed around organizational structures rather than the people responsible for implementation.

Shifting focus to operational needs revealed that customer readiness, guidance, support, and operational coordination were just as critical as the technology itself.

Outcome

This shift established a more customer-centered foundation for onboarding design and became a catalyst for future service design, support, and operational planning efforts.

Artifact Title: Onboarding Discovery Workshops & Stakeholder Research

Designing a Future-State Onboarding Service

As discovery matured, the effort evolved beyond documenting current-state processes.

The goal became defining what a scalable onboarding service would require as DEX moved toward General Availability.

Working sessions translated research findings into future-state concepts focused on reducing onboarding friction, improving readiness, and creating clearer operational pathways.

The Service Model Introduced

Rather than viewing onboarding as a one-time activity, these concepts treated onboarding as an operational capability requiring ongoing stewardship and continuous improvement.

Key Insight

The future-state model reframed onboarding from a one-time implementation activity into an operational capability designed to support customers throughout adoption and growth.

Artifact Title: Future-State Onboarding Service Vision

Creating the Roadmap for Service Evolution

Discovery findings, onboarding blueprints, and future-state concepts were ultimately synthesized into a delivery plan that connected immediate needs with long-term service evolution.

The roadmap established a structured approach for advancing onboarding capabilities while supporting broader General Availability objectives.

The Delivery Plan Connected

This provided stakeholders with a shared view of how onboarding could evolve from a collection of manual activities into a coordinated service capability.

Organizational Outcome

The onboarding roadmap created a shared vision for how customer enablement, support, governance, and operational ownership could mature alongside the DEX platform.

This work laid the foundation for broader conversations around Customer Support Services and long-term service stewardship.

Through onboarding discovery, a broader realization emerged.

Successful implementation depended on far more than technical configuration. Customers needed guidance, readiness support, operational clarity, training, communication pathways, and ongoing assistance throughout adoption.

Onboarding was no longer simply an implementation activity. It was becoming an operational service capability.

Artifact Title: DEX Onboarding Delivery Plan & Service Roadmap

Recognizing the Need for Service Ownership

As onboarding discovery progressed, it became increasingly clear that successful customer adoption depended on more than onboarding activities alone.

Customers required guidance before onboarding, coordination during implementation, and ongoing support after launch. Yet ownership for these experiences was distributed across multiple teams and workstreams.

What began as onboarding analysis was exposing a broader need for operational stewardship across the DEX ecosystem.

Emerging Questions

Key Insight

DEX required more than onboarding processes—it required a coordinated service operating model.

Artifact Title: DEX Onboarding Discovery & Operational Assessment

Mapping the Customer Support Ecosystem

To better understand how support and operational activities functioned across DEX, I partnered closely with the UX Technical Writer and Customer Support stakeholders.

Together, we began documenting the activities, relationships, responsibilities, and handoffs that shaped the customer experience.

Emerging Patterns

Outcome

The work revealed that DEX was operating as a customer support ecosystem long before it was formally recognized as one.

Artifact Title: Initial ecosystem map.

Service Blueprinting the Operational Model

As the ecosystem expanded, operational knowledge became increasingly distributed across teams, documents, and informal processes.

Creating a shared understanding of how the system functioned became critical.

Service blueprinting became the mechanism for making the ecosystem visible.

Blueprint Components

Key Insight

Blueprinting transformed operational knowledge from tribal understanding into a shared organizational asset.

More importantly, it created a mechanism for coordination. Teams could now see how responsibilities, dependencies, customer interactions, and operational activities connected across the broader service ecosystem.

Artifact Title: Early blueprint.

Establishing the Foundation for Service Evolution

As operational understanding matured, the blueprints evolved from documentation artifacts into strategic planning tools.

The work began informing:

Outcomes

Organizational Outcome

What began as onboarding discovery helped establish the operational foundation that would later support the evolution of Customer Support Services, creating greater visibility into how the DEX ecosystem could be understood, coordinated, and continuously improved.

Artifact Title: DEX Onboarding Delivery Plan & Service Roadmap

From Delivery to Service Evolution

As visibility increased, attention shifted from understanding the ecosystem to helping it evolve more intentionally.

Throughout the DEX initiative, research, onboarding analysis, blueprinting, and stakeholder engagement created a clearer picture of how services, teams, and operational activities interacted across the organization.

As understanding matured, a broader question emerged: How do we continuously learn from, prioritize, and improve the service over time?

Questions Emerging

Key Insight

Sustainable service improvement requires operational mechanisms for learning, coordination, prioritization, and continuous improvement—not just project plans and delivery artifacts.

Artifact Title: DEX Ecosystem Assessment & Strategic Findings

Establishing a Framework for Service Evolution

To support long-term coordination, I began defining structures that connected research, planning, governance, and delivery activities.

The goal was not to replace existing delivery practices, but to create a shared framework that helped teams maintain visibility, align priorities, and evolve the service collectively over time.

Framework Components

Key Insight

Operational maturity depends on creating structures that continuously connect customer insight, organizational priorities, and delivery efforts.

Outcome

Created an initial operating model for coordinating service evolution across teams, initiatives, and organizational boundaries.

Artifact Title: DEX Service Operations Framework

Organizing Service Evolution

As the body of work expanded, initiatives were organized according to the role they played in service maturity.

Rather than viewing efforts as disconnected projects, the work was grouped into interconnected strategic lanes that collectively supported understanding, planning, and operational improvement.

Strategic Lanes

Key Insight

Visibility improves when work is organized around service outcomes rather than individual projects.

Outcome

Created a shared framework for understanding how initiatives contributed to broader service maturity and organizational goals.

Artifact Title: DEX Service Roadmap & Strategic Portfolio Model

Exploring Service Measurement

As operational understanding matured, conversations increasingly shifted toward service health and long-term effectiveness.

Teams began exploring how success could be evaluated beyond feature delivery by examining adoption, readiness, engagement, operational effectiveness, and service performance.

Emerging Measures of Service Health

Key Insight

Services become easier to improve when organizations can measure how effectively they are being adopted, supported, and evolved over time.

Key Insight

Established foundational thinking around service governance, operational measurement, and continuous improvement—creating structures that could support long-term service maturity.

Artifact Title: Service Measurement Framework & Adoption Planning Materials

Evolving the Delivery Model

As DEX matured, organizational priorities shifted from expanding internal software delivery capabilities toward enabling vendor-supported solutions.

While the delivery model changed, the need for service ownership, onboarding, governance, support, and operational coordination remained.

The question was no longer: How do we build and operate this ourselves?

It became: How do we successfully enable and govern this service regardless of who builds the technology?

Operational Areas Still Required

Key Insight

Technology delivery models may change, but the service surrounding the technology still requires intentional design and stewardship.

Artifact Title: Future-State Operating Model Discussions

Building the Foundation for Transition

Many of the operational concepts explored through DEX became increasingly relevant as the organization evaluated vendor-supported approaches.

Areas Influenced

Organizational Outcome

The work helped establish a common understanding of how the service would need to operate regardless of whether technology was delivered internally or through external partners.

Key Insight

The lasting value of the work was not tied to a specific software solution. It was the creation of operational structures capable of supporting the service through future organizational change.

Artifact Title: Service Governance & Operational Planning Materials