Latest / Best of LinkedIn: Digital Transformation & Tech / Best of LinkedIn: Digital Products & Services CW 40/ 41

Transcript

Best of LinkedIn: Digital Products & Services CW 40/ 41 · Best of LinkedIn: Digital Transformation & Tech

• 0:00
  Speaker 0: This episode is provided by Thomas Allgaier and Frennus, based on the most relevant LinkedIn posts about digital products in services from CW-Forty and Forty One.
• 0:10
  Speaker 0: Frenness is a BDB market research company that supports enterprise product teams with building feature by future competitive intelligence That shows exactly how their product stacks up against the competition.
• 0:21
  Speaker 0: You can find more info into description
• 0:23
  Speaker 1: And you know we are so glad your joining us for this Today were doing deep dive to the absolute top Digital products and services trends that are just circulating all over LinkedIn right now.
• 0:34
  Speaker 0: Yeah, we've got a really great stack of insights to get through.
• 0:37
  Speaker 0: We're gonna be focusing on how AI is well radically changing How products are actually built?
• 0:42
  Speaker 0: Right
• 0:43
  Speaker 1: And will get into why strategy not engineering is officially the true bottleneck Now exactly
• 0:49
  Speaker 0: Plus we're going talk about how the traditional SaaS market Is facing this really existential threat from users just building their own tools, this whole DIY vibe coding thing.
• 1:00
  Speaker 1: Oh that part is wild!
• 1:02
  Speaker 1: I can't wait to unpack that for you.
• 1:03
  Speaker 0: But let's start with what feels like the most glaring contradiction in tech industry today
• 1:08
  Speaker 1: The shipping paradox.
• 1:10
  Speaker 0: Yeah...the shipping paradox.
• 1:12
  Speaker 0: Look we've literally never been faster at building and shipping software right?
• 1:15
  Speaker 1: Totally.
• 1:16
  Speaker 0: but people actually using these products as customers aren't feeling any impact of speed.
• 1:23
  Speaker 0: Akash Gupta and Antonia Landy actually highlighted this massive finding from an Atlassian survey recently.
• 1:28
  Speaker 1: Right, that Atlassians data?
• 1:29
  Speaker 1: Yeah it was
• 1:29
  Speaker 0: eye-opening.
• 1:30
  Speaker 1: That really was
• 1:32
  Speaker 0: So.
• 1:32
  Speaker 0: eighty percent of product teams say they are shipping code faster now thanks to AI
• 1:36
  Speaker 1: Which sounds amazing.
• 1:38
  Speaker 0: On paper.
• 1:38
  Speaker 0: yeah But the survey shows customers aren't seeing value any sooner.
• 1:43
  Speaker 0: It's like Well its'like.
• 1:44
  Speaker 0: we've given everyone a much faster car but nobody bothered.
• 1:47
  Speaker 0: check if we Actually have
• 1:48
  Speaker 1: map.
• 1:49
  Speaker 1: That is exactly issue.
• 1:52
  Speaker 1: The underlying mechanism there is all about where the bottleneck moved, right?
• 1:57
  Speaker 1: Because I mean the coding got faster Generating.
• 2:00
  Speaker 1: The documentation got faster but the human decision-making process that didn't speed up one bit.
• 2:06
  Speaker 0: now You can really automate the deciding
• 2:08
  Speaker 1: part exactly.
• 2:09
  Speaker 1: the same survey noted That sixty nine percent of people say decision making Is just as slow as it was before generative AI.
• 2:19
  Speaker 1: Wow and we're at a point where AI adoption virtually universal, like ninety-nine percent say it's fully integrated into their workflows.
• 2:27
  Speaker 1: But because these tools blur the lines between disciplines so much, sixty seven percent of people can no longer clearly define their own job
• 2:35
  Speaker 1: responsibilities.".
• 2:35
  Speaker 1: That
• 2:35
  Speaker 0: is wild!
• 2:36
  Speaker 0: So you have designers doing front end engineering work and engineers are suddenly drafting product specs?
• 2:42
  Speaker 0: It just turns in to a disorganized free for all if you aren't careful.
• 2:45
  Speaker 1: It really does... And Richard Alexander Bautista proposed a really critical rule for this exact scenario, he said.
