Cross-functional &amp; process

THE MERHOLZ AGENDA

LDLR DESIGN FIELD NOTES

Directors own the how

Merholz maps why AI lands hardest on UX Directors: the mandate is the How, and the How is theirs alone.

SEP 21, 2026

The Ongoing Plight of the UX Director

Executives own the Why, Directors the How, and AI adoption is the How.

Why it matters

— AI adoption is tooling and process, the How, and the How belongs to Directors

— Mandates arrive with no guidance during the worst technology rollout in history

— The ratio math: a Director over 20 sits peered against a VP over 160

— The 2021 hyperscaling cohort is stuck: orgs flatten and VP roles vanish

Cross-functional & process Storytelling & narrative

NIELSEN NORMAN GROUP

LDLR DESIGN FIELD NOTES

The byline still binds

NN/g's editor opens the workflow: AI drafts, critiques, compresses. A human expert still signs every claim.

BY RALUCA BUDIU / SEP 11, 2026

AI Can Help Write an Article, but It Can't Stand Behind It

AI may contribute words and even ideas, but humans remain responsible for editorial judgment.

Why it matters

— The EU AI Act exempts content under human review; that clause is the hinge

— AI rewrites for concision, hits the 160-character summary, adapts reports into articles

— ChatGPT caught a contradiction in an earlier draft of this very article

— The kicker: NN/g's AI content policy was itself AI-drafted, then human-approved

Read on Nielsen Norman Group →

BUILDING NUBANK

LDLR DESIGN FIELD NOTES

Skills are dependencies

Palma and Martins gate the marketplace: 2,000 skills vetted, 1,600 risks flagged, before one reached a developer.

BY LUCAS PALMA AND PAULO MARTINS / SEP 2, 2026

When AI skills become supply-chain dependencies

A prompt can suggest behavior, but a control outside the model can enforce it.

Why it matters

— Skills read like documentation, but their operational effect is a dependency

— Skill Vetter gates the marketplace: 2,000 scanned, 1,600 risks, 1,000 remediated

— Deterministic rules catch known patterns; an LLM reads intent across instructions

— Ask-before-running lives in the prompt, so the model approves its own action

— Local checks plus CI make the safe path the easiest path

Read on Building Nubank →

Systems & primitives Cross-functional & process

DESIGN SYSTEMS COLLECTIVE

LDLR DESIGN FIELD NOTES

Make breaking it hard

Kumar’s five layers for agent-built UI: tokens, components, context, discovery, and enforcement wired into CI.

BY RAKESH KUMAR / SEP 11, 2026

AI-Generated UI Needs a Design System That Can Enforce It

Don’t ask AI to remember your design system. Make violating it difficult.

Why it matters

— The agent’s dashboard compiled, then shipped a second table component anyway

— Context tells AI what the system is; enforcement tells it what it cannot violate

— An MCP server exposes the contracts; compliance still lives in the pipeline

— Raw hex, arbitrary spacing, and duplicate components all fail the build

— Compliance becomes a metric: token usage, custom components per agent PR

Systems & primitives Cross-functional & process

NIELSEN NORMAN GROUP

LDLR DESIGN FIELD NOTES

Sweep once, teach twice

Kaley and Budiu name the custodial era: production got cheaper than evaluation, so UX triages what already exists.

BY ANNA KALEY AND RALUCA BUDIU / AUG 28, 2026

The Custodial Era of UX: Cleaning Up After AI

It can now take less time to create an experience than to decide whether that experience is useful, usable, trustworthy, or coherent.

Why it matters

— The custodial pattern, five steps: new idea, rapid production, lagging evaluation, user problems, UX cleanup

— Triage before polishing: evidence of need, mental-model fit, integration cost, opportunity cost

— The outcome isn’t always “redesign it” — keep, simplify, integrate, postpone, or remove

— Match evidence to risk: quick tests for low-stakes features, rigor reserved for high-stakes workflows

