VP, AI COE Product Management & Adoption

The VP of AI COE Product Management & Adoption owns adoption and realized value for our AI Marketplace tools (Claude, Gemini, Copilot) and our three strategic custom platforms:
Loom, MemX, and Forge
49, and the colleague experience that spans them. Building capable platforms is necessary but not sufficient; value is created only when colleagues adopt the governed path and change how they work. This role is accountable for that outcome, and for ensuring the experience across platforms is coherent enough that they will. This is a product and adoption function, not a change-management or training function.

Each engineering leader is accountable for whether a platform is built and operated well; this leader is accountable for whether it is adopted, trusted, and delivering measured value, and for carrying the needs of the divisions back into what the engineering pillars build next. Because a colleague’s work moves across Loom, MemX, and Forge
49 in a single workflow, no individual platform team owns the end-to-end experience. This role owns that experience as a product.

The team is organized as a small senior core with a federated adoption reach. The core, cross-platform product management, experience and design research, marketplace and catalog curation, and adoption measurement, stays lean because its leverage is judgment and orchestration, not volume. The labor-intensive work of adoption is federated: a central enablement hub orchestrates a champions network embedded in the divisions, rather than staffing a large central training organization.

The team is intentionally the leanest of the CoE’s direct-report functions. Its authority comes from mandate, not headcount.

The core is organized across four functions, each owning a distinct part of the demand-to-value loop:
Cross-Platform Product Management, Experience & Design Research, AI Marketplace & Catalog, and Adoption Measurement.

• Own the end-to-end colleague experience that spans AI Marketplace tools, Loom, MemX, and Forge
  49, the product no single engineering pillar owns, defining how a colleague’s work moves across platforms as one coherent journey.
• Overseeing engineering pillars’ roadmaps. Adoption evidence sets what Platform Engineering teams build next. The pillars own how and how well; this team owns what matters most and for whom. The CDAO arbitrates when demand and feasibility collide.
• Maintain product-minded ownership of the three-platform experience, validated through continuous engagement with colleagues across R&D, Commercial, PGS, and enabling functions.

• Own the adoption model for the three platforms, including role-cohort rollout on a regular cadence, so capability reaches the colleagues who carry the heaviest load first.
• Operate a central enablement hub that owns the rollout method, AI literacy, and practitioner training, focused on how colleagues think and work with these tools, not only how to click through them.
• Orchestrate a federated champions network. Champions are embedded in the divisions on a hub-and-spoke model, dotted-line and division-funded, not centralized headcount. The hub sets the standard and the cadence; the divisions supply the reach.
• Own the feedback path from the field back into the roadmap, ensuring adoption friction is surfaced as a prioritization signal rather than absorbed silently.

• Own colleague journey mapping and friction analysis across the three platforms, the qualitative discipline that makes "voice of the divisions" a practice rather than a slogan.
• Investigate why colleagues route around the governed path, and translate those findings into product and roadmap direction for the engineering pillars.
• Serve as the qualitative complement to adoption measurement: measurement shows what is happening, design research explains why.

• Own the AI marketplace and catalog scoped to AI-native reusable assets and the three strategic platforms, the reuse-before-build front door that surfaces duplication before a second team builds the same thing.
• Curate the prompt and skill-pattern library, the approved patterns and reusable workflows colleagues call instead of a blank prompt box. This is content and practice curation; the registry and runtime infrastructure are owned by the engineering pillars.
• Coordinate with the Head of Portfolio and Operations on reuse intelligence. Enterprise-wide reuse across all software demand sits with Portfolio and Operations; this catalog is the AI-native, three-platform view that feeds it.

• Own adoption measurement for the three platforms as the source of truth, governed-path versus shadow-path usage, reuse rate, leakage, and hours recovered. This is the steering signal that drives prioritization, not a downstream report card.
• Own value realization for AI Marketplace tools, Loom, MemX, and Forge
  49, and report it up to Portfolio and…