• 2:52
  Speaker 1: teams have to stop measuring AI features and they need to start measuring workflow changes.
• 2:57
  Speaker 0: Because the feature isn't an outcome?
• 2:58
  Speaker 1: Exactly!
• 2:59
  Speaker 1: Just slapping in AI-powered label on textbox that doesn't mean you've solved anything
• 3:06
  Speaker 0: Right.
• 3:06
  Speaker 0: Like, if a customer support team takes twenty minutes to handle the standard ticket and you build an AI draft generator for them...
• 3:13
  Speaker 1: You think you've innovated?
• 3:14
  Speaker 1: Yeah!
• 3:15
  Speaker 0: ...you're a hero.
• 3:15
  Speaker 0: but If the agent still has to spend eighteen minutes reviewing fact-checking And rewriting that draft because it hallucinated policy details....
• 3:23
  Speaker 1: You haven't changed at work flow at all
• 3:25
  Speaker 0: No..You just hit an arbitrary engineering milestone.
• 3:29
  Speaker 0: It only becomes actual business outcome if entire ticket process drops from twenty minutes down to say seven minutes.
• 3:35
  Speaker 1: And when you focus on those workflow changes, it forces a complete restructuring of how product teams operate.
• 3:42
  Speaker 1: Like Markiewicz-Giedus brought up this structural shift happening at Coinbase...
• 3:45
  Speaker 0: Oh yeah the pods!
• 3:46
  Speaker 1: Right they reorganized around what they call AI native pods and some of these pods are literally just one human being
• 3:53
  Speaker 0: One person?
• 3:54
  Speaker 1: One person acting as the central orchestrator.
• 3:57
  Speaker 1: They handle the engineering The design The product management All by using various AI agents to execute the
• 4:02
  Speaker 0: tasks.
• 4:04
  Speaker 0: I mean Having one person orchestrate the entire life cycle sounds incredibly efficient on the surface.
• 4:10
  Speaker 1: But
• 4:11
  Speaker 0: but I have to ask if one person can now do the job of five using AI Doesn't that inherently make the product really fragile?
• 4:20
  Speaker 1: How so well
• 4:22
  Speaker 0: a solitary builder might lack The scar tissue right like the past industry experience.
• 4:27
  Speaker 0: To know why is specific compliance field needs to be on a checkout screen.
• 4:32
  Speaker 0: aren't we Just risking building really polished mistakes at high speed?
• 4:36
  Speaker 1: That is the core vulnerability, hands down.
• 4:38
  Speaker 1: And Gaidus actually issued a warning about this exact dynamic.
• 4:41
  Speaker 1: He did Yeah he noted that AI dramatically compresses exploration speed.
• 4:46
  Speaker 1: You know you can ask an agent to generate ten different versions of a UI in seconds But AI does not compress judgment.
• 4:54
  Speaker 1: Ah The model doesn't know about the regulatory audit.
• 4:56
  Speaker 1: your company failed three years ago, which is literally the only reason that specific annoying compliance field exists.
• 5:03
  Speaker 0: It's the difference between doing something fast and doing the right thing?
• 5:08
  Speaker 1: Exactly!
• 5:09
  Speaker 1: Adi Thacker framed this beautifully using a mathematical concept.
• 5:13
  Speaker 1: he said product management is a vector not a scalar.
• 5:16
  Speaker 0: Okay unpacked it
• 5:17
  Speaker 1: So A Scalar Is Just A Measurement Of Magnitude Right Raw Speed But a vector is magnitude plus direction.
• 5:24
  Speaker 1: Oh, I like that!
• 5:25
  Speaker 1: Yeah Patrick Mack echoed this too.
• 5:27
  Speaker 1: he pointed out because building isn't incredibly cheap.
• 5:30
  Speaker 1: now deciding what to build has become incredibly expensive.
• 5:33
  Speaker 0: Right Because marching in the wrong direction at light speed just means you're wasting resources faster than ever.
• 5:39
  Speaker 1: Exactly
• 5:41
  Speaker 0: So look if Direction and Judgment are our real bottlenecks.
• 5:45
  Speaker 0: Now then figuring Out What To Build Like The Whole Product Discovery Phase.
• 5:51
  Speaker 0: That has to be the most critical part of operation.
