Field Notes — Design Outcomes

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

THE GITHUB BLOG

LDLR DESIGN FIELD NOTES

An Accessibility Agent That Knows Its Limits

GitHub's accessibility agent reviewed 3,535 PRs at a 68% fix rate. The sharper lesson is what they taught it not to 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

How Slack's Design VP Leads Through AI

Slack's VP of Product Design on guiding roughly 70 designers through AI without mandates: stay curious, stay skeptical, and keep the bar high.

BY WILL MINER / MAY 21, 2026

Cross-functional & process Hiring & team

DESIGN SYSTEMS COLLECTIVE

LDLR DESIGN FIELD NOTES

Agents Don't Read Your Documentation

Agents read structure and naming, not docs or goodwill. The informal contract that held design systems together becomes a hard boundary.

MAY 11, 2026

Systems & primitives Craft & detail

MICROSOFT DESIGN

LDLR DESIGN FIELD NOTES

The system is the handoff

Microsoft consolidated Copilot into four surfaces tied together by a 'Throw and Catch' pattern. The pattern, not the components, is the system.

BY JON FRIEDMAN / MAY 12, 2026

A simplified system

Intelligence without continuity can feel like an interruption instead of a thought partner.

Why it matters

— Four canonical Copilot surfaces, not scattered features per app.

— 'Throw and Catch' governs handoff between the four surfaces.

— Context persists across apps. The conversation does not restart.

— On-canvas narrows from exploration to document focus on selection.

Read on Microsoft Design →

Systems & primitives Prototyping & exploration Craft & detail

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

FIGMA

LDLR DESIGN FIELD NOTES

When the canvas reads the code

Most teams treat canvas, code, and PRD as three competing artifacts. Brett McMillin's reframe: a connected system, with an agent translating between them and the designer's judgment moving 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

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

MICROSOFT WORKLAB

LDLR DESIGN FIELD NOTES

The transformation paradox, in data

Microsoft's 2026 Work Trend Index covers 100,000+ Copilot conversations and surveys 20,000 workers across ten countries. Only 26 percent say leadership is consistently 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

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 Maggie Appleton →

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 Maggie Appleton →

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

MICROSOFT DESIGN

LDLR DESIGN FIELD NOTES

Paper that had to earn its geometry

Microsoft spent years replacing plastic packaging with paper. The commitment was easy; getting every millimeter to behave was the actual 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

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 Rauno Freiberg →

Critique & decision-making Prototyping & exploration Craft & detail

LINEAR

LDLR DESIGN FIELD NOTES

An offsite without a Miro board

Linear took designers and engineers to Athens and shipped a working build by Friday. The trust that made the loop close, not the offsite, is what's worth lifting.

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.

Read on Linear →

Craft & detail Cross-functional & process Prototyping & exploration

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