AI Explained Official Podcast • 17m

Overview

This episode is a fast read on a messy 24 hours in AI model releases. The host argues that the real story is not who tops every leaderboard, but how three frontier labs are pushing a new pitch: near-frontier performance at much lower cost.

Most of the focus is on OpenAI's new GPT-5.6 line - Sol, Terra, and Luna - and how those models compare with Anthropic's Fable, Opus, and Sonnet, plus pressure from Grok, Meta, and GLM. The host's main point is that pricing is starting to matter as much as raw capability, especially for business tasks where "good enough" can change workflow habits fast.

Key Takeaways

OpenAI's release looks strong because the host says Sol often lands at about a third of the cost of Anthropic's comparable models, while staying close in performance and sometimes beating them. That changes the buying decision. If the output is close enough, a lower price can matter more than a small benchmark edge.

The host spends a lot of time on benchmarks that try to measure real work rather than toy tasks. On Agents Last Exam, OpenAI says GPT-5.6 Sol hit almost 54 percent versus Fable's 45 percent. The host treats that as more meaningful than a generic leaderboard result because the benchmark was built from real projects across 55 industries, with expert-designed tasks and reproducible scoring. His broader claim is that we did not wait for coding models to get near-perfect before people started using them first, so the same shift could happen in finance, operations, and other white-collar work.

There is a check on the hype. The host points out that some coding comparisons are less clean than they look because benchmark aggregates can reuse the same underlying tests, and some tougher benchmarks did not include GPT-5.6 Sol results. He also notes that Grok 4.5 and GLM 5.2 complicate OpenAI's value story. A model can be "almost as good but cheaper" than Anthropic, yet still look expensive next to Meta, xAI, or Chinese competitors.

Another theme is that verifiable domains are falling faster than messy ones. The host mentions a competitive coding benchmark that an OpenAI model appears to have effectively maxed out. His read is that when answers can be checked cleanly, models improve hard and fast; weaker results elsewhere may say more about evaluation difficulty, sparse training data, or limited reasoning budget than about a hard ceiling in model ability.

Practical Steps

If you buy models for work, do not compare only the top model from each lab. Test three tiers: a flagship, a mid-tier option, and one low-cost alternative from another vendor. The host's argument only makes sense if you measure output against spend.

Run your own benchmark on tasks you already do every week. Good candidates are:

• financial analysis or reporting
• workflow automation in Zapier or similar tools
• coding tasks in terminal environments
• quick app, game, or website prototypes

Track two things together: success rate and total cost per completed task. If a model is slightly worse but far cheaper, it may still be the better default.

For product and design work, test vibe-coding models separately from enterprise reasoning models. The host suggests that for game mocks, websites, and prosumer builds, you may not need the most expensive OpenAI option at all. A cheaper model from Meta or xAI could be enough.

Be careful with benchmark headlines. Check whether the result comes from a fresh benchmark, whether the tasks are reproducible, and whether the same tests are being counted twice in an aggregate score.

Notable Quotes

• "What if we can give you almost as good at a fraction of the price?"
• "There wasn't a singular benchmark that we beat... where we switched from hand coding first to AI coding first."
• OpenAI lead, replying to an Anthropic post: "I smell fear."

Decoder with Nilay Patel • 1h 2m

The Story

Nilay Patel brings Peter Kafka on at exactly the right moment: Comcast has finally started taking apart the empire it spent years insisting made sense. First came the cable network spinoff into Versant, which holds the fading channels nobody seems eager to own outright. Then came the bigger break. Comcast says it will split into one company built around broadband and distribution, and another built around NBCUniversal's entertainment assets: NBC, Peacock, Universal's studio, and the theme parks. After years of hearing Brian Roberts explain why "content plus pipes" belonged together, Kafka reads this move for what it is: an admission that the story never really held.

The conversation keeps circling one old dream. Media and telecom executives have long believed that if you owned both the network and the programming, you could make each one stronger. AOL bought Time Warner on that logic. AT&T bought Time Warner on that logic. Verizon tried a version of it with AOL and Yahoo. Comcast's NBCU deal was the longest surviving example, which almost made it seem smarter than the others. But Patel and Kafka keep coming back to the same point: survival is not the same as success. Comcast held the thing together for 15 years, yet still never found a clean answer for why the combination created special value.

From there, the episode turns to the internet fight beneath all of this. Patel argues that net neutrality sat at the center of the whole plan. If internet providers could have favored their own services, throttled rivals, or charged streamers extra tolls, maybe owning both content and distribution would have paid off. Kafka is less convinced that regulation was the deciding factor, but both agree that Netflix changed the balance. Once Netflix got big enough, consumers expected it to be available everywhere, and any distributor trying to mess with that risked a backlash. That, more than any corporate slide deck, made the old cable-style gatekeeping harder to pull off online.

Versant comes off as a holding pen for declining assets that still throw off cash. Kafka says its job is basically to squeeze value from cable while trying to buy time for something else, a move old media companies have tried for decades and rarely pulled off. NBCUniversal looks stronger, mostly because it owns things that still matter at scale. The parks are hard to copy. The studio still matters. NBC remains one of a few places that can put major sports in front of all of America at once.

By the end, the split feels less like a single transaction than part of a broader unbundling. The old theory that size and vertical integration would protect legacy media is giving way to something messier, where everyone is selling, spinning, or shopping for assets without much confidence about the final shape. Patel and Kafka sound almost energized by that chaos. After years of watching the internet slowly turn television into something duller and more fragmented, the breakups at least make the story interesting again.

Main Themes

The main theme is failure disguised as strategy for a very long time. Comcast's breakup suggests that one of media's favorite ideas, pairing distribution with programming, kept living mostly because nobody wanted to admit it wasn't working. The company could defend the logic in theory, but in practice the internet kept pushing power toward the services people actually wanted, not the networks delivering them.

Another thread is that cable economics still haunt everything. Versant exists because the old bundle is shrinking but not dead, and everybody involved is still trying to pull cash from it while pretending a next act is around the corner. That connects to the sports discussion, where live events, especially the NFL, remain one of the few things that can still hold mass attention and justify giant distribution businesses.

The episode also keeps testing whether markets or regulators set the limits here. Patel sees net neutrality as the barrier that stopped telecom companies from rebuilding cable's control online. Kafka leans more toward consumer demand and scale, especially Netflix's ability to force distributors to carry it on acceptable terms. Either way, the result was the same: the internet did not become a toll road for every media company that owned a pipe. And now Comcast is reorganizing around that fact.

The Pragmatic Engineer • 1h 18m

Overview

This AMA covers why Gergely stepped away from engineering management at Uber, how he thinks about AI in software teams, what hiring is starting to look like, and where engineers can still stand out. The thread running through the episode is pretty consistent: ignore the hype, look at incentives, and stay close to real work.

He is skeptical of grand claims about "AI-native" companies or permanent best practices. His view is more grounded: teams should use AI where it solves an actual problem, and engineers who pair technical skill with business sense are the ones doing well.

Key Takeaways

Gergely says his move into writing was less a master plan than an honest reassessment. After Uber's layoffs and his own fatigue with middle management, he realized that the thing he wanted to do after financial success - write, teach, and share what he knew - was something he could already start. That mattered more than forcing himself into a startup he was not excited to spend a decade on.

On AI and software development, he pushes back on rigid labels. He argues that most strong teams already worked in a practical loop of planning, building, shipping, and adjusting. AI changes the speed and the tools, but not the need for judgment. He seems wary of companies trying to copy Anthropic or another lab just because it sounds current.

His view on hiring is blunt. AI has weakened older signals like take-homes and remote screening because candidates can lean on tools too heavily. He expects more in-person evaluation, more subjectivity, and more friction for candidates. That may be worse for applicants, but he thinks it is where things are heading.

The engineers in demand, according to him, tend to share a few traits: they work on products, care about the business, and have found a way to get hands-on AI experience. Companies want people who can make tradeoffs around model choice, architecture, inference cost, and deployment, not people who only say they use AI coding tools.

He is also less moralistic about code quality than many engineers would like. Bad architecture can be the price of speed, and sometimes that trade makes sense early on. The real mistake is pretending the same standard should apply equally to prototypes, scaling systems, and mature products. AI also lowers the cost of cleanup later, which changes the equation.

Practical Steps

• If you want to stay relevant, get direct exposure to AI at work. Propose an internal tool, a support workflow, or an incident-response helper. Do not wait for permission in the abstract.
• If your company is rigid, look for small experiments that leaders can say yes to. Gergely's point is that many executives want more AI usage and will back practical attempts.
• If you are trying to move upmarket as an engineer, build evidence. Side projects, open source contributions, and internships still matter, especially if your current employer does not give you strong signal.
• For juniors, take the stepping-stone job if that is what is available. He is clear that having a job and doing excellent work there beats waiting around for the perfect logo.
• Match code quality to stage. Move fast on prototypes, tighten up as the product stabilizes, and refactor when the system starts carrying real revenue or risk.
• If you are considering a startup, ask whether you actually want to spend years on that idea. Gergely treats that as a basic filter, not a romantic one.

Notable Quotes

• "If you start a startup, do it because you are ready to spend 10 years of your life on it."
• "I could do that right now." - Gergely, on realizing the thing he wanted after startup success was writing and sharing knowledge
• "Use it if it makes sense and throw it away if it doesn't." - on AI adoption inside companies

One Knight in Product • 55m

Overview

This episode is about the gap between "doing the practice" and getting any real benefit from it. The guest argues that teams get stuck when they copy playbooks, OKRs, templates, and meetings without being clear on what those things are supposed to change in the first place.

The core idea is simple: a way of working should be judged by whether it helps the organization move toward a goal in its own context. If it does not, the answer is not more ritual or stricter compliance. It is to inspect it, adjust it, and sometimes drop it.

Key Takeaways

The strongest thread in the conversation is the distinction between alibi progress and real progress. Alibi progress is what happens when teams perform the motions of modern product work - discovery sessions, canvases, OKRs, recurring meetings - without tying them to an actual outcome. Real progress starts when a team asks, "What is this supposed to do for us?" and then changes the practice to fit that answer.

The guest pushes back on the idea that any method can save a team by itself. OKRs will not fix a company that still rewards output over outcomes. A framework will not change much if leadership still wants long requirement documents and delivery theater. Teams often swap tactics while keeping the same assumptions, then wonder why nothing improved.

A useful move is to treat the operating model like a product. That means defining what success looks like, checking whether the current setup produces it, and changing the setup when it does not. The guest says this often exposes a basic problem: one leader may think the goal is obvious, while everyone else is guessing.

The discussion on OKRs gets more specific. The guest says many OKR failures come from teams being measured on things they cannot really influence, such as company-level revenue or EBITDA. A better approach is to find metrics closer to customer behavior that the team can affect, then make the case for how those metrics contribute to company goals. That connection may not be perfect, but it is better than pretending a product team directly controls a company-wide financial result.

Another strong point is that many process problems are diagnostic problems. Teams say, "OKRs do not work for us," but often cannot say why. Reflective questions help expose the real issue: weak leading indicators, no link to company strategy, or metrics outside the team’s sphere of influence.

Practical Steps

• Pick one practice your team uses now - a meeting, framework, template, or metric.
• Ask three questions:
  • Why are we doing this?
  • What change should it create?
  • How would we know it is working?

If the team cannot answer those clearly, that is already a finding.

Run a short review of recurring rituals. For each one, decide whether to keep, change, or remove it. Do not keep a meeting because it has always existed.

For OKRs or team metrics, separate:

• what the company cares about,
• what the team can influence,
• how the second is expected to contribute to the first.

If your key results are tied to numbers the team cannot move in any direct way, rewrite them around customer behavior or product signals the team can actually affect.

When a solution is handed down, reverse-map it. Work backward from the requested feature and ask what user behavior, problem, or company goal it is meant to change. Even if the work still goes ahead, this gives the team a basis for measuring whether it helped.

Notable Quotes

• "Make sure that the process serves you versus you serving the process."
• "The framework, the method won't save you. Like OKRs won't save you."
• "Treating your way of working like a product."

Worklife with Molly Graham • 36m

Overview

This episode centers on what Molly Graham and Ify Walker call "the work twisties": a period at work when you lose your sense of position, purpose, and trust in your own judgment. Molly opens with her own experience of taking a job that looked right on paper but left her feeling lost, then brings in Ify, founder of executive search firm O4, to name the feeling and explain how she found her way through it after the death of her father.

The conversation also widens into hiring and leadership. Ify connects personal disorientation with how companies make decisions, especially the gap between the stories organizations tell about hiring and what actually happens.

Key Takeaways

The strongest idea in the episode is that getting lost at work is common, but people rarely have language for it. "The work twisties" gives a name to that state where familiar strengths stop feeling accessible and basic decisions suddenly feel hard. Ify describes it as losing not just confidence, but orientation.

Her account makes clear that grief was the trigger, but the harder blow was identity loss. She says her sense of self was tied to being the person who knew what to do. When that disappeared, she started outsourcing judgment to other people, taking in too much advice, and drifting further from her own voice. That pattern is one of the episode's sharper points: advice can become a way to avoid choosing, and that can make confusion worse.

Another useful distinction is between fact and story. Ify describes a practice of separating what is objectively true from the catastrophic narrative built on top of it. The meeting is at 10 a.m. is a fact. "I will fail and won't be able to speak" is a story. That sounds simple, but in her telling it's a way to rebuild mental footing.

The hiring section adds a second thread: companies often say they want "the best person," but Ify argues most organizations hire from who they already know or who feels familiar. She says the real issue is not pretending hiring is a pure meritocracy. Her firm's job is to close the gap between expectations and reality by making cultural rules visible, even when those rules are uncomfortable.

Practical Steps

If you're in your own version of the work twisties, the episode offers a few concrete moves:

• Go back to the last thing you know you can do. Ify compares this to Simone Biles returning to cartwheels. At work, that might mean writing one clear email, running one meeting agenda, or making one decision you fully understand.
• Cut down outside advice for a while. If every conversation leaves you more scattered, stop polling the room. Create enough quiet to hear your own thinking again.
• Make a "fact vs. story" list. Write down what is actually happening, then separately list the fears and predictions attached to it.
• Start smaller than your pride wants. If all you can send is a three-bullet-point note to your team about current priorities, send that.
• If you're grieving or depleted, step off the escalator. Ify says her biggest regret was trying to power through instead of allowing space and silence.

For job seekers, her advice is blunt: be specific about who you are. Don't try to become a fit for every role. She argues that clarity is what lets the right people find you.

Notable Quotes

• "The twisties are this very disorienting sense of losing position. Like where do I fit? Losing your sense of purpose." - Ify Walker
• "It's okay to go away. It's okay to get off the escalator. Just because it's going up does not mean you have to continue to ride." - Ify Walker
• "Be yourself so the people who are looking for you can find you." - Ify Walker

Decoder with Nilay Patel • 1h 8m

The Story

This episode starts with a simple question that keeps getting bigger: what does it mean when a creator is no longer just making videos, but running a company? Nilay Patel talks with Allie Beerman and Raina Pinchansky, who lead UTA's creators division, and the answer is that the job has moved far past brokering sponsorships. Their clients are building businesses with product lines, events, media projects, and teams behind the scenes, and UTA is right in the middle of helping shape all of it.

Both Allie and Raina came up early, back when the internet still felt scrappy and self-directed. Allie came through talent agencies and got hooked on bloggers and online personalities who were building direct relationships with audiences before there was a clear business around it. Raina came from marketing and saw the same shift from the other side: people who looked like hobbyists were quietly turning into media brands. What mattered to both of them was the same thing: these creators had attention, trust, and communities before the rest of the business world quite knew how to price any of that.

From there, the conversation turns into a look at how much work sits behind the image of a creator casually posting online. UTA, as they describe it, now acts less like an old-school Hollywood agency and more like an operating partner. There are regular strategy meetings, product discussions, brand negotiations, analytics, long-range planning. The creators may be the face of the business, but there is a lot of structure underneath, especially once someone moves from sponsored posts into bigger bets like a beauty brand or a consumer product company.

Nilay keeps pressing on the unstable part of all this: the platforms. TikTok, YouTube, Instagram, all of them shape what gets seen and what gets paid, and none of them are under a creator's control. Allie and Raina don't sound panicked by that instability. Their view is that real stars survive platform shifts, and the best managers know how to spot that spark before the metrics tell the full story. They come back often to instinct, taste, and a creator's connection with their audience, which they see as the difference between a quick win and a durable career.

By the end, the conversation lands on two pressure points hanging over the whole business. One is the "influencer cliff," the risk that audiences reject a creator once the relationship turns too openly commercial. The other is AI, which could flood platforms with synthetic content and cheap copies of a creator's image or voice. Even there, Allie and Raina stay fairly steady. They see AI as a tool, not a replacement for personality, and they keep coming back to the same belief: audiences still want a human being on the other end.

Main Themes

The big theme here is that creators are now media companies, but with a different shape than the old ones. Instead of a studio owning the infrastructure and hiring talent into it, the talent sits at the center and the infrastructure gets built around them. That changes what an agency does. It also changes what success looks like. A healthy creator business can no longer rely on brand deals alone; it needs ways to turn attention into something more durable.

Another thread running through the episode is taste versus scale. Nilay is more skeptical of the platforms and where they might lead, while Allie and Raina put more faith in star power and audience connection. That tension gives the episode its edge. Everyone agrees the platforms are volatile. The disagreement is over whether strong talent can stay ahead of that volatility, or whether the system will always tilt power back toward YouTube, Instagram, and whatever comes next.

The episode also circles around a harder point about trust. Selling a product is not the same as getting views, and plenty of creators fail when they try to turn fandom into commerce. The guests argue that the ones who succeed are the ones whose products feel like a natural extension of the content, not a cash grab dropped on top of it. That idea ties everything together: brand deals, product launches, live events, even AI. The business only holds if the audience still feels like it knows who it's dealing with.

One Knight in Product • 57m

Overview

This episode is about how investor-backed companies hire and set up Chief Product Officers, and why that often goes wrong before the person has even started. Bea Kayla Pilgrim, a recruiter and founder of Smithfield Search, talks through findings from her CPO report, based on conversations with 18 product leaders with private equity experience.

The main thread is simple: a CPO role succeeds or fails less on title and more on intent, mandate, and company setup. Reporting lines, commercial clarity, and the actual problem the company wants product to solve all tell you whether product is being treated as strategy or as support.

Key Takeaways

