End-to-End Strategy Execution

William Ulrich argues for using Business Architecture Guild models to bridge the gap between executive perception and customer reality.

53 min Listen to the original Episode page
Business ArchitectureCustomer ExperienceValue StreamsAI AgentsProcess ImprovementGuild Reference ModelsProduct Entitlements

Summary

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.

Key takeaways

  1. 1
    Touchpoints are formally defined in customer journey maps. They're usually tied to an organization's goods, but more importantly and more broadly, its services, which collectively represent the entire customer experience.

    William Ulrich · 3:21

  2. 2
    That paper laid a foundation for connecting the empathetic perspective covered during customer journey analysis with the architectural rigor framed through the lens of the value stream. That white paper formally aligned or formally defined value stream stages with customer journey maps.

    William Ulrich · 6:47

Episode sections

  1. 0:24 – 1:31

    Introduction and the Customer Loyalty Gap

    William Ulrich introduces the topic of dynamic value streams and customer experience, highlighting a significant gap between executive perception and customer reality regarding brand loyalty. He notes that while executives believe loyalty is increasing, customer data suggests otherwise, with many customers leaving due to poor experiences.

  2. 1:31 – 6:47

    Customer Experience Frameworks and Journey Maps

    The speaker defines customer experience through touchpoints and journey maps, which track stages like awareness, purchase, and retention. He clarifies that 'customer' is an external term encompassing patients, constituents, or members depending on the industry, and distinguishes them from internal employees.

  3. 6:47 – 14:27

    Business Architecture vs. Informal Processes

    Ulrich contrasts formal business architecture value streams with informal 'processy' constructs found in Lean Six Sigma or Agile. He argues that formal value streams are state-based and linked to capabilities, whereas informal processes lack the rigor needed for effective customer experience improvement.

  4. 14:27 – 19:18

    Leveraging Guild Reference Models

    The speaker recommends using Business Architecture Guild reference models to jumpstart capability mapping rather than building from scratch or relying on AI to generate maps. He warns that creating these maps manually or via AI can take months or years, whereas pre-tested models are available for individual members.

  5. 19:18 – 26:20

    Value Stream Dual Perspective and Stages

    Value streams are described as a core business architecture domain representing both value consumption (customer view) and value creation (internal view). They decompose into stages, such as 'validate customer,' which deliver specific value items and require enabling capabilities to progress.

  6. 26:20 – 32:51

    Product Entitlements and Capability Mapping

    Product entitlements, which define what a customer is entitled to do with a product, are linked to value stream stages and enabling capabilities. This connection allows solution architects to verify that software services and AI agents correctly support the customer's contractual rights and experience.

  7. 32:51 – 33:50

    Stakeholder Integration and Automation

    The discussion concludes by linking value streams to stakeholder maps, noting that stakeholders (including AI agents) engage at specific stages. Ulrich emphasizes that capabilities lie dormant until required to deliver value, at which point they are automated by software and data.

  8. 33:50 – 52:41

    Dynamic Value Stream Realization and AI Agents

    William Ulrich introduces the concept of transforming static business architecture value streams into dynamic, automated constructs. He outlines a framework where value streams replace traditional customer journey maps by directly incorporating customer touchpoints and capabilities, and proposes using AI agents to act as stakeholders within these automated streams.

Claims worth verifying

Over half of surveyed customers say they stopped using a product or buying a brand because of a bad experience.

William Ulrich ·1:51

How to verify: Cite the specific survey referenced by the speaker in his September 30th podcast or the source data he uses for that statistic; verify via the podcast archive or cited primary research. For recent events, verify 2026-08-04 through 2026-11-04. Use another period only when the speaker explicitly names it.

Only four out of ten customers said that their brand loyalty had grown over the years.

William Ulrich ·1:51

How to verify: Verify against the same survey data cited in the previous claim; check the source of the loyalty statistics mentioned in the September 30th podcast. For recent events, verify 2026-08-04 through 2026-11-04. Use another period only when the speaker explicitly names it.

Nine out of ten executives think that customer loyalty has increased during that same time frame.

William Ulrich ·1:51

How to verify: Verify against the executive perception data from the same survey source cited above; check for the specific study comparing executive vs. customer sentiment. For recent events, verify 2026-08-04 through 2026-11-04. Use another period only when the speaker explicitly names it.

The Business Architecture Guild published a paper titled 'Business Architecture and the Customer Experience: A Comprehensive Approach.'

William Ulrich ·6:47

How to verify: Search the Business Architecture Guild website or library for this specific white paper title and publication date. For recent events, verify 2026-08-04 through 2026-11-04. Use another period only when the speaker explicitly names it.

The Business Architecture Guild has 11 reference models covering industries like transportation, manufacturing, government, financial services, and insurance.

William Ulrich ·14:49

How to verify: Check the Business Architecture Guild membership resources or reference model catalog to confirm the count and industry coverage. For recent events, verify 2026-08-04 through 2026-11-04. Use another period only when the speaker explicitly names it.

The book 'End-to-End Strategy Execution' is co-authored by William Ulrich and Charles Bowman.

William Ulrich ·17:36

How to verify: Verify authorship and title on Amazon.com or the publisher's website. For recent events, verify 2026-08-04 through 2026-11-04. Use another period only when the speaker explicitly names it.

Value stream is one of 10 core domains in business architecture.

Unidentified speaker (UNKNOWN) ·19:22

How to verify: Consult the Business Architecture Body of Knowledge (BizBOK Guide) to confirm the number and names of core business architecture domains. For recent events, verify 2026-08-04 through 2026-11-04. Use another period only when the speaker explicitly names it.

Product entitlements are part of the product domain of business architecture and are formally modeled.

William Ulrich ·26:20

How to verify: Check the BizBOK Guide or Business Architecture Guild reference models for the 'Product' domain and its definition of 'Product Entitlements.' For recent events, verify 2026-08-04 through 2026-11-04. Use another period only when the speaker explicitly names it.

The book 'End-to-End Strategy Execution' contains an appendix detailing business architecture domains and a Chapter 6 on customer experience and product design.

William Ulrich ·25:40

How to verify: Verify the table of contents and chapter titles in the published book 'End-to-End Strategy Execution.' For recent events, verify 2026-08-04 through 2026-11-04. Use another period only when the speaker explicitly names it.

