[
  {
    "start": 0.06,
    "end": 9.56,
    "text": "This episode is provided by Thomas Allgeier and Frennis, based on the most relevant LinkedIn posts about digital products and services in calendar weeks forty-eight and forty-nine."
  },
  {
    "start": 10.1,
    "end": 20.36,
    "text": "Frennis is a B-to-B market research company helping enterprises gain the market, customer, and competitive insights needed to drive customer-centric and cost-efficient product development."
  },
  {
    "start": 21.6,
    "end": 22.72,
    "text": "Welcome back to the Deep Dive."
  },
  {
    "start": 24.56,
    "end": 29.26,
    "text": "Today we're distilling some really critical shifts we're seeing in the world of digital products and services."
  },
  {
    "start": 29.64,
    "end": 34.58,
    "text": "I mean, looking at the industry conversation over the last couple of weeks, one thing is just crystal clear."
  },
  {
    "start": 34.86,
    "end": 35.36,
    "text": "What's that?"
  },
  {
    "start": 35.62,
    "end": 38.52,
    "text": "The product discipline is, well, it's finally growing up."
  },
  {
    "start": 38.96,
    "end": 41.62,
    "text": "It's moving past just shipping features for the sake of it."
  },
  {
    "start": 41.8,
    "end": 41.84,
    "text": "It"
  },
  {
    "start": 41.88,
    "end": 42.28,
    "text": "really is."
  },
  {
    "start": 42.34,
    "end": 43.52,
    "text": "That's the core finding, you know."
  },
  {
    "start": 43.82,
    "end": 47.88,
    "text": "Leaders seem to be done with the vanity metrics, the output, the feature velocity."
  },
  {
    "start": 48.18,
    "end": 53.02,
    "text": "The whole focus has pivoted and pretty intensely toward foundational strength."
  },
  {
    "start": 53.2,
    "end": 54.12,
    "text": "Foundational strength."
  },
  {
    "start": 54.16,
    "end": 55.3,
    "text": "What do you mean by that exactly?"
  },
  {
    "start": 55.72,
    "end": 57.7,
    "text": "I mean, defining and aligning the operating model."
  },
  {
    "start": 58.1,
    "end": 64.959,
    "text": "for one and prioritizing rock solid customer evidence making sure the technical platform is actually ready to scale."
  },
  {
    "start": 65.519,
    "end": 70.18,
    "text": "the market is demanding provable outcomes and well that's changing everything."
  },
  {
    "start": 70.26,
    "end": 72.76,
    "text": "okay let's unpack that this whole mandate for outcomes."
  },
  {
    "start": 73.0,
    "end": 78.54,
    "text": "we can start there with our first theme strategy roadmaps and this outcomes mandate."
  },
  {
    "start": 78.86,
    "end": 81.26,
    "text": "we've all seen that classic flawed roadmap"
  },
  {
    "start": 81.5,
    "end": 81.62,
    "text": "right."
  },
  {
    "start": 81.68,
    "end": 86.42,
    "text": "oh yeah The one that's just a list of features nobody really asked for, prioritized by politics."
  },
  {
    "start": 86.56,
    "end": 87.12,
    "text": "Exactly."
  },
  {
    "start": 87.34,
    "end": 90.7,
    "text": "And the chatter online confirms that this is a systemic problem."
  },
  {
    "start": 90.78,
    "end": 92.58,
    "text": "It's a massive drag on success."
  },
  {
    "start": 93.26,
    "end": 97.38,
    "text": "The real tension seems to be that most roadmaps are just designed to be reactive."
  },
  {
    "start": 97.52,
    "end": 97.62,
    "text": "They"
  },
  {
    "start": 97.7,
    "end": 97.8,
    "text": "are."
  },
  {
    "start": 98.0,
    "end": 100.9,
    "text": "They serve internal stakeholders instead of driving a strategic vision."
  },
  {
    "start": 101.3,
    "end": 103.9,
    "text": "There was a great post from Jasmine grew a gray on this."
  },
  {
    "start": 104.34,
    "end": 107.36,
    "text": "She observed that most roadmaps fail because they are reactive."
  },
  {
    "start": 107.78,
    "end": 113.12,
    "text": "The focus shifts from the product's actual direction to, and this is her quote, who you're trying to please."
  },
  {
    "start": 114.32,
    "end": 119.82,
    "text": "The system itself is often set up, maybe unintentionally, to pull PMs into that reactive whirlpool."
  },
  {
    "start": 120.36,
    "end": 122.38,
    "text": "You know, urgent fixes, sales demands."
  },
  {
    "start": 122.64,
    "end": 124.0,
    "text": "So you're just stuck in that mode."
  },
  {
    "start": 124.06,
    "end": 125.1,
    "text": "You're never strategic."
  },
  {
    "start": 125.4,
    "end": 125.64,
    "text": "Never."
  },
  {
    "start": 126.34,
    "end": 129.82,
    "text": "The conclusion is you have to retire that kind of roadmap."
  },
  {
    "start": 130.16,
    "end": 136.26,
    "text": "You have to set a clear North Star and then really concentrate your resources on outcome driven bets."
  },
  {
    "start": 136.86,
    "end": 138.26,
    "text": "Things that will actually move the needle."
  },
  {
    "start": 138.48,
    "end": 138.64,
    "text": "That"
  },
  {
    "start": 138.72,
    "end": 143.44,
    "text": "transition sounds great in theory, but it immediately brings up the question of ownership."
  },
  {
    "start": 143.56,
    "end": 149.5,
    "text": "I mean, how are product leaders supposed to handle this new pressure to deliver huge business results?"
  },
  {
    "start": 149.7,
    "end": 152.12,
    "text": "Well, that's where the scope of product leadership is expanding."
  },
  {
    "start": 152.46,
    "end": 155.16,
    "text": "And sometimes, frankly, unreasonably so."
  },
  {
    "start": 156.04,
    "end": 157.22,
    "text": "Sean King highlighted this."
  },
  {
    "start": 157.7,
    "end": 163.18,
    "text": "He's seeing product leadership roles that are asked to own these incredibly broad business outcomes."
  },
  {
    "start": 163.42,
    "end": 164.34,
    "text": "Like what, for example?"
  },
  {
    "start": 164.42,
    "end": 171.2,
    "text": "Things like overall policyholder retention for an insurance company, or guest satisfaction across an entire hotel chain."
  },
  {
    "start": 171.8,
    "end": 176.04,
    "text": "But the product team's actual responsibility only covers the digital front end."
  },
  {
    "start": 176.34,
    "end": 178.34,
    "text": "So just the mobile app or the checkout flow?"
  },
  {
    "start": 178.52,
    "end": 178.94,
    "text": "Exactly."
  },
  {
    "start": 179.24,
    "end": 184.14,
    "text": "So the PMs are being held responsible for, I don't know, operational gaps or bad sales training."
  },
  {
    "start": 184.5,
    "end": 185.92,
    "text": "Things completely outside of their control."
  },
  {
    "start": 186.04,
    "end": 187.1,
    "text": "Which is not going to work."
  },
  {
    "start": 187.42,
    "end": 187.48,
    "text": "No."
  },
  {
    "start": 188.28,
    "end": 189.82,
    "text": "He called it product management theater."
  },
  {
    "start": 190.58,
    "end": 196.42,
    "text": "The PM is sort of performing the role of an outcome owner, but they don't have the real levers to pull across the business."
  },
  {
    "start": 196.72,
    "end": 200.04,
    "text": "So the implication is that digital is just one piece of the puzzle."
  },
  {
    "start": 200.28,
    "end": 207.78,
    "text": "product teams have to collaborate way more deeply with ops, sales, support, if they actually want to influence those big results."
  },
  {
    "start": 207.96,
    "end": 208.4,
    "text": "Precisely."
  },
  {
    "start": 208.74,
    "end": 212.98,
    "text": "Otherwise, the digital product just becomes the scapegoat when the service model itself is broken."
  },
  {
    "start": 213.3,
    "end": 215.58,
    "text": "Okay, so that brings us back to strategic clarity."
  },
  {
    "start": 216.16,
    "end": 223.26,
    "text": "If roadmaps are just feature lists and feature lists lead to this theater, we need a whole different system for making decisions."
  },
  {
    "start": 223.42,
    "end": 223.64,
    "text": "We do."
  },
  {
    "start": 224.04,
    "end": 226.52,
    "text": "Sarah Perkins had some really sharp advice on this."
  },
  {
    "start": 226.86,
    "end": 230.68,
    "text": "She said, stop presenting roadmaps and start leading strategic dialogues."
  },
  {
    "start": 231.02,
    "end": 231.5,
    "text": "I like that."
  },
  {
    "start": 231.58,
    "end": 233.48,
    "text": "So it's not about showing a gaunt chart."
  },
  {
    "start": 233.9,
    "end": 236.98,
    "text": "No, it's about forcing the hard uncomfortable questions."
  },
  {
    "start": 237.36,
    "end": 241.58,
    "text": "The kind of questions that separate the companies that will last from the ones that, you know, won't."
  },
  {
    "start": 242.48,
    "end": 244.48,
    "text": "She suggested this customer trust audit."
  },
  {
    "start": 244.78,
    "end": 245.0,
    "text": "Right."
  },
  {
    "start": 245.24,
    "end": 249.1,
    "text": "Asking what single product failure would destroy customer trust overnight?"
  },
  {
    "start": 250.22,
    "end": 253.1,
    "text": "A question like that just cuts through all the tactical noise."
  },
  {
    "start": 253.24,
    "end": 253.34,
    "text": "Yeah."
  },
  {
    "start": 253.44,
    "end": 256.82,
    "text": "It forces everyone to focus on fundamental value and risk."
  },
  {
    "start": 257.32,
    "end": 261.56,
    "text": "And that focus is what leads to the organizational blueprint, right?"
  },
  {
    "start": 261.899,
    "end": 270.46,
    "text": "I saw Joachim Torres, a joker, he noted that when we talk about product culture and the product operating model, we're really talking about the same thing."
  },
  {
    "start": 270.58,
    "end": 273.96,
    "text": "Yeah, essentially, it's the same critical transformation, the same mindset shift."
  },
  {
    "start": 274.04,
    "end": 276.3,
    "text": "you need to get that strategic alignment."
  },
  {
    "start": 276.68,
    "end": 277.58,
    "text": "It's a holistic view."
  },
  {
    "start": 277.94,
    "end": 278.94,
    "text": "That makes a ton of sense."
  },
  {
    "start": 279.28,
    "end": 284.78,
    "text": "The culture is the mindset and the product operating model, the POM, that's the structure that makes it real."
  },
  {
    "start": 285.04,
    "end": 288.28,
    "text": "Which is a perfect transition to our second theme, product operating models."
  },
  {
    "start": 289.26,
    "end": 292.42,
    "text": "The human and the technical challenge of making all this work."
  },
  {
    "start": 292.66,
    "end": 294.24,
    "text": "So where do we start with the POM?"
  },
  {
    "start": 294.8,
    "end": 298.22,
    "text": "Well, if we zoom out, the POM is where the strategy hits the technical reality."
  },
  {
    "start": 299.0,
    "end": 301.42,
    "text": "John Cutler might a point on this that I think is often overlooked."
  },
  {
    "start": 301.82,
    "end": 310.02,
    "text": "He said at any real scale all this talk of POM transformation and empowerment is and I'm quoting hollow propaganda without a serious focus on two things."
  },
  {
    "start": 310.18,
    "end": 311.18,
    "text": "Okay, what are they?"
  },
  {
    "start": 311.42,
    "end": 313.16,
    "text": "architecture and a platform strategy?"
  },
  {
    "start": 313.54,
    "end": 314.7,
    "text": "That's a strong statement."
  },
  {
    "start": 315.08,
    "end": 318.26,
    "text": "Why is architecture so critical to the operating model?"
  },
  {
    "start": 318.68,
    "end": 321.2,
    "text": "Because the model demands speed and autonomy."
  },
  {
    "start": 322.78,
    "end": 330.34,
    "text": "I mean, if every team trying to ship a feature gets stuck in dependency gridlock or tangle deployment pipelines or massive tech debt."
  },
  {
    "start": 330.6,
    "end": 332.48,
    "text": "Then, empowerment is just a word on a slide."
  },
  {
    "start": 332.58,
    "end": 332.66,
    "text": "It's"
  },
  {
    "start": 332.78,
    "end": 333.26,
    "text": "meaningless."
  },
  {
    "start": 333.9,
    "end": 336.04,
    "text": "The architecture has to enable independent teams."
  },
  {
    "start": 336.68,
    "end": 338.74,
    "text": "Otherwise, the POM is just a fancy deck."
  },
  {
    "start": 339.12,
    "end": 342.04,
    "text": "That really clarifies what the organization is actually creating."
  },
  {
    "start": 342.16,
    "end": 343.18,
    "text": "Luca Mahoney put it well."
  },
  {
    "start": 343.3,
    "end": 346.3,
    "text": "He said the core work product isn't just a piece of software."
  },
  {
    "start": 346.44,
    "end": 346.6,
    "text": "Right."
  },
  {
    "start": 346.72,
    "end": 348.42,
    "text": "It's the orchestration of three things."
  },
  {
    "start": 348.98,
    "end": 349.3,
    "text": "People."
  },
  {
    "start": 350.02,
    "end": 350.54,
    "text": "Process."
  },
  {
    "start": 351.02,
    "end": 351.62,
    "text": "and technology."
  },
  {
    "start": 352.04,
    "end": 356.68,
    "text": "All of it designed for maximum system performance and you know the best customer experience."
  },
  {
    "start": 357.12,
    "end": 358.3,
    "text": "The whole system is the product."
  },
  {
    "start": 358.6,
    "end": 363.34,
    "text": "Okay so the system mechanics are important but the implementation that's all human isn't it?"
  },
  {
    "start": 363.4,
    "end": 363.9,
    "text": "A hundred percent."
  },
  {
    "start": 364.22,
    "end": 371.54,
    "text": "Melissa Perry shared that POM implementations fail way less often because of bad frameworks and way more often because of poor change management."
  },
  {
    "start": 371.88,
    "end": 376.94,
    "text": "So you can have the perfect diagram on the wall, but if you haven't won over the people who have to actually live with it."
  },
  {
    "start": 377.22,
    "end": 377.36,
    "text": "It's"
  },
  {
    "start": 377.42,
    "end": 378.74,
    "text": "stalled out, exactly."
  },
  {
    "start": 379.06,
    "end": 380.76,
    "text": "Transformation is a human process."
  },
  {
    "start": 381.24,
    "end": 383.3,
    "text": "It takes influence, stakeholder management."
  },
  {
    "start": 383.52,
    "end": 384.88,
    "text": "You have to navigate the politics."
  },
  {
    "start": 385.1,
    "end": 388.16,
    "text": "I saw a post from Kasim Harani about that, the politics of it."
  },
  {
    "start": 388.3,
    "end": 389.7,
    "text": "Yeah, he was very real about it."
  },
  {
    "start": 389.76,
    "end": 394.02,
    "text": "He said real world product management is knowing when to apply the framework."
  },
  {
    "start": 394.62,
    "end": 400.12,
    "text": "You know, when to say no, and when you just have to say yes to a high-ranking stakeholder, the hippo."
  },
  {
    "start": 400.44,
    "end": 402.0,
    "text": "The highest-paid person's opinion."
  },
  {
    "start": 403.04,
    "end": 405.4,
    "text": "Sometimes that yes is a necessary political move."
  },
  {
    "start": 405.78,
    "end": 407.58,
    "text": "It buys you the capital for the long term."
  },
  {
    "start": 408.02,
    "end": 415.26,
    "text": "It's a tricky balance that one strategic yes on a less-than-ideal request could buy you a dozen strategic no's down the line."
  },
  {
    "start": 415.86,
    "end": 416.84,
    "text": "It's all about judgment."
  },
  {
    "start": 417.2,
    "end": 417.52,
    "text": "It is."
  },
  {
    "start": 418.04,
    "end": 422.34,
    "text": "And speaking of judgment, the POM has to be designed to handle different kinds of demand."
  },
  {
    "start": 423.0,
    "end": 427.96,
    "text": "Shrathikalapu made a great point about needing two distinct intake pathways as you scale."
  },
  {
    "start": 428.14,
    "end": 429.34,
    "text": "A dual intake model."
  },
  {
    "start": 429.6,
    "end": 430.32,
    "text": "Tell me more about that."
  },
  {
    "start": 430.4,
    "end": 432.3,
    "text": "Sounds like a practical way to balance everything."
  },
  {
    "start": 432.5,
    "end": 432.66,
    "text": "Think"
  },
  {
    "start": 432.7,
    "end": 433.52,
    "text": "of it like a hospital."
  },
  {
    "start": 433.78,
    "end": 436.68,
    "text": "You need your scheduled surgeries, but you also need a functioning ER."
  },
  {
    "start": 437.18,
    "end": 438.88,
    "text": "Path one is the product engine."
  },
  {
    "start": 439.36,
    "end": 442.44,
    "text": "It's systematic, evidence-led, driving the core roadmap."
  },
  {
    "start": 442.76,
    "end": 443.3,
    "text": "And path two."
  },
  {
    "start": 443.72,
    "end": 446.2,
    "text": "Path two is for strategic and urgent demand."
  },
  {
    "start": 446.76,
    "end": 452.64,
    "text": "This handles the time sensitive, off the politically charged request from the CEO, or from sales, or finance."
  },
  {
    "start": 452.98,
    "end": 456.68,
    "text": "And the trick isn't just having the two paths, but managing in the flow, I assume."
  },
  {
    "start": 456.88,
    "end": 457.4,
    "text": "That's the key."
  },
  {
    "start": 458.06,
    "end": 459.62,
    "text": "You have to process paths too quickly."
  },
  {
    "start": 460.22,
    "end": 463.82,
    "text": "We're talking rapid assessment cycles, like two to five days, not two months."
  },
  {
    "start": 464.3,
    "end": 465.66,
    "text": "And you offer smart options."
  },
  {
    "start": 466.06,
    "end": 466.38,
    "text": "Like what?"
  },
  {
    "start": 466.6,
    "end": 469.96,
    "text": "Like we can't build that full feature right now, but we can run a pilot."
  },
  {
    "start": 470.5,
    "end": 473.22,
    "text": "Or here's a third-party tool we can use as a shortcut."
  },
  {
    "start": 473.92,
    "end": 477.32,
    "text": "It protects the main roadmap while still respecting that real urgency."
  },
  {
    "start": 477.92,
    "end": 479.96,
    "text": "It requires PMs who are commercially fluent."
  },
  {
    "start": 480.14,
    "end": 485.04,
    "text": "That ability to triage and find alternatives is a perfect bridge to our third theme."
  },
  {
    "start": 485.5,
    "end": 488.88,
    "text": "Customer discovery, evidence, and just building the right thing."
  },
  {
    "start": 489.06,
    "end": 493.48,
    "text": "Because no matter how great your POM is, if you're building the wrong product, the whole thing fails."
  },
  {
    "start": 493.54,
    "end": 493.68,
    "text": "Yeah,"
  },
  {
    "start": 493.88,
    "end": 497.26,
    "text": "Peter Drucker's quote, which Kimmy O'Doreen shared again recently, it still holds up."
  },
  {
    "start": 497.84,
    "end": 501.54,
    "text": "Solving the right customer problem is so much more important than building the product right."
  },
  {
    "start": 501.82,
    "end": 508.58,
    "text": "It all comes down to speed to learn, iterating until your customers make it painfully obvious that you've finally nailed it."
  },
  {
    "start": 509.02,
    "end": 510.76,
    "text": "But that speed is also a trap, right?"
  },
  {
    "start": 510.88,
    "end": 513.74,
    "text": "Especially now, with AI making everything faster."
  },
  {
    "start": 514.039,
    "end": 517.32,
    "text": "Well, Anna Pintar put out a clear warning about this."
  },
  {
    "start": 518.02,
    "end": 523.34,
    "text": "AI makes prototyping incredibly fast, but that velocity can be really deceptive."
  },
  {
    "start": 523.98,
    "end": 526.14,
    "text": "A polished, validated prototype."
  },
  {
    "start": 526.64,
    "end": 527.62,
    "text": "It's not proof of demand."
  },
  {
    "start": 527.76,
    "end": 529.22,
    "text": "It just proves people liked what they saw."
  },
  {
    "start": 529.36,
    "end": 529.82,
    "text": "Exactly."
  },
  {
    "start": 530.22,
    "end": 531.9,
    "text": "It doesn't prove they'll change their behavior."
  },
  {
    "start": 532.5,
    "end": 535.2,
    "text": "Or, more importantly, that they will pay for it."
  },
  {
    "start": 536.04,
    "end": 537.58,
    "text": "Her example was so good."
  },
  {
    "start": 537.92,
    "end": 542.28,
    "text": "The one about the product with four hundred registered users, but only fifteen who are actually paying."
  },
  {
    "start": 542.54,
    "end": 543.08,
    "text": "That's the one."
  },
  {
    "start": 543.6,
    "end": 547.56,
    "text": "That tells you there's a massive gap between interest and realized value."
  },
  {
    "start": 547.82,
    "end": 550.4,
    "text": "And to close that gap, you have to do real detective work."
  },
  {
    "start": 550.52,
    "end": 552.78,
    "text": "You can't just listen to the fifteen people who converted."
  },
  {
    "start": 552.94,
    "end": 553.0,
    "text": "No."
  },
  {
    "start": 553.48,
    "end": 554.36,
    "text": "You have to talk to both."
  },
  {
    "start": 554.74,
    "end": 556.3,
    "text": "The converters and the non-converters."
  },
  {
    "start": 556.72,
    "end": 562.54,
    "text": "That's how you isolate the pattern, figure out who the product is really for and what's stopping the other three hundred and eighty-five people."
  },
  {
    "start": 563.0,
    "end": 564.42,
    "text": "That's modern product discovery."
  },
  {
    "start": 564.78,
    "end": 570.88,
    "text": "So if discovery needs to be this continuous thing, how do the best companies actually institutionalize it?"
  },
  {
    "start": 571.56,
    "end": 573.34,
    "text": "How do you make it part of the daily rhythm?"
  },
  {
    "start": 574.16,
    "end": 576.9,
    "text": "Chantelbatana's analysis of whys was a great example."
  },
  {
    "start": 577.26,
    "end": 582.1,
    "text": "They basically engineered a culture where empathy plus evidence isn't a poster."
  },
  {
    "start": 582.78,
    "end": 584.02,
    "text": "It's infrastructure."
  },
  {
    "start": 584.38,
    "end": 587.0,
    "text": "So discovery isn't just a phase at the beginning."
  },
  {
    "start": 587.32,
    "end": 590.14,
    "text": "No, it runs in parallel with delivery from day one."
  },
  {
    "start": 590.74,
    "end": 592.24,
    "text": "They do a couple of things to make that happen."
  },
  {
    "start": 592.68,
    "end": 596.48,
    "text": "They embed design researchers to continuously test hypotheses."
  },
  {
    "start": 597.06,
    "end": 601.14,
    "text": "And critically, they have product compliance partners co-designing from the start."
  },
  {
    "start": 601.66,
    "end": 605.92,
    "text": "So you know if an idea is safe and shippable before it even gets to the engineering backlog."
  },
  {
    "start": 606.04,
    "end": 606.52,
    "text": "Exactly."
  },
  {
    "start": 606.74,
    "end": 608.94,
    "text": "It's continuous learning baked right into the pipeline."
  },
  {
    "start": 609.14,
    "end": 611.76,
    "text": "That continuous evidence loop feels more important than ever."
  },
  {
    "start": 611.86,
    "end": 613.22,
    "text": "as we get into our final theme."
  },
  {
    "start": 613.58,
    "end": 616.26,
    "text": "AI's impact on design and the new PM skill set."
  },
  {
    "start": 616.62,
    "end": 621.06,
    "text": "Because the speed AI brings is forcing a conversation about what quality even means anymore."
  },
  {
    "start": 621.38,
    "end": 621.64,
    "text": "It is."
  },
  {
    "start": 622.18,
    "end": 624.78,
    "text": "Richard F. voiced a concern that I think a lot of people are feeling."
  },
  {
    "start": 624.96,
    "end": 630.72,
    "text": "This AI hype cycle is leading to a market just flow with half baked kind of boring rushed products."
  },
  {
    "start": 631.06,
    "end": 632.18,
    "text": "They lack creativity."
  },
  {
    "start": 632.42,
    "end": 633.5,
    "text": "And attention to detail."
  },
  {
    "start": 634.3,
    "end": 637.2,
    "text": "That pursuit of speed is sacrificing originality."
  },
  {
    "start": 638.36,
    "end": 641.5,
    "text": "My jesuit be actually called this UX convergent evolution."
  },
  {
    "start": 641.76,
    "end": 642.58,
    "text": "I've seen that term."
  },
  {
    "start": 642.7,
    "end": 647.9,
    "text": "It's where all the interfaces start looking the same because they're all optimizing for familiarity."
  },
  {
    "start": 649.04,
    "end": 651.78,
    "text": "Which, ironically, makes them totally forgettable."
  },
  {
    "start": 652.66,
    "end": 658.92,
    "text": "But the really radical future, which Myrick Neisenbaum envisioned, is something called generative product design."
  },
  {
    "start": 659.14,
    "end": 659.7,
    "text": "Okay, what is that?"
  },
  {
    "start": 660.0,
    "end": 668.0,
    "text": "Imagine LLM that uses your brand's personality and your design system to create a hyper-personalized product view for each user."
  },
  {
    "start": 668.34,
    "end": 668.5,
    "text": "Yeah."
  },
  {
    "start": 668.6,
    "end": 668.96,
    "text": "Instantly."
  },
  {
    "start": 669.48,
    "end": 674.46,
    "text": "Based on their specific context, their needs, their history, we'd move way beyond static interfaces."
  },
  {
    "start": 674.58,
    "end": 674.84,
    "text": "Wow."
  },
  {
    "start": 675.26,
    "end": 676.38,
    "text": "That is a massive shift."
  },
  {
    "start": 676.7,
    "end": 680.46,
    "text": "But to get there, the PM's own foundation has to be rock solid."
  },
  {
    "start": 680.76,
    "end": 680.98,
    "text": "Dr."
  },
  {
    "start": 681.06,
    "end": 683.02,
    "text": "Else Vandenberg had a really powerful take on this."
  },
  {
    "start": 683.1,
    "end": 683.18,
    "text": "Oh,"
  },
  {
    "start": 683.3,
    "end": 683.68,
    "text": "I saw that."
  },
  {
    "start": 683.74,
    "end": 685.56,
    "text": "She said LMS are powerful amplifiers."
  },
  {
    "start": 685.6,
    "end": 687.14,
    "text": "They just amplify whatever you feed them."
  },
  {
    "start": 687.24,
    "end": 688.7,
    "text": "So if you feed them shallow thinking,"
  },
  {
    "start": 688.78,
    "end": 691.42,
    "text": "you get poor results just at a massive scale."
  },
  {
    "start": 691.82,
    "end": 696.44,
    "text": "You absolutely cannot skip the foundation, knowing your audience, grounding the pain points."
  },
  {
    "start": 696.84,
    "end": 699.82,
    "text": "Garbage in, garbage out just faster and bigger than ever."
  },
  {
    "start": 699.88,
    "end": 700.04,
    "text": "Pretty"
  },
  {
    "start": 700.12,
    "end": 700.3,
    "text": "much."
  },
  {
    "start": 700.82,
    "end": 702.6,
    "text": "Akash Gupta broke this down really well."
  },
  {
    "start": 703.0,
    "end": 706.96,
    "text": "He argued that successful AI PMs need expertise on three different levels."
  },
  {
    "start": 707.14,
    "end": 707.56,
    "text": "Which are?"
  },
  {
    "start": 708.0,
    "end": 711.34,
    "text": "First, the foundation so AI and ML concepts, prompt engineering."
  },
  {
    "start": 711.8,
    "end": 716.88,
    "text": "Second is the PM value layer, things like evaluation, cost optimization, choice analysis."
  },
  {
    "start": 717.36,
    "end": 718.58,
    "text": "And third is strategy."
  },
  {
    "start": 718.9,
    "end": 721.72,
    "text": "That PM value layer seems like the real differentiator."
  },
  {
    "start": 721.86,
    "end": 722.12,
    "text": "It is."
  },
  {
    "start": 722.58,
    "end": 731.8,
    "text": "The scarcest skill in AI right now is PMs who actually understand evaluation, who know how to test, iterate and figure out if the model is truly providing customer value."
  },
  {
    "start": 732.26,
    "end": 732.74,
    "text": "It's hard work."
  },
  {
    "start": 732.98,
    "end": 734.32,
    "text": "Which brings us back to judgment."
  },
  {
    "start": 734.52,
    "end": 738.3,
    "text": "If AI can do so much of the execution, what's left for the human PM?"
  },
  {
    "start": 738.8,
    "end": 740.3,
    "text": "Rochelle Valentino framed it perfectly."
  },
  {
    "start": 740.38,
    "end": 742.1,
    "text": "The question isn't, will AI replace me?"
  },
  {
    "start": 742.72,
    "end": 745.94,
    "text": "It's, how do I partner with AI to make better product decisions?"
  },
  {
    "start": 746.18,
    "end": 747.56,
    "text": "The AI is the co-pilot."
  },
  {
    "start": 747.8,
    "end": 749.0,
    "text": "But judgment is the driver."
  },
  {
    "start": 749.42,
    "end": 750.66,
    "text": "AI can cluster feedback."
  },
  {
    "start": 750.84,
    "end": 752.2,
    "text": "It can draft a spec outline."
  },
  {
    "start": 752.72,
    "end": 755.2,
    "text": "But it can't prioritize conflicting stakeholder needs."
  },
  {
    "start": 755.68,
    "end": 758.8,
    "text": "It can't read the nuance of human emotion or organizational politics."
  },
  {
    "start": 759.16,
    "end": 760.92,
    "text": "So how do you operationalize that?"
  },
  {
    "start": 761.44,
    "end": 764.28,
    "text": "How do you pair human judgment with AI speed?"
  },
  {
    "start": 764.9,
    "end": 769.3,
    "text": "Harsha Sravatsa proposed a really fascinating idea, the LLM Council."
  },
  {
    "start": 769.78,
    "end": 771.2,
    "text": "This is such a cool concept."
  },
  {
    "start": 771.4,
    "end": 774.6,
    "text": "It's basically an AI board of advisors for your product."
  },
  {
    "start": 774.86,
    "end": 782.44,
    "text": "You use different AI personas, maybe one inspired by Marty Kagan for strategy, another by Melissa Perry for discovery to review your PRD."
  },
  {
    "start": 782.82,
    "end": 785.78,
    "text": "And the Council gives you feedback before you even start sprint planning."
  },
  {
    "start": 785.86,
    "end": 786.28,
    "text": "Exactly."
  },
  {
    "start": 786.6,
    "end": 789.44,
    "text": "It synthesizes feedback, flags critical gaps."
  },
  {
    "start": 789.82,
    "end": 793.68,
    "text": "You're institutionalizing critical thinking, but using technology to do"
  },
  {
    "start": 793.8,
    "end": 793.86,
    "text": "it."
  },
  {
    "start": 794.26,
    "end": 797.46,
    "text": "That is a perfect way to think about how product management has to evolve."
  },
  {
    "start": 797.94,
    "end": 802.58,
    "text": "It's about using sophisticated tools to enhance our own strategy and judgment, not to replace it."
  },
  {
    "start": 803.08,
    "end": 805.54,
    "text": "So let's try to summarize the big shifts from the last two weeks."
  },
  {
    "start": 805.58,
    "end": 813.68,
    "text": "There's a clear mandate to pivot to outcome-based product operating models, but those have to be grounded in a robust architecture and smart intake pathways."
  },
  {
    "start": 814.2,
    "end": 820.44,
    "text": "And we learned that deep behavioral customer evidence, not just fast prototypes, is the only real cure for that dangerous feature."
  },
  {
    "start": 820.52,
    "end": 820.94,
    "text": "velocity."
  },
  {
    "start": 821.3,
    "end": 823.42,
    "text": "And finally, AI integration."
  },
  {
    "start": 824.12,
    "end": 830.14,
    "text": "It demands that we prioritize strategic judgment and evaluation skills over just, you know, technical shortcuts."
  },
  {
    "start": 830.3,
    "end": 833.14,
    "text": "And if I can add one final thought, looking at the bigger picture."
  },
  {
    "start": 834.3,
    "end": 838.06,
    "text": "The evolution of product operations is the next strategic engine here."
  },
  {
    "start": 838.2,
    "end": 838.5,
    "text": "How so?"
  },
  {
    "start": 839.28,
    "end": 842.28,
    "text": "Well, both Graham Reed and Aidan Zipor pointed this out."
  },
  {
    "start": 842.8,
    "end": 845.06,
    "text": "Product ops isn't just an admin afterthought anymore."
  },
  {
    "start": 845.72,
    "end": 849.3,
    "text": "As AI speeds up engineering and design, the bottlenecks move."
  },
  {
    "start": 849.9,
    "end": 853.64,
    "text": "They shift to organizational alignment, governance, process."
  },
  {
    "start": 853.84,
    "end": 856.48,
    "text": "The exact problems ProductOps is designed to solve."
  },
  {
    "start": 856.56,
    "end": 856.98,
    "text": "Exactly."
  },
  {
    "start": 857.14,
    "end": 860.32,
    "text": "It's becoming the central nervous system for the modern product org."
  },
  {
    "start": 860.72,
    "end": 864.72,
    "text": "It's solving the crucial problems that, before, nobody was really solving properly."
  },
  {
    "start": 864.8,
    "end": 867.42,
    "text": "If you enjoyed this episode, new episodes drop every two weeks."
  },
  {
    "start": 867.92,
    "end": 874.84,
    "text": "Also check out our other editions on ICT and tech, artificial intelligence, cloud, sustainability and green ICT, defense tech and health tech."
  },
  {
    "start": 875.3,
    "end": 876.28,
    "text": "Thanks for diving deep with us."
  },
  {
    "start": 876.32,
    "end": 877.3,
    "text": "We'll see you next time."
  }
]