Bea says one of the strongest signals in a business is where the CPO sits. If the role is buried under another function, that usually suggests product is being treated as delivery or IT, not as a strategic function. She’s careful not to overstate reporting lines as the whole story, but she sees them as a useful tell.

A recurring problem is that companies want a CPO before they’ve defined why they need one. Sometimes the role is hired after product-market fit, before scale, or when growth has stalled and the product is part of the reason. Those are real triggers. But a vague sense that "we should probably have product leadership now" leads to confusion, churn, and wasted time.

Bea draws a clear distinction between product leadership in PE-backed businesses and the more familiar Silicon Valley version. In PE, she says, the environment is more binary. There is a shared value-creation goal, a tighter commercial focus, and less patience for product theatre. The CPO has to connect roadmap decisions to business outcomes, not just team activity.

The report also flags three common failure modes:

• "Feature factory": teams ship a lot without creating measurable commercial value.
• "Land of lost toys": too many half-started initiatives and scattered priorities.
• "Tech debt hangover": old technical decisions slow the company down and limit what teams can do.

Bea argues these problems often slip through standard diligence because financial review does not always show whether product work is disciplined, coherent, or tied to outcomes.

Another strong theme is financial fluency. Product leaders do not need to own every revenue number alone, but they do need to understand how the business makes money and make sure the wider team does too. The host pushes on who should own net revenue retention, and the answer is less about a single department than about having clear accountability and close day-to-day alignment between product, sales, and customer success.

Practical Steps

If you are hiring a CPO, start with the business problem, not the job title. Write down what needs to change in the next 12 to 24 months and how product leadership would help.

Check the reporting line before you open the search. If the CPO will not have access to the CEO or the people making commercial decisions, be honest about whether you want a strategist or a senior delivery lead.

Audit your product function for Bea’s three failure modes:

• Are teams shipping features without tracking business impact?
• Do you have a backlog full of half-finished ideas driven by one-off demands?
• Is technical debt slowing execution enough to affect growth?

Run a basic alignment review across product, sales, and customer success. Set regular touchpoints that are not just for emergencies or escalation. Use them to review customer pain points, product priorities, and revenue signals together.

If you lead product, build your financial fluency early. Learn the numbers that matter to the business, how growth is measured, and what investors or executives expect product to influence.

Notable Quotes

• "If the CPO is buried too far down the organization, it can suggest that business sees product as a function rather than a strategic leader." - Host

• "The role has to be shaped around the actual challenge." - Bea Kayla Pilgrim

• "A CPO without a genuine product problem to solve is an expensive overhead and a source of organisational friction." - Bea Kayla Pilgrim

Decoder with Nilay Patel • 56m

The Story

This live Decoder episode is basically Neil Patel and Amy Lanzi standing in the middle of Cannes and saying out loud what a lot of the ad business says more quietly: the AI sales pitch is getting out of hand. Amy, who runs Digitas North America, starts from a pretty unsentimental place. She says the market is full of wild promises, weird commercial terms, and offers that sound flashy but are bad for the business over time. Publicis even made a Cannes spot mocking those promises, and she makes clear it was not much of an exaggeration.

Her bigger point is that this all feels familiar. She compares the current AI wave to the programmatic era, when people claimed advertising would more or less run itself. That never happened. It still needed people, judgment, and an understanding of brands and markets that software alone could not supply. For Amy, AI is useful, but mostly when it helps teams work faster, test more ideas, and clear away repetitive work. She talks about Digitas building agents from the bottom up, with younger employees finding practical uses inside the day-to-day work, then turning those into tools that solve bigger business problems.

From there the conversation turns to a harder question: what happens when platforms like Meta say they can do the targeting, the measurement, and now the creative too? Neil pushes on this, and Amy pushes back fast. She hates the idea that "creative is targeting," because it turns something emotional into something mechanical. She argues that the industry does not need more content for the sake of more content, and that handing all of this to a platform risks flattening brand identity into an endless stream of optimized filler. Data matters, but only if it helps brands learn, adjust, and avoid burning out the audience.

That same tension shows up in the creator economy. Neil expected AI and platform pressure to drag creator rates down. Instead, Cannes is packed with creators charging more than ever and calling themselves marketers. Amy sees the logic. Demand is high, and the biggest creators now operate like media companies, sometimes on their way to becoming full businesses with products, distribution headaches, and growth plans that look a lot like any other consumer brand. That's where agencies come back into the picture. Once a creator becomes an enterprise, they need help.

By the end, the conversation gets broader and darker. Neil brings up Adam Mosseri's vision of a fully personalized Instagram, where the app becomes different for every user. Amy's reaction is blunt: that sounds terrible. She thinks people will eventually reject platforms that become too isolating, too manipulative, too detached from any shared public experience. Her bet, and maybe her hope, is that community still matters enough to push back.

Main Themes

The thread running through the whole episode is that automation keeps promising to remove the messy human parts of advertising, and the human parts keep turning out to be the whole job. Amy is fine with AI as a tool inside the machine. She is much less interested in treating it as the machine itself.

Another theme is consolidation. Agencies, platforms, retail media players, and creator businesses are all getting bigger because scale now decides who gets to shape the system. But that scale creates new dependencies. Brands need platforms, platforms need brand money, creators need operations, and agencies want to sit in the middle by connecting data, media, commerce, and creative into one growth engine.

The episode also keeps returning to control. Who owns the customer relationship? Who decides what creative gets made? Who gets to shape how people see the world online? Amy's answer is that brands should resist giving all of that away, whether to a platform's AI stack or to a creator's personal style. The work is still to build something distinct, then keep it coherent as every part of the internet tries to turn it into feed material.

AI and I • 41m

Overview

This episode is a field report on how AI is moving from demo to daily work. Dan talks with Natalia, Every's head of consulting, about how she uses agents and coding tools in real operations, both at work and at home.

The thread running through the conversation is simple: AI is great at handling repeatable process, summarizing messy information, and turning ideas into working tools fast. It still needs supervision, judgment, and, in many cases, existing software that already solves hard edge cases.

Key Takeaways

Claudi, Every's internal AI agent, has grown from a half-manual experiment into a system that does real operational work every day. Natalia says it manages dashboards, handles CRM-related tasks, and runs a self-evaluation loop she calls a "trust battery." That progress came from better models, but the work is still not hands-off.

A clear limit showed up too. AI performs well against a standard operating procedure, but it still needs oversight, feedback, and someone to decide what good looks like. Natalia's team is hiring an operations person even with Claudi in place, because surfacing useful signals, guiding conversations, and working with humans still matters.

The conversation pushes back on the idea that companies should replace SaaS with quickly built internal tools. Natalia had a homegrown CRM setup stitched together with Google Sheets, email, meeting notes, and Claudi. It worked for a while, then the maintenance cost caught up. Her point is that you can build many things now; the harder question is whether you should own the upkeep. Tools like Attio and Asana handle a pile of hidden logic that only becomes obvious once volume and complexity rise.

Another strong idea is that AI changes the shape of knowledge work. Natalia compares it to gardening: your job is to set conditions, steer, prune, and review, rather than do every task by hand. That showed up in how she uses Codex and Claude artifacts to make learning materials, travel guides, and planning tools tailored to her needs.

The most grounded example was personal. Natalia used Codex to build a shared care portal for her 81-year-old father. It pulls together nurse reports, WhatsApp updates, follow-ups, and family tasks into one place, with language toggling and responsibility tracking. The value wasn't the app as an object. It was less searching, better coordination, and more time for actual care.

Practical Steps

• Start with a process that already has clear rules. Sales pipeline updates, inbox triage, project tracking, and status summaries are better entry points than open-ended strategic work.
• Audit the maintenance burden of your AI workflows. If your custom tool depends on constant fixing, checking, and prompt tuning, compare that cost against buying software built for the job.
• Use AI as a layer on top of your existing tools. Natalia's examples work because AI can read email, meeting notes, forms, and messages, then pull the signal into one useful view.
• Build small internal tools for specific pain points:
  • a family care tracker
  • an inbox triage dashboard
  • a personalized learning guide
  • a travel planner based on your preferences
• Treat AI outputs like drafts from a fast junior operator. Review them, improve the rules, and decide where human judgment needs to stay in the loop.
• For executives, pay attention to admin drag. The biggest near-term gains may come from offloading coordination work, not from replacing core decision-makers.

Notable Quotes

• Natalia: "AI is really good at executing against a standard operating procedure."
• Natalia: "The question is, should you build and maintain whatever you actually built?"
• Natalia: "Knowledge work now is turning into something like gardening, where when you're gardening, you're creating the conditions for the growth to happen."

Worklife with Molly Graham • 32m

Overview

This episode is a live TED conversation with Molly Graham about careers, leadership, and what it takes to stay sane while work keeps changing. Her main argument is that careers rarely move in a clean upward line, and the biggest growth often comes from taking risky jumps into roles where you do not yet feel ready.

The conversation also gets into how leaders handle scale, why fear makes people cling to old identities, and why asking "dumb" questions is often a sign of strength rather than weakness.

Key Takeaways

Molly Graham uses two simple career images: "the stairs" and "the cliff jump." The stairs stand for the safe, expected path - title, promotion, performance review, repeat. She says many people stay there less because they need to and more because they are afraid. Her test is useful: fear about basic survival deserves respect, but fear of failing may be a sign that the opportunity is worth taking.

A strong point in the episode is her timeline for discomfort. She says the falling phase after a big leap can last six to nine months before a real sense of competence shows up. That matters because many people read early confusion as proof they made the wrong move, when it may just be the normal part of learning.

She also makes a case for being a "professional idiot." In her telling, people who can ask basic questions without protecting their ego often learn faster than everyone else. She says beginner eyes catch things insiders miss, and that many organizations are full of unasked questions because people are too worried about looking foolish.

On leadership, Graham says scale is defined less by absolute size than by the rate of change. She points to teams and companies growing fast and argues that employees often get stuck when they cling to the work that first made them valuable. Her "give away your Legos" idea is about handing off the thing you built so you can grow into the next job before the company outgrows you.

She also argues that leadership is not about making people successful. It is about creating the conditions where they can do their best work. That means paying attention to the messy human side of work, not just process and plans, and finding support outside the company when senior roles get lonely.

Practical Steps

• Sort your fear into categories. Write down what scares you about a job change or stretch assignment. Separate practical risks, like income loss, from ego risks, like embarrassment or failure. Treat them differently.
• Expect a long awkward phase after a jump. If you move into a new role, give yourself a real runway before deciding you are bad at it. Graham says competence may take six to nine months to appear.
• Ask the basic question in the room. If a word, acronym, or decision does not make sense, ask. If you do not want to do it publicly, follow up right after the meeting.
• Build a beginner-feedback loop. Graham says her company asked new hires for a 30-day readout on what looked odd, unclear, or surprising. Managers can copy that by asking new team members what veterans no longer notice.
• Give away work before you feel fully ready. If you are leading in a fast-growing group, identify one responsibility you are hoarding because it defines you. Train someone else to take it so you can move to the next problem.
• Find outside support. Graham makes the case for coaches, peer groups, or trusted mentors because senior jobs get isolating fast.

Notable Quotes

• Molly Graham: "Most people do not stay stuck on the stairs out of necessity. They stay there out of fear."
• Molly Graham: "I am comfortable sounding like a moron."
• Molly Graham: "The world is littered with important questions that never got asked."

Decoder with Nilay Patel • 1h 11m

The Story

This episode starts with a neat bit of symmetry. Years ago, Decoder wanted Weber for its summer grill series and got turned down, so Nilay Patel talked to Roger Daley instead, back when Daley was running Blackstone and riding the wave of griddle mania. Now Daley is back as CEO of Weber Blackstone, having gone from upstart outsider to the person in charge of one of the oldest names in outdoor cooking.

Daley explains that the path there was messy and very financial. Blackstone grew fast enough that it needed dependable manufacturing in China, then new ownership when that manufacturing partner wanted out. That sent him into talks with bankers, a near-SPAC, and eventually into the orbit of BDT, which had long been tied to Weber. At one point Weber almost bought Blackstone. That fell apart. Later, after Blackstone kept growing and hit its targets faster than its investors expected, the deal came back in reverse form: a merger that was, in practice, Blackstone taking over Weber. Even that got stalled for months in FTC review, less because of real antitrust danger than because the commission was stuck in an administrative transition.

Once the deal closed, the real problem showed up. Daley says Weber was still respected by customers and still sold strong products, but it had become layered, siloed, and expensive. He talks about culture in plain terms: Blackstone wants people to pick up the trash in the parking lot because the company is theirs; Weber had become the kind of place where people worried that doing so might step on someone else’s role. That difference, to him, captures the gap between an entrepreneurial company and a legacy one.

So the merger became an integration fight. Daley spent months learning the Weber organization before making top-level changes, then brought in consultants to help sort through duplicated functions, leadership roles, and product teams. He says there were hurt feelings on both sides. Some Weber people felt disrupted, and some Blackstone people acted like they had nothing to learn. He had little patience for either reaction.

By the end of the conversation, the merger starts to look less like a grill story and more like a broad company-building story. Daley is trying to keep Blackstone’s speed and product instinct while using Weber’s brand strength, premium reputation, and manufacturing footprint, including factories in Illinois and Poland. At the same time, he is dealing with tariffs, higher steel and energy costs, price-sensitive customers trading down to charcoal, and the usual internet-age problem of knockoffs flooding Amazon.

Main Themes

The strongest theme here is that old brands rarely fail because customers stop caring. They fail because the company gets too slow, too segmented, and too costly. Daley clearly believes Weber’s problem was not the kettle or the Genesis grill. It was management drift and a structure that made movement harder than it needed to be.

Another thread running through the episode is that retail power still shapes this business. Even with two major brands, Daley says he cannot simply dictate prices or control the market. Retailers have their own labels, their own merchandising strategies, and plenty of alternatives. That makes product planning, pricing, and brand position far more specific than the usual "premium" versus "value" split.

The conversation also keeps returning to how physical goods businesses are getting squeezed from all sides. Tariffs raise costs, moving factories creates headaches, fuel and power prices hit customers directly, and cheap copies appear online almost immediately. Daley’s answer is brand strength, faster product cycles, and a steady stream of accessories and improvements driven by what customers actually do with the products.

What makes the episode interesting is that Daley still sounds like a product guy, even while running a much larger company. He talks about culture and org charts because he has to, but he lights up when the subject turns to griddles, thermometers, kettles, and the next thing people might want to cook outside. That tension sits at the center of the whole conversation: how do you keep the instinct of a founder when your job has become managing scale?

Decoder with Nilay Patel • 1h 3m

Overview

This episode is a wide-ranging interview with Ford CEO Jim Farley about where Ford's EV strategy went wrong, what the company is changing, and how he thinks about competition from China, software, tariffs, and in-car tech. The backdrop matters: Farley is talking from a moment when Ford was betting that its next EV platform would fix the economics and product problems exposed by the Mach-E era.

He argues that Ford's first generation of EVs taught the company what customers will tolerate, what they will pay for, and how far behind traditional automakers are on cost and engineering simplicity compared with companies like BYD and Tesla.

Key Takeaways

Farley says Ford's next EV push is built around one hard lesson: selling an affordable EV is meaningless if it loses money on every unit. His point was less about headline price and more about build cost. He described Ford's answer as a separate "skunkworks" team, kept outside the company's old systems, to rethink the vehicle from scratch.

A big theme was how badly Chinese EV makers have changed the game. Farley described BYD and its peers as the standard Ford has to measure against, not just Tesla or GM. He says the challenge is not only battery cost but the whole package: simpler design, fewer parts, better digital experiences, and government-backed scale.

He was unusually direct about Ford's internal limits. In his telling, the existing organization could not close the gap because its engineering tools, release systems, and habits were too old. He tied that conclusion to a management idea he picked up at Toyota: "gemba," or going to inspect the real problem in person. For him, looking at the weight of a wiring harness and the number of fasteners in a Mach-E versus a Model Y made the decision obvious.

On software, Farley drew a line between supporting Apple and giving Apple full control of the car. Ford wants CarPlay and phone integration because, as he put it, the company should not disrupt a customer's digital life when they get in the car. But he also suggested Apple CarPlay Ultra may go too far if it takes over core vehicle controls. That leaves Ford trying to build more of its own software layer, especially around driver assistance and AI features.

He also spent real time on blue-collar labor. Farley says the U.S. has a shortage of factory workers, tradespeople, and emergency service workers, and that AI investment is tilted too far toward office work. He sees that as a national problem, not just a Ford hiring issue.

Practical Steps

For automakers and operators, Farley laid out a few concrete ideas:

• Simplify the launch product. He says Ford is trying to start with fewer variants, less feature sprawl, and a more controlled rollout.
• Build the first version around core capability. Get the base vehicle, manufacturing process, and software stable before adding more options.
• Inspect real bottlenecks directly. Farley's "gemba" habit is simple: go look at the part, the workflow, and the waste before making a major decision.
• Measure EV strategy on unit economics, not press-release affordability. A low sticker price does not help if the car is unsustainably expensive to build.
• Keep phone integration easy, but be careful about handing core vehicle controls to outside platforms.

For listeners shopping for EVs, one practical point came through clearly: Farley thinks the market is shifting away from premium EVs toward cars around the $30,000 range, where total ownership cost and day-to-day usefulness matter more than novelty.

Notable Quotes

• Jim Farley: "The Chinese are the 700-pound gorilla in our industry for EVs."
• Jim Farley: "Ford does not have the rights, in our opinion, of disrupting someone's digital life when they get in their car."
• Jim Farley: "There are no assurances that we can do this."

AI and I • 43m

Overview

This episode is a conversation with Edwin, founder and CEO of Surge, about the role of data, expert judgment, and evaluation in building advanced AI systems. He frames Surge as a "school for AGI" and argues that the work has moved well beyond basic benchmarks into teaching models taste, judgment, and the ability to act in messy real-world settings.

The discussion also turns to what happens if AI becomes better than humans at more and more intellectual work. Edwin says he could see systems reaching abilities associated with AGI within five years, which raises a harder question than capability: what humans should still choose to do for themselves.

Key Takeaways

Edwin’s main point is that training frontier models now looks less like feeding them facts and more like shaping judgment. Early benchmarks asked whether a model could do middle-school math. More recent work, he says, tests research-level mathematics and open-ended reasoning. He points to the shift from GSM8K to newer benchmarks such as Riemann Bench as evidence that the target is changing fast.

He also argues that evaluation is often the hidden driver of bad model behavior. If labs optimize for shallow public leaderboards, time spent, or flashy outputs, models learn to game those signals. His example from creative writing was blunt: some models produce a metaphor in nearly every sentence because that pattern seems to score well, even when the writing gets worse. In his view, this is a measurement problem as much as a model problem.