• 5:53
  Speaker 1: Unquestionably!
• 5:54
  Speaker 0: But ironically, teams are trying to automate that too?
• 5:57
  Speaker 0: Oh yeah.
• 5:58
  Speaker 1: Aiden Zayapur shared a stat from a listener survey that really highlights how far this is gone.
• 6:03
  Speaker 1: Currently, ninety-four percent of product pros use AI in their research workflows.
• 6:07
  Speaker 0: Okay...that makes sense.
• 6:08
  Speaker 1: but The alarming part Twenty percent of them actually rely on AI overdoing their own original research.
• 6:15
  Speaker 0: Wait
• 6:15
  Speaker 0: Really?!
• 6:15
  Speaker 1: Yes They're having models summarize old data or simulate user personas instead you know, actually talking to human beings.
• 6:24
  Speaker 0: So they're just feeding like a hundred old user interview transcripts into an LLM and asking for the top five themes?
• 6:31
  Speaker 1: Essentially yeah!
• 6:32
  Speaker 1: And the danger there is how these large language models are mathematically designed.
• 6:37
  Speaker 1: They are fundamentally probability engines.
• 6:40
  Speaker 1: Their whole function is predict most likely average answer based on patterns.
• 6:45
  Speaker 1: so by design smooth over contradictions wash out anomalous edge cases.
• 6:50
  Speaker 0: But those edge cases are where the gold is.
• 6:53
  Speaker 0: I mean, if one user out of a hundred's using your software in completely weird unorthodox way that anomaly is usually when big innovation is hiding
• 7:02
  Speaker 1: Exactly Which perfectly aligns with what Christian Idiotti and Teresa Torres were arguing.
• 7:07
  Speaker 0: What do they say?
• 7:09
  Speaker 1: They noted that.
• 7:10
  Speaker 1: look AI is fantastic for preparing for interviews or synthesizing raw notes afterward.
• 7:16
  Speaker 1: Sure
• 7:16
  Speaker 0: admin stuff,
• 7:17
  Speaker 1: but if you let it replace the actual customer conversation You aren't doing better discovery.
• 7:22
  Speaker 1: You are just guessing faster.
• 7:25
  Speaker 0: guessing faster That's a great line
• 7:26
  Speaker 1: It is.
• 7:27
  Speaker 1: they point out that AI raises the floor for novices.
• 7:31
  Speaker 1: So a beginner can write a decent interview script now But it raises the ceiling for experts Because the true advantage isn't having a tool.
• 7:40
  Speaker 1: It's having judgment to know what good looks like and knowing when model is missing nuance.
• 7:45
  Speaker 0: That makes total sense.
• 7:47
  Speaker 0: And Ed Biden actually suggested really practical framework for managing this balance.
• 7:51
  Speaker 1: The discovery budget.
• 7:53
  Speaker 1: Yeah,
• 7:53
  Speaker 0: treating product discovery like financial budget sized entirely by risk.
• 7:58
  Speaker 1: Right I love that approach.
• 8:00
  Speaker 1: How does he structure it?
• 8:01
  Speaker 0: You allocate your research effort based on consequence of being wrong.
• 8:05
  Speaker 0: So, if you're just adding a new date filter to the search page.
• 8:09
  Speaker 1: Low risk
• 8:10
  Speaker 0: Super low-risk The risk of failure is basically zero so it gets tiny discovery budget.
• 8:15
  Speaker 0: maybe few days of cheap validation like running fake door test.
• 8:19
  Speaker 1: Where are we put up button for feature that doesn't exist yet?
• 8:22
  Speaker 1: Just see how many users try.
• 8:24
  Speaker 1: click it
• 8:24
  Speaker 0: Exactly.
• 8:25
  Speaker 0: See there's intent before build it.
• 8:27
  Speaker 0: Low risk and low budget But proposing an entirely freemium tier That changes whole revenue model
• 8:34
  Speaker 1: Oh, that's huge.
• 8:35
  Speaker 0: Right?
• 8:35
  Speaker 0: The risk of getting that wrong could literally be fatal to the business.
• 8:39
  Speaker 0: so... That requires a massive budget!
• 8:41
  Speaker 0: Weeks of deep qualitative human-led discovery.
