Cross-functional & process — 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

FIGMA

LDLR DESIGN FIELD NOTES

Designing agents people can trust

Sheta Chatterjee walks through the design calls behind Gemini Enterprise: a shared AI inbox, team project spaces, and keeping people 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 design 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 →

Hiring & team Cross-functional & process

JAKOB NIELSEN

LDLR DESIGN FIELD NOTES

Profit Comes From Workflow Redesign

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 Systems & primitives

VANESSA BELENO

LDLR DESIGN FIELD NOTES

What Ambiguity Reveals About You

An early-career designer notices she keeps reaching for connective work wherever structure is missing, and asks what that instinct reveals.

JUN 18, 2026

Cross-functional & process Hiring & team

BUILDING NUBANK

LDLR DESIGN FIELD NOTES

Simplicity at scale is strategy

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

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 as an operating system

GitHub's five-year accessibility program turns outward, with audit data, design tooling, and AI agents making inclusion operational rather than aspirational.

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

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

MEDIUM

LDLR DESIGN FIELD NOTES

AI Ate the PM Conversation

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

How I use AI to partner on design problems

The AI holds context across Linear, Slack, and research; you do the thinking. · Code prototypes move feedback from visual details to actual UX problems.

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

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

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

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 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

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

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