Five sessions and a hackathon: engineering team shifts from low AI adoption to daily agent use after structured enablement series
An infrastructure engineering team had low and shallow AI adoption despite having available tools and leadership encouragement — most engineers used AI only for autocomplete or not at all, because a poor-quality early experience had led the team to write off AI as a serious tool, and no one had given them a framework for where it fit in their workflow.
How it works
Common implementation structure
How this type of workflow is generally built, generalized across documented cases — not tied to any one vendor's stack. Click any stage to read what happens there. Specific products that implement these stages appear in “Tools commonly seen” below.
Stage 1 · Low-adoption trigger
Low and shallow AI adoption on a senior engineering team — despite available tools and leadership support — triggered the design of a structured enablement program.
Tools used
MCP Servers
Outcome
Daily AI users grew from two or three engineers to essentially everyone on the team; the two-hour hackathon capstone produced a fleet of production-grade agents, and the program is now expanding to a multi-team hackathon at larger scale.
What failed first
An earlier wave of AI adoption failed because model output quality did not meet the bar the team held their own work to, causing them to classify AI as a 'fun toy, not a serious tool' and stop experimenting entirely.