A second thread is the risk that AI products drift toward the same engagement traps as social media. Edwin says models can be pushed to keep users talking for one more turn rather than helping them finish a task and move on. He gave examples of chatbot follow-ups that sounded like tabloid hooks, which suggests some systems are already picking up these habits.

He sees a better path in delegation rather than addiction. A good assistant should sometimes do work in the background and sometimes tell the user to do it themselves, if that helps them grow. That means the product goal should be human flourishing, not just minutes of usage.

On personalization, Edwin thinks personal data is valuable because current systems still lack real context. Email behavior, browsing patterns, writing style, past decisions, and AI conversation history could all help train systems that understand a person’s preferences more accurately. He also says current memory features often overfit to stray details instead of the things that matter.

Practical Steps

• Audit what your AI tools are optimizing for. If a tool keeps dragging you into extra turns, ask whether it is helping you complete work or just holding attention.
• Use AI for delegation where the task is clear: summarizing inboxes, filtering spam, drafting routine responses, or handling repetitive research.
• Keep your own judgment in the loop for writing, decision-making, and creative work. Edwin’s point is that preserving human agency may need to be a deliberate choice.
• If you build AI products, measure quality with domain experts, not just broad user voting or surface-level preference tests.
• Collect high-signal personal data carefully if you want better personalization: edits to drafts, accepted vs. rejected email suggestions, repeated decisions, and task outcomes are more useful than generic chat logs alone.
• Watch for reward hacking in generated content. Flashiness, verbosity, and ornamental prose can be signs that a model learned the score rather than the skill.

Notable Quotes

• Edwin: "We are building this kind of school for AGI, where AI models come to learn about humanity, where we teach them how to run the world."
• Edwin: "It almost seems like there's nothing that humans can do that AI won't soon be capable of."
• Edwin: "We actually almost have to consciously choose to prove things on our own and to write on our own and create on our own because we have to believe that preserving our humanity is valuable in of itself, even if the output isn't optimal."

HBR On Leadership • 30m

Overview

Linda Hill argues that innovation is not a side project or a perk for good times. It is tied to survival, especially when leaders are dealing with uncertainty, new technology, and pressure to adapt faster than their organizations are built to move.

Her main point is that repeat innovation does not come from a heroic visionary with all the answers. It comes from leaders who build the conditions for people to contribute ideas, test them, and spread what works across teams, partners, and sometimes whole networks outside the company.

Key Takeaways

Hill pushes back on a common idea about leadership: when innovation is the goal, leadership is less about getting people to follow a fixed vision and more about getting them to co-create the future. Leaders still need direction and judgment, but they also need to make room for other people’s "slices of genius."

She says most organizations are weak at the three things innovation depends on:

• collaborating across differences
• experimenting and learning
• making decisions that move ideas forward

A strong planning process is not enough. Hill says you "act your way" to innovation because the path is rarely clear in advance. That means leaders need discipline around experimentation, not the illusion that they can map every step before they begin.

Another theme is that stalled innovation often has less to do with a lack of ideas than with a lack of trust and meaning. People are more likely to speak up, take risks, and work through conflict when they believe the work matters and when they feel respected by the people around them.

She also highlights three leadership roles companies need to build on purpose:

• Architects, who shape the organization so it can innovate repeatedly
• Bridgers, who connect silos like tech and business, and often connect the company to outside partners
• Catalysts, who create broader coalitions that help ideas spread and scale

Hill’s point about "wayfinders" stands out. In periods of uncertainty, leaders often do not know the exact destination. Their job is to help people move through ambiguity using values, judgment, and learning along the way.

Practical Steps

Leaders who want to restart innovation can begin with a blunt assessment of culture and capability. Ask where the current culture helps innovation and where it blocks it. Then look at whether teams can actually collaborate, run experiments, and make decisions without getting stuck.

A few concrete moves from the conversation:

• Create space in meetings for others to speak first. Hill gives one example of a CEO who stopped talking for the first 20 minutes to avoid dominating the room.
• Build a feedback loop for leadership behavior. That can mean a coach or a trusted "sparring partner" who will tell you when your intent and your impact do not match.
• Clarify shared purpose. If people do not see meaning in the work, they are less likely to take the risks innovation requires.
• Identify and promote people who can bridge functions, especially between technical teams and business teams.
• Treat scaling as part of innovation from the start. Ask early who else inside or outside the company needs to be involved to make an idea real.

For senior teams, Hill’s advice is to stop assuming collaboration across silos will happen on its own. If horizontal work is required, design for it.

Notable Quotes

"Leadership is not about followership when it's about innovation. It's about co-creation." - Linda Hill

"You cannot plan your way to an innovation. You can only act your way to one." - Linda Hill

"What we need is we need wayfinders, not pathfinders." - Linda Hill

HBR On Leadership • 1m

Overview

This episode is a closing note rather than a standard leadership interview or discussion. The host announces that HBR on Leadership is pausing new episodes and that this is the last one in the feed, while pointing listeners toward HBR IdeaCast and HBR's leadership newsletter for future leadership and management coverage.

The tone is appreciative and forward-looking. The host thanks the production team and the audience, marking the end of a four-year run and more than 150 episodes.

Key Takeaways

The main message is organizational focus. The host explains that HBR is shifting its attention toward new projects and additional episodes of its flagship show, HBR IdeaCast. That suggests a choice many leaders face: ending one initiative can be part of making room for stronger investment elsewhere.

There is also a clear example of audience transition done well. Rather than simply ending the show, the host gives listeners a path to stay connected through two channels: the Tuesday IdeaCast feed and HBR's leadership newsletter. The handoff is direct and practical.

Another takeaway is the way the episode handles closure. The host does not treat the show as disposable. She names team members, marks the scale of the work over four years, and thanks listeners for showing up each week. That kind of ending reflects a leadership habit that matters: when something stops, say what it meant, who made it possible, and where people can go next.

The final line, "lead with care," also sums up the editorial stance the show appears to have carried. Even in a short farewell, the emphasis stays on thoughtful leadership rather than promotion.

Practical Steps

If you are ending, pausing, or consolidating a project, there are a few useful moves in this episode:

• State the change plainly. Say what is ending, whether it is temporary or final, and what the timeline is.
• Explain the reason at a high level. In this case, the host says the team is redirecting energy toward new work and a flagship show.
• Give people a next step right away. Offer a specific place to follow, subscribe, or stay informed.
• Thank the people behind the work by name when possible. It shows respect and gives the ending some weight.
• Acknowledge the audience's role. If customers, listeners, or employees helped make the project matter, say so directly.
• Close with a value or principle people can carry forward. Here, the signoff reinforces the kind of leadership the show stood for.

For communications teams, this is also a good template for shutdown or transition messages: brief context, honest direction, gratitude, and a clear call to action.

Notable Quotes

• "This show, HBR on Leadership, is hitting pause on new episodes. This will be our final one in the feed."
• "We're directing our energy at new projects and more great episodes of our flagship show, the HBR IdeaCast."
• "Remember, lead with care."

Platformer • 1h 2m

Overview

This episode looks at the gap between the AI industry's public optimism about jobs and the cuts happening inside the companies building the technology. Casey Newton talks with AWS CEO Matt Garman, who argues that replacing junior workers with AI is shortsighted even as Amazon has cut tens of thousands of roles and is building tools that automate parts of recruiting and other office work.

The conversation also covers how companies are moving from flashy AI demos to production systems, where they are seeing returns, and why Garman thinks AI will change jobs faster than cloud computing did.

Key Takeaways

Garman's core argument is that AI will change a lot of white-collar work without simply erasing it. He pushes back on forecasts that entry-level jobs will be wiped out, saying the bigger shift is that roles will look different in two years than they do now. In his view, junior employees still matter because they are cheaper to hire, easier to train into company culture, and often quicker to adopt new tools.

At the same time, the interview makes clear why people are skeptical. Garman describes AI systems that automate recruiting tasks and says directly that Amazon has long used automation to remove work and move employees toward "higher-value" tasks. That is a real displacement story, even if he expects new work to appear nearby. The open question is how often that adjacent work exists, and for whom.

On enterprise adoption, Garman says the first wave of AI pilots mostly failed to show returns because companies were experimenting without clear business goals. What is changing now, he says, is that firms are picking narrower use cases, dealing with security and compliance, and pushing the successful ones into production. He told Casey that in a recent room of about 100 CIOs, around 90 percent raised their hands to say they either already had materially positive ROI or expected it within months. That reflects his read of the market, not an independent survey.

Coding remains the clearest win, but Garman says the bigger shift is what coding gains make possible: agents that can carry out broader business processes. He points to telecom and financial services as areas where companies are starting to use AI for operational work, not just assistance.

The opening segment with Ella Marciano adds a useful wrinkle. Colleges are rushing to create AI majors, but she says many are basically modified computer science degrees with more math and less emphasis on hand-coding. She also notes that weak hiring for young CS workers may not be pure AI displacement; remote work and pandemic overhiring may explain part of it.

Practical Steps

If you're deciding how to train for this market:

• Favor programs that keep core CS fundamentals and add statistics, linear algebra, and optimization.
• Do not assume "AI degree" means a brand-new field. Check the course list.
• Build skill in using AI tools while keeping enough technical depth to judge their output.

If you're leading AI adoption at work:

• Start with a business problem, not a demo.
• Pick use cases where you can measure output: faster bug fixes, more shipped features, shorter response times, lower support costs.
• Move pilots into production only after sorting out data access, security, and compliance.
• Match the model to the task. Do not pay for the most expensive model when a smaller one will do the job.

If you're early in your career:

• Learn to work with AI tools instead of competing with them head-on.
• Get good at problem framing, judgment, and learning new systems quickly.
• Treat adaptability as a job skill, because employers increasingly seem to.

Notable Quotes

"Replacing junior employees with AI" is "one of the dumbest things I've ever heard." - Matt Garman

"Half of white-collar jobs may change, but it doesn't mean wipe out and change are different." - Matt Garman

"If you look at what your job was two years ago and you look at what your job is going to be in two years, it's going to be vastly different." - Matt Garman

Worklife with Molly Graham • 38m

Overview

This episode is about how product culture gets built, tested, and scaled, with Facebook as the main case study. The guest argues that "move fast and break things" was never about recklessness. It was about learning faster than competitors, then building enough guardrails that mistakes teach you something without taking the whole company down.

Key Takeaways

The clearest point is that speed only matters if it improves learning. The guest explains that Facebook's real advantage was not raw shipping velocity for its own sake, but the ability to get feedback from users, react quickly, and keep doing that at huge scale. In a consumer product where tastes shift fast, waiting months to decide what users want is a losing move.

He also makes a useful correction to one of tech's most repeated slogans. The original idea, he says, was "move fast and don't be afraid to break things." That missing clause changes the meaning. The aim was never damage. The aim was to remove fear so teams would test ideas, learn, and improve.

Another strong theme is that culture cannot be copied blindly. What worked at Facebook would be a bad fit in places like aerospace, energy, or other high-risk fields where failure has very different costs. Culture has to match the product, the market, and the founder's own instincts. Otherwise people hear one set of values and get rewarded for another.

The conversation also gets specific about psychological safety. The guest describes incident review meetings where leaders stopped people from blaming the engineer who caused an outage and pushed the room toward a harder question: why was the system fragile enough that one change could cause that much damage? That shift matters. It turns mistakes into design problems instead of character judgments.

One story shows why this matters in practice. During a major outage, an engineer volunteered that their code change might be the cause. That honesty, the guest says, helped restore service much faster and likely saved the business hours of downtime. People only speak that plainly when they know the response will be investigation, not humiliation.

Practical Steps

If you are leading a team, a few moves stand out:

• Define what your culture is for. Ask what kind of business you run and what kind of failure is acceptable. A consumer app, a bank, and a rocket company should not run the same playbook.
• Rewrite slogans into behavior. If you say speed matters, explain what that means operationally: faster experiments, shorter feedback loops, and clear rollback paths.
• Run blameless postmortems. When something fails, ask "how did our system allow this?" before asking who touched it.
• Build guardrails before pushing for speed. Automated tests, staged rollouts, failover systems, and recovery plans are what make fast iteration safe enough to sustain.
• Stress-test your own infrastructure. The guest describes deliberately taking systems offline to expose hidden dependencies before real failures do it for you.
• Check whether rewards match stated values. If you say teamwork matters but only reward individual heroics, people will follow the incentives, not the poster on the wall.

Notable Quotes

• "The speed at which you could learn was the determinant of success."
• "Why in the world do we not have systems that would have prevented this?"
• "When you can build a culture that has intellectual honesty and psychological safety, you're going to win."

Decoder with Nilay Patel • 1h 13m

Overview

This episode is about how Patreon has changed from a payments layer for creators into something much closer to a full creator platform. Jack Conte says the shift was forced by the big platforms: once Facebook, YouTube, Instagram, and TikTok stopped giving creators reliable access to their own audiences, Patreon had to build discovery, media hosting, chat, and free follow tools itself.

The broader argument is bigger than Patreon. Conte sees the current social platform model as bad for creators and bad for people in general, and he thinks AI is making the problem worse by flooding platforms with cheap content while also pulling from creators' work without fair consent or payment.

Key Takeaways

Conte’s clearest point is that the internet moved from follower-based distribution to interest-based distribution, and that broke the direct line between creators and fans. If a creator cannot reliably reach the people who chose to follow them, they do not really own an audience and they cannot build a stable business around that audience.

That explains Patreon's biggest reversal. Conte used to resist discovery features because Patreon was meant to sit at the bottom of the funnel, handling memberships and payments after fans were already won elsewhere. He now says that model no longer works. If Patreon does not help creators grow their audience itself, then creators are stuck depending on companies that can change the rules at any time.

He described Patreon today as an "index of small business media companies." That framing matters because it shifts the company away from being a utility and toward being an operating platform for creators. The additions he pointed to, including native video, chats, feeds, short posts, and free memberships, are all meant to restore direct reach. He says free memberships alone have grown to 185 million, and that Patreon is now sending 1.5 million new followers to creators each month.

On AI, Conte held two positions at once. He called the current treatment of creators "disgusting" because models have been trained on creative work without real permission, compensation, or credit. At the same time, he says Patreon has no choice but to use AI heavily inside the company for coding, internal search, summaries, and operations, because a software company that ignores these tools will fall behind fast.

His product line on AI is sharper than the usual "AI everywhere" pitch. Creators, he says, do not want help making the work itself. They are more open to AI for packaging, marketing, and business admin. That leads to a simple internal rule: use AI to handle the chores around the work, not to replace the act of making it.

Practical Steps

For creators and media businesses, the practical lesson is to rebuild direct audience connections wherever possible.

• Collect direct fan relationships, especially email and free memberships, instead of relying only on platform followers.
• Put free, accessible samples of your work where new people can find them. Conte says discovery without free media did not convert.
• Build community in places where you can reliably reach people, such as owned chats, newsletters, or member spaces.
• Treat platform growth as rented attention. Use it, but do not confuse it with customer ownership.
• If you are testing AI, start with admin and packaging tasks: transcripts, chapter markers, clipping, support flows, scheduling, and finance work.

Conte also gave a solid decision-making playbook for operators:

• Start meetings by asking who strongly disagrees.
• Do not trust the initial framing of A versus B.
• Use pre-reads so meetings are for debate, not background download.
• Name a clear decision maker.
• Say out loud where you are leaning before the meeting ends so the real objections surface.

Notable Quotes

"Patreon is essentially like an index of small business media companies." - Jack Conte

"What ultimately is happening to creative people right now is disgusting." - Jack Conte

"I need AI to help me do my taxes and clean my toilet." - creator feedback quoted by Jack Conte

HBR On Leadership • 28m

Overview

Anne Morris argues that hard problems usually last longer than they should because leaders either avoid them or rush to shallow answers. Her case is that effective change depends on two things working together: trust first, then speed. The episode centers on a five-step approach from her book, "Move Fast and Fix Things," meant to help leaders solve problems faster without creating new damage.

Key Takeaways

Morris pushes back on the idea that speed is reckless by default. She says speed gets blamed for failures that usually come from weak diagnosis, low trust, poor alignment, or unresolved conflict. If those pieces are handled well, moving quickly becomes an advantage rather than a risk.

A strong point in the conversation is that leaders often move too fast at the wrong moment. The biggest mistake is usually in diagnosis. Leaders get rewarded for sounding certain, so they jump from "I've seen this before" to a plan before they have really understood the root causes. Morris argues for more humility at the start: test alternative explanations, talk to people affected by the problem, and make room for hard truths that people usually avoid saying out loud.

Trust, in her view, is not some fragile asset that takes years to build. She says it is being built, rebuilt, and broken all the time, which makes it more workable than many leaders assume. That matters because trust is what gives leaders permission to move faster later.

Another useful idea is her structure for change communication. Leaders often underinvest in the story. Morris says people need a clear "why," but they also need their history acknowledged. Her suggested arc is simple: honor the past, explain the case for change in the present, then lay out an optimistic but disciplined path forward. The Uber example under Dara Khosrowshahi shows how recognizing what came before can help people accept what comes next.

She also makes a practical point about speed inside large organizations. It does not require changing the whole company at once. Teams can create faster ways of working within their own span of control, and that can help keep strong people who want to see progress rather than wait years for decisions.

Practical Steps

• Start with diagnosis, not declarations. Pull together a temporary problem-solving group with people who see the issue from different angles. Ask:

  • What is the actual problem?
  • What are the root causes?
  • What else might explain what we're seeing?
  • Who is affected and what are they seeing that we are missing?

• Create a setting where people can discuss what is usually left unsaid. Morris leans on the idea of making the "undiscussable" discussable. That means leaders need to lower the risk of speaking plainly.

• Before pushing for action, check trust. Where is it weak? With whom? What behavior from leadership has helped or hurt it? Use that to shape the plan.

• Build buy-in with a better change story:

  • Name what the organization did well in the past
  • Acknowledge what is not working
  • Explain why change is needed now
  • Describe the way forward in plain language

• Once the groundwork is in place, move with urgency. Set clear priorities, remove obstacles, and create a way to fast-track the work that matters most. Morris points to examples like labeling certain efforts as the ones that get immediate passage.

• Deal with "conflict debt." If disagreements keep getting postponed, they slow everything down later. Put a process in place to surface and resolve them early.

Notable Quotes