• 8:45
  Speaker 1: That makes perfect sense.
• 8:46
  Speaker 0: And by the way if you are enjoying how we impact these frameworks make sure you subscribe So you catch our future deep dives.
• 8:52
  Speaker 0: We do this every two weeks.
• 8:53
  Speaker 1: Definitely subscribe
• 8:54
  Speaker 0: But okay let me play devil's advocate on this budget framework for a second.
• 8:58
  Speaker 0: Go
• 8:58
  Speaker 1: for it.
• 8:58
  Speaker 0: If I strictly budget my discovery based on what already feels risky Aren't I just guaranteeing that i'll only ever find safe incremental improvements?
• 9:08
  Speaker 0: Like, how do you ever stumble into a massive unexpected aha moment if You Only aggressively research the things.
• 9:15
  Speaker 0: You already know are dangerous?
• 9:16
  Speaker 1: That is A really sharp question and it points to a much deeper issue with How companies manage ideas once they're actually generated.
• 9:24
  Speaker 1: The
• 9:24
  Speaker 0: roadmap problem
• 9:25
  Speaker 1: exactly.
• 9:26
  Speaker 1: Steven Grenise and Helene Amster-Cople both touched on the systemic failure of roadmaps.
• 9:32
  Speaker 1: Grenise noted that roadmps generally fail through a process of addition without subtraction.
• 9:37
  Speaker 0: Oh, man!
• 9:38
  Speaker 0: The backlog only ever grows and never shrinks.
• 9:41
  Speaker 0: we've all been there
• 9:42
  Speaker 1: We ALL have.
• 9:43
  Speaker 1: An executive request comes down BAM Added to the queue A competitor launches something flashy BAM A reactionary feature gets added
• 9:51
  Speaker 0: And nothing get's removed.
• 9:52
  Speaker 1: Right...and six months later The engineering team has twelve different initiatives in progress, all sitting at eighty percent completion delivering absolutely zero value to the end user.
• 10:02
  Speaker 0: It's exhausting!
• 10:04
  Speaker 1: And Cople adds a really harsh truth for founders in this situation... They often assume they need to hire a product manager to organize that chaotic backlog
• 10:13
  Speaker 0: but they don't
• 10:14
  Speaker 1: know what they actually need.
• 10:15
  Speaker 1: as a Product Strategist who has the authority to look them in the eye and tell then their pet ideas simply isn't good?
• 10:22
  Speaker 1: Wow yeah Because the most expensive mistake a company can make isn't building the wrong feature.
• 10:28
  Speaker 1: It's building the right product with peak
• 10:30
  Speaker 1: efficiency.".
• 10:31
  Speaker 1: That
• 10:31
  Speaker 0: is so true, and while Discovery supposed to dictate what we build AI making how?
• 10:37
  Speaker 0: So radically accessible that traditional SaaS companies are suddenly waking up to find they're competing against their own customers.
• 10:43
  Speaker 1: The DIY software trend.
• 10:45
  Speaker 1: Yeah
• 10:45
  Speaker 0: this is crazy.
• 10:46
  Speaker 0: going back to that story from Ashish Patel his team was hit with a five X price hike from their time-tracking software vendor.
• 10:54
  Speaker 1: A five hundred percent increase!
• 10:56
  Speaker 0: Insane, right?
• 10:58
  Speaker 0: So instead of paying it or enduring this brutal migration process to a competitor they just built it themselves.
• 11:04
  Speaker 0: over
• 11:04
  Speaker 1: a single weekend... ...a weekend
• 11:07
  Speaker 0: They fed the AI that previous vendors API specs had generate the front end components to clone the UI and Just hooked up there own database.
• 11:15
  Speaker 1: It's incredible.
• 11:17
  Speaker 0: After a week of minor bug fixing, they processed an entire month's worth of invoicing on their own homegrown tool without a single issue.
• 11:23
  Speaker 1: And what is really fascinating in the catalyst driving this behavior?
• 11:27
  Speaker 1: Todd Orchard and Dan London pointed out that SaaS vendors are frequently there own worst enemies here.
• 11:32
  Speaker 0: How so
• 11:33
  Speaker 1: They push users away with restrictive API rate limits or pad free tiers for useless vanity features while locking core necessary functionality behind massive enterprise paywalls.
