Innovation and the Digital Enterprise · 2025-10-02 · 13 min
Key moments - from our scoring
Substance score
52 / 100
Five dimensions, 20 points each
Patrick Emmons curates a collection of perspectives on digital transformation from over a dozen industry leaders, framing change as fundamentally a people and process challenge enabled by - not driven by - technology. Andrei Gorenkov argues that digital transformation is only 50% technology; the rest involves changing job descriptions, operating models, and revenue models through enterprise change management. Christopher Paquette introduces the protect-and-disrupt framework: protecting core business value while disrupting the ecosystem to create new products and revenue streams. Ann Young highlights how corporate functions (HR, Finance, Ops) face the hardest transformation burden but get overlooked because they don't directly produce revenue. Sandy Castro emphasizes diversity as the engine of invention, while Deepak Kamal reframes AI adoption from 'where can we use Gen AI' to 'what unsolvable problems can we now solve.' Gene Kim's closing argument - echoed throughout - points to organizational wiring (layer three: norms, rituals, processes, architecture) as the true differentiator, not tools or people alone. Contributors like Jeff Miller stress listening, Tanya Hannah demand organizational agility, and Subramanian Kunchitha Patham warn that technology moves faster than training, leaving teams behind. This is essential listening for technology leaders navigating enterprise-scale transformation who underestimate the organizational redesign required.
Because technology is only 50% or less of the work; the other half involves changing job descriptions, operating models, revenue models, and getting people to behave differently, which requires enterprise change management that technology leaders often neglect.
The protect-and-disrupt framework: protect the core of the business and how you create value, while disrupting the ecosystem through new products, services, and revenue models to create comprehensive value for customers.
Layer three is the organizational wiring - norms, rituals, processes, and software architecture that dictate who talks to whom about what and when; it's the difference maker in transformation success because even with the same people (layer one) and same tools (layer two), how teams are wired determines whether they can accomplish work easily or require superhero effort and constant escalation.
Stop asking 'where can we use Gen AI' and instead ask 'what problem in our business couldn't we solve before'; technology is a means to solve previously unsolvable problems, not an end in itself.
Technology moves faster than employees can learn; organizations must deliberately pace digitization to allow associates to be trained on new processes, or teams will be left behind and unable to adapt to the new mode of operations.
Our reviewer’s read on each dimension, with quotes from the episode.
The episode is a compilation of brief sound bites on digital transformation, each offering a distinct perspective, but most clips are kept deliberately short and avoid deep exploration of any single idea. While there are genuine insights (technology as 50% of transformation, org structure's primacy, layer-3 wiring), they are not densely packed - each speaker gets perhaps 60-90 seconds, leaving little room for nuance, counter-argument, or follow-up. The format inherently favors breadth over depth.
It's changing people's jobs descriptions, it's changing operating models, it's changing revenue models, it's a lot of enterprise change management... It's only maybe 50% of the work, maybe even less.
For me it always ties back to org structure... Ownership and accountability is like first principle. Uh, you have to have that to do anything else and drive any other sort of change within the organization.
Several clips present genuinely thoughtful framings - the 50/30 split on transformation, the protect-vs-disrupt matrix, and especially the 'three-layer' model of org wiring are non-obvious. However, the episode lacks sustained originality; it mostly surfaces well-known frameworks (agile, org structure, people-first transformation) repackaged with slight twists. No speaker challenges prevailing wisdom sharply or presents truly contrarian findings.
the why I always talk about it as two parts. One is protecting the core of what the business is and how you create value and then disrupting, disrupting the ecosystem, creating new products, creating new services, new revenue models, new routes to market.
I think one that you just have to learn firsthand, which seems really obvious in retrospect, is just that the same processes and procedures that you have for one team of engineers with, uh, a team of three engineers at the whole company don't work when you have 10 teams of engineers with a hundred engineers at the whole company.
The lineup includes practitioners with apparent seniority and relevant operational experience (org leaders, engineers, transformation leaders, and a reference to Gene Kim, a recognized authority). However, the compilation format prevents substantive vetting - speakers are identified only by name with minimal credentialing, and no guest is allowed enough time to demonstrate depth of experience or scale of achievement. The caliber is likely solid but remains unverified by the transcript itself.
each offering a unique take on how real change happens in organizations. You'll hear from people like Andrei Gorenkov on why transformation has to include people in process. Christopher Paquette on balancing disruption with protection. Ann Young we'll be talking about why attention to internal operations is essential.
And wrapping it up, Gene Kim is going to share his thoughts on the powerful reminder that communication, human connection, the human touch is the foundation of true transformation.
The episode offers minimal concrete examples, metrics, or named case studies. Speakers reference 'unsolvable problems like data cleansing,' 'the NUMI joint venture in Fremont California,' and generalized team-scaling scenarios, but no specific dollar figures, timelines, or measurable outcomes are provided. Most claims remain at the principle level without empirical grounding.
Where you now can do it extremely reliably and extremely rapidly and at a level of quality that is uh, just amazing.
whether that's in DevOps or Agile or like the NUMI joint venture in Fremont California
This is a compilation of pre-recorded interviews stitched together by the host, with almost no live dialogue, follow-up questions, or push-back. The host's role is limited to framing and transitions; there is no evidence of sharp questioning, productive disagreement, or probing into contradictions. The format is closer to a highlight reel than a genuine conversation, undermining the opportunity for depth.
Today we're doing something a little different. A, uh, special compilation episode focused on one of the most recurring and thought provoking themes of across our interviews, digital transformation.
So much insight in these leaders words. It was inspiring to revisit these conversations. I hope you found these takeaways just as valuable as I do.
Computed from the transcript - who did the talking, and the words that came up most.
In this special compilation episode of Innovation and the Digital Enterprise , Patrick Emmons highlights key insights on digital transformation from top tech leaders. Featuring perspectives from Andrei Girenkov, Christopher Paquette, Ann Yeung, Sandee Kastrul, Deepak Kaimal, Jeff Miller, Christina Garcia, Tanya Hannah, Dan Kirsche, Dom Scandinaro, Subramanian Kunchithapatham, and Gene Kim. The episode delves into leading transformative tech teams, balancing disruption and protection, the role of AI, the need to stay nimble, and the foundational significance of human connection and communication in achieving successful digital transformation.
Transcribed and scored by The B2B Podcast Index.
Speaker A: Foreign.
Speaker B: Welcome back to Innovation and the Digital Enterprise, the podcast where we explore what it takes to build and lead transformative tech teams. I'm, um, your host, Patrick Emmons. Today we're doing something a little different. A, uh, special compilation episode focused on one of the most recurring and thought provoking themes of across our interviews, digital transformation. We've pulled together insights from some of our most impactful guests, each offering a unique take on how real change happens in organizations. You'll hear from people like Andrei Gorenkov on why transformation has to include people in process. Christopher Paquette on balancing disruption with protection. Ann Young we'll be talking about why attention to internal operations is essential. And my good friend Sandy Castro who reminds us that innovative change comes from bold, unconventional thinking. Then we'll hear from Deepak Kamal on how Gen AI can be a powerful transformation tool. Jeff Miller is going to share his thoughts on the underrated skill of listening, the foundation, in my opinion, of good leadership and Christina Garcia on the importance of empowering your team to lead change from within. Tanya Hannah is going to talk about staying nimble. Dan Kirsch shares the impact and challenges and opportunities within the actual org structure. Dom Scandinaro discusses how the size of your team changes the shape of transformation. Subramanian Kunchitha Patham points out that technology often moves faster than training and why you can't afford to leave your team behind. And wrapping it up, Gene Kim is going to share his thoughts on the powerful reminder that communication, human connection, the human touch is the foundation of true transformation. It's going to be a great little journey. I'm glad you're joining us. Let's dive in.
Speaker C: M A lot of what we do is sometimes called digital transformation, and it's often led by technology executives. But if you look at what's actually involved in a successful digital transformation, it's changing people's jobs descriptions, it's changing operating models, it's changing revenue models, it's a lot of enterprise change management. So getting people to behave in a very different way. And it's all empowered by technology. So it's a necessary block, but it's not a sufficient block. It's only maybe 50% of the work, maybe even less. So the more you can pick yourself up from your comfy technology chair and get out there into the maybe a little bit uncomfortable business zone, the better position you will be to speak effectively to your business leaders to lead change to achieve digital transformation. And do that in a way that hopefully goes out beyond your blinders and into the broader industry network around you.
Speaker D: M I would always go back to the why behind it. So like asking why would we digitally transform leads you to what is digital transformation? And I think the why I always talk about it as two parts. One is protecting the core of what the business is and how you create value and then disrupting, disrupting the ecosystem, creating new products, creating new services, new revenue models, new routes to market. And between those two, protect and disrupt. You really kind of have the waterfront covered for value creation. So it's about protecting, disrupting to create value for customers.
Speaker A: When companies are going through a lot of transformation, uh, the corporate functions are actually hit the hardest because there is a lot of people and process changes that need to happen and the underlying tech that needs to enable it goes through a big change. And being the backbone of any company, these corporate functions going through a digital transformation are extremely important in order to enable the success of other functions. So I feel like sometimes you don't feel like it's as sexy because corporate functions don't drive revenue right, uh, because they're not revenue producing. But then if not done right, the efficiency of the company and how we can operate gets impacted. Especially during digital transformation and change.
Speaker E: I m really believe that diversity is the primary driver of invention. And all the greatest innovations are coming from people who are thinking or looking at things differently. We know that the next big idea is coming from someone who's not thinking about today's or yesterday's way of doing things or thinking about how to disrupt things, how to make things better, how uh, to reinvent, how to challenge what's wrong.
Speaker F: So to be able to map that back to businesses, it is not so much about saying, okay, where can I use Gen AI in my business? Which is the wrong question to ask. The question to ask is what is a problem in my business that I couldn't solve before? And the solution doesn't have to be Gen AI, but in many cases there are unsolvable problems like uh, data cleansing, data mapping, stuff like that, where you now can do it extremely reliably and extremely rapidly and at a level of quality that is uh, just amazing. So I've seen a lot of organizations that will hire people or label down their technical skill like any label. I have got 15 years experience in Java or I've got 20 years experience in. Net. I can actually say that today, so go by those labels. But what I have seen uh, in my experience over the last 25 years is that the ones who are successful are the ones who are able to navigate that change. It is important to be strong in that technology, but it is also important to know that it doesn't stay static. It is people who are able to navigate that change, shift from one platform to the other, have the curiosity to understand how the new platforms are being developed and to be able to take it on and build on top of it. What you need are people who understand the business, who understand how technology works and to be able to explore and map how these technologies can be leveraged to drive your own business to navigate change. Sometimes almost, uh, ride the waves, almost look for those opportunities where change is driving growth.
Speaker G: Sometimes it's just good to listen and understand, right? And I think as a good life lesson as you go through is just like you got good ideas, but really understanding the local context is really important really to kind of help shape and understand how you actually drive change through the organization.
Speaker H: You control what you control and if new information comes in, we adapt, we adjust. Right? Uh, we change scope, we change our plan, we make alternatives, we adjust the plan. So I think the biggest thing for me right now is helping the engineers feel truly empowered to take control of what they can control and we can set a date based on what we know and what is in our control. And when new information comes up or a situation changes, like we adjust, we have new information and we make better decisions. I think it was Maya Angelou that said that, uh, you make the best decision you have with the information. When you learn more, you do better.
Speaker I: That's where innovation, transformation and growth really occurs. And what we're seeing today, you have to be nimble. Our organizations need agility, scalability. And the only way you can do it is if you can really anticipate what's going to happen. Make sure that your teams and your organizations are there and the technology is, is behind it.
Speaker J: For me it always ties back to org structure. So I focus on that first and I have throughout my career I've kind of fine tuned it. It's not very different I think than most other companies what they implement. The, you know, other tech companies kind of follow this practice as well. It's really standard agile, right. I think that there's some really key principles that are necessary and the reason why I focus so much on this is the need to drive ownership. Right. Ownership and accountability is like first principle. Uh, you have to have that to do anything else and drive any other sort of change within the organization, whether it be architecture, like other sort of collaborative efforts, that sort of thing, you have to have accountability and ownership Especially in super complex projects.
Speaker K: M I think one that you just have to learn firsthand, which seems really obvious in retrospect, is just that the same processes and procedures that you have for one team of engineers with, uh, a team of three engineers at the whole company don't work when you have 10 teams of engineers with a hundred engineers at the whole company. And it isn't immediately obvious when you're in the thick of it that if things are going super well and you're hiring and hiring and hiring and building more and more teams, that you actually need to change anything, right? Because things are going well, people are deploying code, more customers are coming, revenue is increasing. You don't always just take a step back and think about what efficiencies are we missing out on by not adjusting our processes? Or, you know, kind of the opposite, like, what problems are we causing by maybe moving too fast?
Speaker B: M
Speaker L: It's not easy to digitize all these things. Digitizing assets, processes and interactions. Ah, one is, uh, technologically you need to move fast and uh, digitize these things. That's one challenge. The second challenge I would put it as, you need to do it at a much faster pace. And when you have to do it at a much faster pace, then all the existing processes and your associates and uh, your uh, employees are trained on the existing processes. Once you digitize, there are going to be changes. Then you need to train all your associates to be familiar with how. What is the new mode of operations?
Speaker M: The difference maker is really in this kind of layer three, wiring, right? So layer one is the object in front of us. It could be the patient, it could be the code, it could be the binary running in production. Layer 2 is the tools and technology. So that could be the MRI machine, the CAT scanner, the IDE that we're editing our code in. It could be the Kubernetes platform. But the difference makers all in layer three is how do we connect our teams and people together? Norms, rituals, processes, the software architecture we work within that dictate who talks to who about what and when and how, right? And on the one extreme, everyone has what they need when they need it in the right format, and they can get it easily. In the worst case, no one has what they need, right? And so even small efforts require superhero effort, massive coordination costs, escalations, cajoling, politicking, right? Even to get small things done right? And everyone's stuck. And so I just found that kind of really dividing what the spectrum performance looks like and isolating it to layer three. Around organizational wiring just to be so illuminating. It was by far the most intellectually challenging thing I've ever worked on but it's one of the most rewarding. And one more thing I think whenever you study transformations when an organization goes from good to great whether that's in DevOps or Agile or like the NUMI joint venture in Fremont California what almost always happens is that layer one and layer two nothing changes. Same people, same equipment, same floor space right Same capital equipment. The only thing that changes is layer three right and so when we say it's the difference maker it just really says that leaders are truly responsible for that layer three wiring that preordain how to what extent people can do what they need to do easily and well.
Speaker B: So much insight in these leaders words. It was inspiring to revisit these conversations. I hope you found these takeaways just as valuable as I do. Thanks for listening and we'll see you next time. Mhm.
Other episodes covering the same guests and topics, from across The B2B Podcast Index.
Ep. 61 | Rethinking ROI: Balancing Innovation and Stability in Business The Resolution Room · on Digital transformation75 / 100
The Mindset Behind Siemens' Service Success | Brad Haeberle | UNSCRIPTED Ep. 370UNSCRIPTED · on Digital transformation70 / 100
Building Value Through Carve-Outs, Operational Transformation and AIThe Private Equity Podcast, by Raw Selection · on Digital transformation70 / 100
Microsoft's $2.5 Billion AI Investment: Street TalkMachine Learning Podcast · on Digital transformation69 / 100
Digitize Before You Automate: Yoav Kutner, Founder & CEO of OroCommerce, on the B2B Commerce Gap (Recorded at the B2B eCommerce Association)MarTalks- The #1 Ecommerce and MarTech application podcast · on Digital transformation65 / 100
#1 Industry 4.0 Thought Leader on What Manufacturers Get Wrong About Digital Transformation | Insights with Jeff Winter (Belden)Supply Chain Revolution · on Digital transformation65 / 100
Leading IHG's Global Tech with a One Team Mindset with Jolie Fleming60 / 100
Lead With Bold Vision: Guest-Centered Tech with Ulta Beauty's Mike Maresca64 / 100
Make Mistakes Matter: Turning Setbacks into Growth with Michael Ehlers79 / 100
Balancing Speed and Stability in Digital Transformations with Adan Pope73 / 100
Communication and Culture Drive Business Outcomes with Sean McCormack80 / 100