Field Notes, page 2 — Design Outcomes

NIELSEN NORMAN GROUP

LDLR DESIGN FIELD NOTES

Product sense is a closed loop

Kohler rebuts the empathy-plus-creativity definition: sense is pattern recognition built by facing problems, shipping solutions, and staying to see the results.

JUL 24, 2026

A Concrete Definition of "Product Sense" (and How to Build It)

AI may rob you of the chance to develop product sense if you aren't careful.

Why it matters

— Against Walter's empathy-plus-creativity: sense is pattern recognition from completed loops

— Fire chiefs, NICU nurses, chess grandmasters: intuition built by seeing outcomes

— Wicked situations feel like pattern matches and reinforce the wrong lesson

— Stay long enough to see results; document your logic before looking at them

— Half-loop builders feel experienced but never learn whether the building collapsed

Read on Nielsen Norman Group →

Critique & decision-making Research & validation

NIELSEN NORMAN GROUP

LDLR DESIGN FIELD NOTES

Context is the new UX deliverable

When PMs and engineers prompt, every generation is a design decision. Alicea's answer: stop writing documents that persuade humans and curate context that steers models.

JUL 24, 2026

UX-Context Design: Using UX Knowledge to Inform AI-Generated Design

Its success is measured by whether AI output improves, not by whether stakeholders are convinced by it.

Why it matters

— When PMs and engineers prompt, every generation is a design decision

— Personas persuade humans; models need the underlying reasoning instead

— Proposes UX.md beside DESIGN.md: research synthesis, glossary, user and world models

— Research findings become generation constraints, not insights in a report

— Continuously curated beside the code; there is no handoff moment

Read on Nielsen Norman Group →

Systems & primitives Research & validation Cross-functional & process

LINEAR

LDLR DESIGN FIELD NOTES

Recurring work, wound up once

Loop engineering jumps from individual developer habit to team infrastructure: describe a recurring job in plain language and the agent runs it with workspace context.

BY NAN YU / JUL 20, 2026

Introducing Loops

Describe the job in plain language and then choose whether it should run on a schedule or in response to an event.

Why it matters

— Loop engineering jumps from individual developer practice to team infrastructure

— Plain-language job descriptions become scheduled or event-driven agent operations

— Runs from full workspace context: issues, projects, documents, connected tools

— Triage loops can review code and start a fix before an engineer arrives

— Shared visibility: anyone can read instructions and inspect every run

Read on Linear →

Cross-functional & process Systems & primitives

LINEAR

LDLR DESIGN FIELD NOTES

Hardware is borrowing our habits

Boom is building a supersonic airliner and its engine at once, on software's rhythm: short cycles, tools built by every engineer, real parts in hand fast.

JUL 15, 2026

Boom Supersonic builds as fast as it flies

A part you can hold teaches you more than a part you can only model.

Why it matters

— Building Overture and its Symphony engine together, refined against each other in-house

— Aerospace habits date to the 1990s: long planning, slow specialist handoffs

— Every engineer is expected to build tools that streamline their own work

— Software engineers sit with hardware teams instead of a separate world

— XB-1 already flew past the speed of sound without a boom reaching the ground

Read on Linear →

Prototyping & exploration Cross-functional & process

PROOF OF CONCEPT

LDLR DESIGN FIELD NOTES

Step into the pocket, don't scramble

Quarterbacks under a blitz buy time by stepping toward pressure, not fleeing it. Hoang maps the move onto tech's three blitzes and the drift that follows panic.

JUL 26, 2026

Climbing the pocket of pressure

Scrambling out of the pocket creates more vulnerabilities for the quarterback and often creates chaos from the originally intended play.

Why it matters

— Quarterbacks buy time by stepping toward pressure, not fleeing it

— Three blitzes named: competitors on your roadmap, more-with-less, shifting priorities

— Internal pressure comes up the middle; speed collapses the pocket faster

— Avoid the drift: movement without progress, staring at the rush not the field

— Defer blame until the play ends; retrospectives don't steer sinking rafts

Read on Proof of Concept →

Critique & decision-making Hiring & team

THE MERHOLZ AGENDA

LDLR DESIGN FIELD NOTES

Sentiment is an org outcome, not a mood

Twenty exec interviews, the Config crowd, and a 458-response pulse check converge: how your org behaves predicts how design feels about AI.

JUL 23, 2026

The sentiment around AI + Design is... complicated

The bifurcation isn't out there, it's within us.

Why it matters

— Twenty VP-plus interviews, Config crowd-work, and a 458-response pulse check behind this

— Roller Coaster is the plurality sentiment at 26%; the split runs within people

— The less AI-mature the org, the more negative its people, security included

— Directors sit with managers at 33% negative; VPs step-change to 34% positive

— His prescription is grace at scale, created by whoever holds the agency

