Field Notes, page 4 — Design Outcomes

THE MERHOLZ AGENDA

LDLR DESIGN FIELD NOTES

Illegible, not sloppy

Merholz borrows Scott’s legibility lens: businesses fund determinate work, and design’s best moves are indeterminate.

AUG 5, 2026

Design's Legibility Gap

Where the forest had 'board feet,' UX/Design has screens to be built by engineering.

Why it matters

— Prussian scientific forestry grew one beautiful generation; the second collapsed

— Organizations value predictability; predictability requires determinacy; determinacy defines legibility

— Four concepts explored, one chosen — three become invisible to the business

— Every other function passed through business rationalization; design never did

— The ROI of UX is a fool's errand; widen what counts as legible instead

Read on The Merholz Agenda →

Storytelling & narrative Cross-functional & process

FAST COMPANY

LDLR DESIGN FIELD NOTES

Design molts again

Fuller files the AI panic in a 70-year lineage of design deaths, with Figma literally staging the funeral.

AUG 6, 2026

Design is on its deathbed. Long live design!

Design isn't just what it looks like or how it works anymore: Design is how it feels.

Why it matters

— Figma staged a literal funeral pop-up: flowers, black hats, 'Design Is Dead'

— BLS counts near half a million designers, up from 200,000 in 2004

— Figma's own survey: 56% of non-designers now do design work

— Herbert Spencer warned about printing's technical changes in 1958; same speech, new tools

— Lewenstein predicts a service design comeback; Ouilhet coins 'humorphism' for human-scale AI

Read on Fast Company →

Storytelling & narrative Craft & detail

UX COLLECTIVE

LDLR DESIGN FIELD NOTES

Rotate the point of the V

Yeo turns murmurations and goose formations into an operating model: rotating leads, domain pods, and a scheduled molt.

AUG 13, 2026

Rethinking design leadership with swarms and flocks

Nobody can break wind at the front indefinitely without burning out.

Why it matters

— Starlings track only six or seven neighbors; V-formations save 14% metabolic energy

— Honking comes from the back: swap status meetings for async telemetry, 24-hour replies

— Led two launches back-to-back? Hand off the point, and protect it in calibration

— Pods of three or four designers per domain, with a Staff-level craft guardian

— Cap non-negotiable principles at three; schedule a flightless molt for design debt

Read on UX Collective →

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

NUBANK

LDLR DESIGN FIELD NOTES

The bank’s sketchbook

Nubank threw open its studio: 400 seats, a brand refresh, and Eismann closing. Design culture as a public event.

AUG 5, 2026

Nu Design Day

Real cases, learnings at scale, and strategies told by the people who make them.

Why it matters

— First public design event: 400 free seats in São Paulo, gone fast

— Agenda doubles as an org chart: craft, research, content, brand, careers

— Noah Levin argued the PDLC is collapsing into one continuous loop

— A brand refresh presented as feeling: image, sound, and product together

— Recordings promised; the recap is the field note to watch for

See the event page →

Hiring & team Storytelling & narrative Craft & detail

LENNY'S NEWSLETTER

LDLR DESIGN FIELD NOTES

Excellence as an OS

Stone runs engineering, product, and design as one system. Her AI-era hiring bar: systems thinkers, fluency for all.

JUL 19, 2026

Why Netflix is betting on systems thinkers—not specialists—in the AI era

AI fluency as a universal expectation rather than a level-specific skill.

Why it matters

— Systems thinking is now the first skill she screens for

— AI fluency is a universal expectation, not a level-specific skill

— Fewer, more senior PMs; managers spend most of their time making

— The new management problem: the flood of AI output, without losing signal

— Excellence works as an operating system, not a slogan

Listen on Lenny's Podcast →

Hiring & team Cross-functional & process

SLACK DESIGN

LDLR DESIGN FIELD NOTES

Adequate became free

Fernandez turns Butterfield’s 2013 promise into a frame with a gut-check: are we proud to ship this?

BY MIGUEL FERNANDEZ / JUL 17, 2026

Product Quality: A Shared Commitment to Craft in the wake of AI

The distance from nothing to adequate has collapsed. The distance from adequate to loveable has not.

Why it matters

— Craft debt compounds like technical debt; you pay in churn and reputation

— Utility, usability, feel: one craft language across product, engineering, design

— The IKEA effect at scale: we overvalue whatever we prompted

— Looks-finished is not is-finished; visible behavior hides absent structure

— The bar: would I recommend this to someone I care about?

Read on Slack Design →

Craft & detail Critique & decision-making Cross-functional & process

PROOF OF CONCEPT

LDLR DESIGN FIELD NOTES

The next user isn't human

Hoang names the discipline forming around agents as users: access, context, tools, and parallel paths for two minds.

AUG 2, 2026

Agent Experience

Why force an octopus to open a jar with two tentacles because you as a human have two hands?

Why it matters

— Agents are users now: design for access, context, tools, orchestration

— Same goal, parallel paths: search bar for humans, direct query for agents

— Agents don't complain; observability must surface retries, dead ends, silent failures

— Documents go bidirectional: hierarchy for people, structure and metadata for agents

— He asks his agents to run a retro and file feedback

Read on Proof of Concept →

Systems & primitives Prototyping & exploration Cross-functional & process

DESIGN SYSTEMS COLLECTIVE

LDLR DESIGN FIELD NOTES

The rulebook compiles

Williams, from Morales’s talk: latency was your reviewer. When agents erase the wait, governance ships as an output.

JUL 13, 2026

Governance Becomes an Output

Governance doesn't have to be a manual fight. It just has to be encoded.

Why it matters

— Slow production looked like discipline; mostly it was latency doing review

— Remove the clock and the checking goes undone, loudly, all at once

— Morales's build: encode conventions into agents so governance ships as output

— Infrastructure can only encode what the team actually agreed on first

— Ask first: does your system know what it is?

Read on Design Systems Collective →

Systems & primitives Critique & decision-making

GITHUB

LDLR DESIGN FIELD NOTES

Patch as price check

The forty-minute scope debate costs more than the diff now. Abuadas ships a constrained probe and argues from evidence.

BY DALIA ABUADAS / JUL 17, 2026

The cost of saying yes has changed

A thousand-line diff that technically passes but nobody wants to own is not a cheap change. It's a deferred cost.

Why it matters

— The most expensive part of a small request is now the meeting about it

— Generate the first patch as a probe; argue from the diff, not from vibes

— Four-line diff with passing tests: ship it; touches auth middleware: it was never small

— Constrained attempts: smallest patch, behind the flag, contract unchanged, every touched file listed

— The new skill is pricing uncertainty fast, not defaulting to yes or no

Read on GitHub →

Critique & decision-making Cross-functional & process

NIELSEN NORMAN GROUP

LDLR DESIGN FIELD NOTES

Sense is a closed loop

Kohler rebuts empathy-plus-creativity: sense is pattern recognition built by shipping 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, not documents

Every prompt is now a design decision. Alicea’s answer: stop persuading 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

Wound up once

Loop engineering becomes team infrastructure: describe a recurring job in plain language and the agent runs it.

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