Molly Graham: AI Takes the Task, Humans Keep the Burden

Original source: Molly Graham: The grief, burnout, and opportunity hiding inside the AI transition

Show: Lenny’s Podcast. Guest: Molly Graham, who held leadership roles at Google, Facebook, Quip, and the Chan Zuckerberg Initiative, now hosts TED’s WorkLife and runs the leadership community Glue Club. Host: Lenny Rachitsky. Published 2026-09-27. Duration: 01:34:14.

This article synthesizes the complete English automatic captions, with checks against Graham’s companion essay and the original survey discussed in the episode. Management advice, anecdotes, and forecasts remain attributed to the speakers. Section links point to the relevant video passages.

The code is written, a proposal is drafted, and other tasks are moving in parallel. The person at the screen is still supplying context, answering questions, checking results, and deciding what can be handed over.

More work is getting done. The person’s mind has not necessarily become less crowded.

In this conversation, Molly Graham revisits her longstanding advice to pass on familiar responsibilities and create room for new opportunities. Applying it to AI requires a qualification.

Execution can move to AI while accountability and judgment stay with the human. The task list can expand without a corresponding increase in attention. That distinction helps explain how greater capability, exhaustion, and professional opportunity can arrive together.

Handing over a task can leave responsibility behind

Graham developed her advice about relinquishing familiar work while experiencing rapid organizational growth. She recalls a Google department expanding from 25 people to 125 in 9 months. Just as someone established a comfortable way of working, the organization changed again.

Owning a project or a specialty can become part of a person’s identity. When the work moves to someone else, the loss can include the status of being the person everyone relies on for that particular thing.

Her original career advice encouraged letting a capable colleague take ownership and develop their own approach. Stepping back created the attention needed for the next challenge.

AI changes that handover. A person still has to explain the goal, supply context, detect errors, and decide whether the result meets the standard. If that person must explain the outcome to the team, the work still occupies part of their mind.

Graham distinguishes a genuine transfer to a new owner from having another actor execute work for which the original owner remains responsible.

Many AI workflows fit the latter description. Starting more agents can leave one person responsible for more streams of work. Graham says that, in her experience, managing 10 to 12 direct reports already demands substantial attention. That is a personal heuristic, not an established limit for every team or collection of agents.

Supervision needs a budget too. Time saved on execution has to be weighed against briefing, checking, rework, and attention switching. Video: delegation and oversight.

Burnout and excitement can coexist

The conversation draws on Lenny’s Newsletter’s survey of tech workers. In the episode, Rachitsky rounds the burnout figures to about 44% in 2025 and 55% in 2026.

The original survey reports 44.7% rising to 55.7%, an increase of 11 percentage points. The measure includes respondents describing themselves as moderately, very, or completely burned out. Separately, 49.0% say AI has amplified their professional capabilities.

These are respondents’ self-reports, not an industry-wide estimate or proof that AI caused burnout. Feeling amplified also differs from reporting the happiest period of a career.

A recurring experience in the discussion is that tools increase what people can accomplish, and organizations raise expectations accordingly. Time saved today can become tomorrow’s expected output.

Graham also describes the effort of adapting to changing instructions. One period brings pressure to use AI everywhere; the next brings demands to explain what all that usage actually improved. Both the pace of work and the standard by which it is judged keep moving.

Some people are enjoying the transition. They can try ideas faster and make things that previously lay outside their capabilities.

A person can value that new ability and still feel exhausted by the effort of sustaining the pace. Allowing both reactions gives a more faithful account of the experience described in the interview. Video: the survey and workers’ experiences.

Making things becomes supervising them

Some engineers miss the experience of spending uninterrupted hours working through code. Their day now involves assigning tasks, waiting for generated work, inspecting changes, and responding to the next question.

Graham describes a loss of professional identity: a craft developed over years suddenly occupies less of the working day. The additional capability does not automatically replace the satisfaction that used to come with it.

Management preferences matter as well. Some people chose individual contributor careers because they enjoyed making things directly. AI brings briefing, coaching, and review into their work. The title may be unchanged while the daily experience becomes closer to management.

Collaboration can change too. Graham describes a product leader who can build more prototypes independently but misses working through ideas with designers and engineers. A wider scope of individual execution can come with less shared exploration.

Rachitsky borrows Cory Doctorow’s centaur metaphor to distinguish people directing tools from people being directed by systems. It raises a question worth revisiting: does the additional capability also give its user more choice?

When teams shrink, conversation, support, and collective judgment still need to be provided for. Output metrics capture only part of that change. Video: identity, loneliness, and control.

Unchecked output transfers the cost to colleagues

Graham objects to describing AI as an employee who is always smarter and more reliable than its human colleagues. That expectation can encourage people to forward its output without checking it.

She prefers the analogy of an inexperienced assistant: provide context, establish standards, and continue directing the work after the first response. The analogy concerns supervision; it is not a universal assessment of every model’s ability at every task.

The risk becomes visible when the work is forwarded. A proposal may look complete while leaving its essential assumptions unresolved. The recipient then has to understand, verify, and repair it. Time saved by the sender becomes additional work for someone else.

Skipping review does not eliminate its cost. It moves that cost along the chain of collaboration.