• 11:45
  Speaker 0: Yeah, the payable fatigue is real.
• 11:47
  Speaker 1: It is!
• 11:48
  Speaker 1: Users are exhausted from constantly adapting their daily workflows to fit the rigid constraints of a vendor's product.
• 11:54
  Speaker 1: so they turn to models like Claude and start vibe coding their own bespoke tools.
• 11:59
  Speaker 0: Okay I have to ask about this Vibe Coding.
• 12:03
  Speaker 0: Isn't it just the twenty-twenty six version of The Office Excel Macro?
• 12:07
  Speaker 1: What do you mean?
• 12:09
  Speaker 1: Well
• 12:09
  Speaker 0: You know, we all remember Kevin in accounting who built a brilliant automated spreadsheet and an afternoon saved everyone hours of work.
• 12:15
  Speaker 1: Oh yeah
• 12:16
  Speaker 0: But three years later kevin leaves the company The macro breaks And the entire accounting department is paralyzed because they're stuck with an unmaintainable mess.
• 12:24
  Speaker 0: Isn't weekend AIF just more complicated excel macro?
• 12:28
  Speaker 1: It's a very fair comparison, but it misses a crucial evolution in the technology.
• 12:33
  Speaker 1: The fundamental difference between Kevin's macro and todays' agentic systems is that modern AI can be prompted to entirely self-documenting and self testing.
• 12:43
  Speaker 1: When Kevin left his logic was mystery.
• 12:46
  Speaker 1: Today an AIA agent could read the custom application write comprehensive documentation explaining its own architecture, generate testing environments and seamlessly explain the logic to the next Kevin who takes over.
• 12:59
  Speaker 0: Okay so the knowledge transfer is automated too?
• 13:01
  Speaker 1: Exactly though you are absolutely right that the core organizational challenge like deciding who actually owns and maintains this shadow IT when it inevitably needs a security update... That remains unsolved!
• 13:16
  Speaker 0: Right And Steve Brayden actually connected this exact dynamic to the plummeting valuations we're seeing across the SaaS market.
• 13:22
  Speaker 1: Yes, The technical debt issue?
• 13:25
  Speaker 0: Yeah if you look at a mature legacy SaaS product it is usually just bogged down by A decade of technical debt Abandoned integrations Labyrinthian code paths.
• 13:36
  Speaker 1: It becomes so bloated
• 13:37
  Speaker 0: and buyers Look at a platform that takes a year To ship a meaningful update?
• 13:42
  Speaker 0: They refuse to pay premium for especially when they know an AI agent can replicate the tiny, highly efficient core of that software and just ignore all the legacy bloat.
• 13:52
  Speaker 1: Vic Gumbier highlighted the massive cognitive dissonance happening in the market regarding this too.
• 13:57
  Speaker 0: but what did he say?
• 13:59
  Speaker 1: He noted there are business leaders who fully believe AI is capable of automating entire sales department right
• 14:05
  Speaker 0: sure prospecting outreach booking meetings
• 14:07
  Speaker 1: exactly all autonomously.
• 14:09
  Speaker 1: Yet, those same leaders somehow doubt that AI is capable of writing the code for the SaaS product... ...that the sales team was selling.
• 14:17
  Speaker 0: That's a brilliant observation!
• 14:18
  Speaker 1: Why The Blind Spot?
• 14:20
  Speaker 0: It just lags in perception.
• 14:22
  Speaker 1: Meanwhile, the open-source community has already filling this gap.
• 14:25
  Speaker 1: So Hedthiab recently launched an Open Source tool called Product Mode….
• 14:29
  Speaker 1: …that hit over two hundred stars on GitHub almost instantly.
• 14:32
  Speaker 1: What does it do?
• 14:33
  Speaker 1: It literally embeds product management judgment directly into the coding agent.
• 14:38
  Speaker 0: Wait how
• 14:39
  Speaker 1: Before the AI is allowed to write a single line of code, this system forces it to challenge users' assumptions.
• 14:45
  Speaker 1: It actively cuts unnecessary scope and defines clear success metrics.
• 14:48
  Speaker 1: It's trying to automate judgment not just typing.
• 14:51
  Speaker 1: Wow!
• 14:52
  Speaker 0: Automating pushback?
