Critique & decision-making — Field Notes

LINEAR

LDLR DESIGN FIELD NOTES

Review Is Judgment Now, Not Parsing

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?

Read on Linear →

Critique & decision-making Cross-functional & process

DESIGN SYSTEMS COLLECTIVE

LDLR DESIGN FIELD NOTES

Encode Intent, Not Just Components

When agents author your design system, intent must live in tokens and metadata, not only in a practitioner's head.

JUN 29, 2026

The System Knows What You Built. Does It Know What You Meant?

AI has lowered the floor on execution. The ceiling on judgment is still yours.

Why it matters

— The question moved from can AI use your system to can it write it.

— Agents connected to metadata make decisions about what to reach for.

— Discoverability isn't documentation coverage; it's intent legibility where decisions get made.

— Tokens should carry purpose, not just values; metadata should explain what's for.

— Unresolved ambiguity gets filled by the agent's best guess, everywhere, unnoticed.

Read on Substack →

Systems & primitives Critique & decision-making

UX.RASPBERRY

LDLR DESIGN FIELD NOTES

From producing to deciding

A blunt read on where designer value sits in 2026: production is getting automated, so strategy and judgment are what stay human.

MAY 1, 2026

UX Design 2026+: From producing to deciding, from craft to operation

It's no longer about what you produce; it's about what you decide.

Why it matters

— The tedious middle of the job is being automated away.

— Value moves to the before (strategy) and the after (judgment).

— The "Junior Paradox": one senior plus AI replaces two juniors.

— Survival looks T-shaped, with one deep, hard-to-automate strength.

Read on Medium →

Critique & decision-making Hiring & team

DESIGN MAVERICKS

LDLR DESIGN FIELD NOTES

Design is becoming leadership literacy

Forty design leaders in Amsterdam reach the same conclusion: the role is dissolving while the capacity becomes foundational to leadership.

JUN 4, 2026

When AI Builds Everything, Design Becomes Everything

We are training people for a job. We should be cultivating a capacity.

Why it matters

— Intercom now ships over 90% of pull requests authored by Claude Code

— When execution costs nothing, judgment about direction becomes the product

— Atlassian runs 64% ICs, every designer a platform designer, demo before memo

— Frigieri's upstream conditions: workflows, data pathways, decision rights, controls

— The Frozen Middle: everyone experimenting alone without strategic guidance from above

Read on Design Mavericks →

Hiring & team Critique & decision-making Systems & primitives

UX COLLECTIVE

LDLR DESIGN FIELD NOTES

A skeptic's playbook for AI

A research leader of eight argues for measured AI adoption: pressure-tested tools, tracked outputs, and guardrails before enthusiasm.

APR 30, 2026

Thoughtful AI implementation for UXR leaders

I'm arguing for a measured approach to their usage.

Why it matters

— Pressure-test NotebookLM with likely stakeholder questions before opening access

— Capture before and after results when tuning prompts with ops

— Track who queries research repositories and how outputs shape decisions

— Half of Americans are more concerned than excited about AI

Read on UX Collective →

Research & validation Critique & decision-making

THE MERHOLZ AGENDA

LDLR DESIGN FIELD NOTES

The Layoffs Are Social Contagion

Merholz reads the layoff wave through decades-old 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.

Read on The Merholz Agenda →

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

POSTHOG

LDLR DESIGN FIELD NOTES

When FOMO Ships It Too Early

PostHog's CEO on shipping AI before it worked, the architecture fix that turned it around, and betting the product on agents.

BY JAMES HAWKINS / MAY 1, 2026

PostHog's next chapter

FOMO came ahead of progress.

Why it matters

— A one-shot assistant shipped early, returned empty graphs, and felt half-useful.

— The fix was a single query loop so the agent could iterate.

— Agents now create most new dashboards, with MCP usage roughly doubling monthly.

— The bet: a headless, proactive product that ships fixes while you sleep.

— Hawkins is candid about UX churn, and why the short-term pain is worth it.

Read on PostHog →

Prototyping & exploration Critique & decision-making Systems & primitives

UX COLLECTIVE

LDLR DESIGN FIELD NOTES

When the Metric Becomes the Harm

Bertini argues engagement-maximizing AI doesn't fail by accident, and that designers and product leaders own the direction it takes.

MAY 4, 2026

We built this. Now we own it.

That is not a flaw in the design. It may be the design.

Why it matters

— Klarna's bot optimized for throughput over empathy, and the gap shows.

— A companion chatbot getting it wrong carries far higher stakes than a refund delay.

— Maximizing engagement leans into vulnerability, which may be intended, not accidental.

— Harari's warning: autonomous systems may not give us a second chance.

— Responsibility for AI's direction sits with the people building it.

Read on UX Collective →

Critique & decision-making Storytelling & narrative

DESIGN SYSTEMS COLLECTIVE

LDLR DESIGN FIELD NOTES

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

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.

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.

Read on Design Systems Collective →

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

BOOTCAMP (MEDIUM)

LDLR DESIGN FIELD NOTES

