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

DevFeed: [Moving from AI adoption to an AI operating model: How Docusign engineering went beyond tool rollout](<https://devfeed.tech/articles/moving-from-ai-adoption-to-an-ai-operating-model-how-docusign-engineering-went-beyond-tool-rollout-122594.md>)

Original publisher: [Read original article](<https://thenewstack.io/docusign-ai-engineering-adoption/>)

Author: Nick Lucchesi

Published: 2026-11-08T17:00:00Z

Content type: news

Language: en

Sources: [The New Stack](<https://devfeed.tech/sources/the-new-stack.md>)

Topics: [AI Strategy](<https://devfeed.tech/topics/ai-strategy.md>), [AI tools for developers](<https://devfeed.tech/topics/ai-tools-for-developers.md>), [developer-productivity](<https://devfeed.tech/topics/developer-productivity.md>), [Multi-step AI processes](<https://devfeed.tech/topics/multi-step-ai-processes.md>), [coding assistant](<https://devfeed.tech/topics/coding-assistant.md>), [Agent Harness](<https://devfeed.tech/topics/agent-harness.md>), [Developer Enablement](<https://devfeed.tech/topics/developer-enablement.md>), [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [observability](<https://devfeed.tech/topics/observability.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-coding-tools](<https://devfeed.tech/tags/ai-coding-tools.md>), [ai-engineering](<https://devfeed.tech/tags/ai-engineering.md>), [ai-generated-code](<https://devfeed.tech/tags/ai-generated-code.md>), [ai-operating-model](<https://devfeed.tech/tags/ai-operating-model.md>), [ai-workflows](<https://devfeed.tech/tags/ai-workflows.md>), [autonomous-coding](<https://devfeed.tech/tags/autonomous-coding.md>), [boundary](<https://devfeed.tech/tags/boundary.md>), [code-review](<https://devfeed.tech/tags/code-review.md>), [developer-tools](<https://devfeed.tech/tags/developer-tools.md>), [docusign](<https://devfeed.tech/tags/docusign.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [post](<https://devfeed.tech/tags/post.md>), [sponsor-docusign](<https://devfeed.tech/tags/sponsor-docusign.md>), [sponsored](<https://devfeed.tech/tags/sponsored.md>), [sponsored-post](<https://devfeed.tech/tags/sponsored-post.md>)

## AI overview

Docusign's account suggests broad AI tool adoption alone did not sustain productivity gains; it paired rollout with engineering support, reusable workflows, and value focused measurement. A six person Eng AI Champions team set practices and ran workshops, then about 75 embedded AI Multipliers deployed solutions and returned team feedback. Docusign reports active use rose to 93% and code lines updated per developer increased about 52%, while acknowledging code volume does not establish better speed or quality. Its Krew platform lets teams share and extend agents such as workflows combining Chronicle telemetry and Kody coding capabilities. Examples include overnight incident fixes proposed as pull requests and a configuration task where 10 of 12 files were correctly changed in about 15 minutes, with two still needing correction; the company says the work previously took roughly a week. Human review and approval remain required before merging or irreversible actions. Docusign recommends measuring delivery, reliability, customer satisfaction, rework, and costs, with owners and failure feedback for shared workflows.

## Source excerpt

Docusign rolled out AI coding tools across its engineering teams, expecting them to help developers write code faster and do The post Moving from AI adoption to an AI operating model: How Docusign engineering went beyond tool rollout appeared first on The New Stack.