— Feed cleanup lessons back into generation: UX-context files, design systems, content standards

Read on Nielsen Norman Group →

Critique & decision-making Cross-functional & process Research & validation

LINEAR

LDLR DESIGN FIELD NOTES

Three of every four PRs

Ramp built Inspect with six years of Linear as its memory. The agent now writes three of every four merged PRs.

AUG 31, 2026

The coding agent behind 75% of Ramp’s merged PRs

The speed has moved Ramp’s bottleneck from writing code to reviewing it, a constraint any company running agents at this scale will meet.

Why it matters

— Inspect started as a casual idea; three engineers shipped the first version in two weeks

— Built in-house so it fits Ramp’s lifecycle exactly: one API key, their own log schemas, their sandboxes

— A designer takes a dashboard rework most of the way from Figma, then hands the live session to an engineer

— In Slack, “@Inspect, fix this” is often all it takes to open a PR

— A central team defines what agents can access, so functional teams automate safely on shared rails

Prototyping & exploration Craft & detail Cross-functional & process

FIGMA

LDLR DESIGN FIELD NOTES

The prototype pitched

King vibe-coded the WebGPU canvas he’d imagined for years, recruited the team it earned, and shipped in two months.

BY ROGIE KING / SEP 1, 2026

Behind the build: Generative plugins and shaders at Figma

While it had taken us months to build progressive blur in Figma Draw, I could now create the same shader effect with one simple prompt — maybe two to nail it.

Why it matters

— Show, don’t tell: the “FigGPU” prototype did what a years-old obsession and a Loom in Slack never could

— Yassir Solomah validated it for real, replacing WebGL 2 fragment shaders with sandboxed WebGPU pipelines

— Two months to Config: no PRDs, no crits, demos over formal reviews, one massive Slack channel

— The reversal: vibe-coded prototypes served designers but failed developers and PMs — static mocks realigned the team, then code took over

— PropsKit, a web-components Figma UI kit, exists so agent-built plugins look and feel native

Read on Figma →

LINEAR

LDLR DESIGN FIELD NOTES

Fence the cascade, too

Skovhus turns a 1,000-PR styling migration into a boundaries argument: contracts enforced by tooling, built for agents.

BY KENNETH SKOVHUS / AUG 26, 2026

Styling Linear for the future with StyleX

Many of the patterns that are hardest to migrate are the ones that made the old system difficult to reason about at scale.

Why it matters

— Non-negotiables: build-time styles, explicit contracts, deterministic merging, safe long-term bet

— Styling at a distance made deliberately difficult, not discouraged by convention

— Deterministic codemod first; agents took more load as models improved mid-project

— A dev-bar counter and per-component highlighter made progress visible and social

— Lint rules and a type-aware repo checker enforce the conventions afterward

Systems & primitives Craft & detail Cross-functional & process

DESIGN SYSTEMS COLLECTIVE

LDLR DESIGN FIELD NOTES

Pieces, never the puzzle

Donald, a career systems hand, suspects we’ve outgrown design systems and sketches the one that absorbs the product.

BY DAN DONALD / AUG 27, 2026

Do we still need design systems or do they evolve to become something more?

We have the pieces but rarely do we see the puzzle — the products, the features or the journeys they're being used for.

Why it matters

— Design systems stop at patterns; products, features, and journeys stay out of scope

— His coinage: Digital Product Systems, owning business context down through tokens

— Making docs clearer for machines made them better for humans too

— If the system generates the product, the job shifts to system integrity

— New problems, not pattern-following, are where the people stay vital

Systems & primitives Cross-functional & process

LINEAR

LDLR DESIGN FIELD NOTES

Delete the IDE

Turakhia took the editor away from an entire org for two weeks: the old way of working lives there.

AUG 11, 2026

Coinbase's bet on agent-first development

Every conversation now starts with the same question. Why can't an agent do this, and how do we make it possible?