• Anne Morris: "The people who were really getting it right were moving fast and fixing things."
• Anne Morris: "No one has ever said to us, I wish I had taken longer and done less."
• Anne Morris: "Human behavior and the change in human behavior really depends on a strong why."

Platformer • 1h 24m

Overview

This live Platformer event focused on a simple question with a messy answer: as AI gets better at automating tasks, what happens to jobs, software, and the way people work. Casey Newton spoke with Ella Marcianos, Atlassian executive Tamar Yehoshua, and Replica and Wabi founder Eugenia Kuyda about new AI job categories, workplace tools built on company context, and a future where people may make more of their own software.

What came through most clearly is that AI is not just replacing work in a clean, one-to-one way. It is also creating new roles, shifting what valuable work looks like, and lowering the cost of building tools, while raising the bar for judgment, speed, and taste.

Key Takeaways

Ella Marcianos opened with a grounded point: AI is already producing a wave of new job titles, but it is still unclear how many are actually new jobs versus old jobs with AI branding. She cited roles companies are adding, from "AI forward-deployed engineer" to "AI business automation engineer," and suggested the real test will be outcomes. If these hires help customers do things faster or differently in a lasting way, then the category is real. If not, some of this may be rebranding.

Tamar Yehoshua argued that AI at work gets much better when it has company-specific context. Her example was Atlassian's "teamwork graph," which connects data from Jira, Confluence, Slack, and other tools so an AI system can reason over what has happened inside an organization, not just what exists on the public internet. She said that makes it easier to solve recurring incidents, coordinate projects, and reduce repetitive work. Her broader point was that productivity gains matter less on their own than what they free people up to do: better planning, better prioritization, and better product decisions.

She also made a practical distinction that ran through the conversation: people tend to react to AI at work with either curiosity or fear, and adoption often depends on visible internal champions who can show useful results.

Eugenia Kuyda took the discussion in two directions. First, on Replica, she said the early bet was that people wanted connection badly enough that even weak systems could matter if they made users feel heard. That demand, more than early technical quality, helped explain why AI companionship took hold. Second, on Wabi, she made the case that software creation is getting cheap enough that many subscription app categories may be in trouble, especially ones with weak retention and little differentiation. She pointed to fitness, meditation, and lifestyle apps as vulnerable if users can generate tools that fit their own lives better.

Her hiring view was also sharp: if AI makes average execution cheaper, small startups will want fewer people, and those people will need strong product sense, initiative, and the ability to ship without heavy management.

Practical Steps

• Audit your work for coordination drag. Look for tasks that involve chasing updates across docs, tickets, messages, and spreadsheets. Those are strong candidates for AI assistance.
• Start with drafting, summarizing, and project tracking before giving an agent permission to act on its own. Yehoshua was clear that "human in the loop" still matters.
• If you lead a team, create a small group of internal AI champions. Have them test tools, show examples, and share what actually saved time.
• Treat "AI job" claims skeptically. Ask what outcome changed, not whether the title sounds new.
• If you build products, focus less on whether AI can help your team ship faster and more on whether it helps you choose the right thing to build.
• If you're hiring for an AI-heavy startup, screen for agency. Look for people who can spot a problem, decide what to do, and ship without waiting for a lot of process.

Notable Quotes

• "It seems like it's getting really easy to automate a task. At what point does that mean we can automate a job?" - Casey Newton
• "The teamwork graph gives you context, which actually makes the results better." - Tamar Yehoshua
• "If this is the level of understanding that's required for the most amazing conversation, we can probably build that." - Eugenia Kuyda

Worklife with Molly Graham • 33m

Overview

This episode of WorkLife is about what success feels like from the inside, and the answer is usually: messy, stressful, and far less certain than it looks later. Molly Graham talks with former Stripe COO Claire Hughes Johnson about how leaders decide whether to keep going through hard periods or walk away, and how to tell the difference between ordinary pain and a real sign that something is broken.

Their conversation keeps returning to one idea: struggle by itself does not mean you are on the wrong path. The harder part is judging whether the underlying business, role, or team still gives you enough reason to stay in the fight.

Key Takeaways

Claire pushes back on the clean, inevitable version of company-building. She says Stripe's rise did not feel preordained while she was living it. It felt like repeated hits: outages, partner problems, customer churn, regulatory scares, and days destroyed by crisis. What surprised her most was "that we just kept going."

One useful distinction in the episode is between a bad moment and an existential one. Teams often label a painful event as existential when it is really just severe and draining. Claire's point is that leaders need to step back, look at the whole board, and ask whether the fundamentals still hold. If the product is strong, customers are growing, and the company still has real traction, a painful event may be survivable even when it feels awful in the moment.

She also makes a practical case for treating career decisions like investments. Time matters more than money here. If you are choosing whether to join or stay at a company, sentiment and loyalty are not enough. Claire says you should look at the numbers, meet the founder, understand the investors, use the product, and talk to customers. Her view is blunt: people get hurt when they stay because of friendship, reputation, or vague belief instead of facts.

Another strong thread is that people rarely unstick themselves alone. When you are in the middle of a hard situation, your judgment narrows. Claire says asking outsiders for help is often the fastest way to regain perspective. Molly ties this back to the emotional trap of work: when things feel bad, we start telling ourselves a story that everything we have done has been a failure.

Claire's own filter for whether to stay is simple: am I still learning, and am I still having impact? If both answers are yes, that is usually a reason to continue, even through a rough stretch. If one or both turn into no, that is when the real gut check starts.

Practical Steps

• When a crisis hits, write down the facts before naming it. Ask:

  • What actually happened?
  • Is this painful, or is it existential?
  • What evidence says the business or team can recover?

• Do a "whole board" review once a quarter:

  • product strength
  • customer demand
  • revenue direction
  • leadership quality
  • your own role and influence

• If you are considering a new role or debating whether to stay, do due diligence:

  • review basic company numbers if available
  • talk to the founder or senior leaders
  • use the product yourself
  • speak with customers, employees, or former employees

• Build a short list of people you can call when judgment gets cloudy. Ask them to play back what they hear, not just cheer you on.

• Use Claire's two-part test on your current job:

  • Am I learning?
  • Am I having impact? If the answer is no for too long, treat that as a real signal.

• When you feel frozen, make one concrete move. Ask for advice, schedule a hard conversation, or gather missing data. Motion can restore judgment.

Notable Quotes

• Claire Hughes Johnson: "I guess that we just kept going."
• Claire Hughes Johnson: "This is like making an investment, but it's an even bigger investment than your money. It's your time."
• Claire Hughes Johnson: "Am I learning? And am I having an impact?"

Decoder with Nilay Patel • 1h 13m

Overview

This episode is mostly about what Skydio thinks the drone business is becoming: less a camera you fly by hand, more a connected piece of infrastructure that can launch itself, gather information, and plug into bigger systems used by utilities, police, and the military. Adam Bry says that shift toward autonomy is why Skydio left the consumer market and built around enterprise and government buyers.

A second thread runs through the whole conversation: whether the U.S. can actually build advanced drones at scale without leaning on China. Bry argues that manufacturing in the U.S. started as a product decision for Skydio, then turned into a strategic one as policy and geopolitics changed.

Key Takeaways

Bry frames the drone industry in three stages: hobby aircraft, then flying cameras, then autonomous machines that live in docks, connect to the internet, and can be dispatched remotely. His bet is that the third stage will be much bigger than the first two because the value shifts from piloting to repeatable workflows. For a utility, that means inspecting infrastructure. For public safety, it means getting eyes on a scene before people arrive.

He pushes back on the idea that “the data matters, not the drone.” His point is that software only matters if the aircraft is reliable enough to earn trust. He describes drones as closer to self-driving cars that fly than simple gadgets, with problems in aerodynamics, heat, vibration, sensors, compute, and manufacturing all stacked together.

On company building, Bry’s view is blunt: talent matters more than org charts. He compares business to baseball and argues that one standout person can change the trajectory of a product more than structural optimization can. That same lens shapes how he thinks about AI hiring. Skydio is not chasing giant foundation models, but it does need people who can ship AI inside working products.

The manufacturing discussion is one of the strongest parts of the episode. Bry says Skydio has built in the U.S. since the beginning, partly because engineering and manufacturing need to sit close together. He also admits the limits of that claim. China, in his view, is still better at drone manufacturing overall because it has the surrounding supplier base. Skydio’s answer is to keep assembling in the U.S. while pulling major direct suppliers away from China.

On military use, Bry takes a permissive stance. He says Skydio should not be the party setting hard rules on how the military may use its products, including weaponization experiments, because elected governments and military institutions are the ones accountable for those decisions. His argument is that strict company-side limits often bind the “good guys” while bad actors ignore them.

Practical Steps

• If you run an operations-heavy business, look at drones as part of a workflow, not as a flying camera. Start with one repeatable job such as roof inspection, power-line review, site mapping, or emergency response.
• When evaluating drone vendors, ask about autonomy, dock-based deployment, remote operation, software integrations, and reliability, not just camera specs and flight time.
• If you build hardware, keep engineering and manufacturing feedback loops tight. Bry’s point is simple: products improve faster when design and production teams can solve problems side by side.
• Audit supply-chain exposure by layers. Skydio tracks “first-level dependencies,” meaning the suppliers it works with directly, then pushes further back where possible. That is a useful model for any hardware company facing geopolitical risk.
• For leaders making hard decisions, write things down. Bry says writing helps him sort through uncertainty and gives the team a concrete plan to debate.

Notable Quotes

• Adam Bry: “The next chapter is really about autonomy, where the drone lives in a docking station. It’s connected to the internet. It can be flown remotely and autonomously and becomes a piece of infrastructure itself.”
• Adam Bry: “One exceptional person anywhere in the organization can just completely change the trajectory of a product or a business.”
• Adam Bry: “I think it’s just not our place to tell them what they can and can’t do,” speaking about how the military uses Skydio’s technology.

HBR On Leadership • 25m

Overview

This episode is about timeboxing: putting your to-do list into your calendar so each task has a specific slot and a clear limit. Mark Zalsander argues that this is more than a planning trick. For him, it is a way to reduce stress, make better decisions about what deserves attention, and stop drifting through the day reacting to whatever shows up.

Key Takeaways

Zalsander says his early career problems were not about effort. He was working long hours, but without a system for deciding what mattered most. Timeboxing changed that by forcing a simple question: what should I be doing right now, and for how long?

His basic point is that to-do lists fail because they treat every task as floating and interchangeable. A calendar, on its own, can be too focused on meetings. Timeboxing combines the two. You take the finite hours in a day the way you would treat money in a budget and assign them deliberately.

A useful detail from the conversation is that he timeboxes for only 15 minutes each morning. That short planning session covers work, exercise, family time, reading, and anything else that should happen that day. The benefit is not only output. He says the bigger gain is confidence: once the day is mapped, he has a reference point to return to when distractions pile up.

He is realistic about the weak spot in any planning system: estimates are often wrong. His answer is to base time estimates on past experience, then adjust inside the block as the work unfolds. He calls this "pacing and racing" - noticing early whether you are ahead or behind and changing speed or scope before the time runs out.

Another strong point is that timeboxing creates a record. Most people cannot say what they did last Tuesday afternoon. If the calendar reflects real work, it becomes a log for review, reflection, and better estimates later.

On teams, he frames timeboxing as a communication tool. "Will do" leaves everyone guessing. A response like "I've blocked time for 3 p.m. Thursday" gives the other person something they can plan around, and it surfaces deadline problems sooner.

Practical Steps

• Block 15 minutes at the start of each day for planning. Use it to assign time to the work that matters most, not just meetings already on the calendar.
• Put tasks in the calendar, not on a separate list you hope to get to. Give each one a start time and an end time.
• Estimate based on memory, not optimism. Ask: how long did something like this take last time?
• Check progress halfway through a block. If you are behind, cut scope or speed up. If you are ahead, use the extra time to improve quality.
• Build in personal priorities too: exercise, reading, family time, breaks. Zalsander treats those as real commitments, not leftovers.
• When distracted, return to the calendar and pick up the planned task instead of deciding from scratch.
• In team settings, reply with a scheduled delivery point, not a vague promise. That gives colleagues a clearer picture of timing and tradeoffs.
• If visibility is a concern, block time privately at first. As trust builds, share more about what those blocks are for.

Notable Quotes

• "You put your to-do list in your calendar. You set appointments for when you're going to get things done." - Mark Zalsander
• "One thing at a time." - Mark Zalsander
• "I know then that it will be a good day if I stick to that plan." - Mark Zalsander

Decoder with Nilay Patel • 54m

Overview

This episode is mostly about what it takes to run Condé Nast when search traffic is drying up, platform deals are unstable, and the old magazine model no longer carries the business. Roger Lynch argues that the company has had to stop thinking like a print publisher and start thinking like a group of brands that can make money across subscriptions, events, commerce, video, and licensing.

The sharpest part of the conversation is Lynch's view on "Google zero." He says publishers should not expect search traffic to keep supporting their business, and they should plan around direct audience relationships and brand authority instead.

Key Takeaways

Lynch says Condé Nast's turnaround started with structure, not editorial. When he arrived, the company was split by country and by internal power centers, with teams competing against each other instead of the market. His first move was to combine those pieces into one company and push people to operate with shared goals.

He frames Condé Nast's problem in 2019 as a business model issue, not an audience issue. His read was that brands like Vogue and The New Yorker were still gaining digital attention, which meant demand was there even if the old print economics were failing. He says the company has since moved from majority print revenue to majority digital revenue and from losses to profitability.

On platforms, Lynch's position is pretty plain: publishers have to be where audiences are, but they should not assume platforms owe them traffic. He treats TikTok as an example of going where users already expect the brand to be, even before a revenue model is obvious. At the same time, he draws a line at platforms using publisher content to compete directly with publishers.

That is where his argument against Google and some AI companies lands. Lynch says declining search referrals are one thing; scraping journalism to power AI products without a license is another. He says Condé Nast is willing to make deals, as it has with companies including OpenAI, Amazon, Microsoft, and Perplexity, but he views Google's tie between search indexing and AI scraping as anti-competitive.

A second big idea is that authority matters more than scale alone. Lynch does not claim only giant brands survive. He points to niche titles with loyal audiences and a clear point of view as viable, while businesses built mostly on search or social arbitrage are far more exposed when platform traffic drops.

He also makes the case that events such as the Met Gala are more than sponsorship plays. They are brand expressions that create attention far beyond a single night. Lynch says Condé Nast's video around this year's Met Gala reached 3.1 billion views, up from a little over 2 billion last year.

Practical Steps

For media operators, marketers, or anyone running a content business, the episode suggests a few clear moves:

• Stop building plans that depend on search growth. Assume referral traffic can shrink fast and model your business accordingly.
• Put more effort into direct audience channels: subscriptions, newsletters, memberships, repeat video viewers, and commerce tied to clear intent.
• Go to platforms because your audience is there, not because you expect platform loyalty.
• Separate distribution from dependency. Use TikTok, YouTube, and similar channels, but do not let them become your whole business.
• Treat brand authority as an operating asset. Build a point of view people will seek out directly.
• If you own valuable content, push for licensing terms with AI companies instead of giving away use by default.
• Run formal succession planning, especially if a big part of your company's value sits with a few star leaders.

Notable Quotes

• "I don't believe that any of these platforms owe us an obligation to send us traffic or customers or audience."
• "I also don't believe that they have the right to use our content to come and compete directly with us." - Roger Lynch
• "It really is, does your brand have authority? Does it have connection with audience that is really deeper than search or discover traffic?" - Roger Lynch

Eat Sleep Work Repeat - better workplace culture • 43m

Overview

This episode looks past the loud claims about AI taking half of all jobs and gets into what actually happens when new technology hits real workplaces. Bruce Aisley talks with Financial Times writer Sarah O'Connor about her book We Are Not Machines, and the core argument is plain: the future of work is not just about what AI can do, but about who gets to decide how it is used.

O'Connor argues that too much of the public debate treats technological change like weather or a tidal wave - something inevitable that people can only brace for. Her reporting suggests something else. Outcomes depend on power, regulation, consumer standards, workplace culture, and whether workers have any say.

Key Takeaways

One of the strongest points in the conversation is that distance distorts how "automatable" a job looks. From far away, many jobs seem easy to hand over to software. Up close, they involve judgment, timing, relationships, dexterity, and adaptation that are hard to reduce to a workflow chart.

Her example of translators makes that concrete. Machine translation can be useful, and O'Connor is careful not to dismiss it outright. But for high-quality translation, the job is not swapping words one by one. It involves tone, cultural context, social relationships, humor, and taste. What is happening in many cases is not replacement but degradation: skilled people are turned into editors of machine output, with less autonomy and less satisfaction.

She pushes back hard on the language of inevitability. When politicians or tech leaders say AI is "coming" and we must accept it, that framing strips out human choice. O'Connor's point is that technology is shaped by institutions and incentives. Employers make choices. Governments make choices. Consumers make choices. Workers, where they have enough power, make choices too.

Another thread is the danger of losing faith in human abilities. O'Connor says we are being told machines will outperform people at cognitive work, creative work, even empathy. She rejects that framing. A machine can imitate empathic language, but that is not the same as feeling or moral presence. She points to work like grave tending and palliative care to show kinds of intelligence that remain distinctly human.

The gap between workers matters. Senior software developers may find AI makes them more effective because they stay in control of the process. Other workers get boxed into low-discretion roles where they merely clean up machine output. The difference is often bargaining power, not the technology itself.

Practical Steps

For individuals, O'Connor's advice is to pay close attention to what AI actually does in your own job rather than absorbing every sweeping headline. Look for the parts of your work that depend on judgment, taste, trust, physical skill, or emotional presence. Those are the parts worth protecting and building on.

If you have any room to influence how tools are introduced at work, push for choice over compulsion. A useful standard from the Hollywood writers' fight was this: workers should be able to use AI when it improves the work, but not be forced to use it just to cut costs.

For managers and policymakers, the practical agenda is about worker power:

• strengthen workers' voice in decisions about new tech
• make it easier to leave bad jobs through better income support
• expand access to retraining and paid learning time
• set standards for quality so companies cannot quietly lower it and call it progress

The broad test is simple: ask "What problem is this solving?" and then ask who benefits, who loses control, and who absorbs the downside.

Notable Quotes

• "This is not a story of just sitting here in front of a big tsunami and waiting to find out if we sink or swim." - Sarah O'Connor

• "It's a lot less about the technology than it was about all of the other choices and institutions and balances of power." - Sarah O'Connor

• "Pay attention to what's happening in your own world rather than the kind of big headlines that keep coming at you." - Sarah O'Connor

Platformer • 1h 8m

