Zendesk argues that generative AI has shifted the primary bottleneck in software delivery from writing code to what it calls 'absorption capacity' — the organizational ability to define problems clearly, integrate changes coherently, verify correctness, and turn implementation into reliable value. As code generation becomes cheap and fast, the real constraints become architectural coherence, review capacity, and delivery flow. Zendesk proposes four responses: making problem framing a shared product-engineering responsibility, strengthening verification loops (CI, static analysis, observability), using architecture conventions and ADRs as scaffolding for AI-assisted work, and measuring throughput metrics (lead time, change failure rate) rather than output metrics (lines of code, PR volume). The key insight is that AI amplifies whatever structures already exist — clear systems accelerate well, while architecturally drifted systems see inconsistency amplified.
1 Comment
Sort: