---
title: "How Salesforce Scaled Engineering AI Adoption Without Stifling Innovation"
description: "Salesforce’s Hyperforce Runtime Platform (HRP) organization faced scattered AI experiments across 500 engineers in 70-80 scrum teams, with overlapping efforts and tight delivery commitments. The team established a federated AI adoption model with an AI Steering Committee, AI Champions, and the HRPDX shared Claude Code plugin to distribute AI instructions and skills. Teams contributed capabilities by solving their own pain points, with ownership assigned to the building team for end-to-end delivery and support. Within three months, AI adoption approached 100%, yielding a 26% gain in team throughput, a 32% improvement in inner-loop efficiency, and cycle time cut from 22 days to 11 days. The AI paved path model sustains adoption by continuously connecting emerging bottlenecks to available capabilities through metrics and a feedback loop."
---

# How Salesforce Scaled Engineering AI Adoption Without Stifling Innovation

[Salesforce](https://yomu.fyi/company/salesforce) · Paul Constantinides · Nov 10, 2026

**Type:** Problem & solution

## Summary

Salesforce’s Hyperforce Runtime Platform (HRP) organization faced scattered AI experiments across 500 engineers in 70-80 scrum teams, with overlapping efforts and tight delivery commitments. The team established a federated AI adoption model with an AI Steering Committee, AI Champions, and the HRPDX shared Claude Code plugin to distribute AI instructions and skills. Teams contributed capabilities by solving their own pain points, with ownership assigned to the building team for end-to-end delivery and support. Within three months, AI adoption approached 100%, yielding a 26% gain in team throughput, a 32% improvement in inner-loop efficiency, and cycle time cut from 22 days to 11 days. The AI paved path model sustains adoption by continuously connecting emerging bottlenecks to available capabilities through metrics and a feedback loop.

## Context

Salesforce’s Hyperforce Runtime Platform (HRP) had roughly 500 engineers across 70-80 scrum teams already experimenting with AI, but efforts were scattered, overlapping, and lacked shared practices. Tight delivery commitments left little room for new initiatives, and scaling AI adoption risked stifling innovation or becoming another burden.

## Approach / What changed

A federated AI adoption model with an AI Steering Committee, HRPDX shared Claude Code plugin, AI Champions, and an AI Innovation Loop that lets teams contribute capabilities solving their own pain points, which are then distributed, maintained, and measured via the paved path.

## Takeaways

- A federated AI adoption model with an AI Steering Committee, AI Champions, and shared tooling (HRPDX plugin) enabled near-100% AI adoption across 70-80 scrum teams within three months.
- Teams contributed AI capabilities by solving their own pain points, with ownership assigned to the building team for end-to-end delivery, support, and ongoing operation.
- Using SDLC and DORA metrics (lead time, deployment frequency, change failure rate) helped teams identify bottlenecks and choose relevant AI capabilities, driving a 26% throughput gain and cycle time reduction from 22 to 11 days.

## FAQ

### How is ownership assigned in the federated AI model?

The AI Steering Committee guides and recommends AI practices, while engineering managers and their teams own end-to-end delivery, deadlines, and ongoing support for any capability they build. Architects define technical guidance and quality gates, and AI Champions connect the structure to team experience.

### What is the HRPDX plugin and how does it work?

The HRPDX plugin is a shared Claude Code plugin that distributes AI instructions and skills to all developers, providing a baseline foundation. Teams can extend it while retaining their own tools and workflows, and the AI Innovation Loop allows contributions to be scaled, distributed, and measured.

### How did metrics guide AI adoption decisions?

The team used existing data pipelines to expose SDLC and DORA metrics at the scrum and portfolio levels, including pull request-based lead time for changes, deployment frequency, and change failure rate. These metrics helped teams identify their own bottlenecks and choose relevant AI capabilities to adopt.

**Tags:** [AI](https://yomu.fyi/topic/ai), [AI Adoption](https://yomu.fyi/topic/ai-adoption), [DORA Metrics](https://yomu.fyi/topic/dora-metrics), [Engineering Management](https://yomu.fyi/topic/engineering-management), [Salesforce](https://yomu.fyi/topic/salesforce)

- Source: [Salesforce](https://engineering.salesforce.com/how-salesforce-scaled-engineering-ai-adoption-without-stifling-innovation)
- Source URL: https://engineering.salesforce.com/how-salesforce-scaled-engineering-ai-adoption-without-stifling-innovation
- Ingested by Yomu: 2026-11-10T21:00:15.098Z

[Read original post](https://engineering.salesforce.com/how-salesforce-scaled-engineering-ai-adoption-without-stifling-innovation)
