How to Help People Thrive with AI (AI Daily Brief)

Nathaniel Whittemore's weekend big-think + long-reads episode on The AI Daily Brief (July 2026), assembled around three anchors and one 2026 case study:

Section's AI Proficiency Report (sponsor mention) — the workforce-adoption / training gap numbers
David Brooks, The People Who Will Thrive in the AI Age, [The Atlantic] — the relationship-to-mental-effort frame + three archetypes (productive passengers / reluctant optimizers / mental marathoners)
Uber CTO Praveen Napali's Agentic Pods thread on X — 16 pods, 16 business functions, 2-week engineer + domain-expert cadence, headline productivity results
Whittemore's own 2026 prediction on internally deployed vibe coders as the operational future of AI champions

Whittemore's throughline: David Brooks's archetypes are useful diagnostics but Brooks himself is too pessimistic about mobility between them. The actionable move for organisations is not to pick the marathoners and shame the passengers; it's to build organisational structures (agentic pods, champions programmes, internally deployed vibe coders) that pull more people toward higher volition.

Anchor 1 — Section: 69% action, 16% agentic-tool use, <10% can define an agent

Whittemore's read of Section's most recent AI Proficiency Report (numbers relayed in the transcript):

69% of surveyed workers report their organisation has taken some action on AI agents
16% actually use an agentic tool at work
<10% can define an AI agent in their own words
30% of employees at organisations with AI agents have received agentic training (as distinct from generic AI training)

Whittemore's summary of the report: "Agents are here; agentic readiness is not."

Anchor 2 — David Brooks: relationship to mental effort as the differentiator

Whittemore reads long excerpts from Brooks's Atlantic piece [The People Who Will Thrive in the AI Age]. Brooks opens with a set of empirical citations arguing that the "AI takes our jobs" prediction hasn't shown up — instead, work has intensified:

ActiveTrack analysis of 10,000+ workers: after AI adoption, email/messaging/chat app time more than doubled; business software use +94%; focused uninterrupted-work time fell 9% — coined by the researchers as "AI brain fry"
UC Berkeley Haas research: workers using AI take on tasks they previously outsourced (coding, engineering became easier); multitask more by supervising many bots; do work in evenings/weekends/waiting rooms because "AI was handy"
MIT Media Lab: brain connectivity down as much as 55% when using ChatGPT vs. not-using-ChatGPT for similar tasks (Brooks-relayed; unverified in this vault)
Possibility Sciences: gamma-wave activity down ~40% — a sign of cognitive effort (Brooks-relayed; unverified)
GoTo (software firm) survey: 43% of workers submitted AI-generated content they suspected contained errors / low quality

Brooks's proposed principle: "When intelligence is plentiful, volition is valuable."

Brooks's three archetypes (per need for cognition — psychologists' term for how much people enjoy thinking hard):

Archetype	Need for cognition	AI-era failure mode	Brooks's headline diagnosis
Productive passengers	Low	AI makes tasks easy enough that capability atrophies. Brooks cites MIT Media Lab + Possibility Sciences neuro data as the mechanism	Productivity up, thinking skills down
Reluctant optimizers	Medium	Resolve earnestly not to over-rely, but get sucked in under crowded/stressful workdays. GoTo 43% submit-suspect-AI stat is the marker	"If you're going for optimization, you're looking to maximize output, not excellence"
Mental marathoners	High	Wrestle with AI to increase agency; want their work to reflect their unique self; the ~26.2-mile-runner archetype for cognitive effort	"Going to work really hard to resist AI entropy"

Brooks's darkest anchor: Chris Siban (head of school at Rivendell, small private school in Northern Virginia). Siban showed his students a film that took 200+ artists 5+ years to make. Students: "Why do that? AI could have done it in 5 minutes." Siban's coinage: **"the industrialization of detachment."*

Brooks's closing (light) optimism: "willpower has some hereditary basis but it is also extremely sensitive to context. If AI has a tendency to undermine volition, humans can reform institutions to help build it up."

Whittemore's disagreement (mid-episode): "He gives lip service to the idea that those intrinsic levels of motivation are not necessarily fixed, but you can almost tell that he doesn't really believe it. He's giving a nice spin on things to end with some optimism, but it's clear he basically thinks that the marathoners are the only ones who survive this transition."

Whittemore's positive-framed alternative to Brooks's advice:

Brooks: "make sharp distinctions between rote work and creative work — let AI write functional emails, not essays or memos." Whittemore's rebuttal: "do we really think that most of the corporate communications that we're responsible for writing involve within them some paragon of virtue of the effort to discuss the results of the latest meeting?"
Whittemore's bigger opportunity: "not just use AI for things you can already do, but to use AI for things you can't do." The clearest example: build an agent to do something for you if you're not a coder. "Doing so involves a lot of humility, of asking AI how to do something, and then when it tells you how, screenshotting what it said and asking another AI what the heck those words mean, of trying things, coming up against an error, and then having to figure out what that error means, of feeling the power of releasing something that you never could have built before, only to have it crumble on the first touch with other people."

That's the mental-marathon mechanism, but its fuel isn't intrinsic cognitive appetite — it's the level of ambition around what you might go try next, which is context-dependent and institutionally shapeable.

Anchor 3 — AI Champions (WSJ CIO Journal) → internally deployed vibe coders

The WSJ CIO Journal piece Whittemore engages: "AI champions" — employees who volunteer to receive early tool access + special training + opportunities to present to senior executives in exchange for promoting adoption and fielding questions. A law firm example: 60+ champions now formalised into a programme.

Whittemore's critique: the article treats champions as "effectively just internal PR agents." Whittemore's re-framing: the real value of champions is not telling people how good AI is — it's showing them what they could actually be doing if they tried.

Whittemore's 2026 prediction (referenced from an earlier episode): "internally deployed vibe coders" — an extension of Forward Deployed Engineering inside the organisation:

"People who are increasingly using the new capabilities of AI, and specifically agents including the coding and building capabilities of AI agents, to pair and partner with business functions in ways that could help those business functions start to figure out how that new capability set could actually change how they work. Not folks who are helping people figure out how to make their current work happen 20% faster. It would be people who would pair to help business functions figure out how to fundamentally change not only how they do what they do, but even in some cases what they do."

Anchor 4 — Uber's Agentic Pods (the vault-load-bearing case study)

Whittemore ends on Praveen Napali (Uber CTO) tweeting the results of their pods programme:

"Agentic AI adoption is on fire at Uber, and it's changing the way we build, not just in engineering, but across the entire company. Today, 99% of our engineers use AI tools. More than 70% of pull requests are attributed to local or cloud agents, and our engineers have built 2,500-plus agent skills across the software development life cycle. Those numbers are exciting, but they led us to a much bigger question. How do we bring agentic AI beyond engineering?" — Praveen Napali

The mechanism: agentic pods.

~30 handpicked most-AI-proficient Uber engineers, each paired with a domain expert from a business function (finance, legal, operations, marketing, customer support, HR, procurement)
2-week timebox per pod, with a specific daily cadence:

Day(s)	Activity
1–2	Shadow the domain expert. Observe every step; document workflows; ask questions; build intuition.
3	Prioritise opportunities by scale + repetition + business impact + data availability.
4–5	Build a working agent alongside the person doing the job.
6–9	Validate with several others performing the same work. Does it generalise? Does it actually make their job better?
10	Ship.

