An 80% AI Adoption Rate Is Like an 80% Gym Membership Rate. It Doesn’t Prove Anyone Got Stronger.

AI return on investment in software engineering should be assessed through more than adoption rates, seats activated, or prompt counts, as these measures do not show whether developer behavior, engineering outcomes, or business results have improved. A three-layer framework proposed by GitKraken’s Stasia Zamyshlyaeva evaluates cultural adoption depth, system-level changes in delivery and quality metrics such as DORA indicators, and business outcomes including customer satisfaction, while accounting for the cost of AI tools. The discussion emphasizes that higher development velocity is meaningful only when quality is maintained or improved, and that developers who do not adopt AI may reveal accessibility barriers, job-security concerns, or gaps in tool usefulness rather than simple resistance. Panelists also caution that rapid AI-assisted workflows can contribute to burnout, suggesting organizations monitor aggregate signs such as unusually long usage periods or after-hours commits while preserving psychological safety and avoiding individual surveillance. GitKraken promotes its Insights product and AI ROI calculator as tools intended to connect AI usage with code-flow, quality, and delivery measures.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.