Read on The Merholz Agenda →

Research & validation Hiring & team Cross-functional & process

LENNY'S NEWSLETTER

LDLR DESIGN FIELD NOTES

The fault line is identity, not role

The second annual tech-worker sentiment survey finds an industry splitting along AI identity, with designers and researchers at the anxious edge.

JUL 7, 2026

How tech workers are feeling in 2026: a workforce splitting in two

Every gain becomes the new baseline, and the people expected to hit it are running out of room to breathe.

Why it matters

— AI identity beats role, level, and company size combined as an optimism predictor

— Significant burnout jumped from 44.7% to 55.7% in a single year

— 53% would steer a newcomer away; the field's NPS lands at minus 39

— Designers report the most overwhelm, the worst-rated managers, and the biggest comp squeeze

— Top fear isn't replacement at 22%; it's more output for the same pay at 51%

Read on Lenny's Newsletter →

Research & validation Hiring & team

PROOF OF CONCEPT

LDLR DESIGN FIELD NOTES

Taste is a training regimen

Hoang rejects taste-as-gift and lays out four deliberate practice areas — eye, hand, aesthetics, rhetoric — for training design judgment like a discipline.

JUL 19, 2026

Training design senses

Experience isn't time spent; it's evidence of what you can do.

Why it matters

— Agentic tools without foundations: a DJ set handed to a pianist-in-training

— Train the eye by capturing, collecting, and curating what you notice daily

— Copy the masters: reconstruct interfaces from scratch and ask why each margin works

— Aesthetics come third, once the eye and the hand can keep pace with each other

— Rhetoric sharpens judgment: if you can't explain a call, intuition is ahead of reasoning

Read on Proof of Concept →

Craft & detail Critique & decision-making Storytelling & narrative

MC DEAN

LDLR DESIGN FIELD NOTES

Abundance is the new management problem

Production capacity stopped being the constraint. Dean maps what design leaders manage instead: judgment, team cohesion, and the moment to stop generating.

JUL 23, 2026

Design Leadership Just Got Harder

Deciding what good means when the machines will hand you a thousand versions of fine.

Why it matters

— Anchored in the AI in Design Report: 900+ designers, leaders at Anthropic, Stripe, Shopify

— Designers reporting decreased collaboration jumped roughly four-fold in a single year

— Encode your taste so the team and the AI have something concrete to aim at

— Be the one who says stop; endless generation drowns teams in options

— Evaluation systems still measure the old job while expecting AI-native judgment

Read on Substack →

Hiring & team Critique & decision-making Cross-functional & process

DESIGN SYSTEMS COLLECTIVE

LDLR DESIGN FIELD NOTES

Execution got cheap. Understanding didn't.

A designer watches AI produce complete outcomes without touching the reason they exist, and argues design's scarce skill is now interpretation.

JUN 22, 2026

AI Didn't Break Design. It Exposed It.

Execution is becoming cheap and abundant. The real scarcity is understanding.

Why it matters

— AI slipped into design's own layer: pattern recognition and structured decision-making

— Treating AI as a tool locks attention on prompts; it is a meaning-making layer

— Context can be engineered; intent stays unspoken and is harder to construct

— Design systems shift from systems of appearance toward systems of understanding

— The value question isn't which tool next, it's where your value sits now

Read on Design Systems Collective →

Systems & primitives Critique & decision-making

GEOFFREY LITT

LDLR DESIGN FIELD NOTES

Understand to participate

Litt argues understanding agent-written code keeps you fluent enough to have the next idea, and offers four techniques for getting there.

JUL 2, 2026

Understanding is the new bottleneck

A quiz is a speed regulator.

Why it matters

— Agents now verify their own work, so understanding buys creative participation instead

— A project is many loops, and fluency is what lets you have the next idea

— His /explain-diff skill outputs literate diffs: background first, intuition before code

— Every explainer ends in a five-question quiz he won't ship without passing

— Micro-worlds: he had an agent build a debugger so he could learn the system himself

Read on their blog →

Critique & decision-making Prototyping & exploration Cross-functional & process

UX COLLECTIVE

LDLR DESIGN FIELD NOTES

The what slips, one decision at a time

A product designer with no technical background shipped an agent that grades agents, and felt the what start sliding toward the machine.

BY FRANCISCO BARRERA AROS / JUL 10, 2026

The crisis of the what

Nobody handed the what to AI in a strategy meeting.

Why it matters

— He's a product designer with no technical background who shipped an agent that grades agents

— The how was always negotiable; he argues the what is now in play too

— He parts ways with Thompson's map, which holds the what until superintelligence

— The handover comes through small decisions that look like pure execution

— What survives, in his read: judgment built through experience, intuition with scars

Read on UX Collective →

Critique & decision-making Prototyping & exploration