Skip to content

By playing, you agree to uListen's Terms and Privacy Policy and YouTube's Terms of Service.

Lenny's PodcastLenny's Podcast

The new rules of product management in the AI era | Sherif Mansour (Head of AI, Atlassian)

Sherif Mansour is Head of AI and Product Craft at Atlassian (the company behind Jira and Confluence), where he has spent 17 years building and scaling some of the most successful enterprise products in history.

Lenny RachitskyhostSherif Mansourguest
Nov 22, 20261h 21mWatch on YouTube

Summaries, chapters, transcripts, and FAQs on this page are made by uListen, not YouTube.

Great conversations run long. Their best ideas don't have to.

uListen is free on iPhone, iPad, Android, Chrome, and Claude.

See how

CHAPTERS

Jump to publisher timestamps

Chapter summaries

  1. Why PMs aren’t “over” in an AI world: throughput got cheaper, direction didn’t

    Lenny raises the claim that AI makes PMs unnecessary, and Sherif previews a core counterpoint: teams can build faster, but still struggle to choose what to build. Sherif describes an internal experiment where roles blurred into “AI builders,” only for teams to revert once they realized direction—not output—was the bottleneck.

    • •Lenny frames the narrative that AI could replace PMs and asks why PMs still matter
    • •Sherif explains an internal experiment where squads tried operating without PM/design roles
    • •The experiment initially felt faster, then reverted back to traditional roles
    • •Sherif’s takeaway: throughput isn’t the problem; direction is—and teams need more steering
  2. What makes a great PM: filling context gaps and building a “shared brain”

    Sherif defines great PM work in medium-to-large organizations as systematically filling context gaps so teams can make better decisions independently. He emphasizes building a shared understanding across customer, product/market, and business context, especially as teams scale and trust and alignment break down.

    • •Sherif argues PMs don’t own decision-making; they enable decision-making velocity
    • •Great PMs focus on building a shared brain across cross-functional teams
    • •He names three key contexts: customer, product/market, and business context
    • •Scaling product teams breaks trust and shared understanding; PMs help repair that through context
  3. Staying out of the backlog: how context-sharing unblocks teams

    Sherif explains why he tells PMs to “run away” from the backlog: prioritization is often a proxy for unshared context. He describes tactics to spread context—like involving engineers in customer interviews and strategy work—so the team can make day-to-day decisions without waiting on the PM.

    • •Sherif challenges PMs to ask why they think one backlog item matters more than another
    • •He suggests PMs often hold context the team lacks; the job is to distribute it
    • •He prefers engineers attend customer interviews to build empathy directly
    • •He encourages co-creating vision and landscape understanding instead of handing down conclusions
  4. Concrete examples of doing context-sharing well (and why it works)

    Sherif offers practical ways PMs and teams can close context gaps: reverse-engineering the reasoning behind priorities, co-creating designs, and letting engineers explore tools directly. He shares how customer-facing events and booth time also build shared understanding that improves product decisions.

    • •Reverse-engineer your own priority logic to find what context others are missing
    • •Co-creation beats handoffs; designers and teams exploring together changes aha moments
    • •One team had every engineer try AI tools and report back, rather than delegating it to PM/design
    • •Engineers manning customer booths helps them hear feedback firsthand and build shared context
  5. Where PMs should sit on the power spectrum: influence without authority

    Lenny asks where PMs belong between ‘boss’ and ‘equal peer.’ Sherif argues PMs should strive toward being equals with no special decision power, winning alignment through shared vision and context rather than specs handed down to engineers.

    • •Sherif says PMs should strive for an equal-peer model with no extra decision authority
    • •He contrasts spec handoff vs shared-vision collaboration models
    • •He describes high-performing teams where engineers propose features after internalizing context
    • •He frames PM effectiveness as enabling others to make good calls, not controlling decisions
  6. PM Craft Triangle: general manager, scientist, artist—three discovery styles

    Sherif introduces a framework used at Atlassian that classifies PM strengths and default discovery approaches as general manager, scientist, or artist. He explains how each archetype tends to reason, what they optimize for, and why mapping the right PM to the right work matters more than “adding bodies.”

    • •Sherif shares a triangle framework: general manager, scientist, and artist PM archetypes
    • •Scientist PMs are hypothesis-driven and often experimentation-focused
    • •General manager PMs focus on business outcomes like opportunity sizing and revenue
    • •Artist PMs lead with vision and experience, often working backward from an intuitive solution
  7. Using the triangle in hiring and calibration—and why you don’t need to be great at everything

    Sherif explains how the triangle helps evaluate candidates and calibrate PM performance, including how answers reveal a candidate’s natural style. He and Lenny discuss the myth that PMs must excel at every dimension, and Sherif argues it’s better to lean into strengths while building complementary teams.

    • •Sherif describes how interview questions reveal where someone sits in the triangle
    • •He says few people excel equally across all three; larger orgs can hire for specialization
    • •Sherif advocates celebrating weaknesses to create safety and build complementary teams
    • •Lenny adds there’s a baseline competence needed, but not ‘best-in-class’ across every skill
  8. Career coaching unlocks: the right opportunity, slightly above your level

    Sherif shares what most often accelerates PM growth: leaders deliberately giving someone a stretch opportunity aligned to their strengths. He encourages early-career PMs to analyze what they’re praised for, seek similar projects, and explicitly communicate the direction they want to grow.

    • •Sherif says growth hinges on deliberate stretch opportunities just above current level
    • •He describes stepping aside to let a scientist-leaning PM lead a growing product area
    • •Early-career PMs should identify work they’re praised for and replicate the pattern
    • •He suggests using a framework with your manager to discuss your strengths and desired opportunities
  9. Why PM roles are thriving in the AI era: “direct the ship, don’t row it”

    Lenny shares job-market observations that PM roles appear to be growing, and asks why. Sherif explains how an “everyone is an AI builder” narrative failed in practice: output increased, but clarity and direction became the limiting factor—making PM-style steering and alignment even more valuable.

    • •Lenny observes PM roles appear to be thriving relative to some other roles
    • •Sherif recounts Atlassian’s “AI builder squad” experiment and what it revealed
    • •Sherif’s framing: throughput is cheaper; direction is the real constraint
    • •He summarizes this as focusing on directing the ship rather than rowing it
  10. AI amplifies strengths and weaknesses: why specialization still matters

    Sherif uses the ‘mockup tools era’ as an analogy: making building easier doesn’t automatically make everyone good at design. He argues AI expands everyone’s capabilities but doesn’t erase craft boundaries; quality and taste still depend on domain expertise and specialization.

    • •Sherif says earlier tooling made prototyping accessible but didn’t make PMs great designers
    • •He claims PMs can be poor solution designers despite access to tools
    • •AI expands capability, but also amplifies weaknesses alongside strengths
    • •He argues specializations remain important even as everyone’s toolset broadens
  11. What PMs should actually do with AI: start with the context gap, not the tool

    Lenny asks what PMs should be doing with AI—from prototyping to shipping code. Sherif recommends starting with the team’s biggest context gap (customer, market, vision) and then applying AI to accelerate closing that gap, rather than treating ‘PM should code’ as the default path.

    • •Sherif reiterates PMs own decision-making velocity, not decisions themselves
    • •He proposes diagnosing the team’s context gaps first, then applying AI accordingly
    • •He suggests AI can help accelerate customer understanding, market analysis, or vision clarity
    • •Lenny reflects that coding-to-production is rarely the bottleneck in many environments
  12. PM hiring trends: artist PMs, cultural change, and the case for hiring juniors

    Sherif explains what’s trending up in PM hiring: experience-led ‘artist’ PMs and people who can shift how work gets done with AI. He makes a case for hiring juniors because they may be more willing to adopt AI-native workflows, while seniors are better at spotting quality issues—together forming a complementary team.

    • •Sherif says artist/experience-led PMs are trending up as taste matters more
    • •He emphasizes hiring for cultural change: new ways of working with AI, beyond summaries
    • •He argues juniors can bring AI-native habits and are often more willing to try new tools
    • •He notes seniors tend to be stronger at identifying low-quality output and improving rigor
  13. Spotting the “artist streak” early: signals in exercises, storytelling, and prototypes

    Lenny asks what an artist PM looks like and whether it can be identified early. Sherif describes artists as vision- and experience-led, often drawing or prototyping to clarify ideas, and says you can sometimes see these instincts even in junior candidates through how they narrate and present solutions.

    • •Sherif describes artists as vision-led and more data-informed than data-driven
    • •He suggests a signal: someone who naturally draws flows to resolve ambiguity
    • •He shares how APM take-home presentations revealed different discovery styles
    • •He argues it’s easier to accelerate in what you’re naturally good at than to force-fit a new style
  14. When starting with the solution is right: canvases, cow paths, and strategy assets

    Sherif challenges the blanket rule ‘always start with the problem’ by naming scenarios where starting with a solution helps. He describes how providing a broad canvas (like chat or agents) can reveal valuable use cases to productize, and how strategy often starts from existing assets and capabilities before selecting what problems to pursue.

    • •Sherif says starting with a solution can help discover productizable use cases
    • •He gives an example of using chat as a ‘canvas’ that later becomes a more native feature
    • •He describes observing what customers build as a way to determine what to formalize
    • •He argues product strategy can start with existing assets and unique capabilities to decide where to play and how to win
  15. Why “bolting AI on” can be the right strategy—and why nuance beats hot takes

    Sherif argues that for established products, evolving workflows by adding AI into existing user flows can be the most practical path to becoming AI-native. He and Lenny discuss how simplistic viral rules miss context, and Sherif emphasizes that many pieces of product advice have valid opposites depending on situation.

    • •Sherif says ‘don’t bolt on AI’ is a catchy headline that misses nuance for mature products
    • •He argues established products should evolve by enhancing existing workflows with AI
    • •He describes looking at existing human workflows to decide where agents can assist
    • •Sherif and Lenny emphasize understanding the context behind advice rather than copying one-liners
  16. Why managers still matter: common mistakes, founder dynamics, and transparent disagreement

    Sherif explains misconceptions around management—especially the idea you must become a manager to influence strategy—and argues for valuing both IC and manager paths. He shares the most common new-manager mistake (going hands-off too quickly), then offers frameworks for working with visionary founders and handling disagreements through transparency and presenting both sides to teams.

    • •Sherif challenges the belief that exec-level strategic influence requires being a manager
    • •He says new PM managers often go too hands-off too quickly instead of leading by example
    • •He describes working with visionary leaders as catching up to their ‘chapter 10’ context
    • •He recommends clarifying who owns a decision, stating disagreements transparently, and presenting tradeoffs clearly to teams

