Field Notes, page 5 — Design Outcomes

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