• 14:54
  Speaker 0: That really smart!
• 14:56
  Speaker 0: Which brings us into the ultimate question for enterprise teams If anyone can spin up functional app in weekend.
• 15:03
  Speaker 0: The underlying tech is no longer a defensible moat.
• 15:06
  Speaker 0: So how do companies win in this new environment.
• 15:10
  Speaker 0: It seems like it all comes down to flawless execution, rapid activation and aggressively removing friction.
• 15:17
  Speaker 1: Absolutely!
• 15:18
  Speaker 1: Jalila Solomon highlighted a perfect example of this with the recent update on the Dashin Super App.
• 15:23
  Speaker 1: Oh
• 15:24
  Speaker 0: I saw that.
• 15:24
  Speaker 0: Yeah
• 15:25
  Speaker 1: instead forcing users through multi-step authentication process just make payment.
• 15:29
  Speaker 1: The app was updated so user can simply open it scan merchant code and pay immediately without even logging first.
• 15:36
  Speaker 0: That is smooth
• 15:37
  Speaker 1: It is.
• 15:38
  Speaker 1: Can we make the user do less, as a new competitive advantage?
• 15:42
  Speaker 0: Because failure points in software are rarely these massive dramatic crashes anymore.
• 15:48
  Speaker 0: As Atiku O'Rachaman noted User activation usually fails into tiny silent moments of friction.
• 15:53
  Speaker 1: Yes Like a dashboard that loads completely blank for a new user
• 15:57
  Speaker 0: Or mandatory setup form that asks three pieces of info instead just two
• 16:01
  Speaker 1: Exactly.
• 16:03
  Speaker 1: And Gouzi Chukua, Julie Uso-Chuku built on this.
• 16:07
  Speaker 1: She warned teams that their internal metrics are often deceiving them.
• 16:10
  Speaker 0: How so?
• 16:11
  Speaker 1: Well marketing teams will celebrate a sky high click through rate on new campaign.
• 16:15
  Speaker 1: right sure but if the product team isn't tracking the full conversion journey all the way down to actual meaningful account activation then Click means absolutely nothing.
• 16:26
  Speaker 0: Capturing attention is useless If The Product Fiction prevents you from monetizing it
• 16:30
  Speaker 1: Precisely.
• 16:31
  Speaker 1: And monetizing that attention requires a really deep understanding of user behavior.
• 16:36
  Speaker 1: Bushret Choskunar analyzed how Doodle one-to-one mapped their pricing models to the classic pirate metrics.
• 16:43
  Speaker 0: Remind me, That's the AAARR framework right?
• 16:46
  Speaker 1: Right!
• 16:47
  Speaker 1: Acquisition activation retention referral and revenue Got it.
• 16:51
  Speaker 0: So How does that apply to pricing?
• 16:53
  Speaker 1: Well When you offer a freemium model, You are fundamentally delaying the revenue stage because you aren't charging up front.
• 17:00
  Speaker 1: You put massive intense pressure specifically on retention.
• 17:04
  Speaker 0: Oh that makes sense.
• 17:05
  Speaker 0: Because they have to keep coming back
• 17:06
  Speaker 1: Exactly.
• 17:07
  Speaker 1: The product has to consistently prove its value drawing them back in day after day until They finally hit usage wall or realize they need premium features enough To pull out of credit card.
• 17:17
  Speaker 1: If your product doesn't naturally drive high retention A freemia model will bankrupt you.
• 17:22
  Speaker 0: Wow And getting users excited and engaged from day one is critical for that retention.
• 17:28
  Speaker 0: A tier Abdul Rauf analyzed over two hundred product launch posts on LinkedIn to identify what actually drives initial momentum,
• 17:35
  Speaker 1: What did the data show?
• 17:37
  Speaker 0: Two very clear practical rules.
• 17:39
  Speaker 1: first
• 17:40
  Speaker 0: give your new product or feature a specific name.
• 17:43
  Speaker 0: interesting yeah.
• 17:44
  Speaker 0: vaguely announcing an update performs terribly.
• 17:49
  Speaker 0: Naming it earns one point nine times more reposts because people want a concrete noun they can talk about and share.
• 17:55
  Speaker 1: Right, makes the tangible