Why it matters

— Chintan Turakhia had every engineer delete their IDE for two weeks

— Coordination knowledge scattered across heads and Slack is a wall for agents

— Forge turns a Slack bug report into a labeled issue, a fix, and a PR

— Speedruns spread the workflows: one session, 500 PRs in fifteen minutes

— The tracked metric is autonomous operation time, and it keeps climbing

LINEAR

LDLR DESIGN FIELD NOTES

Hours up, not away

Qi’s report from 47,900 workspaces: AI writes half of everything in Linear, PRs are up 111%, and no time came back.

BY TIM QI / AUG 17, 2026

AI usage patterns in software teams

As far as we can observe, teams are working more, not less, suggesting AI has a Jevons paradox quality beyond token consumption.

Why it matters

— AI now authors just under half of everything created in Linear

— Product adoption climbed fastest, 12% to 34% in six months

— CEOs at 201+ companies went 9% to 36% — the report's largest jump

— Coding-agent teams tripled weekly PRs; teams without went 8 to 10

— Nothing shrank to make room — AI landed on top of existing work

Cross-functional & process Research & validation

DESIGN SYSTEMS COLLECTIVE

LDLR DESIGN FIELD NOTES

Local first, system later

Local components as signals, not violations: designers build in place, and the system team governs what earns promotion.

BY VEDANT / AUG 21, 2026

Let Designers Build. Let Design Systems Govern.

The maturity of a Design System isn't measured by how few local components exist.

Why it matters

— Local components are experiments; system components are governed contracts

— Six steps: build, validate in product, review, assess, contribute, publish

— Five teams building the same empty state is feedback, not violation

— Custodian becomes governor and enabler; designer becomes contributor

— Not every successful local pattern deserves promotion to the system

Systems & primitives Cross-functional & process Critique & decision-making

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

Storytelling & narrative Cross-functional & process

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

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 →

Craft & detail Critique & decision-making 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 →

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

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

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

LINEAR

LDLR DESIGN FIELD NOTES

Borrowing our habits

Boom builds a supersonic airliner and its engine at once, on software’s rhythm: short cycles, 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

Prototyping & exploration Cross-functional & process

THE MERHOLZ AGENDA

LDLR DESIGN FIELD NOTES

Sentiment is an outcome

Twenty exec interviews 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

Research & validation Hiring & team Cross-functional & process

MC DEAN

LDLR DESIGN FIELD NOTES

Managing abundance now

Production stopped being the constraint. Dean maps what leaders manage instead: judgment, cohesion, and when to stop.

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

GEOFFREY LITT

LDLR DESIGN FIELD NOTES

Understanding is fluency

Litt argues understanding agent-written code keeps you fluent enough to have the next idea, with four techniques.

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

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

BEN CALLAHAN

LDLR DESIGN FIELD NOTES

The skipped conversation

Callahan splits product quality in two: the design system sets the floor, and how product teams use it sets the ceiling.

JUL 5, 2026

What is product craft in the age of AI and design systems?

The worst product teams can make awful experiences with the best design systems.

Why it matters

— Craft is the skill to deliver higher quality over time; quality is the thing you'd measure

— A system raises the floor, but restraint and knowing when to deviate set the ceiling

— Four scenarios: only high craft on both sides produces a high ceiling

— He reverses himself, since enable-over-police left system teams out of the quality conversation

— The loop: co-define quality, craft toward it, evaluate, bake the wins into the floor

Systems & primitives Craft & detail Cross-functional & process

LINEAR

LDLR DESIGN FIELD NOTES

Review is judgment now

A Linear engineer on how agent-heavy review freed him from parsing lines to judging whether the work earns its place.

BY MACIEK PEKALA / JUN 10, 2026

Reviewing code in the agent era

this shift toward judgment is the one I actually see in my own work.

Why it matters