Overview

This episode pushes back on the soothing line that AI will mostly "change jobs, not remove them." Casey Newton talks with Brookings senior fellow Molly Kinder, who argues that the bigger risk is a long, uneven stretch of disruption she calls the "messy middle": not total job collapse, but enough concentrated damage to upend careers, politics, and public trust.

The conversation stays grounded in one question: if AI starts cutting into white-collar work first, what is the plan for the people who lose status, income, and a path forward? Kinder’s answer is blunt: right now, there really isn’t one.

Key Takeaways

Kinder’s main point is that the debate is stuck between two bad extremes. One side predicts an imminent jobs apocalypse. The other says there is little to worry about because the data does not yet show broad labor-market damage. She thinks both miss what comes next: a drawn-out period where AI takes over enough high-value tasks to hurt specific groups badly, even if most jobs still exist.

Her case for white-collar exposure is straightforward. Large language models are strongest at computer-based work: law, finance, consulting, sales, software, and clerical office roles. Jobs that require physical presence - food service, repair, care work, construction - are less exposed for now because chatbots do not mop floors, cut hair, or fix pipes. That means the first shock may land on the "laptop class," not the workers people usually assume are most vulnerable to automation.

She also points to de-skilling as a separate threat from outright job loss. Even when AI does not remove a role, it can lower the expertise needed to do it, which can push down wages and reduce career ladders. In healthcare, for example, she says workers are already imagining cases where AI guidance lets less-trained people do tasks that used to require more education.

The episode also casts doubt on easy policy answers. Retraining helps in some cases, but the evidence is mixed over the long run. Ella Marcianos cites research on trade-adjustment programs suggesting workers can see income gains years later, but those gains may fade as the market changes again. If AI keeps moving fast, people may be retrained into jobs that are later automated too.

Kinder is especially skeptical of treating universal basic income as the obvious answer. In a world where some people still need to show up and do lower-paid essential work, sending everyone checks large enough to replace lost six-figure salaries could be politically unstable and hard to sustain. She separates two issues that often get mashed together: sharing AI wealth broadly, and helping the people who get hit hardest by job disruption.

Practical Steps

• Watch the early-warning sectors. If you work in software, customer service, marketing, finance, market research, or clerical back-office roles, pay close attention to how your employer is using AI now, not just what executives say in public.
• Audit your job by task. List the parts you do at a computer, especially repeatable writing, analysis, scheduling, coding, or document work. Those are the places AI is most likely to eat away first.
• Build skills outside pure screen work. Relationship management, judgment, coordination, trust-building, and domain expertise tied to real-world settings may hold up better than work that can be done alone at a laptop.
• Push for policy before layoffs arrive. Kinder’s view is that waiting until displacement is obvious will be too late. That means pressing employers and policymakers for retention plans, transition support, and protections for early-career workers now.
• Don’t assume retraining alone will save you. Treat it as one tool, not a guarantee.

Notable Quotes

• Molly Kinder: "What we're really entering is this messy middle period."
• Molly Kinder: "A world where most jobs are intact, but there's a concentrated loss is still a world that is politically, societally, and economically explosive."
• Molly Kinder: "People are not asking for a check and they're not asking for retraining. They're asking to have some security."

Supra Insider • 1h 22m

Overview

This episode is a conversation with Noah, a former product leader who now works as what he calls a "free-range AI consultant." He helps mostly small and mid-sized companies sort through their AI anxiety, figure out what problem actually matters, and then decide where AI fits, if it fits at all.

The discussion is less about flashy demos and more about how AI changes consulting, product work, discovery, and the way small teams operate. A recurring point is that the biggest value often comes from judgment, not raw model output.

Key Takeaways

Noah’s main point is that many companies asking for "AI help" do not actually need an AI strategy first. They need business clarity first. He says the work usually starts with first principles: what the company is trying to achieve, where the bottlenecks are, and whether AI is a real answer or just a reaction to hype.

He breaks AI use cases into three buckets. First is "AI as a coworker," meaning tools that help individuals with everyday work. Second is "AI as operator," where AI handles recurring business tasks inside workflows. Third is "AI in product and engineering," where it either speeds up the team or becomes part of the product itself. That framing helps companies avoid treating every AI problem as the same kind of project.

A strong thread through the episode is that discovery has changed dramatically. Noah describes taking a messy real-world conversation, dropping the transcript into an AI workflow, and quickly turning it into a rough research report and prototype. His point is not that AI output is ready to ship. It is that the speed of getting to a useful artifact has gone way up, which makes conversations sharper and decisions faster.

He also pushes back on the idea that this is all "AI slop." The raw output is not the product. The real value is in the human back-and-forth: deciding what matters, refining the methodology, arguing with the model, and turning repeated insight into reusable systems. He and the hosts treat this codified judgment as a new kind of IP.

Another useful point: product managers may be especially well positioned in this shift. Noah describes PMs as "a high judgment brain with no arms," and argues AI now gives them more ability to act directly. That reduces coordination overhead and lets small teams test more ideas before needing broader buy-in.

He is also clear that context matters. A company like McDonald’s or a regulated business may have good reasons for moving slowly or keeping heavy process. Walking in with Silicon Valley assumptions can break things that are already working.

Practical Steps

• Start with the business problem, not the AI tool. Ask:

  • What goal are we trying to hit?
  • What is slowing us down now?
  • Is this a judgment problem, a workflow problem, or a product problem?

• Sort possible projects into one of Noah’s three buckets:

  • coworker
  • operator
  • product/engineering
    This makes scope, architecture, and ROI easier to reason about.

• Record discovery conversations and reuse them immediately. Turn transcripts into:

  • rough research summaries
  • early prototypes
  • draft proposals
  • lists of next questions
    The point is to create something concrete while the conversation is still fresh.

• Do not automate a process just because it exists. First:

  • write down the process
  • compare that document with what people actually do
  • look for which version gets the best results
  • only then automate

• Build reusable instructions and workflows from repeated work. If you refine the same prompt or method several times, save it as a repeatable skill. That is where compounding starts.

• If you want to reach non-technical customers, create content around their actual business pain, not around AI itself.

Notable Quotes

• "Mostly what I’m spending my time doing is not AI consulting, but actually business consulting." - Noah

• "Every agent needs a human to love them." - Noah, quoting Dan Shipper

• "At its purest, product management is just like a high judgment brain with no arms." - Noah

Worklife with Molly Graham • 41m

Overview

This episode opens a new WorkLife FAQ series, with Molly Graham answering listener questions alongside Ashley Murphy. The conversation stays close to the day-to-day mess of leadership: what to do when you disagree with a CEO, how to know whether you need a coach, and how to explain your value when your background does not fit a clean job title.

What ties the episode together is Molly's view that work gets easier when you stop pretending certainty exists. Instead of chasing perfect answers, she argues for clearer self-knowledge, sharper judgment about where you fit, and more honesty about what a company or leader is actually like.

Key Takeaways

Molly pushes back on the usual "disagree and commit" idea and offers a version she finds more realistic: "disagree and let's see." Her point is that many company decisions, especially in startups, are experiments. After you've made your case, the useful next move is to agree on what success looks like, what metrics matter, and when you'll review the result. That keeps disagreement from turning into quiet resentment or sabotage.

She also makes a sharp distinction between a bad decision you can live with and a fight that is really about culture or values. In founder-led companies, she says culture largely reflects the founder's personality. If a leader is competitive, aggressive, conflict-avoidant, or highly controlling, that tends to show up in the company too. Some of that can shift, but a lot of it will not. Her advice is to stop assuming every problem can be fixed from inside. Sometimes the real question is whether the company is a fit for you at all.

On coaching, Molly breaks support into three buckets: therapist, coach, and advisor. A therapist helps you understand your own wiring and past. A coach helps you get to your own answers through questions and reflection. An advisor gives direct opinions based on experience. She argues that leaders often need all three at different times, and that many people ask for a coach when what they really need is one of the other two.

Her point on generalists is probably the most counterintuitive part of the episode: she says there is no such thing as a generalist. People may have broad titles, but they still have a specialty. The work is figuring out the pattern in the problems you solve best, then describing that clearly enough that the right roles find you and the wrong ones filter out.

Practical Steps

If you disagree with a leader's decision:

• Make your case directly and early.
• Once a decision is made, treat it like a test.
• Define the time horizon, the metrics, and what would count as failure or success.
• Ask yourself whether your resistance is about this decision, or about a deeper values mismatch.

If you're trying to decide what kind of support you need:

• Choose a therapist if you're stuck in recurring emotional patterns or getting triggered in ways you don't understand.
• Choose a coach if you need help thinking better, leading better, or seeing your own blind spots.
• Choose an advisor if you want direct guidance from someone who's handled the same kind of problem before.
• Build your own small group of trusted people instead of expecting one person to cover everything.

If you're struggling to tell your story in a job search:

• Write down two or three times when you felt you were doing your best work.
• Look for repeated patterns in the kind of problems, environments, and responsibilities involved.
• Describe your value in terms of problems solved and tools used, not titles.
• Get specific about roles you should never be hired for as well as the ones where you'd be excellent.

Notable Quotes

"Most of the time no one knows the right answer and you're just picking a path forward." - Molly Graham

"Trying to change culture in a founder-led company is like you're married to someone. How much do you believe they're going to change?" - Molly Graham

"I actually believe every single person in the world has a specialty." - Molly Graham

Decoder with Nilay Patel • 1h 16m

Overview

Nilay Patel talks with Mustafa Suleiman about Microsoft AI's shift from relying mainly on OpenAI to building its own frontier models, the company's Build announcements, and Mustafa's view that "superintelligence" is coming sooner than many people think. The conversation also pushes on the weak spots in that story: public backlash, shaky consumer value, job fears, and the habit in AI of talking as if the future is already settled.

The episode works because Nilay keeps pressing when Mustafa makes broad claims. That leads to a clearer picture of where Microsoft is confident, where Mustafa is extrapolating, and where the industry is still making bets.

Key Takeaways

Microsoft's relationship with OpenAI has changed from simple division of labor to overlap across the whole stack. Mustafa says OpenAI expanded from research into products, enterprise, chips, hardware, and infrastructure. Microsoft responded by trying to become "self-sufficient" on models, chips, and training, while still staying in partnership with OpenAI for years.

Mustafa's case for superintelligence is basically an argument from scaling laws. He says model progress still tracks increased compute, data, and real-world interaction, and that this trend should continue for the next few years. He draws a distinction between AGI, superintelligence, and the singularity: AGI is human-level on most tasks; superintelligence exceeds humans broadly and can produce new knowledge; the singularity is a much more speculative point where systems improve themselves recursively.

One striking point is what Microsoft says it did not do. Mustafa says the new MAI Thinking One model was not built by distilling stronger outside models, even though that would have been faster. His reason is strategic: distillation may copy capability, but it does not build a lab that can pass the teacher.

Nilay pushes hard on the mismatch between enterprise enthusiasm and consumer skepticism. Mustafa argues people already get real value from chatbots, but he concedes the payoff may not yet feel big enough to justify the costs and disruption. His test is blunt: if AI does not make people healthier, happier, smarter, or more productive, people will reject it, and they should.

The most contentious stretch is around labor and consciousness. Mustafa tries to narrow earlier claims about AI replacing white-collar work by saying he meant tasks, not jobs. On AI consciousness, he is unusually direct. He argues models are not conscious, do not suffer, and that treating them as if they might have inner lives is dangerous because it confuses tools with moral subjects.

Practical Steps

• Separate hype from definitions. When AI leaders say AGI, superintelligence, or singularity, ask what they mean in plain language and what evidence they think supports the claim.
• In a company setting, track task-level gains before making job-level assumptions. Measure whether AI actually speeds up writing, summarizing, coding, support, or analysis, instead of assuming whole roles disappear.
• Watch token spend against outcomes. Higher usage does not automatically mean better results. Tie budgets to concrete outputs like faster shipping, fewer errors, or better customer response times.
• If you are evaluating vendors, ask where training data came from, whether models were distilled, and what controls exist for security and IP risk.
• For consumer AI, use a simple filter: does this save time, improve judgment, or solve a real problem you had yesterday? If not, ignore the marketing.

Notable Quotes

• "Superintelligence is coming. I think it's just around the corner." - Mustafa Suleiman
• "If it's not making me healthier and happier, smarter, more capable, more productive, then naturally people are going to be angry and resist." - Mustafa Suleiman
• "We do not want to have to contend with a superintelligence that has ideas about its own suffering." - Mustafa Suleiman

Worklife with Molly Graham • 38m

Overview

This episode is about purpose at work, but the useful part is how Molly Graham talks about finding it when your career has drifted away from what actually gives you energy. In conversation with Anne Morris, she describes leaving a successful path as an operator and COO because the overlap between what she was good at and what she wanted had broken apart. The discussion treats purpose less as a slogan and more as a working test: why you make the choices you make, and what kind of work leaves you feeling alive instead of depleted.

Key Takeaways

Molly’s clearest point is that being good at a job is a bad reason to keep doing it. She says she had become the obvious person for certain leadership roles, but knew she would be miserable in them. That split between competence and desire is a warning sign many people ignore because the outside world keeps rewarding them for the wrong thing.

She also pushes back on the idea that purpose arrives as a clean revelation. Her account is messier than that. A coach helped her leave a role that no longer fit, then helped her reframe that exit from “I’m going to be lost” to “I’m going on an adventure.” That shift in language mattered because people often stay in work they hate simply because they describe change as failure or drift.

Another strong insight is that purpose is usually found through evidence, not abstraction. Molly talks about rating every meeting from 1 to 10 based on how energized she felt afterward. Her pattern was extreme: the 10s were one-on-one conversations and moments of helping people directly. That gave her something more useful than vague self-reflection. It showed where her energy actually went.

She also says the search is rarely linear. Sometimes, in her words, you need to take the interview or even “a whole-ass job” to confirm what is not for you. That is a helpful correction to the pressure many people feel to get it right early. The episode argues that wrong turns are often part of the data.

For both Molly and Anne, vitality is a better guide than prestige. Anne brings in Howard Thurman’s line about asking what makes you come alive. Molly frames a similar idea through a three-part overlap: what you love doing, what you are great at, and what people will pay you to do. Purpose lives somewhere in that intersection, but it takes time to see clearly.

Practical Steps

• Run an energy audit for one week. After every meeting or major task, rate it from 1 to 10 based on how energized you feel afterward. Look for patterns, not isolated moments.
• If you are burned out or coming out of an intense role, set a fixed recovery period before making your next work decision. Molly says her coach had her take three months and focus only on things that reminded her who she was outside of work.
• Keep a list of ideas that make you feel excited. Do not judge them right away. If something gives you energy, write it down first and evaluate it later.
• Ask yourself Molly’s question: “What would you do if you believed you were already enough?” It helps separate real desire from proving behavior.
• Review the last few years of your work and name the moments you are proudest of. Then ask: Which of these would I gladly do again? Which made time disappear?
• When considering a new role, test whether it matches your past patterns of energy, not just your resume or reputation.

Notable Quotes

• Molly Graham: “I realized that the Venn diagram between what I was great at and what I loved doing had changed.”
• Molly Graham: “What would you do if you believed you were already enough?”
• Howard Thurman, quoted by Anne Morris: “Don’t ask what the world needs. Ask what makes you come alive because what the world needs is people who have come alive.”

In Depth • 1h 0m

Overview

This conversation is about what strong marketing looks like when products, audiences, channels, and AI are all moving faster than teams can comfortably track. The guest argues that marketing's real job has not changed: it sits between product, revenue, user perception, and community, and its value comes from making those pieces line up.

Using Figma as the main example, she talks through cross-functional accountability, the shift from VP-level execution to CMO-level company thinking, and why judgment matters more as new tools make content and campaigns easier to produce at scale.

Key Takeaways

The clearest idea in the episode is that marketing should own coherence, not just campaigns. The guest says too many companies split goals across teams in ways that create friction - marketing gets one metric, sales gets another, product influences both, and everyone starts optimizing their own slice. Her fix is shared accountability for the end goal, with teams understanding which inputs they most affect.

She also makes a sharp distinction between a VP or SVP of marketing and a CMO. A senior functional leader pushes an initiative through. A CMO has to ask whether the initiative is even the right use of people, budget, and attention for the business as a whole. She describes the role more like portfolio management: keep the business running, but spend disproportionate time on bigger bets that could create a step change.

Figma's push to widen the definition of design is her example of a high-stakes decision. She says two-thirds of people building in Figma are non-designers, so the company had to bring engineers, marketers, and PMs in without alienating the design community that built the brand. The strategy was to expand who gets to participate in design, not move away from design.

Another strong theme is the tension between growth and brand. She points out that what lifts short-term acquisition can damage long-term brand perception. A spammy ad might win clicks in one channel, but someone has to decide whether that trade is worth it across the full business. That balance, in her view, is where marketing gets hard.

On AI, her point is less "everything changes" than "the playbooks are changing." The fundamentals - curiosity, taste, creativity, adaptability - still matter. What shifts is that teams can now generate more options faster and more cheaply, so the scarce skill becomes judgment: which idea is right, which message will matter, what to ignore, and how to keep the human element from getting washed out.

Practical Steps

• Align teams around one shared business outcome instead of assigning disconnected funnel metrics to each function. Then spell out which inputs each team can influence most.
• Review marketing work as a portfolio. Separate "run the business" work from bigger bets, and protect time and budget for the latter.
• Build regular forums to share facts across the org: key metrics, customer feedback, product updates, support trends, and social sentiment. The guest sees transparency as one of the best defenses against politics and bad decision-making.
• Open up the reasoning behind decisions. If you want better taste across the company, explain why choices were made, what assumptions were used, and what trade-offs were accepted.
• In an AI-heavy workflow, don't just ask how to produce more. Ask what deserves to ship. Create more options quickly, then raise the bar on selection.
• Keep close contact with users. The guest repeatedly comes back to community, support, research, events, and social feedback as the best way to stay grounded when outside perception swings.

Notable Quotes

• "The only team that sits across all of those things is marketing, and it's the job of marketing to make sure that it all works together."
• "You have to goal people on the end goal knowing that there are inputs that different teams can have more influence on at each stage, but everyone has to be focused on the same end goal."
• "There is so much potential to scale quickly at low quality... The job becomes, what is the right outcome? What is the right choice?"

Decoder with Nilay Patel • 48m

Overview

This episode looks at SpaceX's planned IPO through a wider Musk lens: what happened to X after Elon Musk bought Twitter, and what the SpaceX filing says about power, accountability, and market rules. Neil Patel and New York Times reporter Ryan Mack argue that X has plainly weakened as a business, while Musk himself has become richer and harder to check.