Publisher timestamps

  1. 0:00Teaser
  2. 1:24What makes a great PMRead this chapter
  3. 4:17Why your job is to fill context gaps, not make decisionsRead this chapter
  4. 7:10Examples of context-sharing done well and done poorly
  5. 11:25The GM/scientist/artist PM triangle
  6. 12:38How to use the triangle in hiring and calibration
  7. 15:01You don’t need to be great at everythingRead this chapter
  8. 18:09Career coaching: early-career unlocksRead this chapter
  9. 21:14Career coaching: senior PM and manager unlocksRead this chapter
  10. 22:19Why PMs are thriving in the AI eraRead this chapter
  11. 23:42Atlassian’s AI builder experiment—and what it revealed
  12. 25:01Why throughput is no longer the bottleneck; direction isRead this chapter
  13. 28:48What PMs should actually be doing with AI
  14. 31:04What’s trending up and down in PM hiring
  15. 32:44The case for hiring more juniors in an AI world
  16. 38:07How to spot the artist streak early in candidatesRead this chapter
  17. 46:05When starting with the solution is the right move
  18. 52:42Why “bolting AI on” is often the right product strategy
  19. 56:01The importance of nuance over hot takes
  20. 1:01:31Why managers still matter
  21. 1:02:42The most common mistake new PM managers make
  22. 1:04:05How to work with visionary founders and strong stakeholdersRead this chapter
  23. 1:07:12When you disagree: a framework for transparency
  24. 1:10:51Final thoughts
  25. 1:11:37Lightning round

Get more out of YouTube videos.

Read along on your phone, search it beside the video, or ask your favorite AI app what was said.