enterprise AI transformation at scale
John Deere drives AI adoption across 70,000 employees by merging strategy and platform orgs IT RevolutionTL;DW
- John Deere achieved 90% weekly and 70% near-daily AI adoption across 70,000+ employees by providing universal access, training, and safe experimentation—not to maximize immediate productivity, but to prepare workers for larger coming disruption.
- AI transformation differs fundamentally from past changes (Agile, DevOps): no proven playbook exists, technology shifts constantly, and the destination is undefined—requiring continuous experimentation rather than scaled proof-of-concepts.
- Embed AI in employees' existing workflows and applications rather than isolating it as separate tools; this accelerates understanding and adoption compared to asking workers to context-switch to dedicated AI tools.
- Peer-to-peer advocacy from trusted team members drives adoption far more effectively than corporate leadership messaging; recruit natural innovators from the business and amplify their in-context conversations with peers.
- Use metrics that reflect reality: measure 90%+ of developers using AI assistants when they contribute code (not daily/weekly users), avoiding anxiety about oversimplifying roles.
- Leadership must be bimodal: continuously feed leading innovators and early adopters the latest technology while protecting the broader organization from constant disruption, preventing every team from chasing every new trend.
- Experimentation is now a core expectation at every level—individual roles, teams, and use cases—but establish a gatekeeping process to prevent scaling all hype; not everything that works at the edges should scale enterprise-wide.
- Foundational technical practices (automated deployments, test coverage, telemetry instrumentation) shift from optional to required; when coding ceases to be the bottleneck, all other constraints become critical.
- Adoption programs cannot be one-time events; continuously offer introductory through advanced AI training (Agent-in-a-Day through 401-level courses) as technology evolves and new cohorts of employees join the journey.
- Combine platforms and strategy organizations so platform teams understand which emerging patterns should be codified into standard products; you cannot drive technical strategy if platforms don't make the right things easy.
TL;DW
- John Deere achieved 90% weekly and 70% near-daily AI adoption across 70,000+ employees by providing universal access, training, and safe experimentation—not to maximize immediate productivity, but to prepare workers for larger coming disruption.
- AI transformation differs fundamentally from past changes (Agile, DevOps): no proven playbook exists, technology shifts constantly, and the destination is undefined—requiring continuous experimentation rather than scaled proof-of-concepts.
- Embed AI in employees' existing workflows and applications rather than isolating it as separate tools; this accelerates understanding and adoption compared to asking workers to context-switch to dedicated AI tools.
- Peer-to-peer advocacy from trusted team members drives adoption far more effectively than corporate leadership messaging; recruit natural innovators from the business and amplify their in-context conversations with peers.
- Use metrics that reflect reality: measure 90%+ of developers using AI assistants when they contribute code (not daily/weekly users), avoiding anxiety about oversimplifying roles.
- Leadership must be bimodal: continuously feed leading innovators and early adopters the latest technology while protecting the broader organization from constant disruption, preventing every team from chasing every new trend.
- Experimentation is now a core expectation at every level—individual roles, teams, and use cases—but establish a gatekeeping process to prevent scaling all hype; not everything that works at the edges should scale enterprise-wide.
- Foundational technical practices (automated deployments, test coverage, telemetry instrumentation) shift from optional to required; when coding ceases to be the bottleneck, all other constraints become critical.
- Adoption programs cannot be one-time events; continuously offer introductory through advanced AI training (Agent-in-a-Day through 401-level courses) as technology evolves and new cohorts of employees join the journey.
- Combine platforms and strategy organizations so platform teams understand which emerging patterns should be codified into standard products; you cannot drive technical strategy if platforms don't make the right things easy.
Amy Willard details how Deere embedded AI tools into daily workflows for all 70,000 employees, publishes adoption metrics transparently, and merged its strategy and core-platforms organizations so platforms enable rather than block transformation. For its 18,000 technologists, AI assistance in coding now exceeds 90%, shifting the bottleneck to test coverage and instrumentation.