16 pods across 16 different business functions in the past 2 months. Headline productivity results (Napali's numbers):

Workflow	Before	After
Capital allocation across 150 cities	15 hours	30 minutes
Financial pacing reports	2 days	10 minutes
Marketing web quality assurance	2 weeks	50 minutes
Support workflow creation	~9,000 manual workflows	self-service automation

Napali's own reflection on what surprised them the most:

"It was how quickly engineers embedded in unfamiliar domains uncovered opportunities that had been hiding in plain sight. The biggest wins rarely come from automating one task. They come from rethinking an entire workflow. Once you redesign the workflow around AI, you often eliminate handoffs, remove unnecessary approvals, replace legacy tooling, reduce vendor spend, and dramatically accelerate decision-making. The workflow becomes the unit of automation, not the individual task. The most impactful agent skills cut across teams, orgs, functions, tools, and systems."

Uber is now forming a dedicated team to scale this further — to "deeply understand the work, redesign it from the ground up, and use AI to fundamentally change how the business operates."

Whittemore's take on the 2-week results: nice, but the real payoff is over the next several months as the business people themselves start to think differently at core levels about the broader expanse of their work. His prediction: "in many, if not most cases, [the reinvested 1-day-23-hours-50-minutes] won't be doing more of the same work. It will likely be doing new work, orthogonal work, work that was always dreamed but never possible before." The gains from productivity aren't the payoff — the reinvestment of the productivity gains is.

Whittemore's closing frame: challenge people, don't shame them

"I think that in most cases, in both education and work, we haven't really asked people for much for a very long time. We haven't stretched them. We haven't challenged them. We haven't incentivized them to be challenged. We give them discrete buckets of tasks, often to be done for nearly inscrutable reasons, and tell them success is doing those tasks in the time that they have allotted. That might be fine for corporate functioning, but it certainly doesn't maximize people's true potential. And I think, if we do AI well, by which I mean actually supporting it, we will find far more potential in people to be maximized than most people realize is there."

The disagreement with Brooks is straightforward: Brooks reads the marathoners as intrinsically motivated and worries the rest cannot follow; Whittemore reads the archetype boundary as institutionally shapeable, with pods + champions + volition-fuel as the operational moves.

Where this connects to the vault

Mental Marathoners (Brooks Archetypes) (new) — the three-archetype taxonomy holds a compact frame this vault can cross-reference every time the mobility question surfaces (does AI de-skill or upskill, and for whom?).
Agentic Pods (new) — Uber's 2-week engineer + domain-expert pod recipe; the operational form Whittemore has been calling "internally deployed vibe coders". Firm-level extension of Tasks to Responsibilities Shift (Ryberg: individual scope → outcome ownership) and IT Ops Models (A B C) (Brovich: which operating-model shape supports pods).
Cognitive Offloading — Brooks's neuro citations (MIT Media Lab 55% brain-connectivity drop, Possibility Sciences 40% gamma drop) go into the cognitive-tier variant with the flagging note; AI Brain Fry (ActiveTrack coinage) is a distinct workload-intensification mode complementing atrophy.
FOBO (Fear of Becoming Obsolete) — Brooks archetypes recut FOBO by volition-tier: passengers atrophy, optimizers get sucked in, marathoners resist. Whittemore's disagreement with Brooks on mobility is the same shape as his disagreement with Justin Sung on the "same workflow-reasoning that replaces you" — the institutional level shapes what individual response looks like.
Tasks to Responsibilities Shift — Napali's "workflow becomes the unit of automation, not the individual task" is the same move at firm-level: not individual-task ownership (Ryberg), not team-scope (Brovich), not business-model (Alströmer/YC) — the cross-functional workflow itself as the automation unit.
Verification Tax — Uber's 70% agent-attributed PRs + 2,500+ skills are scale evidence that Brovich's verification-tax problem is real (each PR needs verification) but Uber has evidently learned to operate at that scale; Whittemore doesn't dig into their verification approach.
Reverse Information Paradox / Company Brain — Uber's pods discover that "opportunities are hiding in plain sight" because "you have to sit next to the people doing the work". This is Tacit Knowledge Route 3 (video-embodied / keystroke-tracking) done by humans instead of Meta's MCI. The pods are a social mechanism for the same intelligence-exhaust capture problem Satya names on the machine side.

Connects to your work

For P&G Manila IT + the CIO-audience communication programme:

The Uber pods pattern is directly imitable at MIH scale. 30 AI-proficient MIH engineers paired with 30 domain experts (from finance / operations / marketing / customer support / HR / procurement / R&D). 2-week timebox. 16 functions in 2 months. This is the closest working example the vault has of how to actually do agentic transformation in a large enterprise IT organisation — and it's much better documented than the Anthropic-EI framings.
Napali's workflow-not-task automation frame matches the enterprise-IT translation Brovich has been reaching for. Combined with Sarah Guo's IT-Ops-B (embedded pods) framing, MIH has an unusually clear playbook shape now.
Section's 16% / <10% agentic-tool + agent-definition numbers are useful for a Manila IT baseline survey (how does MIH compare) and a benchmark to grow against.
Brooks's three archetypes give a communication vocabulary for the FOBO conversation with MIH: don't tell people not to worry (they hear dismissal); don't tell them they'll be fine (they hear condescension); tell them there's a mobility path from passenger → optimizer → marathoner and here's the institutional support for the transitions. Directly usable as podcast fodder.
Whittemore's "we haven't really asked people for much for a very long time" line is the line for the CEO's "culture as the gating factor" thread from the Jejurikar CPG-Company-of-the-Future essay.

Follow-up — 2026-10-20

The champions anchor above got its full programme design three months later in How to Go from AI Power User to AI Leader (AI Daily Brief) (Whittemore + Nufar Gaspar): the ambassador → internal-FDE spectrum, nomination signals and anti-patterns, the two-sponsor "day after" model, and the builders' checklist. Filed as AI Champions Network; the "internally deployed vibe coders" prediction is now the containment edge case in that playbook.

Sources

raw/processed/How to Help People Thrive with AI.md
YouTube: https://www.youtube.com/watch?v=bl76qV0xwec
David Brooks, The People Who Will Thrive in the AI Age, The Atlantic
Praveen Napali (Uber CTO), X (Twitter) thread on Agentic Pods
WSJ CIO Journal, "AI Champions" article