Lenny's Podcast · Jul 9, 2026
Adam Mosseri, head of Instagram, discusses how AI is reshaping product team structures toward smaller generalist "pods" with a new "product staff" role, while arguing that taste, judgment, and human authenticity become more—not less—valuable as AI automates execution. He also shares Instagram's strategic bet that AI-generated content abundance will drive users toward authentic human creators, making Instagram's creator-centric positioning a tailwind.
Product Staff is Meta's answer to the AI-era PM: a generalist who can do meaningful design, data analysis, and research work without dedicated specialists, enabled by AI tools.
This is the organizational model Meta is betting on *right now* in 2025–2026—not a future hypothesis. If you're a senior PM, this is your role's next evolution; if you're hiring, the question is no longer "which specialist?" but "how generalist can this person be?"
It's the Swiss Army knife that replaced a full toolbox—not as sharp on any single blade, but you can carry it everywhere.
Taste is the judgment about *what to build and why* that remains irreducibly human even as AI handles more of the *how*.
As a PM, your competitive edge is no longer speed of delivery—it's the quality of your judgment about which problems matter. Frameworks and process are table stakes; the differentiator is the ability to make controversial, opinionated calls.
In a world where any chef can now execute any recipe perfectly, the scarce skill is knowing which dish to put on the menu.
The highest-leverage AI skill is not using AI fluently, but knowing precisely when *not* to trust it and where it will improve next.
In regulated, complex B2B environments, wrong trust in AI outputs creates real downstream risk—compliance, quality, stakeholder credibility. Calibrated skepticism is a professional asset, not a deficiency.
It's like knowing the weather forecast's accuracy rate by geography before deciding whether to pack an umbrella—the tool is useful only if you know its error profile.
AI can assist strategy but cannot generate a genuinely differentiated one without heavy human steering, because real strategy requires integrating context—people, culture, regulation, brand identity—that isn't fully legible to a model.
If you outsource strategy to AI without this steering work, you converge on consensus answers. In competitive B2B markets, consensus strategy is a race to the middle. Your value as a senior PM is making the controversial call and defending it.
Asking AI for strategy without constraints is like asking a GPS for the "best route" without telling it whether you're optimizing for speed, scenery, or avoiding tolls.
The best product leaders are curators—of ideas, people, technologies, and strategies—not necessarily the originators of those ideas.
In large orgs with complex stakeholder structures, the bottleneck is rarely idea generation—it's idea selection and alignment. Positioning yourself as a curator is also a more defensible and scalable leadership posture as AI generates more candidate ideas.
A museum curator doesn't paint the art—they decide which art belongs together, in what order, and why it matters.
Recommendation systems don't know you like "surfing"—they know you as a vector of numbers that *happens to correlate* with surfing content, and only now are LLMs able to translate those numbers back into human language.
For any AI-driven product, "explainability" and "user trust" are increasingly product problems, not just model problems. This technique—LLM-as-interpreter of opaque model outputs—is a practical pattern for building user-facing transparency into black-box systems.
The algorithm had a perfect map of your taste written in a language only computers could read—LLMs just invented the translation dictionary.
When synthetic content floods the market, authentic human perspective becomes the scarce premium good—and platforms built around creators are positioned to capture that demand.
This is a live product strategy thesis from a 3-billion-user platform navigating a real market shift. The underlying logic—scarcity inversion when a previously scarce resource becomes abundant—applies to any product category where AI commoditizes supply.
When printed photos became free and infinite, handwritten letters became more emotionally valuable, not less.
Recommendation systems must choose between playing it safe with known preferences (exploitation) and taking calculated risks to discover unknown ones (exploration)—and the balance shapes the entire creator ecosystem.
If you're building any recommendation or discovery surface—internal tool, marketplace, content feed—this trade-off applies. Pure exploitation converges toward incumbents and popular content; only deliberate exploration investment surfaces new value.
Exploitation is a restaurant recommending your usual order; exploration is a sommelier saying "try this—I think you'll be surprised."
A pure chronological feed is a design that sounds user-friendly but structurally rewards institutional publishers who post constantly, causing individual and personal content to drown.
This is a clean example of how system incentives diverge from user intent—a core product design failure mode. Anytime you design a feed, marketplace, or ranking surface, ask: what behavior does this incentive structure reward at scale?
Designing a party where whoever talks loudest gets the most attention—technically fair, but the quietest guests with the best stories get drowned out.
As AI token costs approach the scale of engineer salaries, organizations need the same budget discipline for AI spend that they apply to headcount and infrastructure.
In enterprise contexts with procurement cycles and budget ownership, AI spend governance will land on PMs and product leads to justify. Getting ahead of this with a clear value-tracking model is easier before finance demands it than after.
It's the same problem as cloud cost governance in 2015—everyone was spinning up instances freely until the AWS bill arrived and someone had to own it.
The centaur model keeps humans in strategic control with AI as a powerful tool; the reverse centaur inverts this, with AI directing and humans executing—a dynamic to actively resist.
This is a decision-rights question, not just a productivity question. In regulated industries and complex organizations, surrendering strategic judgment to AI output creates accountability gaps that surface in audits, failures, and stakeholder conflicts.
The difference between a pilot using autopilot (centaur) and a pilot who just follows whatever the autopilot says without understanding or overriding it (reverse centaur).
Knowing that a *piece of content* is AI-generated and knowing that an *account* is AI-operated are two separate trust signals that serve different user needs and face different technical feasibility challenges.
For any platform handling user-generated content or third-party AI agents, this two-layer transparency model (content origin + account identity) is a concrete design pattern for trust and provenance.
Labeling a photo as "edited" tells you about the artifact; labeling the photographer as "stock photo service" tells you about the source—both matter, but for different reasons.
Your team structure is about to shrink—and that's a feature, not a bug.
Meta is actively moving to pods of 6-7 people where a 'product staff' generalist replaces dedicated designers, researchers, and data scientists. If you're a senior PM in a large org, this is the organizational direction; understanding the role's shape and the specialist-on-demand model matters for how you hire and structure work now.
AI is eating execution—your defensible value is judgment and taste.
Mosseri is explicit: vision and strategy are where human cycles will concentrate as AI handles more delivery. For PMs in regulated, complex B2B environments, this means doubling down on opinionated, controversial strategic calls—not process compliance or delivery throughput.
Recommendation system design has concrete lessons for any AI-driven product.
The exploration/exploitation trade-off, embedding illegibility, and LLM-as-interpreter pattern are directly applicable to any product with personalization, discovery, or content ranking surfaces—not just consumer social.
a lot of what a data scientist does at a big company, for instance, is relatively mechanical. And so, you know, there's stuff that they do that is really more like, you know, art and science. And the stuff that's really more like just pulling data, data management, you know, so some of the tools that we're building internally to understand, for instance, a traditional data science question would be a waterfall.
Concrete example of which data science tasks AI tooling is absorbing first—relevant for any PM thinking about team composition or which specialist functions to retain.
I think if you ask an AI just for a strategy lazily, you're not going to get something great. You're going to get something pretty predictable that probably the competition would expect you to do. I think if you want a really more effective one, you need to think long and hard about what are all the different inputs that need to be considered.
Directly actionable for any PM using AI in strategy work—the failure mode is precisely the lazy prompt, and the fix is explicit constraint enumeration.
I actually think some of our strongest product staff are going to be converts from design and from data science who are just looking to expand their reach. And they were influential across functional boundaries before, but this world where those functional boundaries are just wildly blurred just allow them just to jump in.
Reframes the career risk for designers and data scientists—the path is expansion, not replacement. Relevant for cross-functional leadership and talent retention conversations.
You can't launch something to three billion people and not test it first, but you can't test something at our scale and not expect people to cover it and not and be so you have to be ready to talk about it before you even know you want to launch it.
Practical governance point about experimentation communication strategy at scale—the leak is not 'if' but 'when', requiring pre-prepared narratives even for unreleased tests.
I think we can come up with I don't want to see seven photos in a row, but I'm happy to see six photos in a whatever your heart can, you know, whatever your mind can come up with. So, we have a lot of work to do. And so, I'm excited about that.
Signals the product direction for algorithmic transparency and user agency—LLM-interpreted embedding topics that users can edit—a concrete pattern for trust-building in AI-driven personalization products.