The Design System You Didn't Choose

shadcn became the default behind every AI-generated UI. A developer built it. Most design teams never noticed they're now competing with it.

MAY 11, 2026

The most important Design System in 2026 that designers missed was built by a developer.

Every shadcn project is a fork.

Why it matters

— AI tools converged on shadcn as the default shape of generated UI.

— It lives in GitHub and React templates, not Figma, so designers missed it.

— The MCP server turned accidental convergence into installed infrastructure.

— The work isn't fighting the default. It's reading it, then deciding what to override.

Read on Bootcamp (Medium) →

Systems & primitives Critique & decision-making

GITHUB (ENGINEERING & DESIGN)

LDLR DESIGN FIELD NOTES

When 'feels instant' is the spec

Most performance work chases tail latency. GitHub Issues reframed it around distribution shape, then named 4.7% server/cache divergence as the price of feeling instant.

BY ALEXANDER LELIDIS / MAY 14, 2026

From latency to instant: Modernizing GitHub Issues navigation performance

We are willing to serve data that may be slightly stale if that allows the navigation to complete near instantaneous

Why it matters

— Reframed the goal: shape the distribution, not chase p99.

— Five layers: in-memory cache, IndexedDB, preheat, service worker, code-split.

— Accepted 4.7% server/cache divergence as the operating envelope.

— Cache hit went from 33% to 96%. P10 dropped to 70ms.

Read on GitHub (Engineering & Design) →

Craft & detail Systems & primitives Critique & decision-making

DESIGN SYSTEMS COLLECTIVE

LDLR DESIGN FIELD NOTES

AI didn't add to the spec

AI-readiness isn't a separate category. The same fundamentals (tokens, layout intent, accessibility, governance, handoff contracts) finally have to read clearly 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.

Read on Design Systems Collective →

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

WEBFLOW

LDLR DESIGN FIELD NOTES

Where the AI code debt lands

AI-generated code defers cost, it doesn't reduce it. Seven debt categories concentrate far from where the velocity gain was booked, including reviewer fatigue and security debt.

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

When metrics optimize the wrong thing

Frontier AI teams optimize what's measurable, not what matters. Microsoft's user researchers want a seat at the evaluation table, as a safeguard against the metric chosen for being convenient.

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

LINEAR

LDLR DESIGN FIELD NOTES

Linear's hiring playbook, written down

Most companies don't write down how they hire because writing it down forces honesty about what they actually value. Linear did the work and published it.

BY DOUG PARKER / APR 28, 2026

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

LINEAR

LDLR DESIGN FIELD NOTES

Coding agents kept in their lane

An engineer at Linear scopes coding-agent tasks tight enough that they can't wander. The discipline is the same as scoping for a junior teammate.

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.

Read on Linear →

Cross-functional & process Critique & decision-making

MAGGIE APPLETON

LDLR DESIGN FIELD NOTES

When coding stops being the bottleneck

Maggie Appleton reads Steve Yegge's chaotic agent orchestrator as speculative design fiction. The coding bottleneck is gone; the design bottleneck was always there.

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.

Read on their blog →

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

MAGGIE APPLETON

LDLR DESIGN FIELD NOTES

The PR is not a planning tool

Coding agents collapsed the implementation window. The alignment checkpoints that used to live inside it just disappeared, and the PR cannot carry their weight.

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.

Read on their blog →

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

RAUNO FREIBERG

LDLR DESIGN FIELD NOTES

The minimap that became a blur

Rauno tried to solve 'scroll back' with a minimap. The minimap caused jank, the jank needed a blur, and the blur almost worked.

Field Notes

The jank gets increasingly worse when you actually choose to scroll to another message.

Why it matters

— Each solution reveals the next constraint: scroll, minimap, jank, blur.

— AI summaries failed: you remember what you typed, not a summary.

— Blur-and-stack beats layout collapse because fewer objects move.

— Keeping the composer visible preserves task context in minimap mode.

Read on their blog →

Critique & decision-making Prototyping & exploration Craft & detail

LINEAR

LDLR DESIGN FIELD NOTES

Coding agents kept in their lane

An engineer at Linear scopes coding-agent tasks tight enough that they can't wander. The discipline is the same as scoping for a junior teammate.

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.

Read on Linear →

Cross-functional & process Critique & decision-making

NUBANK DESIGN

LDLR DESIGN FIELD NOTES

Killing darlings, statistically

Nubank ran a real A/B test on whether to scale or shut down an internal HR product. The data was unambiguous; the team's reaction to it was not.

BY NUBANK EDITORIAL / AUG 27, 2025

A/B Testing for Decision of scaling or decommissioning an Human Resources product

Increased usage didn't always translate to feeling recognized — a critical insight missed without experimental

Why it matters

— A/B testing applied to decommissioning, not just feature launches.

— Internal tools deserve the same rigor as customer-facing products.

— Usage below threshold: kill it. Above: scale it.

— Hardest part isn't the data, it's letting the team accept it.

Read on Nubank Design →

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