Do your own research

  • Verify the 'Business Architecture and the Customer Experience: A Comprehensive Approach' publication from the Business Architecture Guild for the specific methodology cited.
  • Check the Business Architecture Guild's website for the 11 available reference models and their specific industry applications.
  • Review the 'quality assurance checkpoint tool' mentioned to assess the rigor of the pre-tested models.
  • Compare internal executive surveys on brand loyalty against actual customer churn data to validate the claimed perception gap.
  • Evaluate existing Lean Six Sigma or Agile process maps against the Business Architecture Guild's criteria for state-based navigational rigor.
  • Assess the current state of AI agent integration in value streams to determine if the 'dynamic realization' framework is already partially implemented.
  • Review product entitlement documentation to see if it is formally modeled in business architecture or only loosely defined in legal terms.
  • Investigate the specific capabilities linked to value stream stages to ensure they are automated and active rather than dormant.
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
William Ulrich: Welcome to the Strategy Execution Podcast on VoiceAmericamedia.com. I'm your host, William Ulrich. Today's podcast is titled Dynamic Value Stream Realization, which I subtitled as Streamlining the Customer Experience. We're going to cover both today.
0:40
Unidentified speaker (UNKNOWN): I
0:40
William Ulrich: chose this topic because I think that leadership continues to underserve customers, as I noted in my September 30th podcast. In this episode, I want to strive to bring together three important focal points: the customer experience, formally defined value streams, and automation, which will include
1:00
William Ulrich: AI. If organizations can collectively maximize these three disciplines, they're more likely to build and maintain a stronger customer brand and brand loyalty, and ideally to see the cost of doing business reduced based on high degrees of automation. That's kind of a given if we're putting in AI.
1:20
William Ulrich: We're always looking for cost adjustments and cost realization. But the more important thing I want to cover today is not about cost, it's about customers, and it's about bringing value to those customers.
1:31
Unidentified speaker (UNKNOWN): So
1:31
William Ulrich: I want to begin by laying out my customer perspective, and then we'll move on to discuss dynamic value stream realization. So, in my September 30th podcast, it was titled, Your Customers Are Not Happy Moving from Denial to Action. In that episode, I highlighted the fact that over half of surveyed
1:51
William Ulrich: customers say they stopped using a product or buying a brand because of a bad experience. Only four and ten customers said that their brand loyalty had grown over the years. Yet nine and ten executives think that customer loyalty has increased during that same time frame, which is more than a 50-point gap between the
2:11
William Ulrich: executive perceptions of customer loyalty and the reality of the customer experience today. I mentioned this last data point because it's possible
2:22
Unidentified speaker (UNKNOWN): and
2:22
William Ulrich: maybe even likely that your organization's leadership may not see a pressing the ET. need to invest more seriously in improving the customer experience. And believe me, you're not alone. We see this in practice every day, where the focal point is on collecting the money as opposed to delivering value to the customer.
2:41
Unidentified speaker (UNKNOWN): So
2:41
William Ulrich: this is, of course, a mistake, but my message today is aimed at those organizations that do take improving the customer experience seriously, or at least give it some degree of lip service so that you have a foot in the door that you can open up to have that conversation with leadership. These organizations tend to
3:01
William Ulrich: leverage customer surveys and customer experience design to assess and improve the customer experience. That sounds pretty standard type of thing. Customer experience design focuses on what what's commonly called a touch point, which is a point of engagement with an organization that shapes what a customer feels
3:21
William Ulrich: and thinks about the organization. And not just the organization as a whole, but its products, its people, and its overall brands. It's one of the reasons customers stay loyal to a brand, but it can also be a reason the customers move on to the competition. Touch points are formally defined in customer journey
3:41
William Ulrich: maps. So if you read the literature on customer journey maps, you'll see that touch points are a fairly standardized thing. They're usually tied to an organization's goods, but more importantly and more broadly, its services, which collectively represent the entire customer experience. If you're a service-only company like a bank or an
4:01
William Ulrich: insurance company,
4:02
Unidentified speaker (UNKNOWN): then you're
4:02
William Ulrich: your focal point will be entirely on service. If you're a manufacturing company, you still provide services, same with retail, but those services are alongside of the hard goods that you deliver.
4:17
Unidentified speaker (UNKNOWN): Now,
4:17
William Ulrich: not every organization uses the term customer. I want to make sure that everybody's included in this conversation. I'm not leaving people out. Healthcare providers, for example, use the term patient.
4:28
Unidentified speaker (UNKNOWN): If
4:29
William Ulrich: I work for a government, it's probably going to be something like constituent. And if I'm in a nonprofit association, I might use the term member or beneficiary, all of which are essentially our customers. So while you may not use the term customer, they are your customers.
4:47
Unidentified speaker (UNKNOWN): And
4:47
William Ulrich: just to remind listeners, the customer is always defined as an external party, a third party. There are no internal customers. And if you need to understand more about that, you can listen to some of my prior podcasts done on customers, specifically the uh one I referred to previously.
5:05
Unidentified speaker (UNKNOWN): So
5:05
William Ulrich: those individuals that work internally with us, our colleagues, are also called human resources.
5:13
Unidentified speaker (UNKNOWN): And they
5:13
William Ulrich: can be contractors. contracted or employees or any combination of the above.
5:18
Unidentified speaker (UNKNOWN): So
5:19
William Ulrich: one tool or framework that organizations use to evaluate the customer experience is called the customer journey map. Many of you are familiar with that. Customer journey maps are designed to track every step, interaction, and emotional experience a customer has with an organization and its respective brands and products. It's a good thing. Not
5:38
William Ulrich: everybody uses them, but organizations that are very formal about this do use them. And they have customer experience teams that focus on those. Journey maps are comprised of stages that cover awareness, consideration, purchase, retention, and advocacy for their brands.
5:55
Unidentified speaker (UNKNOWN): So
5:55
William Ulrich: the analysis is done around those lines of thinking.
5:58
Unidentified speaker (UNKNOWN): And
5:59
William Ulrich: those include touch points where the customer interacts with an organization.
6:03
Unidentified speaker (UNKNOWN): The
6:03
William Ulrich: journey map seeks to expose what the customer is feeling and thinking, which can include pain points such as confusion, delays, and more. We've all probably lived through a few of those.
6:14
Unidentified speaker (UNKNOWN): From
6:15
William Ulrich: the survey I cited earlier, it's clear that many organizations are either not tracking the customer experience, they're ignoring what they discover when they do discover things in the customer experience, or just maybe.
6:27
William Ulrich: they have challenges in terms of translating what they've learned during their customer journey analysis into something that's rigorous enough to address the root cause of any issues that customers may encounter. So I think many of you who are familiar with my podcast know where I'm going. To talk about architecture.
6:47
William Ulrich: For more guidance on this, the Business Architecture Guild published a paper a few years back, and it was titled Business Architecture and the Customer Experience: A Comprehensive Approach. Good paper. That paper laid a foundation for connecting the empathetic perspective covered during customer journey analysis with the
7:07
William Ulrich: architectural rigor framed through the lens of the value stream. That white paper formally aligned
7:15
William Ulrich: or formally defined value stream stages with customer journey maps. So they connected the two stage stages, that's where they connected, and the touch points as well.
7:26
Unidentified speaker (UNKNOWN): The
7:26
William Ulrich: approach was later incorporated into the guild's body of knowledge called the BizBach Guide. Some of you may be familiar with it. Others can check out the Business Architecture Guild for more information. The intention was to align what the customer journey. map captured in terms of the customer experience with the formal architecture defined in value streams. Once the
7:46
William Ulrich: value stream connections were established, those domain elements can follow the path out to capabilities, which enable value stream stages, and I'll get into that more later. And information concepts, which capabilities use to deliver the outcomes that they do, the to work that they
8:02
Unidentified speaker (UNKNOWN): do.
8:02
William Ulrich: And from there, the connections between capabilities to technology and to the information concepts to data and so on. There's other elements, but I'll leave those on the side for
8:12
Unidentified speaker (UNKNOWN): now.
8:13
William Ulrich: Some listeners may assume that they already have value streams.
8:17
Unidentified speaker (UNKNOWN): And
8:17
William Ulrich: they must be good to go, right? Oh, yeah. Somebody mentioned to me, for example, the other day in one of those meetings we have about scaled agile or safe that uh they have value streams. So I'll just assume my people have that taken care
8:32
Unidentified speaker (UNKNOWN): of.
8:33
William Ulrich: Or maybe I work with my lean six sigma teams and they've got value streams. Or maybe you've got this concept of the high level process and you pull some down off the internet, so you must be covered. You have to be good to go. You've got a PowerPoint presentation that says we have these high high-level level processes, and that's going to take care of everything.
8:52
Unidentified speaker (UNKNOWN): Let
8:52
William Ulrich: me be clear: I'm not talking about business processes or quasi-value streams that surface from time to time in other business practices. These constructs, in the cases that I've seen, lack the rigor incorporated into formal business architecture. In addition to lacking the rigor, they also tend to have a process orientation.
9:13
William Ulrich: Business architects, when they start to see a value stream become more flow-based, we say that that's becoming processy. It's a term we use. Some may argue that no discipline is implemented with the rigor intended by its forerunners. Fair enough, right? That's true for everything.
9:33
William Ulrich: But it's also true that constructs like so-called high-level business processes are not based on foundational well-tested principles or backed by a formal body of knowledge. They're just things, things that we sometimes run into on the internet or things that what the latest consultant came in and told us about.
9:51
Unidentified speaker (UNKNOWN): The
9:51
William Ulrich: business architecture discipline, on the other hand, as both a discipline and a practice, is based on formal guidelines and principles.
10:01
Unidentified speaker (UNKNOWN): And the
10:01
William Ulrich: value streams are part of the overall business architecture discipline. Not an outlier, not an add-on. It's not like, well, I have this architecture framework, I better add value streams because some people are asking for them. They're front and center as uh part of the glue that holds the business architecture in place.
10:20
Unidentified speaker (UNKNOWN): And
10:20
William Ulrich: business architecture value streams, uh, particularly as are defined by the business architecture guild, are unique constructs that differ from property. process oriented or lean value streams or scaled agile value streams, which might be organized by development teams, often within silos. And business architecture value streams are never, repeat, never
10:40
William Ulrich: siloed in practice or in theory. They also differ from what the process communities term the high high-level level process.
10:47
Unidentified speaker (UNKNOWN): So
10:47
William Ulrich: all of these structures, some of which predate business architecture's formal value. stream definition and some of which came later, share some commonalities.
10:55
Unidentified speaker (UNKNOWN): So
10:55
William Ulrich: first, they lack the state-based navigational rigor of business architecture value streams. And I'll get a little more detail into that as we go.
11:04
William Ulrich: Business architecture value streams rely on capabilities to set object states that allow the value stream to complete tasks
11:11
Unidentified speaker (UNKNOWN): as
11:11
William Ulrich: it navigates its way towards delivering its value. proposition. In addition, while some may use the term value stream, they're largely flow-based by nature. And because they are not connected to a formally defined object in state-based discipline, centered on capabilities, they don't really represent the rigor you need
11:31
William Ulrich: that's required to do effective improvements to your customer experience.
11:36
Unidentified speaker (UNKNOWN): All
11:36
William Ulrich: right, so now we've talked about the formal value stream and how it's connected to business architecture, and we'll get into more of that in the next segment. We've also talked about customer experience and customer journey maps. And right now, those are essentially separate
11:56
William Ulrich: disciplines, and they're being executed normally by separate teams. You may or may not have. a customer experience team. You may or may not have a business architecture team. You may not have either, or you may have both. And if you have both, I'm going to take a guess that there's a good
12:15
William Ulrich: possibility that they're not talking to each
12:18
Unidentified speaker (UNKNOWN): other.
12:18
William Ulrich: Having worked in industry with different organizations that have customer experience teams and working with business architecture teams in those same organizations, I can tell you that one of the things that we've done is from a business architecture perspective, and this is for all of those folks out there who carry that
12:38
William Ulrich: title or that role, is to seek out the customer experience teams and start working with them and seeing how you can help them. More often than not, and it depends and it varies, the customer. experience team does have executive support and executive buy-in. And in fact, there's an
12:58
William Ulrich: understanding of, at least with more advanced organizations in this area, that they want to improve the customer experience. So that the customer experience team does That experience design, which we're going to get into a little bit more later, and also doing analysis on the customer experience so they know where to improve it,
13:18
William Ulrich: they can be quite sophisticated. When that is in place and there is executive buy-in, one of the things that the business architects can do is to approach the business, the customer experience teams, and ask them if they would like to see the work that they do recognized or
13:39
William Ulrich: realized more favorably and in a more formal way from an architecture perspective. And then sit down and explain values streams to them and how they fit together. And you can grab a copy of the guild paper from the website and walk them through that and show them that as well.
13:56
Unidentified speaker (UNKNOWN): So
13:57
William Ulrich: what you can do there is start to bring them into the fold, and that's a really critical and important. step here because what I'm going to talk about today is bringing these disciplines together in a more formal way. And in order to do that, you're going to need to get some buy-in from some of the folks in the customer experience
14:16
William Ulrich: area. That includes, by the way, experience design, which I'm going to meld with product design, and we'll talk more about uh product entitlements and what roles they play as well.
14:27
Unidentified speaker (UNKNOWN): Uh
14:27
William Ulrich: so
14:29
Unidentified speaker (UNKNOWN): a
14:29
William Ulrich: word about the guild reference models because I did reference the fact that uh in in practice, guild reference models are one of the things that support business architecture as a as a practice in the real world. The reference models from the business architecture guild, which which number, I believe, 11, eleven, not all of them have been
14:49
William Ulrich: formally released, but they cover a number of different industry sectors: transportation, manufacturing, uh, government, financial services, insurance, so on.
14:57
Unidentified speaker (UNKNOWN): Uh they
14:58
William Ulrich: cover a number of areas. So if you actually buy into and and and obtain those, and you just have to be an individual member to get those to use them within your organization, don't share them. But within your organization, you can use those for your business architecture and jumpstart it.
15:13
Unidentified speaker (UNKNOWN): Uh
15:13
William Ulrich: those are all built. to formal principle and practice. They are tested actually with a quality assurance checkpoint tool that determines that they are aligning to the formal body of knowledge's best practices. So if you do pursue business architecture, there's no absolutely no reason to start start
15:33
William Ulrich: from scratch. There's no reason, in my view, in any industry to start from scratch. Uh the the we talk about, oh, I'm gonna have to build a capability map. No, you don't. You you go and you get these reference models. Pick the one that's either aligned to your industry or pick the two that align to the two things you do in your business model,
15:53
William Ulrich: and and then begin to customize and modify it, which is what you can do in-house. So just because it's not an exact fit, it has nothing to do with the fact that you can't use those in- practice. When I hear people talking about, oh, I'm going to use AI to build a capability map, I kind of cringe because it's like, first of all, it it's going to take you weeks or
16:12
William Ulrich: months to get to get back into place, unless you've got some very unusual AI to get in place what they've done with a lot of these capability maps, these value streams, these information maps, uh the stakeholder maps, the organization maps. and in some cases the product maps that come with these reference models. They will take not just months, but
16:32
William Ulrich: potentially years out of the work you need to do to set up a business architecture.
16:36
Unidentified speaker (UNKNOWN): All
16:36
William Ulrich: right, so I wanted to just put a plug-in for those. Again, you can join the guild as an individual, which is which is cheap on any day, and download those models and use them in your own company uh as you see fit, uh, customizing them as you go. There is no reason to rely on 10 or 12-year-old quasi-capability maps that
16:56
William Ulrich: don't have value streams or anything else associated with it when you can get rigorous defined capability maps and the rest of business architecture, including value streams, through a simple download. So, with that, we're going to take a short break. We're going to come back to value streams. I want to explain them in a little more detail. which is going to be
17:15
William Ulrich: extremely important because we're going to do some things with value streams that may be new for a lot of folks, two things, in fact, that are new. So we'll pick that up in our next segment. You're listening to the Strategy Execution Podcast with William Ulrich, co-author of End-to-End Strategy Execution from Inception Through Solution Deployment.
17:36
William Ulrich: You can get our book at Amazon.com or other outlets. We'll be right back after a short break.
17:48
Unidentified speaker (UNKNOWN): The
17:49
Unidentified speaker (speaker_0): groundbreaking new book, In to End Strategy Execution. From inception through solution deployment, tackles initiative failures and wasted investments head on. Co Co-authors authors William Ulrich and Charles Bowman take readers on a guide. guided journey that not only helps leadership formulate a strategic vision, but lays the foundation
18:08
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.
18:25
Unidentified speaker (speaker_2): Follow Voice America at facebook.com forward slash voiceamerica for juicy updates from your favorite radio shows and podcasts.
18:39
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.
18:52
William Ulrich: 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, Spotify, or wherever you get your podcasts. We left off discussing formally defined value streams. So some listeners may have some background in this area, others may be
19:11
William Ulrich: unfamiliar with the nature of value stream navigation. and its role of business architecture.
19:18
Unidentified speaker (UNKNOWN): What
19:18
William Ulrich: I want to do is just give you a little background so we're all on the same page.
19:22
Unidentified speaker (UNKNOWN): The
19:22
William Ulrich: value stream represents a multifaceted business architecture domain, one of 10, by the way. So some people think, oh, I've got a capability map and I have a business architecture. You do not. You have a capability map and it's questionable as to whether it's any good. Uh, What you want to look at from a business architecture perspective are the core domains. Value
19:42
William Ulrich: stream is one of those, capabilities is one, information is one of those. And you also want to look at the extended perspectives. I'm going to cover some of these today.
19:50
Unidentified speaker (UNKNOWN): So
19:51
William Ulrich: it's really one of ten domains. Value streams concurrently represent the dual perspective, and this is what makes them unique from all pretty much all other constructs within or outside of business architecture. They represent a dual perspective of value consumption, which is from the perspective of the triggering
20:11
William Ulrich: stakeholder. It might be a customer, it could be an internal stakeholder, but it could be a customer. And one of value creation, which is everybody else's perspective. Value consumption is viewed through the lens of the triggering stakeholder, which may be a customer, as I said, or other stakeholder.
20:27
William Ulrich: value streams deliver value propositions to that stakeholder. For example, if I'm a customer and I'm signing in to transfer money from one bank account to another, that might be something that I want to do. That would be a value stream. And once that got to
20:47
William Ulrich: the end and the transaction was completed and everything was done. documented, that would be the end of the value stream. The value proposition would have been satisfied, and I as a customer would be very happy. I would like that to go with no glitches, obviously. It could also be me as a customer sending a shipment somewhere. Once it's delivered and everything
21:07
William Ulrich: is wrapped up and I've got confirmation of all that, uh then essentially the value proposition's been satisfied. So you sort of get the idea there. We'll break it down a little more, but you kind of get the uh the big picture. Value delivery, it's again, it's not restricted to customers. We can have value streams that are partner triggered. Uh and there's a lot of
21:27
William Ulrich: them that are in-house triggered. For example, a marketing executive requesting a new campaign, or even a doctor ordering a set of tests on a patient. But right now I want to focus on the customer because that's the real focal point of today's discussion. One more bit of detail to share on background, which I think is important to our
21:47
William Ulrich: topic. So please bear with me. Value streams decompose into value stream stages. So each stage delivers value value items that accrue to the value proposition. So let's take the customer signing in to transfer money from one account to another.
22:03
William Ulrich: They would need to go through a validate customer stage prior to being allowed to see or update the financial account.
22:10
Unidentified speaker (UNKNOWN): The
22:10
William Ulrich: customer's ability to proceed is a resulting value item from this stage. So the value item is, hey, I get to move on. It's accepted me. Now, sometimes you try to put your information in and it doesn't get accepted. That means you're stuck in that stage and you need you can't get out. But if it does validate you, authenticate, and authorize you, you
22:30
William Ulrich: can then move on
22:31
Unidentified speaker (UNKNOWN): and
22:32
William Ulrich: you can complete your transaction. So value creation versus value consumption is where formal architecture really comes into play. So otherwise, you're just looking at it from the customer perspective. Different pieces of value are being delivered, eventually your value proposition is satisfied. But if you take the flip side view, which again,
22:52
William Ulrich: value streams maintain both views, value streams in their respective stages are actually formal structures that are enabled by outcome-producing enabling capabilities. So we have a whole collection of capabilities associated with each value stream stage, and they deliver outcomes which collectively deliver value. So that's how they
23:11
William Ulrich: work. So if you understand that much, you've got a big jump on understanding business architecture.
23:18
Unidentified speaker (UNKNOWN): But
23:18
William Ulrich: to ensure that value streams work in practice, organizations require a principle-based capability map that business architects can use to pick and choose capabilities to enable a cross-section of value streams. So the assumption here is if I'm going to
23:32
William Ulrich: construct, uh and now you have these value streams, and I want to construct the perspective of the enabling. capabilities and how they're involved. I need to have a good capability map to draw from. I can't make them up on the fly. Believe me, trust me, you cannot make them up on the fly. You need to go through
23:52
William Ulrich: the exercise of capability mapping to get to a good capability map. You have to follow rigorous principles. And if you don't, the rest of what I'm going to be saying here today. is going to be pretty meaningless to you. So I just want to make sure that that is clear for everybody. The enabling capabilities deliver outcomes. And those
24:12
William Ulrich: outcomes will make value streams or what make value streams actionable and deliver the value being sought by the triggering stakeholders. So let's take an example.
24:20
Unidentified speaker (UNKNOWN): On
24:21
William Ulrich: the validate customer stage of a value stream, which allows a customer to transfer money from one account to another, it requires capabilities that authenticate the customer. It's called customer authentication. Capabilities to authorize the customer, it's called customer authorization, and allow financial
24:41
William Ulrich: account access, which is called financial account access management, right? And deliver other outcomes to get to the value item that lets the customer know that. they've been validated. So it's pretty straightforward.
24:54
Unidentified speaker (UNKNOWN): Um,
24:55
William Ulrich: if you just sit down, take some time, take a breath,
24:58
Unidentified speaker (UNKNOWN): get
24:59
William Ulrich: rid of the preconceived notions, and learn what object-based capability mapping is about, and outcomes are about you can put all that together.
25:07
Unidentified speaker (UNKNOWN): So
25:08
William Ulrich: once eligibility has been achieved and the initiating request, requests, the pending financial transaction and other business object states, a lot. allow for the value stream to navigate to the next stage, you can move on and do the rest of its work.
25:20
Unidentified speaker (UNKNOWN): Now,
25:20
William Ulrich: if you're new to business architecture, don't worry. Uh, if you need more insights into value stream specifics, especially in context of our discussion today, you can check out the appendix of our book, uh End-to-end Strategy Execution. Uh you can you can find that. I talked about where you can find that a little earlier. I'll talk about it again later. Uh in that appendix, uh that
25:40
William Ulrich: there's a provision for uh both new and existing practitioners uh to understand the discipline in a nutshell and get a full snapshot. And then it also breaks down each of the domains, how they fit together, um, how all the connections are made. So it's all the underlying business architecture pieces. And again, that's an
26:00
William Ulrich: appendix in our book. Uh we kept that. out of the main part of the book because we refer to business architecture in the book. But we don't want people to have to sit there scratching their heads on what we're talking about. So you can go to the appendix quickly and look things up. So prior to moving on, there's one other domain element I want to cover today regarding value streams, and it has a
26:20
William Ulrich: direct impact Act on customers,
26:22
Unidentified speaker (UNKNOWN): and
26:22
William Ulrich: that's called the product entitlement. And if you haven't, if you're not familiar with the product entitlement, it's part of the product domain of business architecture. It is a formal thing, it is formally modeled, formally defined. The guild has at least one reference model that has product entitlements laid out.
26:41
Unidentified speaker (UNKNOWN): So
26:42
William Ulrich: given their advanced nature, the average business architecture is unlikely to represent products and their corresponding entitlements in their business architecture.
26:51
William Ulrich: But if you do, great for you. If you don't, you should start taking a look at it because it's really another way to look at your organization, another way to look at capabilities and the role that they play, right? So let's let's take a let's take an example.
27:06
Unidentified speaker (UNKNOWN): So
27:06
William Ulrich: let's say a customer triggers a value stream to transfer money from one financial account to another. We introduced that earlier. This would involve a number of product entitlements. The product in this example is a checking account product.
27:18
Unidentified speaker (UNKNOWN): And
27:19
William Ulrich: the checking account product, when I sign up for the checking account, will come with a whole bunch of entitlements. It'll say that I can sign in, I can look at the account, I can change things, and so forth. I can write checks on the account, I can transfer money in, transfer money out, and so forth. Those are all entitlements.
27:36
Unidentified speaker (UNKNOWN): And
27:36
William Ulrich: they're typically formalizing the agreement that most people. probably never read, but they would be formalized when you set up your financial account. Product entitlements are geared at answering a question that begins with: as a customer, I want to,
27:52
Unidentified speaker (UNKNOWN): and
27:52
William Ulrich: then you can fill in the blanks. So
27:55
Unidentified speaker (UNKNOWN): if
27:55
William Ulrich: I'm taking our checking account example, I would say, as a customer, I am entitled. to, I'm sorry, I want to or entitled to, right? As a customer, I'm entitled to
28:08
William Ulrich: to ensure that only
28:10
Unidentified speaker (UNKNOWN): I
28:10
William Ulrich: can access the account. I would also say that as a customer, I am entitled to have the ability to see the account balance. Okay, that's an entitlement. A third entitlement would be: as a customer, I am entitled to have the ability to withdraw money from the account.
28:27
Unidentified speaker (UNKNOWN): Now,
28:27
William Ulrich: there's a whole bunch of other entitlements, and usually any given product, even a financial product, as simple as a checking account, would have probably
28:35
William Ulrich: a couple dozen or more entitlements, product entitlements associated with it. Now, why are these relevant and important? Why would I even care about these things, right? Isn't it that taken care of by somebody else? Well,
28:49
Unidentified speaker (UNKNOWN): if
28:49
William Ulrich: I can incorporate the concept. of product entitlements into architecture, I'm halfway to improving how I service the customer, right? Because now I can take action on them. So why would I want to define and associate product entitlements to value stream stages? Is the question I'm somebody's probably thinking. Well, it depends on one's role. A given solution
29:09
William Ulrich: architect, for example, might have little interest in product entitlements, right? But each of these product entitlements are enabled by a combination of capabilities. So actually, solution architects should care about product entitlements because product entitlement mapping is a cross check against the enabling capabilities that go
29:29
William Ulrich: along with the value stream that delivers those entitlements. So there's a connection, right? So you've got these value stream stages and you've got these capabilities and you've got software service design. designers and solution architects designing software services that are going to automate those capabilities. Maybe it's in AI, maybe it's not.
29:46
Unidentified speaker (UNKNOWN): The
29:46
William Ulrich: same capabilities that enable those value streams to work are the ones that satisfy the product entitlements for the customer. So as I go through and look at my value stream and I look at my stages, I said, well, what's what's the what are the entitlements? Those entitlements have certain capabilities, which I talked about. a couple minutes ago. And those capabilities will also
30:06
William Ulrich: show up
30:07
Unidentified speaker (UNKNOWN): as
30:07
William Ulrich: enabling the different value stream stages in that same value stream. So it's a closed loop. It's a closed loop. It's a very formal thing, right? And we want to understand this if we want to improve the customer experience that goes along with the entitlements that they're delivered when they have a different various products, right?
30:26
Unidentified speaker (UNKNOWN): So
30:26
William Ulrich: the this allows us to align the value consumption view of the customer of what they're getting, which I as a customer uh want to be I'm entitled to these things, right? The value consumption view with the value creation view of in-house capabilities, stakeholders, and technologies.
30:46
William Ulrich: So what we've done there is we've used the product entitlement to meld. the customer or the stakeholder consumption, value consumption view with the value creation view. And it's particularly important for customers because it can shorten the path to delivering solutions.
31:05
Unidentified speaker (UNKNOWN): So
31:05
William Ulrich: I introduced the importance of customer experience design at the beginning of this podcast. So let's talk about product designers and customer experience. designers and what their interest might be in specifying and ensuring the availability of product entitlements across an organization's product portfolio.
31:25
Unidentified speaker (UNKNOWN): So
31:25
William Ulrich: the entitlements largely frame a product design. So it says: these are the things I want the customer to be able to do if they have this product, if they've signed up for this product. So it helps you. frame product design. It also
31:42
William Ulrich: ties back to an architecturally rigorous representation of the customer experience. So it's also involved in the customer experience design. How do I want the the design is more about the how? How do I want my customer to experience these things? Especially because entitlements are shared across products and customers
32:03
William Ulrich: because the pro the entitlements for, let's say, a checking account are going to be similar to some of the entitlements that are shared across a savings account and some other accounts for sure.
32:13
Unidentified speaker (UNKNOWN): So
32:13
William Ulrich: in this case, the bank's checking account product requires a well-defined set of entitlements, each of which would align to the value stream stages where they would be engaged by the customer. And entitlements are just another way that the formality incorporated into business architecture helps improve the customer experience.
32:31
Unidentified speaker (UNKNOWN): So
32:31
William Ulrich: I would just say for more about customer experience design and product design, you can check out chapter six of our book, where we get into these and tie those pieces together. And that's where our architecture and design disciplines are broken down as part of our overall view of strategy execution. I want to look at one last important connection.
32:51
William Ulrich: of value streams maintain. This one is to the stakeholders engaged in contributing value along the value stream journey. Every business architecture has a stakeholder map, or should, where various stakeholders are associated with value stream stages in which they engage. And in my example of authenticating and authorizing a customer to access
33:11
William Ulrich: their financial account, this is usually, but not always, done by solving. software, which is acting in a proxy role for the customer service agent. The stakeholder could be an AI agent, but I'll pick up more on this later. So the stakeholders play a big role, and I want to tie those into the automation perspective as we go.
33:30
Unidentified speaker (UNKNOWN): So
33:30
William Ulrich: I'll stop here, but I want I want the uh I want listeners to get the big picture, right? Value streams represent how things work in the real world using capabilities that lie dormant until they are required to deliver stakeholder value. Capabilities, in turn, are automated by software with the corresponding information required represented as data. This perspective is an accepted
33:50
William Ulrich: view in business and solution architecture circles, but it calls the mind of question that as an industry, I don't think it's been fully explored. I think we've underexplored the role of value streams in automation and where we can go with it. And I'm going to definitely cover a lot more about that as we jump into the next segment.
34:07
Unidentified speaker (UNKNOWN): So
34:07
William Ulrich: if we know our capabilities and information concepts are represented in the real world in terms of software and data, how do we represent value streams in that same vein? Is there a way to bring them into the real world into a live, actionable way?
34:21
William Ulrich: Is there some sort of equivalent real-world automation that organizations can seek to deploy to find further automate the perspective formalized in the business architecture value stream? Because I've explained how all the pieces of a value stream fit together and how we can begin to connect those to the customer journey, right?
34:40
Unidentified speaker (UNKNOWN): But
34:40
William Ulrich: I want to explore this further as part of the next segment. And the next segment is gonna going be to on dynamic value stream realization. And it's gonna going to tie together everything we've talked about. so far: the customer experience and value stream value delivery and the capabilities and the roles they play with
34:59
William Ulrich: automation. And we're going to pull the stakeholders in as part of that. But before I do that, let me take a quick break. You're listening to the Strategy Execution podcast with William Ulrich, co-author of N10 Strategy Execution from Inception through Solution Deployment.
35:15
Unidentified speaker (UNKNOWN): You
35:15
William Ulrich: can get our book on Amazon.com or other outlets. We'll be right back after a short break.
35:28
Unidentified speaker (speaker_0): Do your strategic objectives fail to deploy? Wondering why technology budgets keep growing but deliver less? Are your strategy deployment efforts splintering into dozens of district? disjointed, disconnected projects? Does your organization lack a clear vision for maximizing AI and related technology investments long term? If this
35:48
Unidentified speaker (speaker_0): sounds 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.
36:01
Unidentified speaker (UNKNOWN): When it
36:02
Unidentified speaker (speaker_3): comes to business you'll find the experts here. Voice America Business Network.
36:13
Unidentified speaker (speaker_3): We're back on the Voice
36:14
Unidentified speaker (speaker_0): America Business Channel, where William Ullrich is breaking down the hidden barriers that keep organizations stuck in repeated failures. Let's continue.
36:25
William Ulrich: Welcome back to the Strategic. Strategy Execution Podcast. I'm William Ulrich, co-author of N10 Strategy Execution from Inception to Solution Deplement.
36:33
Unidentified speaker (UNKNOWN): You
36:33
William Ulrich: can check out this podcast at voiceamericamedia.com or subscribe to it on Apple Podcasts, Spotify, or wherever you get your podcast.
36:41
Unidentified speaker (UNKNOWN): In
36:41
William Ulrich: this final segment, I want to discuss how to bring value streams, the customer journey, and dynamic realization into a real-world perspective as a means of maximizing. the customer experience. So, first, I want to explore how value streams might be able to take the place of what has historically been captured by customer journey maps.
37:00
Unidentified speaker (UNKNOWN): The
37:01
William Ulrich: second item I want to cover is to explore value streams can be transformed into dynamic real-time constructs. And lastly, I'll introduce the idea of value stream stakeholder participants as AI agents who have the ability to act increasingly independently over the long term.
37:19
William Ulrich: So the question to start with is: can a value stream incorporate or subsume the customer journey map? And if so, why would that be useful?
37:30
Unidentified speaker (UNKNOWN): So
37:30
William Ulrich: the idea is that an organization with a mature business architecture would already have a set of value streams and engage with the customer in a variety of ways. Mapping those value streams to customer journey maps is a useful interim step, as I noted in the Guild White paper earlier in our discussion today. It lays the foundation for what I'm talking about here.
37:51
William Ulrich: But if customer journey maps and value streams were combined, the customer journey could be explored directly while interacting with other formal architecture domains, such as capabilities. information concepts, and so
38:04
Unidentified speaker (UNKNOWN): on. So
38:05
William Ulrich: the idea of merging these structures cuts out one step toward improving the customer experience through automation. They become one and the same, and value streams start to be used more broadly by the customer experience team and others.
38:19
Unidentified speaker (UNKNOWN): So
38:19
William Ulrich: consider that every customer point of engagement or touch point across an organization's business ecosystem is. captured in some subset of the organization's value streams. In these cases, customer personas, which are essentially different types of stakeholders or different types of customers in
38:39
William Ulrich: context, in a business architecture, stakeholder map are mapped directly to one or more value stream stages. Customer engaging value streams represent a subset of the total number of value streams. in a given organization. And they're interesting because they cover things that you may not have thought of. So, for
38:58
William Ulrich: example, a customer that is engaging with a merchant, the role of the uh bank or the financial institution is really behind the scenes with the financial transactions underway, but that value stream is actually represented in a bank. or financial institution's set of value streams. And
39:18
William Ulrich: that live action of something being transferred from a bank account to another account would be something that the bank would have visibility into. So uh, but if you take a look at a typical organization, you might have, for example, 30 to 35 value streams in total. That can vary.
39:37
Unidentified speaker (UNKNOWN): Uh
39:38
William Ulrich: there are some. government agencies, for example, that might have more. Uh, and there's also organizations that have under 30,
39:46
Unidentified speaker (UNKNOWN): uh,
39:46
William Ulrich: if you have a simplistic business model. It has nothing to do with the size of your organization. It has to do with the complexity of your business model. I don't care if you're the biggest insurance company in the world, if all you do is sell one type of insurance and have no financial products, you have a fairly simple business
40:06
William Ulrich: architecture, regardless of how much money you make or how big you are. Of these 30 to 35 value streams, only a quarter to a third, third might be more accurate, but at the outside a third, would typically involve value streams where the customer engages directly. So examples for a bank would include setting up or updating a
40:26
William Ulrich: financial account.
40:27
William Ulrich: executing a transaction, and settling a payment. Those are all value streams. These value streams become candidates to subsume customer journey maps because all of the experiences for a customer are happening at these touch points. So the experiences are actually occurring within the value streams themselves.
40:47
William Ulrich: Each value stream stage where a customer participates would need to be mapped to one or more customer touch points and experiences. These in turn might be associated with various product entitlements delivered under those stages.
41:00
Unidentified speaker (UNKNOWN): So
41:00
William Ulrich: there are other experience related elements in a customer journey that can be incorporated into a value stream based perspective as well. So, in other words, I'm suggesting that the value streams can essentially replace customer journey maps
41:13
Unidentified speaker (UNKNOWN): with
41:13
William Ulrich: value streams being more. specific and more directly tied to the other architectural elements. And the need for mapping customer journey maps to value streams and capabilities is eliminated because they become one and the same. This is a huge leap for organizations, but if you don't have a very developed
41:33
William Ulrich: customer journey environment or customer experience environment, it may be something you explore out of the gate. In other places or other situations, you're gonna have to start working with the customer journey or customer experience teams to try to come up with some ideas around this if you can convince them to do
41:49
Unidentified speaker (UNKNOWN): so.
41:50
William Ulrich: So I want you to note first that none of the navigational rigor or value centric perspectives associated with value streams goes away. What I'm suggesting is that we consider adding customer journey elements. to the value stream concept itself along the same lines as we uh map the product entitlements and capability
42:10
William Ulrich: cross-mappings and so forth.
42:13
Unidentified speaker (UNKNOWN): Now,
42:13
William Ulrich: this brings me to my next topic: uh dynamic value stream realization. So uh one of the first piece of this segment talked about melding customer journeys into value streams. Now I want to talk about can we realize value streams as automated things in
42:33
William Ulrich: the real world, uh as opposed to just the capabilities, which we know we can automate in the real world? So, in theory, can we take a value stream that represents a customer journey and set of experiences and transform it into a real-time solution that might be adjusted and improved more fluidly than we can do today? The basis for this discussion is the
42:53
William Ulrich: value stream and it's linked to enabling capabilities and the software services that automate those capabilities. Over the years, value streams have been viewed, at least by some, as a way to orchestrate software services. This dates back quite a ways, and uh I've been talking about that for well over a decade.
43:13
William Ulrich: This becomes a reality only. if the value stream itself is in some way executable. So dynamic value stream realization essentially envisions how a value stream is transformed from a static architecture perspective in your business architecture into a dynamically activated construct. If the value stream itself is
43:32
William Ulrich: automated, it would require that software implement the value stream stages to stage the to stage and navigation, and the initiation of the software services that automate the capabilities that are traditionally statically cross mapped to each value stream stage. The navigation environment would necessarily require the ability to orchestrate each
43:52
William Ulrich: stage, the work tasks, the work queues, and interface technologies, and importantly, state-based stage stage-to-stage to stage navigation. Now, again, all of these work. tasks and work queues, they all have capabilities that do the work. So the work itself would be done by capabilities. But the orchestration of
44:10
William Ulrich: those capabilities, which become software services in the real world, their orchestration would be through some sort of automation of the value stream itself. Another thing that would be important, but it's also important, and we talked about it in some detail in our book. in chapter nine, is that of a hierarchical state machine.
44:31
William Ulrich: And we talk about that specifically in conjunction with value stream navigation and dynamic rules-based routing and how those pieces fit together. So while Charlie Bowman and I in the book did not lay out the full dynamic uh value stream navigation approach, we did supply the basics in chapter nine.
44:51
Unidentified speaker (UNKNOWN): and
44:51
William Ulrich: it really leading into chapter nine with chapter six. So it's worth checking out. If you haven't gotten the book yet, you can take a look at that. But we do lay out the basics. In particular, we lay out the construction of a hierarchical state machine, which can implement the dynamic rules-based routing maps that are laid out in chapter six. So, again, all the pieces fit together.
45:11
William Ulrich: And uh always interested in what people have to say when they take a look at
45:14
Unidentified speaker (UNKNOWN): the
45:15
William Ulrich: some of that.
45:16
Unidentified speaker (UNKNOWN): Uh
45:16
William Ulrich: so to be clear, I'm describing what I'm describing is an advanced deployment of business architecture and enabling technologies. Well, it may not come along in this form for a while. The technology's here today, in my view, to deploy the overall approach. The question is more around whether organizations are ready to think outside the box on these topics and begin to explore these
45:36
William Ulrich: things, and also to do the other work. necessary. So regular listeners are gonna, they're gonna have heard what I'm gonna say next. None of this will work if your data is not a comprehensive representation of the information concepts defined in your business architecture. Net data must be complete, of high integrity, and importantly,
45:55
William Ulrich: architected in a way that is implementable in practice.
46:00
Unidentified speaker (UNKNOWN): So
46:00
William Ulrich: my messaging in this regard fully supports. my position I took in my October 21st podcast that suggested that it's time to abandon traditional flow-based process modeling in favor of dynamic rules-based routing approach we detailed in our book.
46:15
Unidentified speaker (UNKNOWN): So
46:15
William Ulrich: if you want more on dynamic rules-based routing, I did talk about it in that uh episode of the podcast, but uh you can also check out the book. So it's important to try to bring some of these concepts together and that's what I'm doing here from a podcast to podcast to podcast perspective. So this is just one more step in
46:35
William Ulrich: moving beyond business pro flow-based business process models in favor of more dynamic approaches, with value streams being the overarching uh state-based State based approach, with dynamic rules-based routing being the in-stage in stage uh state based approach to navigation.
46:55
William Ulrich: Before I wrap today, I want to add in one more important element to our story, and that is envisioning stakeholders as AI agents. Most business architecture stakeholder maps represent both the internal and external stakeholders that participate in various value stream stages to contribute to value delivery for the triggering.
47:15
William Ulrich: stakeholder. And today we focused on that triggering stakeholder being the customer, gave some examples, banking examples, financial institution, and so
47:23
Unidentified speaker (UNKNOWN): on. But
47:24
William Ulrich: in my prior example, I mentioned a customer looking to move money from one financial account to another. This is likely to be mostly automated today, and even the help center will have AI agents engaging. But consider the many stakeholders who actively engage in other value streams. both externally and internally triggered, are humans. So if we
47:44
William Ulrich: consider these stakeholders as AI agents
47:47
Unidentified speaker (UNKNOWN): and
47:48
William Ulrich: we extend our dynamic value stream realization vision over internally triggered and partner-triggered value streams, having AI agents serve in these stakeholder roles is just an extension of the overall vision. So I want you to note that I'm not by any means looking to eliminate humans from the loop. On
48:08
William Ulrich: the other hand, if if organizations are going to continue spending tens or hundreds of millions of dollars on AI, and I've I've gotten into that a little bit in some earlier podcasts this season,
48:20
Unidentified speaker (UNKNOWN): uh,
48:20
William Ulrich: they should have a vision as to where they want to go and where they want to land. And that vision shouldn't just be, well, we'll see where we are at the end. of next quarter, and we'll we'll try and experiment here or try and experiment there. Do you have the architectural discipline? Do you have the vision that goes with the architectural division that that architectural vision?
48:40
William Ulrich: Do you have the funding to drive a strategic roadmap, as I talked about in a prior podcast as well? Uh, a strategic transformation roadmap. You have the vision to put these pieces to start moving in that direction so that the money you're spending on AI starts to rebalance, as I've said in prior podcast again, so that you're
49:00
William Ulrich: spending more money on delivering value as opposed to delivering waste. Because right now, according to stats from a number of different resources, the money being spent on AI is largely being wasted. It's not being spent intelligently.
49:16
William Ulrich: So the dynamic, dynamically enabled value stream is one such landing place that works from a strategic perspective as opposed to throwing as much spaghetti at the wall as possible and seeing what sticks, which is sort of the approach that's going on today.
49:29
Unidentified speaker (UNKNOWN): So
49:30
William Ulrich: I'll pick up on this uh agent theme further in uh coming upcoming pro product podcasts. And I want to include the ethics of AI deployment in organizations as well, because I think I think that ethics area is one that while it might be explored more generally in society, the ethics
49:50
William Ulrich: of AI and what AI is doing to us and for us, et cetera, et cetera, I'm not sure that those ethics are being explored in as much detail from a organizational corporate government environment. internally as we're trying to deploy AI. Because again, we're experimenting. And if we're experimenting in the
50:10
William Ulrich: blind, where we don't have a vision and a strategy and a roadmap and an architecture to support that,
50:19
Unidentified speaker (UNKNOWN): uh,
50:19
William Ulrich: where are we going to land? It could be landing in some bad places, right? So
50:25
Unidentified speaker (UNKNOWN): uh
50:25
William Ulrich: in the meantime, uh try to focus on your strategic vision. And as always, always execute uh based on formal architecture and design perspectives. Uh I point people back to our book, and I know they do that a lot, but um you know you can it the book is an adjunct uh it to well, this podcast is actually an adjunct to
50:45
William Ulrich: the book. Uh or you could look at it the other way around, the book is an adjunct to the podcast, but in either way. uh, you wanna really pick up a copy of the book because it's gonna give you the insights uh in more detail that I'm talking about here today. And all the pieces are tied together underneath there.
51:03
Unidentified speaker (UNKNOWN): Um,
51:03
William Ulrich: you can keep uh experimenting, but at some point someone is going to ask the question of whether or not you have an idea where you wanna want to land at the end of the day uh with AI and with the other money you're spending. on technology. So with that, I'm going to close it back out. You've been listening to the Strategy Execution Podcast with William Ulrich,
51:23
William Ulrich: co-author of N Strategy Execution from Inception Through Solution Deployment. Please send your comments and questions to W M M U L R I R-I-C-H, C H that's W M M Ulrich at T S G, like Tom Sam Group. T S G Consulting Inc., that's INC. So TSG Consulting Inc.,
51:43
William Ulrich: all one word.com. I'm also on LinkedIn if you want to look me up. You can check out the podcast at voiceamericamedia.com or subscribe to it on Apple Podcasts, Spotify, or wherever you get your podcasts. And you can get our book on Amazon.com On.com or other outlets. Thanks for joining me, and I'll see you next week.
52:05
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.
This page was produced automatically: the audio was transcribed with nvidia/parakeet-tdt-0.6b-v3+sortformer-v2.1 and interpreted by Qwen3.6-35B-A3B-UD-IQ3_S.gguf. Transcription and interpretation can contain errors; always confirm against the original episode. Nothing here is investment advice.

More from End-to-End Strategy Execution

All insights