Field Notes — Design Outcomes

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

Taste Is Care, Not a Gift

Figma's chief design officer reframes taste as care, not gift, and names three things she screens for when hiring.

BY LOREDANA CRISAN / JUN 8, 2026

You never stop cultivating taste

Great designers have language for things most people only feel.

Why it matters

— Taste is care: for the user, the craft, and the result.

— It grows from love of the craft plus care for people.

— She hires for discernment: can they name what's not working, and why?

— Empathy and creative energy round out the three signals she looks for.

— Even Dyson ran 5,127 prototypes; the first output is never final.

Read on Figma →

Craft & detail Hiring & team

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

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

IT'S NICE THAT

LDLR DESIGN FIELD NOTES

Designers should write about design

Elizabeth Goodspeed argues writing is another way to work through the same questions your design already circles, and well worth the effort.

BY ELIZABETH GOODSPEED / APR 2, 2026

Elizabeth Goodspeed on why design writing needs designers writing

their writing and their work circle the same inquiries, even as the format changes

Why it matters

— Writing and design tend to come from the same place.

— The idea of a "beat": questions you keep returning to.

— Designers catch distinctions outsiders miss, which makes the prose more precise.

— Writing forces you to name what taste usually leaves implicit.

Read on It's Nice That →

Storytelling & narrative Craft & detail

JAMIESON ROTHWELL

LDLR DESIGN FIELD NOTES

Shipping binaries, not just mockups

After three decades built around the handoff, Jamieson Rothwell now ships working software and treats those build choices as design decisions.

MAY 11, 2026

Product Design in 2026: Am I still a designer?

Shipping is the new designing.

Why it matters

— The old ritual, design then hand off blueprints, is over for him.

— LLMs and coding agents turn static design into active construction.

— Local-first as a design choice: his tool Warren guards data ownership.

— A small cross-platform system, Sitka, keeps React, HTML, and Swift aligned.

— Barrier to entry collapsed; the barrier to greatness is still taste.

Read on Medium →

Prototyping & exploration Systems & primitives Craft & detail

THE FOUNTAIN INSTITUTE

LDLR DESIGN FIELD NOTES

How senior design hiring changed

Jeff Humble gathers a hiring playbook where every tip is from this year, aimed at senior designers rethinking their career strategy.

BY JEFF HUMBLE

7 Ways Hiring is Evolving for Senior Designers

Shipped, traceable work beats case studies.

Why it matters

— Get comfortable with live problem-solving, not just polished case studies.

— Shipped, traceable work now carries more weight than a portfolio narrative.

— Advice pulled from various experts, all of it dated to this year.

— A good moment to experiment with how you position yourself.

Read on The Fountain Institute →

Hiring & team 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

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

GEORGE XING

LDLR DESIGN FIELD NOTES

Shipping Solo With Agent Workflows

A solo builder lays out the agent framework, test automation, and remote setup that made his product workflow far faster.

MAY 6, 2026

Prototyping & exploration Systems & primitives

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

ALPHA BYTES

LDLR DESIGN FIELD NOTES

Why Taste Becomes the Moat

As AI flattens production, the author argues cultivated taste and a clear point of view become a designer's real edge.

MAY 15, 2026

Craft & detail Storytelling & narrative

VIOLETTA BONENKAMP

LDLR DESIGN FIELD NOTES

Design as Executable Knowledge

A founder argues the real shift is encoding brand rules and taste into reusable files non-designers can run.

JUN 1, 2026

Systems & primitives Craft & detail

DESIGN WITH AI

LDLR DESIGN FIELD NOTES

Five Habits for Designing With AI

Notes from ÌníOlúwa Abíódún's talk on shipping AI agents: scope sharply, write to think, then explore rough prototypes.

MAY 24, 2026

Prototyping & exploration Craft & detail

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

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

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

HARVARD BUSINESS REVIEW

LDLR DESIGN FIELD NOTES

AI is the new workplace confidant

Employees increasingly turn to AI for advice, support, and friendship. The researchers argue leaders must protect human connection at work.

BY CONSTANCE NOONAN HADLEY AND SARAH L. WRIGHT / MAY 1, 2026