They also dig into how the IPO appears set up to keep Musk firmly in control, even as public investors are pulled in through index funds and market demand. The core tension is simple: the underlying businesses have mixed fundamentals, but the offering is being sold on belief in Musk and his future promises.

Key Takeaways

X appears to be a business failure on its own terms. Mack says revenue and user growth have stalled, and Neil points to the filing as evidence that most major metrics are down. The one area showing strength is data licensing, including sales tied to AI. Yet that decline may not matter much to Musk personally, because X now functions as part of a larger group of companies rather than a stand-alone business that must justify itself.

A big theme is that Musk may have "won" even while Twitter/X lost. Mack's point is that Musk used the platform as distribution, influence, and a piece of a larger financial structure. X was folded into xAI and then connected with SpaceX, which means its weak business performance can be absorbed inside a much bigger story.

The discussion on corporate governance is the sharpest part of the episode. Mack says Musk controls about 85 percent of voting power at SpaceX through super-voting shares, which gives him broad power over board decisions, compensation, and company direction. That leaves public shareholders with limited ability to act as a real check.

The pay package described in the filing is another red flag. Mack says Musk received restricted stock tied to huge goals like a Mars colony and space-based computing, but can already vote those shares and even borrow against them with board approval. Since he controls the board, that approval is not much of a barrier. The goals look grand, but the structure still gives him power now.

On the business side, Starlink is presented as the only clearly profitable engine in SpaceX. The rest, especially AI efforts, are burning cash. Mack's read is that investors are not buying current performance so much as Musk's ability to keep selling a bigger future: space data centers, Mars manufacturing, AI services, and whatever comes next.

Practical Steps

• Read IPO filings past the headline valuation. Focus on voting rights, share classes, board control, arbitration clauses, and compensation terms.
• Separate the company from the founder. Ask whether the business works without the CEO's story carrying it.
• When you hear giant total addressable market claims, look for the math. If the numbers amount to "trust me," treat them as marketing, not analysis.
• If you invest through index funds, check what that means for ownership of companies you may not have chosen directly. Passive investing can still expose you to governance risk.
• Watch for cross-company dealmaking inside founder-led groups. Weak assets can be protected or reflated when they are merged into stronger, more exciting businesses.

Notable Quotes

• Ryan Mack: "X is simply not growing."
• Ryan Mack: "At the end of the day, most investors are betting on Elon's words."
• Ryan Mack: "The normal levers of accountability for someone like that have gone out the window."

HBR On Leadership • 25m

Overview

This episode looks at "personal power" - the kind of influence that comes from how people carry themselves, not from title or rank. Chris Lipp argues that the leaders who earn the most respect often project agency, responsibility, and action, even when they have little formal authority.

He says personal power is less about dominance or charisma than about believing you can create impact and acting in ways that signal that belief to others. The conversation ties that idea to hiring, promotion, negotiation, and day-to-day meetings.

Key Takeaways

Lipp defines personal power as a belief in your own ability to create impact. In his view, it rests on three foundations: a sense of control, an internal orientation, and a bias toward action. People with personal power look for where they can affect a situation, stay connected to their own values instead of chasing approval, and move rather than freeze.

One of the more surprising points is that value affirmation can change how others see you. Lipp says research shows that before an interview, writing for a few minutes about a core personal value can shift your mindset enough that you come across as more leaderly and more compelling. The point is not positive self-talk about skill. It is anchoring yourself in what matters to you.

He also pushes back on the idea that being agreeable earns influence. Adding value matters, but it is not enough if you never assert yourself. His example of a colleague accepting an offer below market gets at this: fear-driven deference can read as low power, while asking for fair treatment can make others see you as more worthy of it.

Another useful idea is that taking responsibility can raise status, even after a mistake. Lipp points to Bob Iger owning a major error early in his career at ABC Sports. Rather than damaging him, that admission led Rune Arledge to treat him with more respect. The signal was not "I failed." It was "I have control and will deal with it."

In meetings, the highest-status people are not always the loudest or the deepest subject-matter experts. Lipp says they often shape the flow of the discussion. They steer, synthesize, and draw others out. That is a form of influence people often miss.

Practical Steps

• Before an interview, presentation, or hard conversation, spend 4 to 5 minutes writing about one of your core values and why it matters in your life. Lipp says this can shift you into a more grounded, powerful state.
• When a situation feels outside your control, ask: "What part of this can I influence?" If the answer is only your response, start there.
• In negotiations, ask for fairness plainly. Do not assume self-advocacy will make you less likable.
• If you make a mistake, take responsibility early and directly. Avoid blame-shifting. People often read ownership as competence and steadiness.
• In meetings, do more than contribute ideas. Help direct the conversation. Ask questions, summarize what you heard, connect points, and move the group to the next issue.
• If you manage others, give them autonomy around execution and share goals clearly instead of overprescribing every step.

Notable Quotes

• "Personal power is our belief in our own capability to create impact." - Chris Lipp
• "Powerless words are powerless no matter how persuasive they are." - Chris Lipp
• "The person who has the most power in a room is the person controlling the spotlight." - Chris Lipp

Platformer • 1h 10m

Overview

This episode looks at AI and jobs from two angles: who is gaining right now, and what public policy should do before any larger wave of displacement hits. Casey Newton talks first with Ella Marquianos about chip workers at Samsung and TSMC cashing in on the AI boom, then with labor economist Catherine Ann Edwards, who argues that the bigger problem is not proving exactly how many jobs AI has changed but building a government response that works when people lose work for any reason.

Edwards is skeptical of grand claims about an AI-driven "idle class." She thinks AI may already be affecting hiring and staffing in some places, but she also says the weak labor market, high interest rates, and employer power explain a lot more of what young workers are facing right now.

Key Takeaways

One clear point from the episode is that AI's gains are showing up unevenly. Ella describes how Samsung's chip workers pushed for better compensation and won, with large bonuses tied to the semiconductor unit's profits, while workers in other divisions got far less. Her read is simple: unions work when workers have leverage, and right now chipmaking employees have it.

Edwards pushes back on the obsession with pinning down the exact number of jobs AI has destroyed or created. Her view is that policymakers do not need a perfect body count to act. If mass displacement is a risk, the government should build stronger systems now instead of waiting for economists to settle every measurement question.

She also rejects the Silicon Valley story that AI will produce a permanently unemployable class. Productivity gains may let firms operate with fewer workers in some functions, she says, but that does not automatically mean tens of millions of people become useless. The real issue is whether people who lose income have support, bargaining power, and a path into other work.

On younger workers, Edwards says AI may be part of the story, especially in entry-level knowledge jobs, but it is far from the whole story. She points to a cooling labor market and "upskilling," where employers demand more credentials when hiring slows, as a bigger reason many young people are stuck.

She is especially hard on UBI as the default answer from tech leaders. In her view, cash alone does not fix worker-employer power imbalances, and many elite supporters seem drawn to it because it preserves their wealth while easing public anger.

Practical Steps

For government, Edwards' advice is concrete:

• Build a stronger long-term unemployment system that helps people retrain, relocate, or start small businesses.
• Pay for mobility when jobs are in a different region.
• Invest in training for fields with real shortages, such as nursing and teaching.
• Strengthen antitrust enforcement rather than treating concentration as inevitable.
• Raise more revenue by rolling back parts of past tax cuts, tightening the tax code, and lowering the estate tax exemption.

For workers, especially younger ones:

• Treat the first job as a starting point, not a verdict on your future.
• Keep moving if a role is a bad fit; Edwards says mobility tends to improve pay and job matching.
• Look broadly across sectors instead of assuming one degree should lock you into one career track.
• Where possible, support collective bargaining. The Samsung example suggests workers closest to AI profits can win better terms when they organize.

Notable Quotes

• "Everyone's talking about it, no one's doing it." - Catherine Ann Edwards, joking about AI adoption and hype
• "It wasn't about the type of job that was lost. It was that people didn't have income. And that's what you respond to, the person and not the former employer." - Catherine Ann Edwards
• "We have to put workers and the economy first and not morph everything we do around a technology as cool as it may be." - Catherine Ann Edwards

Worklife with Molly Graham • 28m

Overview

This episode is a conversation with Mark Rober about how he built a huge YouTube audience without letting the platform set the terms. He talks about the patience he learned at NASA, why he has stuck to one video a month for 15 years, and why sustainability matters more than speed when you are building creative work or a business.

The thread running through the whole discussion is restraint. Rober says he avoids chasing fame, trends, and rapid expansion, and that choice has helped him stay excited about his work while growing a large audience and company.

Key Takeaways

Rober's years at NASA shaped his sense of effort and payoff. He spent seven years working on the Mars Curiosity rover, knowing the mission would come down to a few minutes of descent where it either worked or failed. That seems to have trained him to accept long timelines, delayed feedback, and high stakes without needing constant rewards along the way.

On YouTube, he has resisted the usual pressure to post more often or copy whatever the algorithm rewards. His view is simple: if one viral video pushes you into making the same thing forever, the platform starts deciding who you are. He says his original reason for starting mattered here. He was trying to share ideas he found interesting, not chase money or attention.

One of his clearest points is that "get rich" and "get famous" are bad reasons to start creating. He argues that both goals move further away as you approach them. In his telling, there are plenty of healthy reasons to make things - curiosity, skill-building, storytelling, and the satisfaction of making something good.

He also talks openly about approval. He says that wanting people to like what he makes can be productive at work because it pushes him to raise his standards. But he also knows that this impulse can become unhealthy in personal relationships, where it turns into trying to earn love or meet impossible standards.

The strongest idea in the episode is his definition of burnout. He describes it as the point where you are still doing the work but no longer getting the reward from it. His answer is to keep "the treadmill" at a speed he can maintain. That applies to output, hiring, spending, and even how much parasocial connection he wants with his audience.

Practical Steps

• Pick a pace you can keep for years, not just for a hot streak. If your current workload depends on adrenaline, it is probably too fast.
• Set a reason for doing the work that is not fame or money. Write it down. If your decisions start drifting, use that reason as a filter.
• Do not let one successful project trap you in an identity you do not want. A hit can be useful without becoming your whole job.
• Grow headcount slowly. Rober says he waited to leave Apple until he had a large audience, and he started his company only when he could fund it himself. The point is to avoid building obligations that force bad decisions later.
• Keep lifestyle inflation in check. He connects flashy spending with pressure, not freedom.
• Separate audience appreciation from emotional dependence. Enjoy the feedback, but be careful about building daily intimacy with strangers if that starts to distort your judgment or peace of mind.

Notable Quotes

• "There are a thousand great reasons. There's only two really bad reasons. And the two really bad reasons are to get rich and to get famous." - Mark Rober
• "When you're still doing the work, but you're not getting the reward for it. And so for me, the trick is like, look, keep it at a jogging speed." - Mark Rober
• "Teachers are the best. Like, it's the most important job on the planet." - Mark Rober

Big Technology Podcast • 1h 11m

Overview

This episode is a broad check-in on where the AI race stands, with Google, OpenAI, Anthropic, Apple, and Meta all under the microscope. Alex Kantrowitz and MG Siegler spend most of the conversation on one question: if AI shifts people away from the open web and toward agent-driven "super apps," who wins that transition and who gets left behind.

They argue that Google looks less secure than it did a few months ago, Apple is heading into a tense WWDC with a lot to prove, and Meta still looks like a company searching for a coherent next act. The show ends with breaking news that Anthropic has confidentially filed for an IPO, which raises the pressure on OpenAI.

Key Takeaways

Google's I/O felt thin because the main thing people expected, Gemini 3.5 Pro, was not ready. MG says Google led with Gemini 3.5 Flash instead, rolled it through many products, and then had to explain that the stronger model would come later. That left Google looking out of sync with how AI companies now ship: not on annual conference schedules, but whenever the model is ready.

The bigger issue, in their view, is not just model quality. It's product direction. OpenAI and Anthropic are moving toward tools like Codex and Claude Code that start in coding but point toward something larger: AI systems that can use your browser, your computer, and your accounts to complete tasks. Alex argues that "super app" is the right frame here. These products are moving toward becoming the interface for how people use the internet.

That creates a real threat to Google. If users start asking ChatGPT or Claude to search Gmail, compare hotels, book services, or act across websites, Google's role as the main front door to the web weakens. MG points out that Google still thinks in browser and product-silo terms, while the new winners may be the companies that unify chat, agents, coding, and browser control into one experience.

Apple's foldable iPhone comes up next. MG's read is that the form factor may be shorter and wider than people expect, possibly making it better for typing when folded. He thinks Apple has to do more than ship a folding screen. It needs to give the device a reason to exist beyond novelty.

On WWDC, both expect a lot of attention on Siri, but not necessarily a dramatic breakthrough. They also raise the possibility that Apple could use the event to signal a broader transition, whether that's management succession or changes to App Store economics.

Meta comes off as the weakest story in the group. MG calls out the company's messy subscription naming, weak morale, and unclear strategy outside ads. The sense is that Meta is spending heavily, trying many things, and still struggling to show a clean story about where it is headed.

The late-breaking Anthropic IPO filing matters because it sharpens the comparison with OpenAI. MG says public investors are likely to compare the two directly, and Anthropic's recent momentum in coding and enterprise makes that uncomfortable for OpenAI.

Practical Steps

• Watch AI product moves through the lens of interface control, not just model benchmarks. Ask: does this tool help users do work directly, or is it still just a chatbot?
• If you work in product or strategy, test how these agents fit into real workflows now. Connect one to Gmail, have it summarize threads, pull travel details, or draft follow-ups. That shows where current products are already better than traditional interfaces.
• If you're evaluating big tech companies, pay attention to internal structure. The hosts' point on Google is useful: companies with many strong product silos may struggle when the winning product needs those silos to collapse into one.
• For Apple watchers, WWDC should be judged less by flashy demos and more by whether Siri becomes dependable enough to trust with actual tasks.
• For founders, the conversation suggests a simple test: build for the layer where users act, not the layer they used to visit.

Notable Quotes

• "Google looks sort of silly for not having their model ready to go." - MG Siegler
• "The agents and the chatbots are going to merge." - Alex Kantrowitz
• "Google should have the single best place to do any sort of agentic email workflow... and they don't own that right now." - MG Siegler

Lenny's Podcast: Product | Career | Growth • 1h 19m

Overview

This episode centers on Benedict Evans's view that AI is a major platform shift on the scale of the internet or smartphones, but not a magical break from economic history. His argument is that AI will change a lot, though the shape of that change is still unclear, and many of today's loudest claims about instant job collapse or permanent dominance by model labs are way too confident.

Key Takeaways

Evans keeps coming back to one point: we are early. His comparison is the internet in 1997 - exciting, uneven, full of promise, and still missing most of the products and business models that will later look obvious. A small group of people use AI heavily, but outside tech, adoption is far less complete than the online discourse suggests.

On jobs, he pushes back hard on the "jobpocalypse" story. His view is that new technology has always removed some work while creating new kinds of work that were hard to name in advance. He argues that people are good at spotting the jobs that might shrink and bad at seeing the jobs that will appear after workflows, companies, and markets adjust. He also points out that even the leading AI companies are still hiring heavily, which cuts against the idea that useful AI immediately means fewer humans.

A second theme is the difference between a task and a job. AI may automate pieces of work - making slides, writing code, retrieving information - without replacing the broader role around judgment, coordination, politics, customer insight, and decision-making. That helps explain why consulting and professional services may grow during AI adoption rather than disappear. Companies need outside help to figure out where AI fits, how to redesign workflows, and how to deploy it safely.

He is also skeptical that foundation model companies will keep all the value. His case is simple: if models remain similar enough and competition stays strong, margins get pressured and value moves up the stack to products with better distribution, user experience, and specific use cases. In that world, AI models look less like Windows and more like cloud infrastructure.

Practical Steps

If you're worried about your career, Evans's advice is blunt:

• Do not reject AI on principle and call that a strategy.
• Use the tools enough to understand where they help, where they fail, and what good judgment around them looks like.
• In your field, separate the repeatable task from the actual job. Ask what part of your work is button-clicking and what part depends on trust, judgment, or context.
• Learn how AI changes workflows in your industry, not just what the demos show. A law firm, retailer, hospital, and software company will adopt this differently.
• Build credibility as someone who can work with AI without being fooled by it, especially by hallucinations and weak output.

For companies, the implied playbook is to run real workflow audits, test AI in narrow domains first, and expect change to happen over years, not weeks.

Notable Quotes

• "AI is as big a deal as the internet or mobile, and only as big a deal as the internet or mobile." - Benedict Evans
• "You can always see the job that's going to go away. And you don't know the new job because it doesn't exist yet." - Benedict Evans
• "Don't stick your head in the sand and say, 'I hate all of this stuff.' ... What helps is you diving into this and coming out, understanding what you can do with it." - Benedict Evans

The Ezra Klein Show • 1h 14m

The Big Idea

This episode is about a blunt question: what if Trump is not mainly trying to help Republicans win the midterms? What if he cares more about keeping the Republican Party scared, loyal, and under his control?

Ezra Klein lays out that idea and tests it against Trump's actions. His basic case is simple. If Trump were focused on winning more seats, you would expect him to act like a coach trying to win a game: calm the team down, focus on the scoreboard, and avoid unforced errors. Instead, Ezra says Trump is acting more like an owner trying to make sure everyone in the building knows who signs the checks.

The guest, Republican strategist Liam Donovan, partly agrees. He doesn't go as far as Ezra does, but he does say that when winning elections conflicts with Trump's grip on the party, control often seems to win.

Why It Matters

This matters because it changes how you read what Trump is doing.

If you think his goal is "help Republicans win," some of his choices look irrational. Why back risky candidates? Why pick fights inside the party? Why say things that hand Democrats easy attack ads?

But if the goal is "make Republicans fear crossing me," those same moves make more sense. It's like a boss who would rather fire a few good workers than let the rest think disobedience is allowed.

That has big effects beyond one election. It shapes who runs, who speaks up, who stays quiet, and what kind of Republican Party exists after Trump leaves office.

Key Concepts

Control vs. electoral success

Ezra's argument is that Trump sees the Republican Party as his shield and his power source. Congress matters, but party obedience matters more.

So when Trump goes after Republicans he sees as disloyal, even if they are useful in tough states, the point may not be to improve the party's chances. The point may be to send a message. Touch the hot stove once, and everyone else in the kitchen learns fast.

Why Trump's numbers are weak