— PRs merged jumped 50% in a quarter, and rubber-stamping started to tempt him.

— Agents now cover correctness, so his reclaimed time goes to system fit.

— He asks whether the change solves the right problem, not just whether it works.

— Review becomes the rare moment teammates look at each other's work directly.

— Quality shifts from correct to useful: does this earn its place?

Critique & decision-making Cross-functional & process

FIGMA

LDLR DESIGN FIELD NOTES

Agents people can trust

Sheta Chatterjee walks the design calls behind Gemini Enterprise: a shared AI inbox and people kept in control.

BY SHETA CHATTERJEE / APR 29, 2026

How to design agentic tools for work

the user's focus should always be on their goal, not on managing AI

Why it matters

— One brand language up top, real differentiation down at the feature level.

— The guiding rule: keep focus on the goal, not on managing AI.

— An AI Inbox shows what each agent is doing and needs.

— Chat threads become shared project spaces, so the AI joins the team.

— Transparency and an obvious way to intervene, since the stakes are real.

Read on Figma →

Systems & primitives Cross-functional & process Craft & detail

MARTYN REDING

LDLR DESIGN FIELD NOTES

The leadership reckoning

Martyn Reding argues the old shape of design leadership is gone, and lays out what changed and how to adapt.

OCT 24, 2025

How to survive the design leadership reckoning.

Design leadership as we know it, is over, but it's going to be OK.

Why it matters

— The market's appetite for elaborate design-thinking practices has clearly cooled.

— Over 70% of 2024 leadership roles wanted craft skills and a portfolio.

— Fewer leadership techniques in the feed, more posts about burnout.

— The path forward mixes shape-shifting with a few solid foundations.

Read on Medium →

JAKOB NIELSEN

LDLR DESIGN FIELD NOTES

Redesign the workflow

Citing a 515-startup field experiment, Nielsen argues AI pays off when teams redesign whole workflows, not single tasks.

APR 9, 2026

Cross-functional & process Hiring & team

VANESSA BELENO

LDLR DESIGN FIELD NOTES

What ambiguity reveals

An early-career designer keeps reaching for connective work wherever structure is missing, and asks why.

JUN 18, 2026

BUILDING NUBANK

LDLR DESIGN FIELD NOTES

Simplicity is strategy

Five lessons from 127 million customers, where hiding complexity is a deliberate architectural and cultural decision.

BY MARISTELA CALAZANS / FEB 16, 2026

What changes when your product reaches 127 million people

Simplicity at scale is not a design preference. It's a strategic decision.

Why it matters

— Quarterly Customer Connection visits put teams in unstable-internet, older-device reality

— Accumulated friction, not catastrophic failure, is the real loyalty killer

— Caixinhas cut a dozen fund options to a two-step habit-building flow

— Global core, local nuance shipped Colombia's Bre-B six months faster

— Intelligent friction: slowing users down protects life savings on unusual transactions

Read on Building Nubank →

Cross-functional & process Research & validation Craft & detail

GITHUB

LDLR DESIGN FIELD NOTES

Accessibility, shipped

GitHub’s five-year program turns outward: audit data, design tooling, and AI agents make inclusion operational.

BY ED SUMMERS / MAY 21, 2026

Building GitHub's next chapter in accessibility

Accessibility is never done.

Why it matters

— Audit analysis found 48% of issues preventable in the design phase

— Figma Annotation Toolkit documents accessibility intent before a line of code

— Copilot triage auto-populates 80% of metadata, cutting resolution time 62%

— Pull request files-changed page rebuilt accessibly across seven shipped updates

— Copilot CLI shipped screen reader mode and colorblind themes from day one

Read on GitHub →

Systems & primitives Craft & detail Cross-functional & process

THE MERHOLZ AGENDA

LDLR DESIGN FIELD NOTES

Layoffs as contagion

Merholz reads layoffs through org theory: under uncertainty, executives copy each other, then call it AI strategy.