Graham consequently criticizes management practices that focus on generated volume, lines of code, or token consumption. Organizations also need to know whether work advanced the goal and how much repair it left behind.

She recalls an engineering report in which rewritten lines of code rose to roughly 8 times their previous level. The interview does not identify the report, sample, or comparison method, so this article cannot independently verify the figure. It remains an attributed recollection, not an established industry statistic.

A more actionable check is to include downstream review and rework when deciding whether a workflow has actually become less demanding. Video: output, quality, and rework.

Vision, judgment, and trust need human ownership

When people previously asked Graham which responsibilities they should protect, she generally encouraged them to keep letting go. AI has changed her answer.

She now argues for explicit human ownership of direction, quality judgments, consequences, and trust. Someone who cannot describe what a good result would be will struggle to decide whether a generated proposal should be accepted.

Rachitsky suggests a division of work with humans at both ends: a person sets direction, AI helps with execution, and a person reviews and revises the result.

The initial choice matters. He uses Airbnb and Booking.com to illustrate how teams can pursue different experiences. Maximizing booking conversion and creating a calmer interaction can lead to different design decisions. This is his illustrative comparison, not an independent evaluation of the products.

AI can help pursue an objective. The owner still has to decide whether that objective is desirable and what experience it will create.

In her companion essay, Graham similarly argues for greater care over which capabilities to hand off. Her aim is to make more room for a person’s distinctive strengths while preserving the ability to judge the work. Video: what should stay with humans.

Roles can expand while delivery standards remain

Graham describes a design leader at a financial company who built something with new tools but was prevented from shipping it because designers were not allowed to release code.

She acknowledges that controlling changes to production systems is justified in that setting. What she wants reconsidered is whether a job title should determine the boundary of someone’s capabilities in advance.

Designers can test interactions more thoroughly, product managers can build working prototypes, and engineers can participate earlier in understanding needs. The tools lower the cost of trying those expanded roles.

Following her reasoning, organizations can ask more specific questions: who understands the need, who can verify quality, and who accepts responsibility after release? Those answers provide a basis for deciding how the work should be delivered.

Roles can become broader while verification and accountability remain explicit. Removing old divisions without arranging appropriate checks can turn an opportunity for broader contribution into another source of rework. Video: the boundary between design and engineering.

Acknowledge the old work, then help shape its next version

Graham does not expect people to welcome every change. A familiar way of working can disappear, and a beloved craft can move to the margins of a job. Acknowledging that loss is reasonable.

She draws on Chip Conley’s idea that some endings deserve a deliberate farewell. A team can discuss what it valued and what it has lost before considering what to try next.

Another influence is journalist Manoush Zomorodi. Graham takes from her career a thought experiment: how would someone prepare if their profession continued to exist but took a different form every 6 years?

That framing is intended to support action; it does not guarantee the survival of any particular job. Graham is skeptical of some layoffs described as AI-driven and believes new work will emerge. These are her judgments, not evidence that AI plays no role in any layoffs.

Focusing on how a profession changes can at least suggest concrete things to learn: which constraints have loosened, and which existing abilities could be carried into the next version of the work?

Rachitsky also leans toward the view that the current transition leaves time to adapt. Neither speaker can guarantee the pace of technical development or future employment. Their firmer recommendation is to accept being a beginner again and use conversations with peers to test perceptions. Video: loss, learning, and opportunity.

Managers demonstrate what accountability looks like

A leader who forwards an AI-generated strategy directly to a team also communicates a working standard: material that has not been carefully considered is acceptable as a finished contribution.

Graham wants leaders to demonstrate a different standard. Explain what has been verified and what remains uncertain. Acknowledge their own learning. Make it possible for a team to discuss confusion about the transition.

She points to Clay’s AI writing policy. The public policy allows AI assistance while requiring authors to confirm that a document expresses ideas they will take responsibility for and respects its readers’ time.

Managers also need to make room for human support. Graham rejects the assumption that more capable tools automatically reduce the value of management. Helping people understand expectations, handle conflict, and develop confidence under uncertainty remains useful work.

That does not establish a case for adding management layers at every company. Her argument is that supporting people, defining standards, and accepting the consequences of decisions still require someone to do them well. Video: advice for managers.

Redesign the division of work through a small experiment

A practical application of the conversation is to start with a recurring task. The following is an editorial suggestion drawn from the discussion, not a prescribed process from the speakers.

First, establish whom the work serves, what problem it should solve, and how completion will be judged. Then give AI a bounded part of execution whose result can be checked.

A person retains consequential choices and final review while tracking the effort spent briefing, waiting, checking, and repairing. At the end, assess both the quality of the work and whether colleagues have less additional work to absorb.

A longer-term question is whether the saved time allowed the person to do more of what they are good at and want to keep doing. If it only created room to supervise more tasks, the division of work and the expectations around it need adjusting.

Rachitsky recommends pausing before starting work to consider whether AI could help. Graham adds a quality test: the result should deserve other people’s attention and hold up to continued use. Video: learning habits and quality standards.

A better division of work expands human capability while making room for responsibility, quality, and satisfaction. That is the direction Graham preserves in her revised advice: remain willing to let go and learn, while choosing carefully what deserves continued personal ownership.