---
title: "AI Adoption"
description: "2 posts about AI Adoption, summarised, each linking to the original."
---

# AI Adoption
> 2 posts about AI Adoption, summarised, each linking to the original.

## Articles

### [Chaos, then control: the maturity model most AI rollouts skip over](https://yomu.fyi/post/chaos-then-control-the-maturity-model-most-ai-rollouts-skip-over.md)
- Company: [Stack Overflow](https://yomu.fyi/company/stack-overflow.md)
- Author: Eira May
- Published: Nov 19, 2026
- Type: Problem & solution

Many engineering organizations see uneven results from AI coding tools despite high adoption because they skip the crucial middle stages of a proper rollout. Vivek Raghunathan, SVP of engineering at Snowflake, advocates a five-stage progression: let chaos reign, discover what works, codify it into a shared language, rein in chaos by scaling that language, then reorganize. The skipped stages—discovering effective practices and naming them as patterns—turn individual competence into organizational knowledge. Raghunathan’s team built a pattern language of roughly 14 named practices, including planning in writing before coding and fencing agents into separate git worktrees. They spread these practices through structural mechanisms like focus weeks rather than mandates, and resist reorganizing until the earlier stages have produced reliable knowledge about what AI-assisted work looks like.


### [How Salesforce Scaled Engineering AI Adoption Without Stifling Innovation](https://yomu.fyi/post/how-salesforce-scaled-engineering-ai-adoption-without-stifling-innovat.md)
- Company: [Salesforce](https://yomu.fyi/company/salesforce.md)
- Author: Paul Constantinides
- Published: Nov 10, 2026
- Type: Problem & solution

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.