MAY 23, 2026

Monkey see, monkey mandate

The uninformed copy the foolhardy.

Why it matters

— Pfeffer named it years ago: layoffs spread by imitation, not evidence.

— Mimetic isomorphism, copying peers under uncertainty, explains RTO, AI mandates, and cuts.

— Token-spend quotas reward activity over impact, like counting lines of code.

— CEOs trust peers in other contexts more than the teams who know their own.

— The cost lands on people who were never in the room.

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

MEDIUM

LDLR DESIGN FIELD NOTES

AI ate the PM talk

A multi-agent read of 638 Lenny pieces, June 2019 to March 2026, charting what production loses and judgment keeps.

MAR 18, 2026

What 638 Practitioner Voices Reveal About Product Manager's AI Transformation

Speed raises the bar for where rigour is applied, rather than lowering it.

Why it matters

— AI-tagged content jumped from 4% of output to 67% in three years.

— Built transparently: five Claude agents reading the corpus, the method shown in full.

— Jenny Wen argues the design process designers were taught is effectively over.

— Products become organisms that learn, pushing pricing toward outcomes, not seats.

— What endures: conviction, taste, influence, and a focus on outcomes.

Read on Medium →

Research & validation Prototyping & exploration Cross-functional & process

UX COLLECTIVE

LDLR DESIGN FIELD NOTES

AI holds the context

Shakir’s workflow: the AI holds context across Linear, Slack, and research while the designer does the thinking.

MAY 15, 2026

How I use AI to partner on design problems

Why it matters

— The AI holds context across Linear, Slack, and research; you do the thinking.

— Code prototypes move feedback from visual details to actual UX problems.

— Bad ideas surface faster when they're running, not sitting in Figma.

— Decision tracking lives in a folder per round, not buried in comment threads.

— The longer the project runs, the more useful the accumulated context becomes.

Read on UX Collective →

Prototyping & exploration Cross-functional & process Research & validation

DESIGN SYSTEMS COLLECTIVE

LDLR DESIGN FIELD NOTES

Fund the infrastructure

Shadi Abd’s positioning move: frame system work as infrastructure with a named cost of inaction, at portfolio level.

MAY 15, 2026

How to Position System-Level Design Work So It Actually Gets Funded

Why it matters

— Frame it as infrastructure, not UX, or it gets deprioritized before the meeting ends.

— If you don't define the cost of inaction, leadership assumes there isn't one.

— The ask isn't an improvement; it's a block on compounding operational inefficiency.

— Four things need to be undeniable: the problem, the cost, the scope, and governance.

— Portfolio-level framing gets director attention; product-level framing gets project-scoped budget.

Cross-functional & process Storytelling & narrative Critique & decision-making

THE GITHUB BLOG

LDLR DESIGN FIELD NOTES

Taught what not to touch

GitHub’s accessibility agent reviewed 3,535 PRs at a 68% fix rate. The sharper lesson is what it won’t touch.

BY ERIC BAILEY / MAY 15, 2026

Building a general-purpose accessibility agent, and what we learned in the process

LLMs have an unfortunate bias towards producing accessibility antipatterns.

Why it matters

— Two sandboxed sub-agents, a reviewer and an implementer, beat a parallel swarm.

— A complexity score tells the agent when to stop and escalate.

— High-risk patterns like drag-and-drop and data grids are off-limits by design.

— Only 35 of 55 WCAG criteria are machine-detectable, so manual review still anchors the work.

Read on The GitHub Blog →

Craft & detail Cross-functional & process

SLACK DESIGN

LDLR DESIGN FIELD NOTES

Leading through AI

Slack’s VP of Product Design guides roughly 70 designers through AI without mandates, keeping the bar high.

BY WILL MINER / MAY 21, 2026

Cross-functional & process Hiring & team

DESIGN SYSTEMS COLLECTIVE

LDLR DESIGN FIELD NOTES

