Moving from AI adoption to an AI operating model: How Docusign engineering went beyond tool rollout

This piece looks at how Docusign went from a rollout of AI coding assistants that stalled to a broader operating model across its engineering organization. It explains how a small central champions team and embedded Multipliers spread shared practices, and how the company built an internal platform called Krew that lets engineers share and reuse agents for recurring tasks like overnight error triage and configuration changes. The article also covers why the company is shifting its yardstick from adoption rates and code volume toward delivery speed, quality, and reliability, and it stresses that human sign-off stays required before any code merges. Readers get a practical view of what sustaining AI programs beyond the initial enthusiasm tends to demand, along with the caveats the company itself acknowledges.