HeyDesigner · 8 Jun 2026Loop engineeringAddy Osmani argues that individual prompt-crafting is being replaced by 'loop engineering' — designing automated systems with five components (scheduled automations, worktrees for parallel agents, skills files encoding project knowledge, tool connectors, and sub-agent verification) plus persistent memory that run coding agents continuously without human intervention. Boris Cherny, head of Claude Code at Anthropic, is cited as evidence this is now operational practice, not theory.
When coding loops replace human-in-the-loop prompting, the quality ceiling shifts entirely to the 'skills' files — structured documentation of project conventions — meaning teams without mature, machine-readable component specs and design system contracts will produce higher-variance, lower-quality output at greater token cost than teams that have invested in documentation infrastructure.
Roman Pichler argues that as AI tools automate data analysis, backlog management, and prototyping, emotional intelligence — specifically self-awareness, empathy, and the ability to manage stakeholder conflict — becomes the primary non-replicable differentiator for product managers. The piece frames EQ not as a soft supplement to PM craft but as the core competency that determines whether AI-augmented PMs make better strategic decisions or worse ones with faster throughput.
As AI tooling compresses the time PMs spend on synthesis and documentation, the quality of human judgment in discovery, prioritisation, and stakeholder alignment becomes the rate-limiter for product outcomes — which means EQ deficits that were previously masked by busyness become visible and consequential.
John Cutler argues that organisations mandating AI adoption are systematically destroying the psychological conditions — agency, trust, and dignity — required for teams to actually innovate with AI. Drawing on Bandura's social cognitive theory, he distinguishes between individual agency (how a person adapts to AI on their own terms) and organisational affordances for agency (the environment that enables or suppresses it), arguing that most corporate AI mandates conflate the two and produce compliance theatre rather than genuine capability.
Top-down AI adoption mandates without squad-level experimentation space will produce vanity metrics — AI usage rates, prompts per sprint — that mask whether the tooling is actually improving decision quality or product outcomes, creating a false confidence that compounds when leadership reads adoption rates as capability.