• 17:56
  Speaker 0: exactly.
• 17:57
  Speaker 0: Second rule if you use of video The first three seconds dictate everything.
• 18:03
  Speaker 0: You have to skip the corporate throat clearing in this low logo fades And just immediately show the product solving problem.
• 18:10
  Speaker 1: That's great tactical advice.
• 18:12
  Speaker 1: But, you know as teams hyper focus on these micro interactions and distribute their work across smaller AI pods a major operational vulnerability emerges.
• 18:22
  Speaker 1: What's that?
• 18:23
  Speaker 1: Matthew Small pointed out that in the transition away from monolithic structures to this highly distributed autonomous teams organizations have lost horizontal visibility.
• 18:33
  Speaker 0: Ah!
• 18:33
  Speaker 0: The cross-team connection ensuring the entire product actually makes sense.
• 18:40
  Speaker 1: Small proposes that organizations need to introduce a service owner role, To sit directly alongside the traditional product owner.
• 18:48
  Speaker 0: Okay how do they differ?
• 18:50
  Speaker 1: While the Product Owner is focused on creating new value through localized changes The Service Owner is responsible for protecting That Value across the entire end-to-end customer journey.
• 18:59
  Speaker 1: They connect the dots when a user's workflow breaks because it has to cross Through six different AI pods
• 19:05
  Speaker 0: And Ravi Metta approached this from an org design perspective too right.
• 19:09
  Speaker 0: Yes He noted that while the formal title of product manager might disappear in some these highly automated companies, The actual work-of-product management remains absolutely mandatory.
• 19:20
  Speaker 1: The tasks don't go away?
• 19:21
  Speaker 0: Exactly understanding the customer's needs Setting a cohesive strategy connecting technical outputs to business outcomes.
• 19:28
  Speaker 0: You can distribute those tasks among different people but you cannot eliminate them.
• 19:32
  Speaker 1: But wait let me ask you something.
• 19:34
  Speaker 1: If we are fragmenting the PM role into these highly autonomous one-person AI pods to gain speed.
• 19:40
  Speaker 1: But then, we suddenly realize things are disjointed.
• 19:43
  Speaker 1: so we introduce service owners to sit above them and stitch the journey back together.
• 19:48
  Speaker 1: Haven't we just reinvented corporate middle management bureaucracy under a shiny new name?
• 19:53
  Speaker 0: You know it is classic pendulum swing of organizational design.
• 19:56
  Speaker 1: It really is.
• 19:57
  Speaker 0: We rapidly decentralized everything because wanted the sheer speed that AI agents offer.
• 20:02
  Speaker 0: Now the friction of a disjointed user experience is forcing us to realize we need to re-centralize slightly To maintain coherence.
• 20:09
  Speaker 1: Yeah, We have to find the middle ground.
• 20:11
  Speaker 0: The companies that ultimately dominate this next era software are gonna be the ones That figure out how to perfectly balance the raw Scalable speed of agentic systems with the cohesive contextual judgment Of human strategy.
• 20:24
  Speaker 1: Beautifully said you've got the fast cars now?
• 20:26
  Speaker 1: We just have to figure out How to draw them up
• 20:29
  Speaker 0: exactly.
• 20:30
  Speaker 0: well thanks for joining Us on This deep dive.
• 20:32
  Speaker 0: If you enjoy this episode, new episodes drop every two weeks.
• 20:35
  Speaker 0: Also check out our other editions on Cloud Insights and Sovereignty, ICT & Tech Insights, AI in Agents Systems, Sustainability in Green ICT, DefenseTech and HealthTech.
• 20:47
  Speaker 1: And we will leave with one final thought to mull over drawing some provocative ideas shared by Venkatesh Krishnan and Cameron Tonkinways.
• 20:55
  Speaker 1: Look, if AI systems can eventually synthesize the collective history of a product's entire life cycle cataloging every past decision Every abandoned prototype.
• 21:05
  Speaker 1: Every regulatory mistake and every strategic pivot into queryable wisdom Are we moving toward a future where accompanies most valuable asset isn't its source code or even it's active user base but its institutional memory?
• 21:20
  Speaker 1: Because everyone has access to the fastest car in the world The only thing that truly gives you an advantage is remembering exactly where you've already crashed.