Donovan says part of Trump's low approval comes from a gap between what voters wanted and what Trump delivered. Many voters wanted a return to the feel of pre-Covid life, especially on the economy. That's an easy promise to sell and a much harder one to produce.

He also says Trump now has more loyal people around him, which means fewer guardrails. In his first term, some aides blocked or softened his instincts. This time, he is getting more of what he actually wants. And voters may not like the full-strength version.

Candidate choices send signals

The Texas fight over John Cornyn and Ken Paxton is one example. Cornyn looked safer. Paxton looks riskier. Backing Paxton may help Trump prove he still decides who matters in the party, even if it makes the general election harder.

That pattern shows up elsewhere too. The warning to Republicans is plain: disagree with Trump, and he may try to wreck your career.

The party after Trump

They also talk about a coming split in the GOP, especially among younger Republicans. One side is more traditional and Fox News-shaped. The other is more online, more suspicious of foreign wars, and more drawn to figures like Tucker Carlson.

Trump currently holds those groups together by force of personality. The open question is what happens when he is gone. Donovan's view is that Republicans will need someone who can keep the attitude of Trumpism without relying entirely on Trump himself.

The Bottom Line

The episode's main point is that Trump may see the Republican Party less as a team to help win elections and more as a machine he must personally control.

If that's right, some of his strangest decisions stop looking like mistakes and start looking like the point. Winning Congress would be nice. Owning the party may matter more.

Big Technology Podcast • 59m

Overview

This episode looks at whether the AI boom is running ahead of reality. Alex Kantrowitz and Ronjon Roy focus on rising token costs, weak links between AI spending and shipped products, Anthropic's new financing round, and Robinhood's plan to let chatbots trade on users' behalf.

The core debate is simple: are companies seeing real returns from AI, or are they burning money in a rush to experiment, impress management, and keep up with the market? The hosts agree the technology is useful. They disagree more on whether today's waste is a normal early phase or a warning sign.

Key Takeaways

The sharpest point in the conversation is the gap between AI spending and business output. Alex points to data from Entelligence AI saying only 18% of spending on advanced AI coding tools is turning into shipped products that reach users. If that number is anywhere close to right, the problem is less "token maxing" and more that most usage still isn't tied to results.

Ronjon argues some of this waste is expected. In his view, companies have had only a few months with coding tools that got meaningfully better around late 2025, so high burn with weak returns is not shocking. He says a normal cycle would involve experimenting, finding what works, cutting what doesn't, and then tightening usage. The problem is that the market has turned that messy phase into a giant financial story before the work is mature.

They also spend time on how AI revenue may be getting flattered by spending loops. The discussion points to big cloud companies investing in AI labs, then booking revenue when those labs buy compute back from them. Ronjon's concern is not that the accounting is fake in a legal sense, but that it can make demand look cleaner and steadier than it is. If enterprise buyers pull back, the effects could hit multiple layers at once.

Anthropic's latest round is treated as both a real milestone and a market signal. Alex sees it as proof that Anthropic has become OpenAI's strongest rival, largely on the back of coding products. Ronjon sees the valuation as part business achievement, part effort to set expectations ahead of a public listing.

The Robinhood story lands somewhere between funny and plausible. The idea of letting an AI agent trade a dedicated account sounds reckless in a retail setting, but both hosts admit that software may eventually handle routine investing choices better than many humans do.

Practical Steps

For companies using AI tools, the advice is pretty concrete:

• Track token spending at the team and workflow level, not just in aggregate cloud bills.
• Tie AI use to shipped output. If a team is consuming heavily and not releasing anything, that needs attention fast.
• Start with one process where the gain is easy to measure, then expand from there.
• Cut waste in the workflow itself. Ronjon gives examples like changing how context is passed to models and breaking data into smaller structured chunks to lower token use.
• Don't treat a short burst of experimentation as proof of long-term value or failure. Review what happened, then decide where to invest more.

For individual users, the Robinhood and Gmail examples point to a broader rule: be careful what permissions you hand over. These tools are getting more useful, but each connection gives them more control over money, messages, and decisions.

Notable Quotes

"AI has got to not waste 82% of the tokens in order for this boom to continue." - Alex Kantrowitz

"If everyone just approached this in a nice, responsible way and just built and just learned... we would be okay." - Ronjon Roy

"I think we're going to see a pullback and we are going to recognize... if things aren't being done strategically... obviously you're not going to see any kind of ROI." - Ronjon Roy

How I AI • 13m

Overview

Claire Vo gives an early read on Anthropic's Opus 4.8 after a few hours of testing in coding and business workflows. Her take is pretty clear: the model looks strong on paper and can do impressive first-pass work, but it loses reliability at the edges, especially when follow-up fixes, existing codebases, or grounded strategy work matter.

Key Takeaways

The headline from her tests is that Opus 4.8 seems best at the first 80 to 90 percent of a task. In Claude Code, she says it handled a one-shot feature build well: it took a spec, made a plan, coded autonomously for about 20 minutes, and produced something that worked on a preview branch. For greenfield feature work, that is a good result.

The trouble started once she tried to refine and extend the output. She says the model repeatedly stumbled on the "last 10%" and introduced bugs during iteration. More concerning, she saw outright hallucinations when the model was bug hunting, which stood out because she says she had not seen that kind of made-up reasoning in a long time. Her read is that the model was acting on hypotheses rather than checking against the actual code or data.

That pattern showed up again in existing codebases. When she asked Opus 4.8 to help rebase branches after a large underlying PR changed the code state, it needed repeated correction cycles and kept creating edge-case issues. Her point is less that the model cannot code and more that it has trouble figuring out where, exactly, to intervene in a messy, real codebase.

She also expected more initiative from a model positioned as a top coding agent. In a playful test, she asked it to build something her nine-year-old would find exciting. The prompt it proposed sounded ambitious, but the shipped result was more ordinary than she expected. Even after pushing it toward something "more fun" and 3D, she felt the model did competent work without showing much imagination or stretch.

On business tasks, her comparison between Opus 4.7 and 4.8 was even less flattering for the newer model. Using the same context, she asked both versions to review how she had spent the last three months and suggest where her focus should shift to grow the business. She says 4.7 stayed grounded in numbers and context, while 4.8 had a harder time finding the right data, overemphasized small signals, and produced strategy that felt vague. In a follow-up roadmap prompt, she says 4.8 even implied research it had not actually done, then admitted it had not searched the sources she asked about.

Practical Steps

• Use Opus 4.8 for first-pass builds, prototypes, and new feature surfaces where speed matters more than polish.
• Treat follow-up debugging as a separate phase. Verify every claimed root cause against logs, code, or tests before accepting a fix.
• Be careful with existing codebases. If you ask the model to rebase, refactor, or patch around prior work, expect to review branch state and edge cases manually.
• Ask the model to cite what it actually inspected. A direct prompt like "List the files, queries, and sources you used before answering" may expose weak grounding early.
• Compare outputs across model versions on strategy work. Claire's test suggests the older model may be better when the job depends on numbers, context, and restraint rather than broad synthesis.
• If you want ambitious output, state the bar explicitly and review whether the result matches it. The model may default to "good enough" unless pushed hard.

Notable Quotes

• Claire Vo: "It does really, really well until it doesn't do well."
• Claire Vo: "In real code bases, the edges destroy it."
• Claire Vo: "It 100% made up things based on a hypothesis, not data."

Worklife with Molly Graham • 30m

Overview

This episode centers on Caroline Wanga's idea of "career mapping" as a way to make decisions when you do not know what you want to do next. In conversation with Jessi Hempel, she explains how she moved from an intern role at Target to the C-suite, then later to leading Essence Ventures, by treating uncertainty as something to work with instead of something to hide.

Wanga also talks about purpose, failure, and the difference between intuition and the "inner saboteur." The through line is agency: you may not control every career outcome, but you can be far more active in shaping your path than most people think.

Key Takeaways

Wanga's main point is that not knowing is normal, and the mistake is treating that uncertainty like a personal flaw. Early in her career, a mentor helped her turn "I have no idea what I want" into a map of experiences to test. That shift matters. Rather than choosing an identity too early, she focused on trying key parts of the business and asking, "What do I want to learn from this?"

Her version of a career map is practical. Each role or experience should be tied to a few specific learning goals, not a fixed timeline or title obsession. Once you have learned what you came to learn, you can make a "strategic yes" and continue, or a "thoughtful no" and move on. That keeps people from staying stuck in roles that have already taught them what they can.

Another strong point is that career growth is relational. Wanga says her progress was shaped by people who asked one more question when she was afraid to admit she did not know. She also made her map visible to mentors and leaders so they could advocate for her when talent decisions were being made behind closed doors.

She pushes back on the usual talk about "personal brand." Her argument is that people should focus on personal purpose instead. In her view, splitting yourself into a work self and a real self is exhausting and less useful than knowing your strengths, your weak spots, and the kind of work that fits who you are.

On failure, she argues that people are taught to hide it when they should be studying it. And on decision-making, she says senior leaders need to tell apart intuition from self-sabotage. Those voices can sound similar, but they point in very different directions.

Practical Steps

• Build a simple career map around a question, not a title. Start with: "What am I trying to figure out next?"
• List 3-4 experiences that could help answer that question within your current company or field.
• For each experience, define a few learning goals. Example:
  • Do I like managing people?
  • Do I want to stay in this kind of company?
  • What kind of work gives me energy?
• Share that map with trusted mentors, managers, or peers outside routine status meetings. Ask them to tell you what support exists and where they see fit or gaps.
• Study your workplace before making moves. Wanga's approach worked in part because she understood what her company valued and how development conversations happened there.
• Shift from "How do I improve all my weaknesses?" to "Where are my natural strengths, and how can I spend more of my time there?"
• When facing a big decision, write down the voice of your intuition and the voice of your inner saboteur. Compare tone and intent. One is trying to guide you; the other is trying to shut you down.

Notable Quotes

• "Forget your age. Focus on where you are in your professional career."
• "If you don't, play with the map. That's how it works." - Caroline Wanga
• "I don't work on personal brand. I work on personal purpose." - Caroline Wanga

The Aboard Podcast • 48m

The Story

This episode starts with a joke that lands because it is barely a joke: the guest has built something "incredibly exciting and incredibly boring," which turns out to be custom accounting software. Paul Ford and Rich Ciotti bring on Craig Mod, who lives in Japan and has the kind of work life that breaks ordinary bookkeeping tools. He is an American citizen, pays taxes in Japan, still has to file in the US, earns money through memberships and books, and runs a one-person creative business spread across countries, currencies, and institutions. That setup alone explains why off-the-shelf software starts to feel less like help and more like a trap.

Craig is a good guest for this because he is not a tourist in tech. He has been programming since childhood, studied computer science and fine arts, and has spent years moving between software, publishing, design, and art. His writing life grew out of that mix. He built his own membership program instead of using someone else's platform, then used that support to fund long solo walks across Japan. Those walks become nightly dispatches, photographs, and eventually books. It's a striking life, but the business side of it is a mess in the way many independent careers are a mess: several revenue streams, paperwork everywhere, and a lot of dread when tax season arrives.

That dread is what pushed him to build. The software he describes is less a reinvention of QuickBooks than a personal command center. It tracks income, expenses, expected taxes, and medical receipts, and it remembers the forms and patterns from prior years. The point is not novelty. The point is relief. He wanted a system that fit his actual life instead of forcing his life into someone else's categories.

From there the conversation widens. Rich and Paul use Craig's project as a way to talk about AI as software, not magic. Rich keeps bringing the discussion back to a grounded point: if you understand how software gets stood up, you can do a lot with these tools. Craig's accounting app is one example of what happens when a person with domain knowledge and technical fluency finally gets tools that let him make exactly the thing he needs.

Then the tone shifts. Craig raises a darker question about abundance, meaning, and what happens if machines take over more of the labor that once structured human life. Rich pushes back. He thinks that ten years from now, much of this will still look recognizable, with people using AI in ordinary ways inside ordinary organizations. He does not see AGI swallowing everything so much as culture slowly absorbing the tools. The disagreement never turns into a fight. It feels more like three people circling the same uncertainty from different angles.

Main Themes

The clearest theme is that AI becomes interesting when it leaves the demo stage and enters some annoying, specific corner of real life. This episode is about taxes, receipts, and filing obligations, but that is what makes it persuasive. Craig did not build software to prove a theory. He built it because his life had too many exceptions for standard products to handle cleanly.

A second theme is that the people getting the most out of this moment are the ones who already understand how software is put together. All three speakers keep returning to that gap. Craig can build his own tool because he knows the stack, the architecture, and the logic behind it. Rich and Paul are blunt that this is still out of reach for most people, not because they lack intelligence, but because software knowledge has usually been taught through frameworks and jobs rather than through a plain-language map of how systems fit together.

The last thread is about limits, both human and technical. Craig sees AI opening extraordinary creative and practical power while also stirring up old fears about value, work, and purpose. Rich answers with a more grounded faith in human habits and human mess. Between them, the episode makes a useful point: the future may arrive through very strange tools, but it will still run into ordinary people, old institutions, and the same unresolved questions about what matters.

HBR On Leadership • 29m

Overview

This episode looks at how Shake Shack pushed into kiosks, mobile ordering, and AI without giving up the hospitality that made the brand popular in the first place. The discussion centers on a basic tension: how do you add speed, data, and scale in a labor-heavy business while keeping the experience human?

Stephanie So, Shake Shack's chief growth officer, and HBS professor Christopher Stanton use the company's shift during and after COVID to show how digital tools can change ordering, staffing, and even menu decisions. A lot of the conversation comes back to one idea: digital works best when it removes friction, not when it makes the brand feel colder.

Key Takeaways

Shake Shack did not treat digital as a pure tech project. The company saw kiosks and ordering tools as part of the guest experience, which meant design choices mattered beyond efficiency. So says the team studied competitors closely, even sending a designer into restaurants with a GoPro to watch the experience from a customer's point of view. One lesson stuck: if a kiosk is "as big as a human," it can feel like a replacement for a person rather than a tool.

The episode makes a strong case for being a fast follower. So calls it the "second mouse strategy" - let someone else take the first hit, learn from their mistakes, then move quickly with a better version. Stanton argues this made sense for Shake Shack because customers come for the food and brand, not because the company has the newest ordering hardware. That gave Shake Shack room to wait, learn, and then roll out kiosks quickly across its stores.

The data coming from digital ordering changed how Shake Shack thought about menu choices and upselling. So says the company found that when customers were asked to actively choose between a single, double, or triple burger, more people picked doubles than when a default option was preselected. The same pattern showed up with add-ons like avocado and bacon. The takeaway is simple: customers often upgrade on their own if the interface asks them clearly, without pushy prompts.

There is also a labor angle. Stanton points out that automation can cut both ways. It can remove repetitive work and free employees to focus on hospitality, or it can turn staff into kiosk troubleshooters and hurt morale. The quality of the employee experience shapes the customer experience, so digital tools have to be judged on both fronts.

Practical Steps

• Study customer behavior in the real setting, not just in dashboards. Watch how people enter, order, hesitate, and react to the physical setup.
• Design self-service tools so they do not dominate the room. Keep them useful but visually restrained.
• Avoid default choices when you want better customer intent data. Ask people to make an active selection and track what changes.
• Test whether digital prompts can replace awkward verbal upselling. Customers may spend more when they feel in control.
• Measure digital changes against both guest satisfaction and employee workload. If staff spend their shift fixing machines, the system needs work.
• If your product is not a tech product, consider waiting for others to test early versions of new tools. Then move fast once the format is proven.
• Build one connected view of the customer across app, web, and in-store ordering so offers, rewards, and personalization carry across channels.

Notable Quotes

• Stephanie So: "If it's as big as a human, then it looks like it's trying to replace a human."
• Stephanie So: "The first mouse likely won't get the cheese... but if you're the second mouse, actually you can get the cheese out of there without any risk to your life."
• Christopher Stanton: "There is a risk in being second in some industries... but in this case, there's probably not a ton of risk because it's not a tech play that the customer is coming for."

AI and I • 41m

Overview

This episode is a debate around Dan's essay "After Automation" and the gap between AI panic and how work actually changes inside a company that uses AI heavily every day. Dan and Brandon argue that more automation does not automatically mean less human work; in many cases, it creates more demand for judgment, direction, and cleanup.

They frame Every as an early signal: the team says it has grown from a handful of people to about 30 while becoming more "agent native," which pushes against the claim that white-collar work is simply disappearing. The core question is what humans still do when models can produce decent work on command.

Key Takeaways

Dan's main argument is that AI makes "yesterday's expert competence" cheap. Models can produce code, writing, designs, and analysis that look impressive at first pass, so non-experts can now do work that used to sit behind a specialist gate. That shift feels threatening, but the output is often only partly right. It gets you close, then hands the problem back to a person.

That creates a paradox: when lots of people can generate acceptable first drafts, the volume of almost-good work explodes. The bottleneck moves upstream and downstream. Humans still need to decide what matters, define the task, review the output, and turn rough material into something that actually works in context. Experts do less of the old production work and more of the finishing, steering, and system design.

A second point is that "autonomous" and "having agency" are not the same thing. Dan says current agents can act on behalf of a user and may get much better at carrying out long tasks, but they still do not possess their own aims in the way a human does. His view is that the industry is pushing models toward compliance, not independent will, and that matters when people imagine runaway replacement.

They also push back on dramatic layoff stories. The discussion mentions companies that cut staff in the name of AI and then, in Dan's account of customer service examples he reviewed, sometimes have to bring people back because the implementation fails or customers refuse to deal with bots. Adoption is shaped by technical limits and human preference, not just by what is possible in a demo.

Practical Steps

If you want to stay useful as AI spreads, the advice here is simple:

• Keep up with new models and test them on your real work, not toy prompts.
• Use AI for first drafts, research passes, code scaffolding, and repetitive tasks, then review the result hard.
• Get better at framing problems. Clear instructions and good taste become more valuable when production gets cheap.
• Build review systems: checklists, repo rules, editing standards, and approval steps that catch "close but wrong" output before it ships.
• Pay attention to where people still want a human. In support, sales, and other service roles, customer trust can limit automation.
• If you write or think for a living, use AI as a partner in iteration. Dan describes dictating arguments, asking Claude to reflect back what he was trying to say, and listening to machine-read drafts to spot weak points.

The practical message is not to predict the entire labor market. It is to work with the tools now so you are fluent when expectations change.

Notable Quotes

• Dan: "AI makes yesterday's expert competence cheap."
• Dan: "The further away an agent gets from a human, the less valuable it is."
• Dan: "If you ride the models, you're going to be okay. You're going to have a job. You're going to do great work and you don't have to worry."