AI didn't add to the spec

AI-readiness is the old spec finally enforced: tokens, layout intent, and governance now have to read to a non-human.

APR 27, 2026

Legible by Design: What AI Readiness Actually Demands of a Design System

The best systems are the ones that remain coherent even when the people who built them have moved on

Why it matters

— AI doesn't need a new system. It exposes the broken one.

— Five load-bearing properties: tokens, layout intent, a11y, governance, handoff.

— Legibility to machines reveals what was always opaque between humans.

— Stewardship beats generation. The system has to outlive its authors.

Systems & primitives Critique & decision-making Cross-functional & process

WEBFLOW

LDLR DESIGN FIELD NOTES

Where AI debt lands

AI code defers cost instead of cutting it: seven debt categories land far from where the velocity gain was booked.

BY ANKIT AGRAWAL / MAY 12, 2026

The cleanup cost of ungoverned AI-generated code

It costs a contributor five minutes to generate a low-quality AI pull request, and hours for the maintainer to verify and reject it.

Why it matters

— Seven debt categories, segmented by who actually pays the bill.

— Time-to-exploit window collapsed from months to days.

— Five minutes to generate a PR. Hours to reject one.

— Triage PRs by risk class. Output is the wrong metric.

Read on Webflow →

Critique & decision-making Cross-functional & process Systems & primitives

MICROSOFT DESIGN

LDLR DESIGN FIELD NOTES

The missing seat

Frontier AI teams optimize what’s measurable, so Microsoft’s researchers want a seat where the metrics get chosen.

BY MARTIN LINDE DANTY, RABEEZA A., ANNE KLÆRKE-OLESEN, MADHUMAY SINHA, MICHAEL O'SULLIVAN / APR 28, 2026

The missing seat at the frontier team table

When evaluation is driven primarily by available data, teams risk optimizing what is measurable rather than what actually matters.

Why it matters

— User research belongs in evaluation, not adjacent to it.

— Session-length looked strong. Task-completion cut repeat queries by a third.

— Sales-order workflow assumed isolation. Research surfaced cascading approvals.

— Concept tests caught a workflow misread that would have cost weeks.

Read on Microsoft Design →

Research & validation Cross-functional & process Critique & decision-making

FIGMA

LDLR DESIGN FIELD NOTES

The canvas reads code

McMillin reframes canvas, code, and PRD as one system: an agent translates, and judgment moves through both.

BY BRETT MCMILLIN / APR 30, 2026

Workflow lab: Expanding the canvas with Figma MCP

The artifact isn't a bug report. It's a shared reference for a design conversation.

Why it matters

— Agents surfaced ten product states the original canvas missed.

— Visual diff replaces the bug ticket as a design artifact.

— On canvas exploration stays cheap. In code every direction costs.

— Source of truth becomes connected artifacts, not one canonical file.

Read on Figma →

Prototyping & exploration Cross-functional & process Systems & primitives

LINEAR

LDLR DESIGN FIELD NOTES

Hiring, written down

Writing down how you hire forces honesty about what you value. Linear did the work and published it.

BY DOUG PARKER / APR 28, 2026

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

MICROSOFT WORKLAB

LDLR DESIGN FIELD NOTES

Workers ready, orgs not

Microsoft’s 2026 Work Trend Index, 20,000 workers across ten countries: only 26 percent see leadership aligned on AI.

BY MICROSOFT WORK TREND INDEX TEAM / MAY 5, 2026

Agents, human agency, and the opportunity for every organization

Workers are ready. Their organizations aren't.

Why it matters

— One in five workers sit in the Frontier zone.

— One in ten are ready individuals blocked by the organization.

— Only twenty-six percent say leadership is consistently aligned on AI.

— Sixty-five percent fear falling behind. Forty-five percent stay in old work.

Read on Microsoft WorkLab →

Cross-functional & process Research & validation Storytelling & narrative