Employees Are Relying on AI for Personal Support. That's Risky.

Research shows how AI can weaken human connection at work.

Why it matters

— More than half of 1,545 surveyed knowledge workers feel lonely at work

— Workers seek career advice, emotional support, and friendship from AI

— AI conversation can quietly substitute for, then erode, human connection

— The authors call on leaders to intervene before reliance hardens

Read on Harvard Business Review →

Hiring & team Research & validation

GOOGLE LABS

LDLR DESIGN FIELD NOTES

Vibe design gets a canvas

Stitch evolves into an AI-native infinite canvas: design agents, voice critique, and DESIGN.md portability between design and code tools.

BY RUSTIN BANKS / MAR 18, 2026

Introducing "vibe design" with Stitch

Close the gap from idea to reality in minutes rather than days.

Why it matters

— Start from business objective and intended feeling, not a wireframe

— An agent manager tracks parallel explorations across the infinite canvas

— DESIGN.md exports design rules as agent-friendly markdown between tools

— Voice critique makes real-time updates while you stay in flow

— Stitch screens together and press play to preview full journeys

Read on Google Labs →

Prototyping & exploration Systems & primitives

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

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

BOOTCAMP (MEDIUM)

LDLR DESIGN FIELD NOTES

Stop Designing Outputs, Design Relief

An early-career designer makes the case for building leverage: encode taste into tools and remove friction instead of polishing more screens.

DEC 18, 2025

Stepping Into 2026 as a Designer (When You're Still Early in Your Career)

I wasn't designing outputs anymore. I was designing relief.

Why it matters

— Polished screens are cheap now, so execution alone no longer carries value.

— He stopped refining artifacts and started building small tools that remove friction.

— A junior's edge: no fixed identity, so quiet experiments come easier.

— Taste still matters, but it scales only once you encode it.

— The move is from producing screens to shaping how they get produced.

Read on Bootcamp (Medium) →

Systems & primitives Prototyping & exploration

MEDIUM

LDLR DESIGN FIELD NOTES

The Senior Path Isn't Linear

A short, honest reflection on stalls, rebuilds, and why recalibration, not uninterrupted success, is what separates senior designers.

MAR 16, 2026

The Hidden Part of Becoming a Senior Designer

Sometimes the comeback is where the real designer is formed.

Why it matters

— The clean junior-to-leadership arc is mostly a myth; progress stalls and restarts.

— Rejection feels personal when your work is visible, subjective, and always evaluated.

— Rebuilding fundamentals and portfolios is a reset, not a backward step.

— What separates seniors is resilience and a willingness to keep evolving.

Read on Medium →

Craft & detail Hiring & team

DESIGN SYSTEMS COLLECTIVE

LDLR DESIGN FIELD NOTES

Fully Machine-Readable Design Systems

AI reads your design system differently; structured metadata beats prose documentation. · Foundations should be always-on; components served on demand through an MCP.

MAY 14, 2026

Fully Machine-Readable Design Systems

Why it matters

— AI reads your design system differently; structured metadata beats prose documentation.

— Foundations should be always-on; components served on demand through an MCP.

— At Indeed, JSON cost five times less than Markdown for the same query.

— Progressive disclosure maps what AI needs without flooding its context window.

— The system you wrote for designers won't work for agents without a rewrite.

Read on Design Systems Collective →

Systems & primitives Craft & detail Research & validation

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

DESIGN SYSTEMS COLLECTIVE

LDLR DESIGN FIELD NOTES

Your System Can't Explain Itself. That's the Problem.

Most design systems are a shared palette and a Confluence page nobody trusts. · A real system enforces its contracts; agents expose every gap you papered over.

MAY 18, 2026

Your System Can't Explain Itself. That's the Problem.

Why it matters

— Most design systems are a shared palette and a Confluence page nobody trusts.

— A real system enforces its contracts; agents expose every gap you papered over.

— Can your system explain itself to an LLM without hallucinating your brand?

— AI didn't create this problem; it's revealing the documentation debt you already had.

— Legibility is the work. Not the components. Not the tokens. The clarity.

Read on Design Systems Collective →

Systems & primitives Craft & detail Storytelling & narrative

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

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

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