Big Technology Podcast • 56m

Overview

Alex Kantrowitz talks with former Twitter CEO Dick Costolo about what could happen if SpaceX, OpenAI, and Anthropic hit the public markets soon. The core point is that IPOs are driven as much by story and expectation as by revenue and margins, and once a company is public, that story can trap it.

They also get into the stress public markets create inside companies, why AI valuations may run into political and physical limits, and what Meta and X say about morale, product instinct, and the current tech cycle.

Key Takeaways

Costolo’s main point is simple: the hardest part of going public is not the listing day pop, it’s what happens after. In private markets, valuation moves in occasional jumps and employees can mostly ignore it. In public markets, stock prices swing daily, often for reasons that have little to do with the business. He says leaders need to prepare employees for that whiplash before the IPO, or the company gets pulled into constant anxiety.

He uses Twitter as the warning case. The company’s IPO story centered on massive user growth, so even when Twitter beat on revenue or EBITDA, the market punished it if monthly active users missed expectations. His argument is that early messaging matters because investors keep grading the company against that first promise.

On the three possible AI IPOs, Costolo sees very different setups. He argues SpaceX has the easiest public-market story because Elon Musk already knows how to keep investors focused on a distant future rather than current numbers. OpenAI, in his view, has the toughest setup because Sam Altman has made huge compute and spending commitments that public investors will try to match against a still-developing business model. Anthropic may have the cleanest middle path: a steadier enterprise story, less hype, and less pressure to explain giant promises.

A second big theme is that AI companies may face limits that have nothing to do with model quality. Costolo thinks public resistance to data centers is a real threat. He points to growing backlash from both left and right over power use, water use, local disruption, and weak job creation. If those projects slow down, the AI leaders’ expansion plans get harder to justify.

On pricing and competition, he agrees with the view that OpenAI and Anthropic may be pushed into price pressure rather than easy price increases, especially if products stay close enough in quality. That makes the long-term economics less clear than headline valuations suggest.

The conversation ends on culture and status. Costolo says repeated layoffs destroy trust when management keeps changing the explanation. He also argues that Silicon Valley’s fixation on who got rich from the AI boom creates a miserable comparison game, one that leaves even the winners unhappy.

Practical Steps

• If you’re taking a company public, train employees for volatility ahead of time. Explain that the stock may move 15 to 20 percent on no real news and that this does not automatically mean the business changed.
• Be careful with the promise you make at IPO. Investors will keep measuring you against that first narrative, sometimes more than they measure the quarter itself.
• If you run an AI company, build a public case for why your infrastructure helps society. Don’t assume the value is obvious, especially when new data centers face local opposition.
• If you lead through layoffs, say what went wrong plainly. Recycled corporate language makes people assume management is hiding the truth.
• If you invest, watch ordering and timing. Costolo’s view is that the first big AI IPOs may absorb a lot of available public-market appetite, which could shape outcomes for whoever comes later.
• If you work in tech, don’t organize your life around who hit the AI lottery. Costolo’s advice is blunt: comparison is a bad strategy and usually turns into resentment.

Notable Quotes

• Dick Costolo: "You need to prep the team for, hey, we’re about to go into a world where the price of the stock can change, even though nothing particularly happened today."
• Dick Costolo: "The narrative and the story and your ability to help the market think about the way you want to tell the story is just as important as the specific numbers in the quarter."
• Dick Costolo: "Living a life of comparison, it doesn’t matter where you are in that stack, it’s a losing strategy."

Platformer • 1h 2m

Overview

This episode looks at what AI coding tools may do to software jobs, with Anthropic's Boris Cherny making the case that the shift is already underway. Casey Newton presses him on whether tools like Claude Code are just making engineers faster or starting to change the role itself, and the answer is more unsettling than simple job-loss talk.

The conversation also ties that bigger claim to what workers are already seeing: pressure from management to use AI, weak incentives, and a lot of confusion about what "good" AI adoption actually looks like.

Key Takeaways

Boris says the future is less about software engineers disappearing overnight and more about the job blurring into something broader. At Anthropic, he says managers, product people, and designers are all coding now, while some engineers spend less time writing code directly and more time directing agents. His point is that "programming" has changed many times before, from punch cards to modern languages, and this is another turn of the wheel.

He does not claim a clean outcome for employment. He says both things can happen at once: some companies will need fewer engineers because each one can do more, while other companies will hire more because higher output creates room for more products and experiments. That is a more believable frame than a single forecast about total job collapse.

One striking thread is that the people getting the most from these tools are not always the obvious experts. Boris points to Anthropic hackathons where, he says, winners included an electrician, a doctor, and a carpenter rather than career engineers. His argument is that AI may reward people with clear problems to solve, not just people with the strongest technical résumé.

The episode also shows how badly many workplaces are handling adoption. Ella Marcianus cites Microsoft's survey of 20,000 AI users: workers say AI helps them produce new kinds of work and spend more time on higher-value tasks, but only a small share say they are rewarded for experimenting. That gap helps explain the odd behavior she describes at Amazon and Meta, where employees reportedly chase token-use leaderboards rather than clear business results.

A quieter but important point: Boris says product matters because people need direct experience with AI to judge its effects. Anthropic, in his telling, builds tools partly so society can see what is coming rather than debate abstractions.

Practical Steps

• If you manage a team, stop measuring AI use by volume. Token counts and vague mandates invite waste. Define what better work looks like: faster turnaround, fewer errors, stronger output, or more experiments shipped.
• Model the behavior you want. Ella cites Microsoft research suggesting AI use rises when managers show how they use it in their own jobs. Give examples, prompts, and specific tasks, not speeches about the future.
• Give people room to experiment safely. Boris argues that good ideas often come from unexpected corners of an organization. Small budgets, access to tools, and permission to test matter more than top-down hype.
• If you're early in your career, learn how to supervise AI systems, not just how to type code. That means writing clear instructions, checking outputs, testing work, and understanding systems well enough to catch bad decisions.
• Keep one foot in fundamentals. Even if agents do more of the hands-on work, you still need enough technical judgment to know when the model is wrong, expensive, insecure, or overcomplicating the task.

Notable Quotes

• "There's going to be a lot of companies that need less engineers because engineers are more productive... At the same time, there's going to be a lot of companies that need a lot more engineers." - Boris Cherny
• "Everyone on the team codes. You don't have to be an engineer anymore." - Boris Cherny
• "AI is like all stick and no carrot." - Casey Newton

Decoder with Nilay Patel • 51m

Overview

Nilay Patel talks with Google and Alphabet CEO Sundar Pichai right after Google I/O, where Google pushed Gemini models, AI agents, and major changes to Search and YouTube. The conversation starts with how Pichai has reorganized Google for the AI race, then moves into harder questions about whether AI search is eroding the open web and what Google thinks a healthy information market looks like now.

The episode lands on two big tensions: Google wants AI to turn search into action, not just answers, and it also wants to keep the web, publishers, and creators alive while doing it. Pichai argues those goals can coexist, though he admits some current AI search experiences are too opinionated and still need work.

Key Takeaways

Pichai says Google’s response to ChatGPT was not just a product push. It forced a structural rewrite inside the company. He combined research groups into Google DeepMind, set up a centralized AI infrastructure team, added a chief AI architect role, and started weekly AI product reviews to move faster and make fewer slow, committee-style decisions. His view of management is simple: most decisions are not that consequential, so speed matters more than perfection.

A second theme is convergence. Google may show AI as separate products today - Gemini, Search, Spark, agent tools, NotebookLM - but Pichai sees them as pieces of one system. The long-term goal is an assistant that can reason, use tools, write code, and carry context across products. He describes agents less as a standalone category and more as a built-in capability that should disappear into the experience.

Search is where the interview gets sharp. Nilay presses Pichai on "Google zero," the idea that Google keeps more attention for itself by answering queries directly instead of sending traffic out. Pichai does not accept the framing, but he does admit the product is changing and that low-quality clicks are being filtered out. He says Google is still committed to linking users to the broader web, while also meeting demand for faster, more direct answers. When Nilay shows him a poor search result for "best Chromebook," Pichai says his own reaction is that the answer is "more opinionated than it should be."

On public distrust of AI, Pichai rejects the idea that this is just a branding problem. He says people have real reasons to be uneasy: job disruption, energy use, deepfakes, and the speed of change itself. He treats that anxiety as rational, not as user error.

The last section turns to AGI. Pichai says the exact timeline matters less than the fact that systems will get much more capable soon. He and Demis Hassabis appear aligned that AGI, however defined, is closer than many institutions are prepared for.

Practical Steps

• Separate big decisions from routine ones. Pichai’s rule is that most choices should be made quickly so the organization keeps moving.
• If you run teams, build shared infrastructure before adding more products. Google’s AI push worked better once models, tooling, and review processes were centralized.
• Treat early product overlap as normal, then merge later. Google let teams experiment first and is now trying to unify things like notebooks and agents.
• Audit where your product has become too "opinionated." Pichai’s reaction to the Chromebook result is a useful test: if the system sounds more certain than the evidence supports, it needs adjustment.
• Plan for traffic shifts now. Publishers and creators should not assume old search patterns will hold. Build direct audience relationships, subscriptions, and distribution beyond Google.

Notable Quotes

• "There are very, very few decisions which are really consequential, and most decisions aren't." - Sundar Pichai
• "I think it's probably more opinionated than it should be for the particular query you showed me." - Sundar Pichai, on a flawed AI search result
• "Three years from now, whether you and I call it AGI or not, doesn't matter because it'll be very, very powerful and we have to prepare for it." - Sundar Pichai

In Depth • 1h 2m

Overview

This episode is about what has and has not changed in selling software in the AI era. The guest argues that despite the hype around product-led growth and AI-native buying, a lot of the old rules still hold: enterprises still need change management, training, clear rollout plans, and people they trust.

The biggest shift is with AI-native customers, where the pace is much faster and the communication style is more continuous. But even there, the guest’s core view is that great sales still comes down to smart people, strong judgment, clear process, and real care for the customer.

Key Takeaways

The guest pushes back on the idea that AI has made traditional sales obsolete. In enterprise, he says success still depends less on raw technology than on helping large groups of people change how they work. At Windsurf, teams that got structured rollouts, training, and in-person support saw better results than companies that simply dropped tools into an internal marketplace and hoped adoption would happen on its own.

He also makes a strong case for opinionated selling. Buyers do not just want access to software; they want a vendor that can say, “Here is the best way to do this, here is why, and here is how we’ll help make it work.” That is what separates a partner from what he calls a software vending machine.

For AI-native customers, the buying motion looks different. These teams already understand the basics, so the sales motion shifts from education to workflow tuning. The cycle compresses from weeks to days, much of the interaction happens in Slack or text, and sellers need to operate in a more constant stream of communication. Still, the traits that make someone good remain about the same: curiosity, problem-solving, care, and follow-through.

On building sales orgs, the guest’s view is practical: process should raise the floor without capping the ceiling. You want a simple, measurable system that creates consistency, but you do not want so much structure that reps stop using judgment. His example was memorable: no sales process will tell a rep to teach a customer’s kid guitar over Zoom, yet those human moves are often what make teams stand out.

He also argues that enablement matters more, not less, in the AI era. AI can help with practice and recall, but enterprise sellers still need real understanding, especially when deals involve politics, change management, and internal power dynamics that no model can fully read.

Practical Steps

• For enterprise rollouts, do not rely on self-serve adoption alone. Build a rollout plan with training, workflow discovery, milestone tracking, and follow-up sessions.
• Give customers a clear upfront value proposition for training. Spell out what they should expect in week one, week four, and week 12.
• Keep your sales process simple. The guest recommends a small number of stages, each with three to five clear requirements to move forward.
• Instrument the funnel by stage. Track timing and conversion from outbound or inbound lead to first meeting, evaluation, scoped proof of value, and close so coaching is tied to facts.
• Invest early in enablement, partner relationships, and data infrastructure, even before they seem urgent. The guest says this paid off later as revenue scaled.
• For AI-native accounts, communicate in the channels they already use. Stay close to the workflow, respond fast, and work in an ongoing thread rather than formal weekly recaps alone.
• Hire people you expect to trust with real autonomy. If every decision has to come back to the leader, the org slows down and accountability gets blurry.

Notable Quotes

• “Change management dictates success in the enterprise more than technology.”
• “You can’t fake giving a shit.”
• “I want us to have a super measurable, predictable sales process, but I want what we do to raise the floor. What I don’t want is for us to cap the ceiling.”

HBR On Leadership • 31m

Overview

This episode looks at what it takes for a family business to survive across generations and still grow. The conversation centers on Johnson Security Bureau, a third-generation security company in the South Bronx, and the choices its CEO, Jessica Johnson-Cope, faces as she tries to scale without giving up the values her family built the company on.

Professor Henry McGee frames the case around three paths: stay focused on New York, expand geographically, or move into cybersecurity. The discussion keeps coming back to the same tension: growth creates opportunity, but it also puts culture, quality, and judgment under pressure.

Key Takeaways

Johnson Security Bureau’s story is about more than succession. Johnson-Cope describes the business as part of a larger family mission: creating jobs and mobility in a low-income community. That shapes how she thinks about growth. Expansion is not just about revenue; it is also about who gets hired, which partners get chosen, and whether the company can keep serving people the way her grandparents intended.

One strong point in the episode is that longevity in a family business does not happen by accident. McGee says owners need a real succession plan, early exposure for the next generation, and a way to manage family emotion before it turns into business conflict. Johnson-Cope adds another layer: access to strong networks matters. Her family’s connections to civic, business, and community leaders helped the company stay informed and supported across decades.

The conversation also shows why restraint can be a leadership strength. When a major client wanted the company to take on a much larger assignment, Johnson-Cope did not automatically say yes. She stepped back to ask whether the firm could deliver at the standard it expected of itself. That says a lot about her operating style: growth only counts if the business can execute well and stay aligned with its values.

Cybersecurity comes up as the most attractive and risky option. McGee points out that traditional guard services tend to have thin margins, while cybersecurity can be far more profitable. But the move is not simple. It means hiring different talent, competing with firms that already know the space, and changing what kind of company Johnson Security Bureau is. Johnson-Cope’s view is practical: physical security alone will not carry the company far enough, and trusted advisors have made clear that security firms that ignore technology will fall behind.

Practical Steps

• Build succession on purpose. Identify likely successors early, give them exposure to the business, and be clear about roles before a crisis forces the issue.
• Separate family feelings from business decisions as much as possible. That may mean formal governance, outside advisors, or regular decision processes everyone agrees to follow.
• Use networks as working assets. Stay close to mentors, industry experts, customers, and community leaders who can open doors and give honest advice.
• Pressure-test growth opportunities before accepting them. Ask:
  • Can we deliver at our current standard?
  • Do we have the people and systems in place?
  • Will this partner or acquisition fit our values?
• Treat adjacent expansion carefully. If you are moving into a field like cybersecurity, start by mapping the talent, capabilities, and competitive gaps instead of assuming your current model will carry over.
• Watch ego in decision-making. Johnson-Cope’s point is simple: when ego gets loud, judgment gets worse. That is usually the moment to call an advisor.

Notable Quotes

• Jessica Johnson-Cope: "If I wanted to see change in terms of the economy, where we lived and where we conducted business, that change would have to start with me."
• Jessica Johnson-Cope: "What's the point of having trusted advisors if you don't trust their advice?"
• Henry McGee: "The key to success is managing all the family dynamics."

HBR On Leadership • 38m

Overview

This episode looks at what it takes to move from individual contributor to leader, especially for women who may need to work through both self-doubt and other people's outdated perceptions. Executive coaches Muriel Wilkins and Amy Su argue that leadership starts before the title does, and that the shift is as much internal as it is visible to others.

They talk through the awkward parts of that transition: learning to see yourself differently, getting others to catch up, and figuring out whether leadership is even the path you want.

Key Takeaways

A central point is that leadership is not something you switch on after a promotion. Wilkins says many people wait until they have formal authority before acting "leaderly," but that delay holds them back. The work starts earlier: speaking with judgment, asking better questions, showing composure, and taking responsibility for how others experience you.

The guests make a sharp distinction between asking for input as a follower and asking for input as a leader. Amy Su gives a practical example: instead of asking, "How should I price this proposal?" start with your own recommendation, explain your reasoning, then invite feedback. That small change signals judgment and ownership without shutting others out.

They also point out that internal change often happens faster than external recognition. You may know you've grown, but coworkers may still see the intern or junior employee you once were. For people who have spent years inside one company, that can become a real obstacle. The advice here is twofold: use your institutional knowledge and relationships as assets, but pay attention to signs that the organization has stopped updating its view of you. If the roles you want keep going to outside hires, that may be a message.

Another strong theme is that women can accept leadership opportunities too gratefully and not ask whether they are being set up to succeed. Wilkins pushes against that instinct. If you're offered a role, the organization already wants you. Ask for visible backing from your manager, especially if former peers will now report to you, and make sure the conditions around the role support your success.

The conversation also covers visibility and trust in remote work. Virtual settings make both harder because people see less of your context. The guests say visibility now takes more planning: decide who needs to know you, how they should know you, and why. Trust depends more heavily on follow-through, responsiveness, and clear communication about delays.

Practical Steps

• Start leading before you get the title. In meetings and one-on-ones, lead with your point of view first, then ask for feedback.
• Learn your organization's leadership criteria. If there is a formal competency model, get it from HR and use it to spot the skills you need to build.
• If you're promoted internally, ask for explicit support from your boss. If former peers will report to you, discuss how that transition will be introduced and backed.
• Watch for signals that your company still sees an old version of you. If that pattern continues after direct career conversations, test your value in the outside market.
• In remote work, be selective about visibility. Identify the key stakeholders, the right channel, and the purpose before filling calendars with meetings.
• Build trust by replying quickly, even if only to confirm receipt and set expectations for a fuller response later.
• Before saying yes to extra work, ask whether you're stepping up from a leadership mindset or slipping into an old habit of being the reliable junior person.
• If you're unsure about pursuing leadership, look at the next three to five years rather than treating it as a lifetime choice.

Notable Quotes

• "The minute I have a client who says, with real conviction, that they do want to lead, that's actually the biggest breakthrough because they have to own it." - Muriel Wilkins

• "You're lucky to have me." - Muriel Wilkins, on the mindset people should bring when stepping into a bigger role

• "The world of possibilities to demonstrate a higher order of leadership is available to all of us at every moment, whether somebody gives us permission or not." - Amy Su