Working Surfacelink · 31 Oct 2026
04
A ship's autopilot steers from a paper chart fed into its wheel, while a lookout seen from behind climbs the mast with a telescope toward open sea the chart does not show, the whole scene drawn with wide empty margins on every side.
Nielsen Norman Group

The Role of UX in Agentic Software Factories

Tanner Kohler · 30 October 2026

Company story · roles · critique & review · Changing roles

Read the original
Takeaway

Tanner Kohler of Nielsen Norman Group finds that Anthropic's playbook for AI-built software gives user experience staff no stage or approval, and urges them to claim the context agents read.

Summary

Tanner Kohler is a researcher at Nielsen Norman Group, a user experience research firm. Kohler examines a playbook Anthropic published in August 2026, in which AI agents do most of the work and product owners and engineers approve a chain of Markdown documents. User experience knowledge appears only as context for the agents, and the playbook never mentions user research.

Key points
  • In the playbook the product owner approves each idea and iterates on the AI-generated mockup, and engineers approve the plan and each release. No stage or approval belongs to user experience staff.
  • The test stage compares the built screen with the product owner's mockup, so a flaw introduced early passes unchallenged. Monitoring watches system health, so a confusing feature that people abandon shows no distress.
  • Kohler advises practitioners to draft the organisation's user experience skills and attach their names, so that they are brought in when a spec raises a concern.
  • Kohler also advises writing down which changes need a person's review, such as changes to navigation, and adding signals such as task abandonment and support ticket spikes to the monitoring.
Implication

A design team whose company is moving to AI-built software can decide now who owns the context the agents read and which changes must come to a person. The piece is written by a firm that sells training in this field, and it examines one playbook rather than a team's results.

Plays
Design

Write into the AI agents' user experience context which changes need a person's review, such as changes to navigation or flows that depart from conventions.

Engineering

Add task abandonment, conversion drops and support ticket spikes to the monitoring of deployed software, so that a drop in user success gets the same automated response as a spike in server errors.

Derived by Working Surface from the article; more in the Playbook. Source line: Context can encode only what we already know.

Source issue

31 October 2026: as AI agents produce more of the work, teams move the checking to the people and records closest to the real output.