DEVOURED
When everyone has AI and the company still learns nothing
Companies are pouring millions into GitHub Copilot and Claude licenses but capturing zero organizational learning because individual AI productivity gains stay isolated in code reviews and Slack threads that never become shared capabilities.
What: Robert Glaser argues that AI adoption has entered a "messy middle" where tools are everywhere but learning stays local. One engineer delegates root-cause analysis to Claude and saves two weeks; a support team automates tickets; a product owner prototypes real software—all in the same company, none of it visible to leadership or shareable. He references Ethan Mollick's "Leadership, Lab, Crowd" framework and proposes three organizational capabilities: Agent Operations (governance and control), Loop Intelligence (measuring which AI workflows create learning vs. sprawl), and Agent Capabilities (distributing useful patterns). Core proposal: a "Loop Intelligence Hub" that instruments actual work loops to identify which teams need tighter guardrails, which patterns should move to the platform, and which workflows are ready for looser delegation.
Why it matters: AI inverted the iteration constraint—prototyping is cheap, organizational learning is hard—but companies still use change management built for expensive iteration (sprint planning, handoffs, brown bags). As token costs become metered, the competitive advantage is shifting from model access, which can be rented, to learning velocity: who moves AI discoveries from individuals to organizational capabilities fastest.
Deep dive
- Mollick's key insight: individual productivity gains from AI don't automatically become organizational gains—people get faster, companies learn nothing
- The "messy middle" starts when AI use is everywhere, uneven, hidden, and disconnected from organizational learning—the adoption unit is no longer the organization or team, but "the loop inside the work"
- Real AI work happens inside code reviews, production incidents, product prototypes—by the time it becomes a best-practice slide, "the important learning has often lost its teeth"
- Modern software process (sprint planning, estimation, standups) exists because human iteration used to be expensive; AI makes iteration cheap but organizations still ask for two-week sprint commitments
- The "open bar" of unlimited token usage won't last—model routing, token budgets, usage-contingent pricing will force the question "what changed because we spent those tokens?" not "how much did we spend?"
- Three necessary capabilities: Agent Operations (control), Loop Intelligence (learning), Agent Capabilities (distribution)—"one without the others gets weird quickly"
- Proposes a "Loop Intelligence Hub" or "feedback harness" that instruments real work loops to understand where AI creates leverage vs. sprawl, which teams need tighter guardrails, which patterns should become platform capabilities
- Critical governance risk: if this becomes employee surveillance or productivity scoring, "people will game the signals" and hide their best workflows—"the company will get the worst possible version of adoption: visible compliance and invisible learning"
- The competitive advantage is learning velocity—"access to frontier intelligence can be rented, but operational control and organizational learning cannot"
Decoder
- Agentic engineering: AI-assisted software development where engineers delegate multi-step tasks to AI agents that can iterate, make decisions, and produce working software with varying levels of human oversight—ranges from tight synchronous "co-driving" to loose asynchronous delegation
- Dark factory: Manufacturing term for fully automated production requiring no human presence; used here metaphorically for software workflows where AI handles entire classes of components from intent to tested output with minimal human intervention
- Loop Intelligence: Proposed capability for measuring which AI-assisted work loops produce organizational learning versus isolated productivity gains or aimless sprawl—tracks whether teams are ready for looser delegation or need tighter guardrails
- Elastic loop: Framework from Glaser's earlier work describing how AI collaboration stretches from tight synchronous pairing to loose asynchronous delegation depending on context, risk, and team capability
Original article
Access to frontier intelligence can be rented, but operational control and organizational learning can not.
Explore all 66 articles in today's digest
Fresh dev news, AI-digested daily. Never miss a trend at devoured.fyi