--- title: How Microsoft sees engineering bottlenecks changing with AI description: Tim Bozarth, Microsoft's CVP of CoreAI and leader of the Engineering Thrive initiative, discusses how AI is reshaping engineering productivity measurement and... canonical: https://daily.dev/posts/how-microsoft-sees-engineering-bottlenecks-changing-with-ai-i7vvtyy23 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: How Microsoft sees engineering bottlenecks changing with AI | daily.dev og:description: Tim Bozarth, Microsoft's CVP of CoreAI and leader of the Engineering Thrive initiative, discusses how AI is reshaping engineering productivity measurement and... og:url: https://daily.dev/posts/how-microsoft-sees-engineering-bottlenecks-changing-with-ai-i7vvtyy23 og:image: https://api.daily.dev/og/posts/i7VvTYY23.png og:image:alt: How Microsoft sees engineering bottlenecks changing with AI og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # How Microsoft sees engineering bottlenecks changing with AI **[Engineering Enablement](https://daily.dev/sources/engineering_enablement)** · 6 min read · 3 upvotes · 0 comments ## Summary Tim Bozarth, Microsoft's CVP of CoreAI and leader of the Engineering Thrive initiative, discusses how AI is reshaping engineering productivity measurement and where new bottlenecks are emerging. Engineering Thrive defines productivity through speed, ease, and quality, rejecting activity metrics like PR counts in favor of outcome-based measures. As AI accelerates code creation, planning and validation are becoming the dominant constraints on frontier teams. Bozarth argues that verification and confidence in AI-generated code matter more than raw throughput, and that durable engineering skills — systems thinking, judgment, and a maker's mindset — remain essential regardless of abstraction level. Engineering leaders are urged to measure idea-to-value rather than PR velocity. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What percentage of engineering time was historically spent on operations before AI tools became widespread? Operations alone historically consumed roughly 70% to 80% of engineering time, with creating and operating software together accounting for more than 90% of total engineering time. Tim Bozarth, Microsoft CoreAI's Corporate Vice President, notes that on frontier teams using AI, code creation now takes dramatically less time, shifting the bottleneck toward planning and validation instead. _Engineering leaders rethinking where time actually goes under AI-assisted workflows can track this shift via daily.dev._ ### Why is code review considered a confidence bottleneck rather than just a throughput problem? Code review is really about establishing confidence that a change is trustworthy, not simply inspecting code line by line. Higher pull request throughput from AI-generated code has increased the volume of change humans must evaluate, and confidence can also come from testing, continuous rollouts, feature flags, and canary deployments rather than manual review alone. _Teams debating how to scope code review around AI-generated changes can follow this discussion on daily.dev._ ### Should engineering teams go back to measuring lines of code and pull request counts to track AI's impact on productivity? No, activity metrics like lines of code and pull request counts are considered inadequate measures that the industry already rejected years ago. Tim Bozarth of Microsoft CoreAI argues that more engineering activity does not necessarily mean more value, and recommends outcome-based metrics instead, such as product quality, end-to-end speed, and idea-to-value, which are harder to game than any single activity measure. _Leaders deciding how to measure AI's real impact on their teams can weigh this outcomes-first approach on daily.dev._ ## Similar posts on daily.dev - [It’s time to rethink how we measure engineering productivity](https://daily.dev/posts/it-s-time-to-rethink-how-we-measure-engineering-productivity-nobwkqmxy) · LeadDev · 0 upvotes · 0 comments - [The Reality of AI in Engineering: Why Productivity Gains Get Absorbed by System Constraints](https://daily.dev/posts/the-reality-of-ai-in-engineering-why-productivity-gains-get-absorbed-by-system-constraints-rvc84zzir) · SD Times · 0 upvotes · 0 comments - [The current impact of AI on engineering velocity](https://daily.dev/posts/the-current-impact-of-ai-on-engineering-velocity-lic0nalsa) · Software Engineering Research · 0 upvotes · 0 comments - [Software engineering’s bottleneck is no longer code](https://daily.dev/posts/software-engineering-s-bottleneck-is-no-longer-code-qxqgvlbgm) · The Next Web · 5 upvotes · 1 comments --- Tags: [#microsoft](https://daily.dev/tags/microsoft), [#productivity](https://daily.dev/tags/productivity), [#ai-coding](https://daily.dev/tags/ai-coding), [#dora-metrics](https://daily.dev/tags/dora-metrics) [View this post on daily.dev](https://daily.dev/posts/how-microsoft-sees-engineering-bottlenecks-changing-with-ai-i7vvtyy23) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"How Microsoft sees engineering bottlenecks changing with AI","url":"https://daily.dev/posts/how-microsoft-sees-engineering-bottlenecks-changing-with-ai-i7vvtyy23","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/how-microsoft-sees-engineering-bottlenecks-changing-with-ai-i7vvtyy23"},"datePublished":"2026-08-07T15:51:23.911Z","dateModified":"2026-09-14T06:29:15.280Z","description":"Tim Bozarth, Microsoft's CVP of CoreAI and leader of the Engineering Thrive initiative, discusses how AI is reshaping engineering productivity measurement and...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/9a75f42c4682318621450e9758792880?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/9a75f42c4682318621450e9758792880?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Engineering Enablement","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Engineering Enablement","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/3c8216b036d34c1cbe1678385355f35d","url":"https://daily.dev/sources/engineering_enablement"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/how-microsoft-sees-engineering-bottlenecks-changing-with-ai-i7vvtyy23","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":3},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"microsoft,productivity,ai-coding,dora-metrics","timeRequired":"PT6M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Engineering Enablement","item":"https://daily.dev/sources/engineering_enablement"},{"@type":"ListItem","position":3,"name":"How Microsoft sees engineering bottlenecks changing with AI"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/how-microsoft-sees-engineering-bottlenecks-changing-with-ai-i7vvtyy23#faq","mainEntity":[{"@type":"Question","name":"What percentage of engineering time was historically spent on operations before AI tools became widespread?","acceptedAnswer":{"@type":"Answer","text":"Operations alone historically consumed roughly 70% to 80% of engineering time, with creating and operating software together accounting for more than 90% of total engineering time. Tim Bozarth, Microsoft CoreAI's Corporate Vice President, notes that on frontier teams using AI, code creation now takes dramatically less time, shifting the bottleneck toward planning and validation instead. Engineering leaders rethinking where time actually goes under AI-assisted workflows can track this shift via daily.dev."}},{"@type":"Question","name":"Why is code review considered a confidence bottleneck rather than just a throughput problem?","acceptedAnswer":{"@type":"Answer","text":"Code review is really about establishing confidence that a change is trustworthy, not simply inspecting code line by line. Higher pull request throughput from AI-generated code has increased the volume of change humans must evaluate, and confidence can also come from testing, continuous rollouts, feature flags, and canary deployments rather than manual review alone. Teams debating how to scope code review around AI-generated changes can follow this discussion on daily.dev."}},{"@type":"Question","name":"Should engineering teams go back to measuring lines of code and pull request counts to track AI's impact on productivity?","acceptedAnswer":{"@type":"Answer","text":"No, activity metrics like lines of code and pull request counts are considered inadequate measures that the industry already rejected years ago. Tim Bozarth of Microsoft CoreAI argues that more engineering activity does not necessarily mean more value, and recommends outcome-based metrics instead, such as product quality, end-to-end speed, and idea-to-value, which are harder to game than any single activity measure. Leaders deciding how to measure AI's real impact on their teams can weigh this outcomes-first approach on daily.dev."}}]} ```