William Ulrich outlines seven patterns causing strategy execution failure, citing high waste rates and cultural barriers.
Summary
William Ulrich argues that strategy execution fails frequently due to seven specific patterns, including broken execution chains, siloed cultures, and data weaknesses. He cites statistics showing that strategy failure rates average 50% and that hundreds of billions in digital and AI investments fail to meet expectations. Ulrich advocates for a five-stage execution framework supported by formal business architecture to address these issues. He emphasizes that leadership often misallocates resources by focusing on deployment rather than initial scoping and architecture. The episode concludes with recommendations for introspective statistical analysis and reading specific industry literature.
Episode sections
- 0:04 – 2:41
Introduction and Strategy Failure Statistics
William Ulrich introduces the topic of seven deadly patterns undermining strategy execution. He cites a Forbes piece referencing the Journal of Management & Organization, stating strategy execution failure rates range from 7% to 90%, averaging 50%.
- 2:41 – 3:39
Digital and AI Investment Waste
Ulrich cites GenPAC Research Institute data showing $400 billion of nearly $600 billion in digital project spending failed to meet expectations. He notes that current AI investment waste dwarfs these figures, indicating a worsening situation for strategy execution.
- 3:39 – 6:01
Need for Internal Statistical Analysis
The speaker argues organizations must conduct introspective reviews of their investment returns over the past three to five years. He suggests tracking objective achievement rates and project metrics like time/cost overruns and cancellations to build a success/failure portfolio.
- 6:01 – 12:02
Pattern 1: Broken Execution Chain and Skipping Prerequisites
Ulrich defines the five-stage strategy execution chain and criticizes organizations for skipping impact assessments and future state definitions. He uses a medical analogy to illustrate the absurdity of demanding a solution without a diagnosis or clear objectives.
- 12:02 – 21:22
Pattern 2: Culture, Politics, and Silos
The speaker identifies silos, culture, and politics as an 'evil triad' that undermines execution. He argues that silo-based budgeting and compensation models drive replication, poor interoperability, and shadow systems, and suggests holistic budgeting and compensation as remedies.
- 21:22 – 29:12
Pattern 3: Lack of Holistic Perspective
Ulrich discusses how siloed thinking leads to a lack of holistic perspective, reinforced by policy barriers and non-interoperable systems. He criticizes the concept of internal business unit exchanges as a 'myth' that fails to address the root cause of siloing.
- 29:12 – 32:34
Pattern 4: Innovation Confined to the C-Suite
The speaker argues that innovation should not be confined to the C-suite, citing the example of an engineer at Cisco who left to found Zoom after his ideas were ignored. He advocates for feedback loops to allow rank-and-file employees to influence strategy.
- 32:34 – 33:55
Feedback Loops and Initiative Delivery Failures
Speaker 1 discusses the necessity of formal feedback loops within a strategy execution framework to ensure all stakeholders have a voice. He introduces 'Pattern Five: Program Delivery Blues,' noting that organizations consistently fail to deliver initiatives, which directly undermines strategic goals.
- 33:55 – 37:35
The Standish Group Statistics and Initiative Failure Patterns
The speaker cites the Standish Group to highlight historic poor performance in initiative implementation over the last 25-30 years. He describes two common responses to failure: doubling down on funding or executing a slow drawdown where the initiative is gradually scaled back without acknowledgment.
- 37:35 – 42:50
Misallocation of Investment in Deployment vs. Formulation
Speaker 1 argues that investments to reverse initiative failure have incorrectly focused on the deployment stage (Stage 5) using methodologies like SAFe or Agile. He contends that success is often determined before deployment begins, requiring investment in initiative scoping, future state articulation, and rationalization (Stages 2-4).
- 42:50 – 49:17
Data as the Weak Link in Strategy Execution
The speaker identifies 'Pattern Six: Data is the weak link in the chain.' He cites McKinsey and a Data and AI Leadership Executive Survey, noting that only 26% of organizations are data-driven and 91% cite cultural impediments as the primary barrier. He warns that leadership has hollowed out data architecture teams despite the critical need for quality data.
- 49:17 – 51:37
Addressing Data Gaps and Architectural Investment
To address data issues, the speaker recommends leveraging Stage 2 (Impact Assessment) and Stage 3 (Future State Architecture) to define data targets and logical data models. He argues that skipping these stages leads to fragmented, bottom-up data models that fail to integrate, whereas formal top-down investment in data architecture reduces code footprint and supports AI.
- 51:37 – 56:01
Technological Immaturity and Legacy Systems
Speaker 1 introduces 'Pattern Seven: Business strategy is captive to technological immaturity.' He notes that two-thirds of IT spending is wasted and organizations struggle to adopt new technologies like AI while relying on outdated procedural design paradigms. He suggests using formal business architecture to integrate new tech and retire legacy systems.
- 56:01 – 1:00:03
Conclusion and Recommendations
The speaker concludes by urging leaders to follow the five-stage strategy execution framework supported by formal business architecture. He advises collecting statistics on past failures to build a factual case for change and recommends reading 'Confessions of an Enterprise Architect' by his co-author, Charlie Bowman.
Claims worth verifying
According to a Forbes piece citing the Journal of Management & Organization, the success rate of strategy execution is low, with the percentage of failure ranging widely between as low as 7% to as high as 90%, averaging around 50%.
Unidentified speaker (speaker_1) ·2:27
How to verify: Search Forbes archives for articles citing the Journal of Management & Organization regarding strategy execution failure rates; verify the specific statistics quoted. For recent events, verify 2026-08-18 through 2026-11-18. Use another period only when the speaker explicitly names it.
GenPAC Research Institute found that of nearly $600 billion spent on digital projects, almost $400 billion of it was invested in projects that fell short of stated expectations and investment returns.
Unidentified speaker (speaker_1) ·3:00
How to verify: Search for GenPAC Research Institute reports or press releases from 2026-08-18 through 2026-11-18 detailing digital project spending and failure rates. For recent events, verify 2026-08-18 through 2026-11-18. Use another period only when the speaker explicitly names it.
Wasted AI investments are dwarfing the GenPAC numbers, according to separate stats.
Unidentified speaker (speaker_1) ·3:20
How to verify: Search for recent industry reports or studies from 2026-08-18 through 2026-11-18 comparing AI investment waste to previous digital project waste figures. For recent events, verify 2026-08-18 through 2026-11-18. Use another period only when the speaker explicitly names it.
The strategy execution chain has five stages: establish strategy, assess impact, architect/design future state, formalize initiative/funding, and deploy solution.
Unidentified speaker (UNKNOWN) ·6:18
How to verify: Verify against the book 'End-to-End Strategy Execution' by William Ulrich, specifically the framework outlined in the text. For recent events, verify 2026-08-18 through 2026-11-18. Use another period only when the speaker explicitly names it.
Peter Drucker is credited with saying 'culture eats strategy for breakfast'.
Unidentified speaker (speaker_1) ·12:42
How to verify: Search for the origin of this quote in Peter Drucker's published works or reputable business history sources. For recent events, verify 2026-08-18 through 2026-11-18. Use another period only when the speaker explicitly names it.
An engineer at Cisco was ignored when he proposed a new platform-like data management system, then left to form Zoom.
Unidentified speaker (speaker_1) ·30:36
How to verify: Verify historical records of Zoom's founding and Eric Yuan's employment history at Cisco; check Cisco's internal history or public records regarding the ignored proposal. For recent events, verify 2026-08-18 through 2026-11-18. Use another period only when the speaker explicitly names it.
Zoom took off during COVID and beyond, with almost half the market share at one point.
Unidentified speaker (UNKNOWN) ·30:51
How to verify: Search for Zoom's market share data during the COVID-19 period (2026-2026) from market research firms like Gartner or IDC. For recent events, verify 2026-08-18 through 2026-11-18. Use another period only when the speaker explicitly names it.
The strategy implementation survey identifies aligning implementation to a company's culture as the toughest strategy implementation challenge.
Unidentified speaker (speaker_1) ·15:37
How to verify: Search for the 'Strategy Implementation Survey' results cited by the speaker, likely from a business architecture or management consulting firm. For recent events, verify 2026-08-18 through 2026-11-18. Use another period only when the speaker explicitly names it.
The success rate of strategy execution failure ranges from 7% to 90%, averaging around 50%.
Unidentified speaker (speaker_1) ·32:34
How to verify: Forbes article citing the Journal of Management & Organization; verify via Forbes archive and Journal of Management & Organization publications. For recent events, verify 2026-08-18 through 2026-11-18. Use another period only when the speaker explicitly names it.
Standish Group statistics highlight historic and continuing poor performance of organizations when implementing initiatives over the last 25-30 years.
Unidentified speaker (UNKNOWN) ·33:57
How to verify: Standish Group 'Chaos Report' archives; verify via Standish Group website or library archives for reports published between 2026 and 2026. For recent events, verify 2026-08-18 through 2026-11-18. Use another period only when the speaker explicitly names it.
Organizations that harness big data and analytics are 23 times more likely to acquire customers, 9 times more likely to retain customers, and 19 times more likely to be profitable.
Unidentified speaker (speaker_1) ·43:11
How to verify: McKinsey Global Institute study on big data; verify via McKinsey & Company publications or MGI website. For recent events, verify 2026-08-18 through 2026-11-18. Use another period only when the speaker explicitly names it.
Only 26% of organizations report having achieved being data-driven, and only 19% report having established a data culture.
Unidentified speaker (speaker_1) ·44:17
How to verify: Data and AI Leadership Executive Survey; verify via the survey publisher's website or press releases from the survey organization. For recent events, verify 2026-08-18 through 2026-11-18. Use another period only when the speaker explicitly names it.
91% of survey respondents in the Data and AI Leadership Executive Survey identified cultural impediments as a great challenge to becoming data-driven.
Unidentified speaker (speaker_1) ·44:58
How to verify: Data and AI Leadership Executive Survey; verify via the survey publisher's website or press releases from the survey organization. For recent events, verify 2026-08-18 through 2026-11-18. Use another period only when the speaker explicitly names it.
Two-thirds of IT spending is wasted.
Unidentified speaker (UNKNOWN) ·52:03
How to verify: General industry statistic often cited by Gartner or IDC; verify via Gartner or IDC research reports on IT spending waste. For recent events, verify 2026-08-18 through 2026-11-18. Use another period only when the speaker explicitly names it.
William Ulrich is the co-author of 'End-to-End Strategy Execution from Inception through Solution Deployment'.
Unidentified speaker (speaker_1) ·40:42
How to verify: Book publication details on Amazon.com or publisher's website; verify via ISBN search. For recent events, verify 2026-08-18 through 2026-11-18. Use another period only when the speaker explicitly names it.
Charlie Bowman wrote 'Confessions of an Enterprise Architect'.
Unidentified speaker (speaker_1) ·57:36
How to verify: Book publication details on Amazon.com or publisher's website; verify via ISBN search. For recent events, verify 2026-08-18 through 2026-11-18. Use another period only when the speaker explicitly names it.
TSG Consulting Inc is the company of William Ulrich.
Unidentified speaker (speaker_1) ·58:59
How to verify: TSG Consulting Inc website (tsgconsultinginc.com); verify via company 'About Us' page. For recent events, verify 2026-08-18 through 2026-11-18. Use another period only when the speaker explicitly names it.
Primary sourceDo your own research
- Verify the Forbes article and Journal of Management & Organization study cited for strategy failure statistics.
- Review GenPAC Research Institute reports on digital project ROI and waste metrics.
- Check Standish Group's CHAOS Report for historical initiative success/failure rates.
- Examine McKinsey Global Institute publications on big data and analytics performance impacts.
- Read 'Confessions of an Enterprise Architect' by William Ulrich and Charlie Bowman for the proposed framework.
- Assess internal IT spending reports to identify the proportion of budget allocated to legacy maintenance versus innovation.
- Audit current data governance policies and cultural barriers to data-driven decision making.
- Review internal project post-mortems for evidence of 'slow drawdown' or buried audit reports on failed initiatives.
Full transcriptexpand
- 0:04
- Unidentified speaker (speaker_0): Welcome to the Voice America Business Channel show that reveals the real reason strategy execution keeps failing. William Ulrich, one of the authors of End-to-End Strategy Execution, is here to clear the fog and guide you toward meaningful results. Now, here's William.
- 0:24
- Unidentified speaker (speaker_1): Welcome to the Strategy Execution Podcast. on VoiceAmericamedia.com. I'm your host, William Ulrich. Today's podcast is titled Why Strategies Fail, or more aptly, The Seven Deadly Patterns Revisited. So we're going to talk today about the seven deadly patterns that undermine strategy
- 0:44
- Unidentified speaker (speaker_1): execution. Readers of my um end-to-end strategy execution book will recognize the focus. on strategy execution failure and the underlying causes.
- 0:55
- Unidentified speaker (speaker_1): And I
- 0:55
- Unidentified speaker (UNKNOWN): if
- 0:56
- Unidentified speaker (speaker_1): you take a look at the book, you'll find in chapter two, I go through the seven deadly patterns. And in chapter three, I target different ways to address those deadly patterns so that they don't undermine your strategies.
- 1:10
- Unidentified speaker (UNKNOWN): So
- 1:10
- Unidentified speaker (speaker_1): in my view, these strategies, um, the challenges that you're running. into with these patterns are being ignored in mass because they tend to fly against the comfort zone that too many leadership teams have landed in. And as I go through them, you'll probably recognize a lot of this within your own organization and
- 1:30
- Unidentified speaker (speaker_1): some of the challenges that you're getting leadership to uh address in terms of uh skipping impact assessments. not defining a clear target state before throwing a whole lot of money into a bucket and starting to attempt to do technology work without any clarity of where you're going. The list
- 1:50
- Unidentified speaker (speaker_1): goes on.
- 1:51
- Unidentified speaker (UNKNOWN): So
- 1:51
- Unidentified speaker (speaker_1): you'll probably see a lot of these things. And in my view, I've got stats on a lot of these, and I'll quote those stats. But in my view, I really don't think the messaging is getting through. So I decided. I needed to put this out in a little story to kind of support what's in the book.
- 2:09
- Unidentified speaker (UNKNOWN): So
- 2:09
- Unidentified speaker (speaker_1): let me jump in. I want to give you some stats, as I said. According to Forbes piece citing the Journal of Management and Organization, there's general agreement that the success rate of strategy execution is low, with the percentage of failure ranging widely between as low as 7%.
- 2:27
- Unidentified speaker (speaker_1): to as high as 90%, averaging around 50%. That's a uh half failure rate, half success rate. But a whole bunch of them fall in one side versus the other.
- 2:40
- Unidentified speaker (UNKNOWN): So,
- 2:41
- Unidentified speaker (speaker_1): in other words, half of all strategies fail, but other studies paint an even worse picture. Another way to look at strategy execution successes or lack thereof involves spending. So we all know that leadership has a close eye on budgets. And that's one of the things we do have their attention on. GenPAC Research
- 3:00
- Unidentified speaker (speaker_1): Institute found that of nearly $600 billion spent on digital projects, almost $400 billion of it was invested in projects that fell short of stated expectations and investment returns. In other words, they didn't deliver on what they said they were going to deliver. These numbers predate the stats associated with AI spending, the AI, what I call
- 3:20
- Unidentified speaker (speaker_1): the AI spending tsunami that's now underway. Wasted AI investments are dwarfing, according to stats, separate stats I don't need to get into here, but they're basically dwarfing the Gen PAC numbers. In a nutshell, when it comes to strategy execution, the situation is as bad as it's ever been.
- 3:39
- Unidentified speaker (speaker_1): And the stats along the lines of AI investments are actually worse than the Gen PAC numbers. So, while I've been sounding the board like a broken record on this topic, organizations need to start being analytical and introspective regarding their own strategy deployment and initiative failure. You've You're got going to take a look at what you're
- 3:59
- Unidentified speaker (speaker_1): doing in-house. And I still am not finding. enough people or enough teams that are starting to collect statistics on their own organization's investment returns over the past three to five years. I think it should be a focal point. And frankly, I think leadership should initiate those. But if leadership
- 4:19
- Unidentified speaker (speaker_1): doesn't do it, then the strategy team does. And if the strategy team doesn't do it, then somebody else has to pick up, pick up and carry the water. If you can't,
- 4:28
- Unidentified speaker (UNKNOWN): if
- 4:28
- Unidentified speaker (speaker_1): you don't bring supporting evidence to leadership that what they're doing doesn't work, they're going to continue to ignore your message about correcting what's wrong. They don't want to hear anything about architecture. I mean, I'll talk about it all day, but they don't want to hear anything about that. But if you can demonstrate through your own statistical analysis
- 4:48
- Unidentified speaker (speaker_1): that what they are doing is not working.
- 4:51
- Unidentified speaker (speaker_1): you can start getting some movement.
- 4:54
- Unidentified speaker (UNKNOWN): So,
- 4:54
- Unidentified speaker (speaker_1): on tracking these stats, what should we look at? Start with assessing how many of the organization's objectives, and if they don't have real objectives, which is going to be true for a lot of you out there, the mandates that they've set without formal objectives, but see how many have been met over the last three to five years. How well have they done? A second set of statistics to track.
- 5:15
- Unidentified speaker (speaker_1): track involve initiative or project uh time and cost overruns, cancellations, or shortfalls in terms of delivering business value.
- 5:24
- Unidentified speaker (UNKNOWN): So
- 5:25
- Unidentified speaker (speaker_1): you want to build a success and failure portfolio. Initiatives are considered successful if they're on time, on budget.
- 5:34
- Unidentified speaker (UNKNOWN): And
- 5:34
- Unidentified speaker (speaker_1): if they're late, that's okay. If they're a little over, that's okay. But on time, on budget, and they deliver. what they said they were going to deliver to the business community. However, if they run triple time or quadruple time, or they never end, or they're canceled, or they don't deliver any value, then you have a different issue. Okay, so let's um
- 5:54
- Unidentified speaker (speaker_1): with that backdrop, and I'll I'll just reiterate this when we wrap today. Let me move on to the seven deadly patterns.
- 6:01
- Unidentified speaker (UNKNOWN): I
- 6:01
- Unidentified speaker (speaker_1): want to jump into the discussion here. So pattern number one: the strategy execution chain is broken. What do I mean by that? So, first let me define it. So, again, some of you are familiar with it, but I just want to recap it. The strategy execution chain has five stages. They establish strategy,
- 6:18
- Unidentified speaker (UNKNOWN): they
- 6:18
- Unidentified speaker (speaker_1): assess the impact of the goals and objectives coming out of that strategy. They architect and design the future state, which can be a major investment. They formalize the initiative and funding
- 6:30
- Unidentified speaker (UNKNOWN): to
- 6:30
- Unidentified speaker (speaker_1): deliver on those goals and objectives.
- 6:33
- Unidentified speaker (UNKNOWN): And
- 6:33
- Unidentified speaker (speaker_1): they deploy the solution that achieves a stated strategy. So five stages. The work is done, the heavy lifting is done all the way through. Most people think, well, I know what I've been told I need to do. They've given me my money. Now I'm going to start start making changes or start writing cards. code or start investing here or start doing this.
- 6:53
- Unidentified speaker (UNKNOWN): And
- 6:54
- Unidentified speaker (speaker_1): then they end up failing because they haven't done the prerequisite work. I'll talk about that. Skipping over the key parts. So one way to make sure your organization falls short of its goals and objectives is to bypass the impact assessment and to bypass the future state definition. When organizations pursue these paths of
- 7:13
- Unidentified speaker (speaker_1): skipping impact. assessments and defining the future state, strategy execution teams end up working in the blind. They don't understand the impacts of their business and technology changes that they're supposed to be making. And more problematic, they have no idea what the future looks like. What I've heard leadership say is just
- 7:33
- Unidentified speaker (speaker_1): figure out the architecture once you start developing.
- 7:36
- Unidentified speaker (UNKNOWN): Well,
- 7:37
- Unidentified speaker (speaker_1): that doesn't work. We had a saying. many, many decades ago, and I'll date myself, is uh they start a project, they tell you what they want, and there's two of you sitting in a cubicle, and you say, You go, you go start, I'll go talk to the user, you just start coding, right? Start doing some work. Well, it's still like that today, only on
- 7:57
- Unidentified speaker (speaker_1): a much grander scale. The lack of the future state with full clarity around the target state architecture.
- 8:03
- Unidentified speaker (speaker_1): and design means that strategy execution teams don't understand what the target is that they're targeting or what they're trying to get to. And it could be dramatically different from what they have today. They end up unsure of how, where to distribute work, as a lack of clarity as to when they are finished, or even close to being finished. What's the result? The business
- 8:23
- Unidentified speaker (speaker_1): community doesn't see its goals and objectives addressed. Initiative. costs go up, endless initiatives keep adding resources, but fail to deliver. And at some point, failure is the only way out. And one quick clue: if your testing efforts are taking three and four or five times longer than you estimated, it means you the whole thing
- 8:43
- Unidentified speaker (speaker_1): is screwed up and you probably need to go back to square one. People don't like to hear
- 8:48
- Unidentified speaker (UNKNOWN): that
- 8:49
- Unidentified speaker (speaker_1): because they think that if they just throw more money into it, they should get to the end of it. And by the way, I have seen these scale up to ridiculously absurd numbers, where even the board of directors gets involved and said, We need to stop spending this money, it's not getting us anywhere.
- 9:07
- Unidentified speaker (UNKNOWN): So
- 9:08
- Unidentified speaker (speaker_1): consider how many times executives in your organization make the mental leap from a need that they have to fulfill. to giving you some money that says fix this thing with little clarity of the overall objectives. Fix this thing could be a major upgrade to an ERP system, or it could be any one of a number of other things, right? We start using
- 9:28
- Unidentified speaker (speaker_1): AI. I don't care how you use it, just justify that you're using
- 9:31
- Unidentified speaker (UNKNOWN): it.
- 9:32
- Unidentified speaker (speaker_1): They don't have a clarity of their objectives. They don't know the scope of impact, and they don't know what the future looks like. Their approach is often mandated. mandate or mandate-oriented, not objective-driven, so you don't know if you're actually satisfying anything.
- 9:44
- Unidentified speaker (UNKNOWN): So
- 9:45
- Unidentified speaker (speaker_1): let me do a medical analogy. I've I've for those readers of my book, you've probably seen
- 9:50
- Unidentified speaker (UNKNOWN): this.
- 9:51
- Unidentified speaker (speaker_1): It'll help bring things into focus. Imagine that an individual has a pain in his side and bursts into the doctor's office, throws money on the table, and demands that the doctor cut him open and remove his appendix. The doctor, having professional and ethical convictions, refuses to act, opting for a careful diagnosis to determine the root cause and
- 10:11
- Unidentified speaker (speaker_1): scope of the pain. After determining the source of the pain, the doctor would propose some tests. And in addition to the test, they would propose some treatment options. Having established a path forward, the doctor and the patient would then agree to a series of treatments. timelines, and funding coverage.
- 10:30
- Unidentified speaker (UNKNOWN): This
- 10:30
- Unidentified speaker (speaker_1): medical analogy seems absurd until one considers that business leaders mirror this approach on a regular basis. This is what we do today in reality. Business leaders would never consider commissioning a new building without engaging engineers and architects.
- 10:46
- Unidentified speaker (UNKNOWN): You
- 10:47
- Unidentified speaker (speaker_1): don't do the site work, you don't do the prep work.
- 10:50
- Unidentified speaker (speaker_1): Yet those same business leaders regularly exercise this behavior when it comes to executing strategy. It's just what they do. It is a habit that they've gotten into. And there's been very little pushback from the teams in the middle that are supposed to execute. The question is: where are the ethical and
- 11:10
- Unidentified speaker (speaker_1): professional principles of the second and third tier leadership? like the doctor in my story, to apply the professional guidance and principal behavior to leadership's ill-proposed directives. Somebody has to put their hand up and say, wait,
- 11:26
- Unidentified speaker (UNKNOWN): we
- 11:26
- Unidentified speaker (speaker_1): don't know the impact of what we're doing. We're just going to go spend money. We don't know what the future looks like. We're just going to go spend money.
- 11:34
- Unidentified speaker (UNKNOWN): So
- 11:34
- Unidentified speaker (speaker_1): if you're stuck in a situation, focus on demonstrating the absurdity of this the situation. situation. Use analogies, try common sense,
- 11:42
- Unidentified speaker (UNKNOWN): but
- 11:42
- Unidentified speaker (speaker_1): at some point, somebody's got to get the message across.
- 11:47
- Unidentified speaker (UNKNOWN): If
- 11:47
- Unidentified speaker (speaker_1): you need to go through the over one of the messaging here is you're going to run into is what I call the oversized egos commonly found in senior leadership Your teams. team. So be careful. Take heed. Don't get yourself fired while you're doing this.
- 12:02
- Unidentified speaker (UNKNOWN): All
- 12:03
- Unidentified speaker (speaker_1): right, let's jump on to pattern number two: culture, politics, and silos form an evil triad. You probably have heard me rail against silos in the past on a number of different occasions because they're sort of the one that sticks out. But all of these things are collect are part of a
- 12:22
- Unidentified speaker (speaker_1): bigger element. They're interrelated. It's a three-part challenge, but they're locked together. Much has been written regarding the impact of politics and culture. Management consultant Peter Drucker often is credited with saying culture eats strategy for breakfast. True, very true. Drucker encouraged people to work within the culture versus trying to
- 12:42
- Unidentified speaker (speaker_1): change it, but culture can still destroy viable strategies. And sometimes it's the culture that needs to change. And I I have no greater respect than anybody else. I'm the most respected for Peter Drucker. But I think at some point culture needs to shift, which raises a big conundrum for individuals
- 13:02
- Unidentified speaker (speaker_1): seeking to address these challenges. Adhering to a strategy execution framework that challenges traditional views of organizations, views that date back more than a century to the writings of Frederick Taylor, is not for the feign of faint heart. The biggest issue that is a result of
- 13:18
- Unidentified speaker (UNKNOWN): and
- 13:19
- Unidentified speaker (speaker_1): feeds cultural and political dysfunction is the existence of business unit silos. The reality is that strategies are often formed in silos, but even when they're not, they're almost always executed across silos.
- 13:36
- Unidentified speaker (speaker_1): Silo-based thinking undermines strategy execution. by relegating what should be holistic planning to a myriad of silo-based units, business units, reinforced by silo-oriented budget models, silo-oriented deployment teams, and also important silo-oriented technologies or software systems.
- 13:56
- Unidentified speaker (UNKNOWN): So
- 13:56
- Unidentified speaker (speaker_1): let's take a look at a typical scenario. Goals and objectives are handed down to a series of what I'll call uh tier two business leaders, uh VPs, larger organizations, VPs, maybe directors. Those leaders, each of which control large portfolios and corresponding budgets, pass those goals
- 14:16
- Unidentified speaker (speaker_1): and objectives down to their directors. Each of these directors distribute these same directives to silo-based deployment teams.
- 14:27
- Unidentified speaker (UNKNOWN): The
- 14:27
- Unidentified speaker (speaker_1): result is that much of the work being done is replicated, inconsistent, and suffers from poor interoperability. You want to know what interoperability issues look like? Take a look at your systems and take a look at all the spreadsheets that are being used and other shadow systems to make sure that those systems can work together. If you
- 14:47
- Unidentified speaker (speaker_1): eliminate those shadow systems, the systems stop working.
- 14:51
- Unidentified speaker (speaker_1): That is an interoperability problem. That is a data problem. That is a technology problem.
- 14:57
- Unidentified speaker (UNKNOWN): And
- 14:57
- Unidentified speaker (speaker_1): when you work in silos, you create those problems. You are responsible for it. And this is not a technology issue. This is a business issue. And the more leadership continues down the path of silo-based thinking with cultures and compensation systems and everything else built around them, the more of the issues you're going to have. The lack of system and data interoperability
- 15:17
- Unidentified speaker (speaker_1): is a hallmark of ineffective, high-cost, low payback initiatives and resulting systems and data. It's a vicious circle. The result is a degradation of the customer experience, competitive performance, and future strategy execution efforts, and the proliferation of more high-risk shadow systems.
- 15:37
- Unidentified speaker (speaker_1): According to the strategy, implementation survey, the toughest strategy implementation challenge involves aligning implementation to a company's culture. And we take that as a very true element here. The way to address this is to explain the issues that result from silo-based planning and deployment, specifically pointing out that
- 15:57
- Unidentified speaker (speaker_1): silos, culture and politics are wrapped around those, collectively, are
- 16:02
- Unidentified speaker (UNKNOWN): a
- 16:02
- Unidentified speaker (speaker_1): major impediment to successful strategy execution. So, what should we do about this particular one? Well, what we really want to focus on is sort of reversing that trend. And it's going to have to be done systematically.
- 16:19
- Unidentified speaker (UNKNOWN): And
- 16:19
- Unidentified speaker (speaker_1): again, you're going to have to demonstrate why there's value in it. And that can take a lot of work. But leadership should define and holistic horizontal planning and the compensation models to address the silo, the culture, and the politics-related roadblocks. If budgets are reapportioned across business
- 16:39
- Unidentified speaker (speaker_1): units and business leaders, as holistic shared budgets, the main driver of silo-based siloed-based planning and deployment is removed, which is the budget. stranglehold that that organizations have or that leadership puts on different initiatives. Everybody's got
- 16:59
- Unidentified speaker (speaker_1): their own budget. And they're allowed to spend that money any way they want to spend
- 17:04
- Unidentified speaker (UNKNOWN): it.
- 17:04
- Unidentified speaker (speaker_1): That is up to them.
- 17:06
- Unidentified speaker (UNKNOWN): So
- 17:06
- Unidentified speaker (speaker_1): if budgets are reapportioned across business units and business leaders, the main driver of siloed planning and deployment is removed. That's a big one. Okay, so we got to start with the budgeting model,
- 17:19
- Unidentified speaker (UNKNOWN): and
- 17:19
- Unidentified speaker (speaker_1): we've got to explain to leadership that that's an issue. I tell people when they're implementing a business architecture program, and they have a focus on
- 17:31
- Unidentified speaker (speaker_1): deploying a business architecture at an ecosystem-wide level, which is what they should
- 17:36
- Unidentified speaker (UNKNOWN): do,
- 17:37
- Unidentified speaker (UNKNOWN): and
- 17:37
- Unidentified speaker (speaker_1): leadership asks. them to do this because there's a door open there. That one of the first things they need to explain is if they want to use a business architecture effectively, what they need to do is to start to start thinking about the organization as a whole, not as a bunch of little tiny pieces.
- 17:58
- Unidentified speaker (speaker_1): So when we think about funding things at a holistic level, we'll get to compensation in a minute, right? We want to address those issues so we can get a business architecture in place that starts to look at the organization. I'll talk more about this in my next next segment, that starts to look
- 18:18
- Unidentified speaker (speaker_1): at the organization as a single unit,
- 18:21
- Unidentified speaker (UNKNOWN): a
- 18:21
- Unidentified speaker (speaker_1): single ecosystem as opposed to a whole bunch of little tiny broken pieces.
- 18:26
- Unidentified speaker (UNKNOWN): The
- 18:26
- Unidentified speaker (speaker_1): other one is compensation models, because leadership is oftentimes directors and leadership is compensated by what that group does, regardless of how damaging whatever they're doing is to the group next to them or the third group. In fact, a lot of times there's competition
- 18:47
- Unidentified speaker (speaker_1): for both budget as well as compensation. So that you want to make more money because you want your team bigger and you want to implement more things and you want to be more successful.
- 18:56
- Unidentified speaker (UNKNOWN): And
- 18:56
- Unidentified speaker (speaker_1): it happens to be that whatever you're implementing, which is based on a silo-based budget, happens to be happens to undermine everything else that the organization is doing currently.
- 19:07
- Unidentified speaker (UNKNOWN): So
- 19:07
- Unidentified speaker (speaker_1): you're actually undermining the overall effect. So not only do budget models need to shift. but the compensation models need to shift. So the collective success of the organization is how everyone is judged, not just on how well I do in my little bucket. Business leaders seeking
- 19:27
- Unidentified speaker (speaker_1): to transform historic approaches to strategy execution should not underestimate the historic challenges associating with making this shift.
- 19:36
- Unidentified speaker (UNKNOWN): A little
- 19:37
- Unidentified speaker (speaker_1): later on today, I'm going to say that maybe. data is the hardest part or technology is the hardest part, but I still do believe that the culture and the politics and the silos may be one of the biggest issues that organizations are facing if they want to reverse the trends on strategy execution
- 19:56
- Unidentified speaker (speaker_1): challenges. So after break, we're going to move on to deadly pattern number three.
- 20:02
- Unidentified speaker (UNKNOWN): But
- 20:03
- Unidentified speaker (speaker_1): uh let me do a quick break. You're listening to the Strategy Execution Podcast with William Ulrich, co-author of End-to-End Strategy Execution from Inception through solution deployment. You can get our book on Amazon.com or other outlets. We'll be right back after a short break.
- 20:27
- Unidentified speaker (UNKNOWN): Do
- 20:27
- Unidentified speaker (speaker_0): your strategic objectives fail to deploy? Wondering why technology budgets keep growing but deliver less? Are your strategy deployment efforts splintering into dozens of disjointed, disconnected projects? Does your organization lack a clear vision for maximizing AI and related technology investments long long-term? term? If this sounds
- 20:47
- Unidentified speaker (speaker_0): familiar, order a copy of William Ulrich and Charles Bowman's. new book, End-to-End Strategy Execution from Inception Through Solution Deployment, and get the answers you're looking for today.
- 21:00
- Unidentified speaker (speaker_2): Voice America is on LinkedIn. Connect with us today.
- 21:10
- Unidentified speaker (speaker_0): We're back on the Voice America Business Channel, where William Ulrich is breaking down the hidden barriers that keep organizations stuck in repeated failures. Let's continue.
- 21:22
- Unidentified speaker (speaker_1): Welcome back to the Strategy Execution Podcast. I'm your host, William Ulrich. You can check out our podcast at VoiceAmericamedia.com or subscribe to it on Apple Podcasts, Podcast, Spotify, or wherever you get your podcasts.
- 21:36
- Unidentified speaker (UNKNOWN): All
- 21:36
- Unidentified speaker (speaker_1): right, so I went through Dudley. deadly patterns one and two before break. Let me jump in with uh deadly the deadly pattern that's undermined strategy execution. Number three, organizations lack holistic perspective. And yes, this is related to the prior one on silos and
- 21:56
- Unidentified speaker (speaker_1): culture, but a lack of holistic perspective is a casualty of that siloed mentality.
- 22:03
- Unidentified speaker (UNKNOWN): And
- 22:03
- Unidentified speaker (speaker_1): it's reinforced by policy-oriented communication barriers between business units, and I want to get into those here, along with the budgets and, of course, compensation models, as I talked about, and non-interoperable application systems and data. So one resulted in the next. As we
- 22:23
- Unidentified speaker (speaker_1): built things into silos,
- 22:26
- Unidentified speaker (UNKNOWN): we
- 22:26
- Unidentified speaker (speaker_1): started doing that in the 60s and 70s and 80s and 90s,
- 22:29
- Unidentified speaker (UNKNOWN): and
- 22:30
- Unidentified speaker (speaker_1): we got locked into those silos, both system and data-wise. We then mirrored
- 22:35
- Unidentified speaker (UNKNOWN): the
- 22:36
- Unidentified speaker (speaker_1): which which by the way were mirrored after the business units that initiated those systems. We then mirrored the business units after those silos because of the technology. So we got locked again in what I call the vicious circle.
- 22:50
- Unidentified speaker (UNKNOWN): The
- 22:50
- Unidentified speaker (speaker_1): holistic business ecosystem perspective, which can be traced to business leaders and execution teams viewing an organization as a series of independent silos, right? So the underlying issue here is that leadership and execution teams view the organization as a whole bunch of
- 23:09
- Unidentified speaker (speaker_1): independent parts, which casually need to communicate periodically. and can do that through the same way you communicate with business partners, the same way you communicate with customers. Yet customers look at you as a single unit. They may have a bad experience with one of your silos and
- 23:29
- Unidentified speaker (speaker_1): leave. And then you're sitting there trying to figure out why they left because we thought we had a good relationship.
- 23:36
- Unidentified speaker (UNKNOWN): And
- 23:36
- Unidentified speaker (speaker_1): that happens all the time. But either way, call it human nature or more likely conditioning of workers when they enter the silo business system, everybody sort of takes on that silo-based thinking. And then we start and we go up, right? We get promoted, we end up in leadership, so we do silo-based planning.
- 23:57
- Unidentified speaker (speaker_1): It doesn't seem common sense to think that if organizations can assess issues from a big picture perspective and work collectively to lay out a strategy to address all aspects of the issue, that they could do a more effective job at formalizing and shared data perspectives and highly interoperable systems. In other words, if you work as a unit, wouldn't it
- 24:17
- Unidentified speaker (speaker_1): make more sense if you looked at things holistically so you could solve them holistically and probably end up, by the way, saving a whole bunch of money than initiating a whole bunch of independent projects that don't connect or don't work together, that you then have to launch other projects to try to make all the connections to. Wouldn't it make more sense to do that planning
- 24:37
- Unidentified speaker (UNKNOWN): so
- 24:37
- Unidentified speaker (speaker_1): that you can end up with
- 24:40
- Unidentified speaker (speaker_1): interoperable solutions
- 24:42
- Unidentified speaker (UNKNOWN): and
- 24:43
- Unidentified speaker (speaker_1): a coordinated set of work that doesn't waste a lot of time because you're competing versus coordinating and collaborating?
- 24:51
- Unidentified speaker (speaker_1): with a lot of the other pieces of the organization that all need to work off the same strategy. We create these puzzles for ourselves. And I've been seeing a buzzword around lately about cohesion. Stop using it as a buzzword and start taking it seriously and start looking at some of the recommendations I'm making. If you really want to deal
- 25:11
- Unidentified speaker (speaker_1): with uh getting a more cohesive organization, you're going to have to look at these issues and you're going to need to be brave enough to stand up to leadership
- 25:20
- Unidentified speaker (UNKNOWN): that
- 25:21
- Unidentified speaker (speaker_1): doesn't agree with you on cohesion. They may say they do, but if they really do, they need to break down these silos and start looking at the organization in a more holistic way. Silo thinking is so prevalent. If you don't think it's in your organization, it's so prevalent that the IT industry has created an artificial solution to address. the fact that organizations
- 25:40
- Unidentified speaker (speaker_1): don't work and act as a cohesive coordinated unit. It's called the business unit to business unit internal service exchange, or what some people just call business services. Business services are things you offer customers. It keeps them happy.
- 25:56
- Unidentified speaker (UNKNOWN): It
- 25:56
- Unidentified speaker (speaker_1): keeps them as your customers, it keeps them coming back. They're not things that you offer to the cubicle next door or the business unit in the next building. You're supposed to work as one unit. How can you do business unit to business unit exchanges
- 26:11
- Unidentified speaker (UNKNOWN): and
- 26:11
- Unidentified speaker (speaker_1): expect to be working as a single unit?
- 26:14
- Unidentified speaker (UNKNOWN): So,
- 26:14
- Unidentified speaker (speaker_1): for readers of our book, you can check out a section titled The Myth of the Internal Business Unit or Business Service, rather, and you can start to see what I'm talking about. This is the solution that's really occurs. a curse. It's worse than the issue that it pretends to address, which is siloing. You have to address siloing at the roots.
- 26:34
- Unidentified speaker (speaker_1): Otherwise, you're you're just a bunch of independent units.
- 26:39
- Unidentified speaker (UNKNOWN): And
- 26:39
- Unidentified speaker (speaker_1): in these internal service exchanges, along with unenforceable service level agreements, which I always have to laugh because I say it's not an agreement unless it's legally enforceable. Can you sue somebody for breaking a service level agreement? No.
- 26:52
- Unidentified speaker (UNKNOWN): So
- 26:52
- Unidentified speaker (speaker_1): it's a ridiculous thing to even have in place in the first place. They create a false perspective of things working effectively, all while the business units involved lose more and more touch with the end customer. Shut this problem practice down as soon as you can.
- 27:07
- Unidentified speaker (UNKNOWN): How
- 27:07
- Unidentified speaker (speaker_1): else can we change this entrenched way of thinking where we're looking at the organization as a bunch of parts instead of one unit? One way is to leverage a holistic business architecture frame perspective of your business ecosystem. And I mentioned this in the last segment,
- 27:23
- Unidentified speaker (UNKNOWN): but
- 27:23
- Unidentified speaker (speaker_1): the business architecture capability map, the information map, the stakeholder map, and its value streams view an organization as a cohesive whole.
- 27:32
- Unidentified speaker (UNKNOWN): Now,
- 27:32
- Unidentified speaker (speaker_1): somebody may not believe that, right?
- 27:34
- Unidentified speaker (UNKNOWN): If
- 27:35
- Unidentified speaker (speaker_1): you're working in a business unit and you are the only one using business architecture, you're not making much use of business architecture.
- 27:42
- Unidentified speaker (UNKNOWN): So
- 27:42
- Unidentified speaker (speaker_1): let me bring home the point. Leadership can reorganize as much as they want. They can move all the chess pieces around. They can consolidate business units. They can split business units, they can change leadership, and so
- 27:56
- Unidentified speaker (UNKNOWN): on.
- 27:57
- Unidentified speaker (speaker_1): But the capability map, the value streams, the stakeholder breakdown. and the information it uses will look the same. If you have a well defined capability map and value streams and information map, it won't change
- 28:17
- Unidentified speaker (speaker_1): when you do a reorganization, unless you're changing the business model and introducing new capabilities.
- 28:24
- Unidentified speaker (UNKNOWN): Or
- 28:24
- Unidentified speaker (speaker_1): you're changing the business model that warrants a new value stream.
- 28:28
- Unidentified speaker (UNKNOWN): So
- 28:28
- Unidentified speaker (speaker_1): if you want to shift the holistic thinking, one easy way to do it is to adopt a principle-based business architecture as a basis for strategy execution. Let me add one point. Addressing a lack of a holistic perspective does not require a reorganization. I just think that's important for me to say. Although holistic planning may lead to such a
- 28:48
- Unidentified speaker (speaker_1): conclusion, and if you want to use the business architecture, organization map, which I've covered in uh in prior uh podcast episodes, you can do that to do a more intelligent reorganization. Rather, an organization only needs to visualize its business ecosystem through a holistic lens using business architecture that serves in this
- 29:08
- Unidentified speaker (speaker_1): role. So you don't actually need we to do a reorganization.
- 29:11
- Unidentified speaker (UNKNOWN): All right,
- 29:12
- Unidentified speaker (speaker_1): so that was on addressing the uh lack of
- 29:15
- Unidentified speaker (speaker_1): working as a holistic organization. Let me move on to pattern, deadly pattern number four. Good ideas are confined to the C suite. And there's a good way to address this, and I'll talk about that. Innovation should never be confined to a small circle of business leaders. You discover innovation through work. I hear about innovation teams,
- 29:35
- Unidentified speaker (speaker_1): they live in an ivy Ivory tower, they don't have any exposure to the work. being done in the rank and file by the real people doing the real work. Innovation teams should come out of the Ivory Tower and get into the in into the operational environment and start doing the work. And innovations will come popping up all over the place.
- 29:56
- Unidentified speaker (speaker_1): But you know, for me, which is maybe why I, you know, never chose to to be in the particular research entity. end of things and lock myself in a tower, um, to me, innovation it requires experience and getting your hands dirty. Right. So that's what I really like to sort of say is you need to rely on
- 30:16
- Unidentified speaker (speaker_1): those folks. So when strategic planning's confined to ideas that only emanate from the C-suite, great ideas and the viability for implementing them never make it to strategic plans. It In is brought his book, From Incremental to Exponential, Vivek Wadwa, who I have a great respect for, explains how an engineer working at Cisco was ignored when he proposed a new platform like data
- 30:36
- Unidentified speaker (speaker_1): management. That engineer left Cisco to form Zoom because the executives would now listen to his suggestions. Zoom, of course, took off during COVID and beyond. It's a widely used video platform across the market.
- 30:51
- Unidentified speaker (UNKNOWN): with
- 30:51
- Unidentified speaker (speaker_1): almost half the market share at one point. So leaving Cisco's product in the dust. What happened? Somebody came up with an idea because they were working in the rank and file. They were, they got their hands dirty, they understood what was needed. Leadership didn't want to listen to them.
- 31:09
- Unidentified speaker (UNKNOWN): All right,
- 31:09
- Unidentified speaker (speaker_1): so let's talk about one way to try to make sure these good ideas are not confined to the C-suite. And I'm going to go back to the five-stage strategy execution framework.
- 31:19
- Unidentified speaker (UNKNOWN): You
- 31:19
- Unidentified speaker (speaker_1): want to create feedback loops at each stage of the strategy execution framework so that at any point, if there's a viable challenge to a proposed course of action or overall strategy execution scope,
- 31:33
- Unidentified speaker (UNKNOWN): the
- 31:33
- Unidentified speaker (speaker_1): feedback loops should ensure that issues or related factors cycle back to business leaders, planners, and other relevant stakeholders. You can feedback to the prior stage, say I need more input,
- 31:44
- Unidentified speaker (UNKNOWN): or
- 31:44
- Unidentified speaker (speaker_1): you could feedback all the way up, saying, I don't understand this objective. Can you help me clarify it?
- 31:51
- Unidentified speaker (UNKNOWN): When
- 31:51
- Unidentified speaker (speaker_1): you get handed mandates, and I
- 31:54
- Unidentified speaker (UNKNOWN): I've
- 31:54
- Unidentified speaker (speaker_1): covered this in other things, but I just want to throw it out there. And One feedback loop, when you get handed mandates, go back to leadership and say, I need a little more clarity about what you're seeking. Would you say that your objective here is to do such and such? And that one of our courses of action would be to do this.
- 32:14
- Unidentified speaker (UNKNOWN): And
- 32:15
- Unidentified speaker (speaker_1): then you say, if your objective is to do such and such, and we can measure that objective and adhere to that objective, would it be possible that the approach that we take, the course of action that we pursue, might be a little different than the one you're suggesting in your mandate? So that's a one feedback loop, but that's one of
- 32:34
- Unidentified speaker (speaker_1): many feedback loops. You can go back to architecture team, you can go back to wherever you want to go to get the feedback, to provide the feedback to get what you need to keep moving forward. That way, everybody has a voice in what's happening. And I sit in places all the time saying, this is never going to work, but management doesn't want to hear it, so we're just going to go ahead and do
- 32:54
- Unidentified speaker (speaker_1): it anyway. Knowing that a year from now, the project's going to be an abject failure.
- 32:59
- Unidentified speaker (UNKNOWN): And
- 32:59
- Unidentified speaker (speaker_1): we've seen that in the real world all the time. I'm sure many of you out there have.
- 33:04
- Unidentified speaker (UNKNOWN): So
- 33:04
- Unidentified speaker (speaker_1): feedback loops along a formally adhered to N10 strategy execution framework is one way to get everyone engaged in delivering a solution that achieves a strategy set up by leadership.
- 33:15
- Unidentified speaker (speaker_1): Let's go on to pattern number five. Program delivery blues undermines strategy. That's the uh sort of a funny little name that I gave to this one. But basically,
- 33:25
- Unidentified speaker (UNKNOWN): uh
- 33:25
- Unidentified speaker (speaker_1): we have trouble delivering our initiatives. There's all kinds of steps on
- 33:29
- Unidentified speaker (UNKNOWN): that.
- 33:30
- Unidentified speaker (speaker_1): And if you if organizations cannot successfully deliver on their initiatives, common sense would dictate that strategy execution is falling short. I'm not delivering what I need to deliver, therefore, I'm probably not meeting my strategic goals and objectives.
- 33:46
- Unidentified speaker (UNKNOWN): So
- 33:46
- Unidentified speaker (speaker_1): in the prior stats, I shared uh reinforce the relationship between initiative failure and the inability to successfully deliver an organization's business strategy.
- 33:55
- Unidentified speaker (UNKNOWN): And
- 33:55
- Unidentified speaker (speaker_1): previously cited from Stanish Group,
- 33:57
- Unidentified speaker (UNKNOWN): uh,
- 33:58
- Unidentified speaker (speaker_1): statistics from Stanish Standish Group highlighted the historic and continuing poor performance. of organization when it comes to implementing initiatives. A lot of the investment over the last 25, 30 years has been in the lead up to deployment, right? So we're trying to fix it. We realize we have an issue,
- 34:15
- Unidentified speaker (UNKNOWN): but
- 34:15
- Unidentified speaker (speaker_1): it doesn't seem to be getting better based on the statistics. Uh the statistics say that you know organizations are consistently underperforming. And that the fact that they're underperforming, regardless of industry sector, or region, means that this is a highly ubiquitous and seriously problematic challenge. Challenged and failed initiatives often land
- 34:35
- Unidentified speaker (speaker_1): with a thud like a rocket that never achieves flight.
- 34:39
- Unidentified speaker (UNKNOWN): But
- 34:39
- Unidentified speaker (speaker_1): they're usually swept under the rug by the very business leaders that initiate initiated and drove the mandate-driven Driven investment.
- 34:47
- Unidentified speaker (UNKNOWN): So
- 34:47
- Unidentified speaker (speaker_1): we've all seen it, but let me just toss out a couple of things that I I've seen. The way it worked in decades in history over many decades in industry is that some big initiative with a fancy name, because they make that, that's their big splash, you get a new CIO or whatever, call it NextGen or Project 2000. Yeah, those are real, is launched
- 35:07
- Unidentified speaker (speaker_1): and has a huge budget allocation thrown at
- 35:10
- Unidentified speaker (UNKNOWN): them.
- 35:11
- Unidentified speaker (speaker_1): As failures become evident, one of two things happen.
- 35:16
- Unidentified speaker (speaker_1): One is that leadership doubles and triples down on funding and resources, all while getting no closer to delivering on the same, some sort of vague target.
- 35:26
- Unidentified speaker (speaker_1): It's human nature, it's stubbornness, it's the inability to take outside input, it's the inability Ability to, to it's or it's it's the blind reliance on some systems integrator that. you know keeps buying golf games or rounds of golf for your CFO, whatever it is, right?
- 35:45
- Unidentified speaker (UNKNOWN): The
- 35:46
- Unidentified speaker (speaker_1): other thing that happens is that there's a slow drawdown. This is when they do start realizing they need to shut something off. A slow drawdown, reducing the intent of the initiative until it resembles Rhesembles nothing close to the original proposal.
- 36:01
- Unidentified speaker (UNKNOWN): And
- 36:01
- Unidentified speaker (speaker_1): as you do draw drop it down, down, work is slowly terminated, resources are reallocated, and they do it gradually so nobody notices. Leadership either declares victory on the one hand or bans anyone from ever mentioning the initiative again going forward. So you can bring those initiatives up.
- 36:21
- Unidentified speaker (speaker_1): Again, I always caution people when you're doing this, try not to get yourself fired, but you can bring those up. in conversations. What about this? What happened? Why didn't it work? Where's our post mortem? Why aren't we looking at what happened? And I've seen people actually do audits on these things. They brought in a third party to do an audit.
- 36:40
- Unidentified speaker (UNKNOWN): And
- 36:40
- Unidentified speaker (speaker_1): I've seen some of those audit reports. And the audit reports were good, but they still didn't heed them. They went off without any clear business objectives. So they spent a whole bunch of money. money. So, you know, when you're investing in these things and they do fail and you do an audit report, don't bury the report.
- 36:58
- Unidentified speaker (speaker_1): And I've seen, you know, CIOs and other leadership bury reports because they don't want to know. Because it wouldn't, it looks like to them like they're failing. They're not. This is a whole systemic set of issues that almost every organization.
- 37:15
- Unidentified speaker (speaker_1): has. And the more quickly you face them, the more quickly you can address them.
- 37:21
- Unidentified speaker (UNKNOWN): So,
- 37:21
- Unidentified speaker (speaker_1): how do we address this initiative failure issue? So, as noted in Standish group research, there's a long history of unsuccessful programs, projects, and other time-bounded things. So, more generally, they're called initiatives. Initiative. So the first step is:
- 37:35
- Unidentified speaker (UNKNOWN): how
- 37:36
- Unidentified speaker (speaker_1): are we doing with it, right?
- 37:38
- Unidentified speaker (UNKNOWN): Um,
- 37:38
- Unidentified speaker (speaker_1): if you can't, if organizations can't deliver successful initiatives, you're underperforming when it comes to strategy execution. If you're underperforming around strategy execution, we know what those issues are. You're not getting done what you need to get done strategically. So investments today to reverse the poor showing on initiative delivery have largely focused on strategy execution
- 37:58
- Unidentified speaker (speaker_1): framework stage five. That's the deployment stage,
- 38:01
- Unidentified speaker (UNKNOWN): that's
- 38:02
- Unidentified speaker (speaker_1): the deployment. stage of strategy execution, right? It's where the work is done. It's where the deliverables are made. It hasn't focused on the strategy formulation piece. It hasn't focused on the impact assessment piece, which is huge. It hasn't focused on the future state definition, the third
- 38:22
- Unidentified speaker (speaker_1): stage, architecting the future state and designing the future state. It hasn't focused on the how initiatives are formed. In fact, all of that's ignored. And all kinds of money is thrown into all kinds of back end investments, scaled agile, safe, all kinds of other things is where the money's tossed.
- 38:41
- Unidentified speaker (UNKNOWN): But
- 38:41
- Unidentified speaker (speaker_1): the fate of many initiatives is often sealed prior to entering the deployment stage. These deployment stage stage-based based investments have little impact, you know, the investment. investments that you've made in those stages have had little impacts on this Standish group statistics over the last 25 years. Success was already sacrificed prior to the first line of code being written.
- 39:01
- Unidentified speaker (speaker_1): Failure was imminent, whatever you define as failure. To reverse this trend of unsuccessful initiatives, you should consider investing time and resources in initiative scoping and future state articulation. and initiative rationalization and optimization so that the initiatives aren't working in these same
- 39:21
- Unidentified speaker (speaker_1): silos that your funding and compensation models are working
- 39:24
- Unidentified speaker (UNKNOWN): in. So
- 39:25
- Unidentified speaker (speaker_1): that falls into strategy execution stages two and three and four. That's what you need to invest in. And stop throwing more and more money into the back end because no matter how many different methodologies. or whatever practices you come up with,
- 39:41
- Unidentified speaker (UNKNOWN): and
- 39:42
- Unidentified speaker (speaker_1): I'm a fan of Agile, you know, along with a lot of other things, I'm a fan of uh service-oriented architecture and agile and all the other good things. As long as you consider, keep trying to just throw the money into the back end of strategy execution, you're going to keep failing.
- 39:57
- Unidentified speaker (UNKNOWN): And
- 39:57
- Unidentified speaker (speaker_1): you're going to keep failing in big ways, not in small ways. People say, well, you know, fail quickly. We're talking about failure on scale, a failure that needs to be hidden, failure that needs to be written off.
- 40:08
- Unidentified speaker (UNKNOWN): So
- 40:08
- Unidentified speaker (speaker_1): until that shift in thinking and execution becomes a reality, organizations can continue to throw good money after bad in stage five and do little to effectively change the status quo when it comes to delivery, uh, initiative of deliveries and execution.
- 40:21
- Unidentified speaker (UNKNOWN): I
- 40:22
- Unidentified speaker (speaker_1): want to wrap up the last couple in the last segment, I want to wrap up a last couple of deadly patterns. and then go into a few recommendations going forward. But prior to that, I want to take a quick break. You're listening to the Strategy Execution podcast with William Ori, co-author of End to End Strategy Execution from
- 40:42
- Unidentified speaker (speaker_1): Inception through Solution Deployment. You can get our book on Amazon.com or other outlets, and we'll be right back after a short break.
- 40:58
- Unidentified speaker (UNKNOWN): The
- 40:58
- Unidentified speaker (speaker_0): groundbreaking new book, In-to-Ind Strategy Execution, from Inception Through Solution Deployment, tackles initiative failures and wasted investments head on. Co-authors Authors William Ulrich and Charles Bowman take readers on a guided journey that not only helps leadership. formulate a strategic vision, but lays the foundation
- 41:18
- Unidentified speaker (speaker_0): for making that vision a reality. The book uses practical examples, analogies, and case studies to chart a path forward for C-suites, implementation teams, and everyone in between. Get a copy today and join them on the journey.
- 41:34
- Unidentified speaker (UNKNOWN): When
- 41:34
- Unidentified speaker (speaker_3): it
- 41:35
- Unidentified speaker (speaker_0): comes to business,
- 41:35
- Unidentified speaker (speaker_3): you'll find the experts here. Voice America Business. Network.
- 41:45
- Unidentified speaker (speaker_0): We're back on the Voice America Business Channel, where William Ulrich is breaking down the hidden barriers that keep organizations stuck in repeated failures. Let's continue.
- 41:57
- Unidentified speaker (speaker_1): Welcome back to the Strategy Execution Podcast. I'm William Ulrich, co-author of End-to-End Strategy. Execution from Inception through Solution Deployment. You can check out this podcast at voiceamericamedia.com or subscribe to it on Apple Podcasts, Spotify, or wherever you get your podcasts.
- 42:15
- Unidentified speaker (UNKNOWN): So
- 42:15
- Unidentified speaker (speaker_1): in this last segment, I want to hit on two
- 42:19
- Unidentified speaker (UNKNOWN): of
- 42:19
- Unidentified speaker (speaker_1): what I consider the most challenging and intransigent deadly patterns. They really are tough ones.
- 42:28
- Unidentified speaker (speaker_1): They're all difficult, they're all challenging. But this one in particular takes a lot of focal point, investment, and maybe changing of attitudes and thinking.
- 42:39
- Unidentified speaker (speaker_1): The first involves data,
- 42:41
- Unidentified speaker (UNKNOWN): and
- 42:41
- Unidentified speaker (speaker_1): the second one involves technology.
- 42:44
- Unidentified speaker (UNKNOWN): So
- 42:44
- Unidentified speaker (speaker_1): I'm going to wrap up on some ideas on where to focus, but let me get into the data piece first.
- 42:50
- Unidentified speaker (UNKNOWN): So,
- 42:51
- Unidentified speaker (speaker_1): pattern number six: data is the weak link in the chain. How important is data and the need to deal with it early in strategy execution? Well, according to McKinsey Global Institute study, organizations that harness big data and analytics are 23 times more likely to acquire customers,
- 43:11
- Unidentified speaker (speaker_1): nine times more likely to retain customers, and 19 nineteen times more
- 43:14
- Unidentified speaker (UNKNOWN): than the customer.
- 43:15
- Unidentified speaker (speaker_1): likely to be profitable. Wow, that's what I say to those stats. Um, even if you only believe those are half true,
- 43:24
- Unidentified speaker (UNKNOWN): it
- 43:24
- Unidentified speaker (speaker_1): still makes data investment critically important.
- 43:27
- Unidentified speaker (UNKNOWN): So,
- 43:28
- Unidentified speaker (speaker_1): in other words, data is critical to an organization's success, but it's a weak spot. The investment level in data at most organizations appears to be totally ignoring these finance. findings, which I find very interesting given all the money leadership pays out to McKenzie and other strategic planning firms.
- 43:47
- Unidentified speaker (UNKNOWN): The
- 43:47
- Unidentified speaker (speaker_1): least that you that leadership could do when they're paying out that money is when these organizations are delivering a powerful message, is to listen to it and take it seriously and to take some action on
- 44:00
- Unidentified speaker (UNKNOWN): it. Let's
- 44:01
- Unidentified speaker (speaker_1): take a look at another. set of stats that uh gets into a little more detail. According to the Data and AI Leadership Executive Survey, and this one involves AI, organizations continue to struggle to become data driven, with only 26%
- 44:17
- Unidentified speaker (speaker_1): reporting having achieved this goal, and only 19% reporting having established a data culture. Data culture is as important. as everything else around this. That means everybody's thinking about data. That means investments in data are not frowned upon, they're not ignored, they're not
- 44:36
- Unidentified speaker (speaker_1): skipped over.
- 44:38
- Unidentified speaker (UNKNOWN): And
- 44:38
- Unidentified speaker (speaker_1): there's enough of that going on out there. Um, I'll get into a little more of my personal experience. The survey also found that cultural impediments remain the greatest barrier to organizations becoming data driven, with 91%. 91.9%, almost 92% of survey respondents identifying culture, cultural impediments as a great
- 44:58
- Unidentified speaker (speaker_1): challenge. What cultural impediments are there against data? It's shocking. It is absolutely shocking.
- 45:06
- Unidentified speaker (UNKNOWN): And
- 45:07
- Unidentified speaker (speaker_1): I think all the data architects out there who are diligently working away in the various corners of the organizations that you work in.
- 45:15
- Unidentified speaker (speaker_1): it's time to start maybe stepping up. And I know by nature, having worked with a lot of data architects, you may not want to be the face of challenging these issues. But the long the more you can
- 45:29
- Unidentified speaker (UNKNOWN): and
- 45:30
- Unidentified speaker (speaker_1): you're and you're respected, the better.
- 45:33
- Unidentified speaker (UNKNOWN): And
- 45:33
- Unidentified speaker (speaker_1): I've told this to uh leaders of data architecture teams at larger organizations. You're respected. The CIO speaks so highly of
- 45:43
- Unidentified speaker (UNKNOWN): you.
- 45:44
- Unidentified speaker (speaker_1): People will listen to you if you say something. Step up and say something, right? I want to just share my findings on my experience around this. The degree of which leadership has decimated or hollowed out data architecture teams and related data management teams has been leaving, it leaves myself and my colleagues aghast. It's it's shocking. It's
- 46:04
- Unidentified speaker (speaker_1): just always mouth dropping, and I hear it all the
- 46:06
- Unidentified speaker (UNKNOWN): time. So,
- 46:08
- Unidentified speaker (speaker_1): how can leadership continue to ignore the need for well-architected high-quality data when early returns from AI investments have suffered due to data limitations? You got McKinsey telling you one thing, you've got uh you know, pretty much agreement from these uh, you know, what's out there in terms of the need for data, especially. with AI coming
- 46:28
- Unidentified speaker (speaker_1): into play. And it continues to get ignored. And I just want to say in a future podcast, I will be dealing specifically with data as a focal point for the conversation. So not only are organizations not making data a priority, but there are false barriers blocking organizations from achieving these goals. These barriers involve
- 46:48
- Unidentified speaker (speaker_1): perceived security constraints, which can be dealt with through technology, data integration, where one business unit thinks it owns its data and it can't be shared with any other organization or business unit.
- 47:02
- Unidentified speaker (UNKNOWN): And
- 47:03
- Unidentified speaker (speaker_1): it certainly can't be integrated. And then ineffective cross-business unit cooperation. We talked about that with uh The silos and holistic challenges and so on.
- 47:12
- Unidentified speaker (UNKNOWN): The
- 47:12
- Unidentified speaker (speaker_1): biggest issue is that the data gaps. there's data missing. And if you don't think so, take a look at a good business architecture, take a look at the information map and see if you've got all the data associated with all the business objects identified in the business architecture. My guess is you do not. And when you realize
- 47:32
- Unidentified speaker (speaker_1): you do not, you will realize what's missing. And because it's missing, technologists have to go through extraordinary hoops
- 47:42
- Unidentified speaker (UNKNOWN): to
- 47:42
- Unidentified speaker (speaker_1): accommodate those gaps. What's an example? Well, if you don't have data that represents uh work tasks, work items or tasks, work queues that are assigned to stakeholders, all of which has to be reflected in your data, events and state tracking that is associated
- 48:02
- Unidentified speaker (speaker_1): with all those data elements. When you don't have those elements, what do you do? You code business process flow-based diagrams and you turn that into code. If it's data focused and data-based, and you take care of those gaps, and you clean up the architecture and you deal with it, you clean up
- 48:22
- Unidentified speaker (speaker_1): fragmentation,
- 48:24
- Unidentified speaker (UNKNOWN): now
- 48:24
- Unidentified speaker (speaker_1): you can employ a data. data-oriented or data-based approach to getting work done that doesn't rely on a flow-based approach. I covered this in an earlier podcast this season, so you can go back and take a look at
- 48:37
- Unidentified speaker (UNKNOWN): it. But
- 48:38
- Unidentified speaker (speaker_1): that's one of the things data can do for you. And if you do that, your code footprint will decrease dramatically.
- 48:46
- Unidentified speaker (UNKNOWN): So
- 48:46
- Unidentified speaker (speaker_1): if we keep doing things the old ways and we keep ignoring the data and we keep allowing these gaps to occur, we're going to end up with the same problems we've got today, only it'll be five or ten years from now, and it'll be with new technology.
- 48:59
- Unidentified speaker (UNKNOWN): So
- 48:59
- Unidentified speaker (speaker_1): those challenges have to be addressed. There are other headwinds facing these organizations, but um, you know, the ones that care, I guess many headwinds, and the ones that still care are the ones that are paying attention, and then the ones that ignore it because of the headwinds are gonna are going to be problematic. So, how do we address this?
- 49:17
- Unidentified speaker (UNKNOWN): Well,
- 49:18
- Unidentified speaker (speaker_1): strategy execution stage two assess the business impact, identifies the business information impacts that should be the focus of a viable solution, which includes data targets. And if the information concepts from the business architecture are identified as problematic, that should ripple into the data side. And if the data doesn't
- 49:38
- Unidentified speaker (speaker_1): represent those information concepts, that's going to be a big wake up call. So, first of all, stop skipping over the impact assessment stage. It's going to tell you where you need to invest in data.
- 49:48
- Unidentified speaker (UNKNOWN): And
- 49:48
- Unidentified speaker (speaker_1): it's going to give you some indicators as to what you need to do to invest in there. Stage three, articulating the or architecting the business solution,
- 49:57
- Unidentified speaker (UNKNOWN): or
- 49:57
- Unidentified speaker (speaker_1): essentially establishing the future state, also includes specific tasks to formalize data architecture. based on business goals and objectives. In stage three, architects should ideally be delivering a business architecture-driven conceptual data model and logical data model.
- 50:13
- Unidentified speaker (UNKNOWN): And
- 50:13
- Unidentified speaker (speaker_1): if you use other patterns or other modeling perspectives, that's fine. But you should be delivering those and related standards, requirements, and constraints. These data models will form the foundation for solution deployment and the physical data. models necessary for implementation. When leadership adopts the five-stage strategy execution framework with
- 50:33
- Unidentified speaker (speaker_1): a focus on defining target state, data architecture, and design, the results serve as a basis for successful strategy execution and solution deployment. In the absence of the work that goes on in this stage three, architecting the future state, deployment teams will end up building bottom-up. narrowly defined point-in-time data models that
- 50:53
- Unidentified speaker (speaker_1): fail to integrate and
- 50:55
- Unidentified speaker (speaker_1): interoperate with other new and existing software deployments. More silos, more bottom-up, no top-down, no holistic approach, no cohesive set of information that you can work from. This has to stop. You've got to make the investment. You've got to make the top-down investment. And
- 51:15
- Unidentified speaker (speaker_1): until you shift your culture to a data culture, which apparently is an issue, and start investing in data with all these prerequisite sort of items that you need to work on, you're going to keep suffering these issues. And data is going to undermine your AI work. It's going to continue to undermine your AI work
- 51:35
- Unidentified speaker (UNKNOWN): as
- 51:35
- Unidentified speaker (speaker_1): long as you keep ignoring them.
- 51:37
- Unidentified speaker (UNKNOWN): So
- 51:37
- Unidentified speaker (speaker_1): I think data education. at every level has to be the focus for leadership to reset investment priorities. Deadly pattern number seven business strategy is captive to technological immaturity. I think there's probably a few people who would maybe disagree, but I think most people would agree with this particular one.
- 51:55
- Unidentified speaker (UNKNOWN): The
- 51:56
- Unidentified speaker (speaker_1): previously cited statistics regarding two-thirds of IT spending being wasted on uh being wasted are a strong indicator.
- 52:03
- Unidentified speaker (UNKNOWN): uh,
- 52:04
- Unidentified speaker (speaker_1): at least to me, that an organization's strategies are stymied or being held captive by its inability to adopt and maximize the use of new technologies.
- 52:12
- Unidentified speaker (UNKNOWN): And
- 52:12
- Unidentified speaker (speaker_1): this includes AI.
- 52:14
- Unidentified speaker (UNKNOWN): So
- 52:14
- Unidentified speaker (speaker_1): my most recent podcast focus on dynamic value stream realization and leveraging business stakeholder definitions as a basis for integrating AI agents into those value streams
- 52:25
- Unidentified speaker (UNKNOWN): to
- 52:25
- Unidentified speaker (speaker_1): address an element of where. AI can play a role in future state architecture deployments. But again, those are based on a formal architecture, a rigorously formed architecture that you can use as a baseline for dynamic value stream realization, where you're automating the value stream
- 52:45
- Unidentified speaker (speaker_1): in real time,
- 52:47
- Unidentified speaker (speaker_1): and you're taking and turning the stakeholders associated. with that with AI agents. So you can go back and take a look at those podcasts.
- 52:56
- Unidentified speaker (UNKNOWN): The
- 52:56
- Unidentified speaker (speaker_1): reality is that adoption and deployment of leading edge technology are not strong suits for many organizations as they struggle to deploy new technologies, even as the majority of in-house application systems remain locked in older technologies. Organizations have been putting their collective heads in the sand for decades regarding these technologies. One example. software deployments leveraging
- 53:16
- Unidentified speaker (speaker_1): new languages and technologies still tend to rely on procedural design and coding paradigms that were introduced decades ago, essentially recreating tomorrow's legacy systems. And very important, those new technologies and new systems are relying on the older systems that I've been talking
- 53:34
- Unidentified speaker (UNKNOWN): about.
- 53:35
- Unidentified speaker (speaker_1): So, a side question of this is do we really believe that the level of maturity of today's average IT organization is up to building a cohesive plan to leverage these new technologies when they've taken little action against their existing portfolios? I wonder, I hear people that are saying, oh, we're sending these people over to uh agentic AI
- 53:54
- Unidentified speaker (speaker_1): class. It's like these people need to go to other classes before they go to agentic AI classes, right?
- 54:02
- Unidentified speaker (UNKNOWN): So,
- 54:03
- Unidentified speaker (speaker_1): how do we handle this technology challenge? First, consider how organizations can avoid creating tomorrow's legacy systems today, which is often based on the pension for deploying teams using ineffective, outdated software analysis and design techniques. Second, determine how you can integrate the couple and reduce dependence on poorly architected legacy systems. There needs to be a
- 54:23
- Unidentified speaker (speaker_1): plan around those. The impact assessment stage of strategy execution, not only focus focuses on where technologies need to be invested in, but it also focuses on areas where you can probably find things that can be retired if you can deploy a target state, a future state.
- 54:39
- Unidentified speaker (UNKNOWN): So
- 54:40
- Unidentified speaker (speaker_1): addressing these two factors while leveraging formal architecture disciplines will take you a long way to Of reversing the trends of technology out of performance.
- 54:48
- Unidentified speaker (UNKNOWN): The
- 54:49
- Unidentified speaker (speaker_1): other way to address the new AI tech. technology that so many companies are investing in is to leverage formal architecture. And I will say this over and over again, and I have lots of ways where I'm explaining why and how you should leverage formal architecture as a baseline for deploying AI, including, by the way, dynamic value stream
- 55:08
- Unidentified speaker (speaker_1): realization and using the stakeholder mass masks from business architecture for defining AI agents and other types of
- 55:14
- Unidentified speaker (UNKNOWN): things.
- 55:15
- Unidentified speaker (speaker_1): things. But you want to start with the business architecture as a basis for defining how to maximize the value of these new technologies. The business architecture, everything stems from there. That's what's being used end-to-end in all five stages. And don't let anybody tell you business architecture is not used in stage five. All five stages of strategy
- 55:34
- Unidentified speaker (speaker_1): execution. The unifying message is. that you have a five-stage strategy execution framework,
- 55:42
- Unidentified speaker (UNKNOWN): and
- 55:43
- Unidentified speaker (speaker_1): you want to make sure that that framework is supported by a well-defined principled business architecture. And that you follow that stage work through that stage, the stage work through. So you don't skip impact assessments, you don't skip target state, you make those investments up front.
- 56:01
- Unidentified speaker (UNKNOWN): You
- 56:01
- Unidentified speaker (speaker_1): then define your initiative. initiatives around those well-honed perspectives, and you're going to get better results at the end.
- 56:10
- Unidentified speaker (speaker_1): Some people say slow down to hurry up. So instead of getting stuck in three or four or five times the initial investment perspective or the initial time estimates for your back-end initiatives, you're delivering those in an effective way, but you're spending the time. time up front, making the investments
- 56:30
- Unidentified speaker (speaker_1): necessary to ensure that those are going to deliver value. So the whole sort of premise with addressing these whole deadly patterns is based on following the framework, doing what you need to do, taking my other recommendations that I've hit Pit on today, and moving through systematically based on a formal
- 56:49
- Unidentified speaker (speaker_1): architecture.
- 56:50
- Unidentified speaker (UNKNOWN): By
- 56:50
- Unidentified speaker (speaker_1): the way, on business architecture, if someone working in their basement sends you a capability map, have the wherewithal to determine it's just another piece of noise. I tried to be polite about that, that needs to be ignored. And my last point:
- 57:04
- Unidentified speaker (UNKNOWN): stop
- 57:04
- Unidentified speaker (speaker_1): thinking that architecture is going to slow you down. It's going to speed you up. It's going to lead you to a path that's going to deliver value. Some people don't want to hear about it. Usually those are people who don't. understand
- 57:15
- Unidentified speaker (UNKNOWN): it.
- 57:16
- Unidentified speaker (speaker_1): And if you don't and and and I get it, I I get that enterprise architects have probably been their own worst enemy over the last couple of decades. I get it. I understand that. Uh my co-author Charlie Bowman has a great book on uh the confessions of an enterprise architect, if you want to take a read on that one. And I get that. But that
- 57:36
- Unidentified speaker (speaker_1): doesn't doesn't mean you don't need to have architecture to be successful with strategy execution and initiative deployment. If it's not going well, figure it out. If nobody believes you that it's not going well, collect statistics over the last three to five years on how well you've been doing with deploying business objectives and
- 57:57
- Unidentified speaker (speaker_1): goals. And also meeting your initiative targets. And tell your story, support it with facts, bring it to the table. And then when somebody says, okay, what do you want me to do about that? What you say is, well, let's break it down. Let's go through the
- 58:16
- Unidentified speaker (speaker_1): end-to-end strategy execution framework, what pieces you need to use, and how you can go through and nullify these seven deadly patterns, which are undermining. the work that you're trying to
- 58:28
- Unidentified speaker (UNKNOWN): do. We're
- 58:29
- Unidentified speaker (speaker_1): going to talk about in a future podcast a lot about data. And that's going to be good. And we're going to have some guests on to do that. And then we'll continue our story and discussion for this season. You've been listening to the Strategy Execution podcast with William Ulrich, co-author of End-to-End Strategy Execution from Inception
- 58:49
- Unidentified speaker (speaker_1): through Solution Deployment. You can send your comments and questions to my email, W M M U L R I C H
- 58:59
- Unidentified speaker (speaker_1): at T S G, like Tom Sam George, Consulting Inc. That's TSG Consulting INC, TSG Consulting Inc.com. You can check out the podcast at voiceamericamedia.com VoiceAmerica Media.com or subscribe to it on Apple Podcasts, Spotify, or wherever. you get your podcasts. You can get our book on Amazon.com or other
- 59:19
- Unidentified speaker (speaker_1): outlets where you can buy your books. Thanks for joining me today, and I will see you next week.
- 59:27
- Unidentified speaker (speaker_0): Thanks for listening to today's episode. Join William Ulrich every Wednesday on the Voice America Business Channel as he continues uncovering the truth behind strategy execution and how to. finally get it right. See you next week.
More from End-to-End Strategy Execution
Synthetic Stakeholders in the Age of AI
Episode discussion: Business architecture experts define synthetic stakeholders as AI agents and advocate for formal governance to manage AI deployment risks.
Speakers’ claims: William Ulrich and Speaker 1 define 'synthetic stakeholders' as AI agents acting as autonomous software systems within business architecture frameworks. They argue that traditional deterministic systems and flow-based process models are too rigid for AI, necessitating dynamic rules-based routing and state machines. The speakers warn against unmanaged AI deployment, citing rising AI-related layoffs and the risks of 'shadow systems' like spreadsheets. They emphasize that business units, not IT, should manage AI agents, with strict security privileges and formal documentation to prevent chaotic 'AI agent wars'.
Dynamic Value Stream Realization: Streamlining the Customer Experience
Episode discussion: William Ulrich argues for using Business Architecture Guild models to bridge the gap between executive perception and customer reality.
Speakers’ claims: William Ulrich highlights a significant perception gap where executives believe brand loyalty is increasing, while customer data shows many are leaving due to poor experiences. He advocates for using formal Business Architecture value streams over informal process maps to better align customer journey stages with organizational capabilities. Ulrich recommends leveraging pre-tested reference models from the Business Architecture Guild to avoid the time-consuming task of building capability maps from scratch or relying on AI. He explains how linking product entitlements to these value streams allows for rigorous verification of customer rights and service delivery. Finally, he proposes transforming static architecture into dynamic, automated value streams powered by AI agents.