Field noteAug 4, 20261 min read1 source

Ant Murphy Argues Cheap Coding Moves Product Work Beyond Epics

Ant Murphy argues that product work should be managed through outcomes, opportunities, assumptions, and measurable experiments rather than epics and user stories.

In one minute

The AI-era angle is that when implementation gets cheaper, product management shifts from specifying work packets to validating outcomes and assumptions.

New Runtime synthesiseditorial-diagram
A whiteboard split diagram contrasting epic backlog work packets with an outcome-led loop of assumptions, experiments, and measured learning.
New Runtime synthesis.New Runtime synthesisOriginal source ->

Ant Murphy's argument against epics and user stories fits the AI software moment because coding is becoming less of the scarce bottleneck.

If implementation gets cheaper, the weak link moves upstream. A team can generate more tickets, more code, and more variants, but that does not mean it knows which customer outcome matters or which assumption is false. Managing through outcomes, opportunities, assumptions, and measurable experiments is a better control loop than managing through a backlog of work packets.

For New Runtime, the point is practical: agentic coding increases output, so product leadership needs a tighter validation frame. The unit of management becomes the verified outcome, not the user story that caused code to exist.

Evidence / sources

  1. 1antmurphy.me/newsletter/stop-using-epics-and-user-stories
All Field Notes

Next reads

Read next

Open the graph
  1. 01topicProduct ManagementExplore the product-management topic hub.
  2. 02topicAi SoftwareExplore the ai-software topic hub.
  3. 03topicWorkflow DesignExplore the workflow-design topic hub.
  4. 04archiveField NotesOpen the latest editorial analysis.
  5. 05source ledgerSource LedgerInspect the public source evidence graph.
Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate...

Open the JSON contract