{"version":"1.0","type":"rich","provider_name":"Acast","provider_url":"https://acast.com","height":250,"width":700,"html":"<iframe src=\"https://embed.acast.com/$/659557afc7c0640016f29135/6a1051742912aeb1d09bcddb?\" frameBorder=\"0\" width=\"700\" height=\"250\"></iframe>","title":"Claude Code at the Organization Layer: What Actually Changes","thumbnail_width":200,"thumbnail_height":200,"thumbnail_url":"https://open-images.acast.com/shows/659557afc7c0640016f29135/1779454272068-d468a3b5-5665-4ded-97af-b4d689867013.jpeg?height=200","description":"<h1>What Actually Changes When Claude Code Reaches the Whole Engineering Organization</h1><h3><br></h3><h3><br></h3><h3>Metrics That Actually Matter</h3><p><strong>Stop measuring:</strong></p><ul><li>Lines of code per developer</li><li>Token consumption</li><li>Individual productivity</li></ul><p><strong>Start measuring:</strong></p><ul><li>Cycle time (Claude-assisted vs non-assisted PRs)</li><li>Time to first PR for new hires</li><li>PR throughput with quality counterweight (defect rate, rollback frequency)</li><li>Incident resolution time</li><li>Maintenance burden trajectory</li></ul><h3>Non-Engineers Building Software</h3><p><strong>Examples from one company:</strong></p><ul><li><strong>Support team:</strong> Tool surfacing relevant past tickets and customer history</li><li><strong>Finance team:</strong> Expense categorization assistant</li><li><strong>HR team:</strong> Onboarding checklist app pulling from live systems</li></ul><p><strong>What engineering built:</strong></p><ul><li>Architecture patterns for internal apps</li><li>Plugin marketplace with pre-approved skills/MCP connections</li><li>Managed permissions (read from X, write to Y, not Z)</li><li>Audit logs for AI-generated changes</li></ul><p><strong>The shift:</strong> Engineering didn't build the apps. Engineering built the conditions under which apps could be built safely.</p><p><br></p>","author_name":"Danar Mustafa"}