LINEAR

LDLR DESIGN FIELD NOTES

Kept in their lane

A Linear engineer scopes agent tasks tight enough that they can’t wander, the same discipline as scoping for a junior.

How we use Linear Agent at Linear

Matthijs gets the best results from coding agents by breaking the work into small, targeted steps.

Why it matters

— Scoping for an agent is the same discipline as scoping for a junior.

— Three-team workflow shows where agents add real leverage.

— PM-ships-the-fix works because the change was small, not the agent.

— Marketing-shaped piece. The underlying tactics are still real.

Cross-functional & process Critique & decision-making

MAGGIE APPLETON

LDLR DESIGN FIELD NOTES

The design bottleneck

Appleton reads Yegge’s chaotic agent orchestrator as design fiction: the coding bottleneck fell, the design one stayed.

JAN 23, 2026

Gas Town’s Agent Patterns, Design Bottlenecks, and Vibecoding at Scale

Design becomes the limiting factor: imagining what you want and figuring out the gnarly details to make it real.

Why it matters

— When agents write faster than you design, vibe-designing is a footgun.

— Mayor/Polecat hierarchy sketches a real coordination pattern for agents.

— Code distance shifts with domain, stakes, and team size.

— Infrastructure matters more than models. Validation loops, not smarter agents.

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

MAGGIE APPLETON

LDLR DESIGN FIELD NOTES

The PR can’t plan

Agents collapsed the implementation window, and the alignment checkpoints that lived inside it went with it.

APR 13, 2026

One Developer, Two Dozen Agents, Zero Alignment

Code is so cheap we don't properly stop to think before prompting it. We lose more alignment points.

Why it matters

— Planning and building are no longer separate phases. The tools still are.

— The PR now carries upstream checkpoints it was never designed for.

— Most alignment context lives in people's heads. Agents can't reach it.

— Ace is a research prototype. The diagnosis is sharper than the fix.

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

MICROSOFT DESIGN

LDLR DESIGN FIELD NOTES

Paper earns its geometry

Microsoft spent years replacing plastic with paper. Committing was easy; making every millimeter behave was the work.

APR 21, 2026

Paper, please: The box that did more with less

A variance of one to two millimeters risked scratching the device or allowing damage during transit.

Why it matters

— Foam absorbs impact by being soft. Paper does it by structure.

— Over 1,000 prototype boxes to get coatings, paper, and inks working.

— Smaller boxes per pallet linked sustainability and shipping cost.

— Measurement ran as a second project tracking progress across thousands.

Read on Microsoft Design →

Cross-functional & process Craft & detail Systems & primitives

LINEAR

LDLR DESIGN FIELD NOTES

No Miro board in Athens

Linear flew designers and engineers to Athens and shipped a working build by Friday. The part worth lifting is the trust.

BY KARRI SAARINEN / MAR 28, 2024

How we redesigned the Linear UI (part II)

It's always better to do a redesign quickly. Otherwise, you will block almost every project and create design debt.

Why it matters

— Mornings for design iteration, afternoons for engineering pairs.

— Working build behind a feature flag by Friday.

— Compressed loop only works when trust replaces handoff rituals.

— Specific technical calls: LCH over HSL, Electron cross-platform tax.

Craft & detail Cross-functional & process Prototyping & exploration

LINEAR

LDLR DESIGN FIELD NOTES

Kept in their lane

A Linear engineer scopes agent tasks tight enough that they can’t wander, the same discipline as scoping for a junior.

BY RHEA PUROHIT / APR 10, 2026

How we use Linear Agent at Linear

Matthijs gets the best results from coding agents by breaking the work into small, targeted steps.

Why it matters

— Scoping for an agent is the same discipline as scoping for a junior.

— Three-team workflow shows where agents add real leverage.

— PM-ships-the-fix works because the change was small, not the agent.

— Marketing-shaped piece. The underlying tactics are still real.