>>Hey everyone. Lisa Martin of the cube here, HPE and AMD better together with Shi is the name of our segment. And I'm here with four guests. Please. Welcome Charlie Mulrooney global presales engineering manager at Athi John saws also of Shi joins this global pre-sales technical consultant. And back with me are Terry Richardson, north American channel chief and Dr. John Fry, chief technologist, sustainable transformation at HPE. Welcome gang. Great to have you all here. >>Thank you, Lisa. Thanks. You good to be here? >>All right, Charlie, let's go ahead and start with you. Keeping the earth sustainable and minimizing carbon emissions. Greenhouse gases is a huge priority for businesses, right? Everywhere. Globally. Can you talk Charlie about what Shi is seeing in the marketplace with respect to sustainable? It? >>Sure. So starting about a year and a half, two years ago, we really noticed that our customers certainly our largest enterprise customers were putting into their annual reports, their chairman's letters, their sec filings that they had sustainability initiatives ranging from achieving carbon neutral or carbon zero goals starting with 2050 dates. And then since then we've seen 20, 40, and 2030 targets to achieve net neutrality and RFPs, RFIs that we're fielding. Certainly all now contain elements of that. So this is certainly top of mind for our largest customers, our fortune two 50 and fortune 500 customers. For sure. We're, we're seeing an onslaught of requests for this. We get into many conversations with the folks that are leading these efforts to understand, you know, here's what we have today. What can we do better? What can we do different to help make an impact on those goals? >>So making an impact top of mind, pretty much for everyone, as you mentioned, John SAS, let's bring you into the conversation. Now, when you're in customer conversations, what are some of the things that you talk about with respect tohis approach to sustainability, sustainable it, are you seeing more folks that are implementing things tactically versus strategically what's going on in the customer space? >>Well, so Charlie touched on something really important that, you know, the, the wake up moment for us was receiving, you know, proposal requests or customer meeting requests that were around sustainability. And it was really around two years ago, I suppose, for the first time. And those requests started coming from European based companies, cuz they had a bit of a head start over the us based global companies even. And what we found was that sustainability was already well down the road and that they were doing very interesting things to use renewable energy for data centers utilize the, they were already considering sustainability for new technologies as a high priority versus just performance cost and other factors that you typically have at the top. So as we started working with them, I guess at beginning it was more tactical cuz we really had to find a way to respond. >>We were starting to be asked about our own efforts and in regards to sustainability, we have our headquarters in Somerset and our second headquarters in Austin, Texas, those are lead gold certified. We've been installing solar panels, reducing waste across the company, recycling efforts and so forth charging stations for electric vehicles, all that sort of thing to make our company more sustainable in, in, in our offices and in our headquarters. But it's a lot more than that. And what we found was that we wanted to look to our vast number of, of customers and partners. We have over 30,000 partners that would work with globally and tens of thousands of customers. And we wanted to find best practices and technologies and services that we could talk about with these customers and apply and help integrate together as a, as a really large global reseller and integrator. We can have a play there and bring these things together from multiple partners that we work with to help solve customer problems. And so over time it's become more strategic and we've been as a company building the, the, the, the, the forward efforts through organizing a true formal sustainability team and growing that, and then also reporting for CDP Ecova and so forth. And it's really that all has been coming about in the last couple of years. And we take it very seriously. >>It sounds like, and it also sounds like from the customer's perspective, they're shifting from that tactical, maybe early initial approach to being more strategic, to really enabling sustainable it across their organization. And I imagine from a business driver's perspective, John saws and Charlie, are you hearing customers? You talked about it being part of RFPs, but also where are customers in terms of, we need to have a sustainable it strategy so that we can attract and retain the right investors we can attract and retain customers. Charlie, John, what are your thoughts on that? >>Yeah, that's top of mind with, with all the folks that we're talking to, I would say there's probably a three way tie for the importance of attracting and retaining investors. As you said, plus customers, customers are shopping, their customers are shopping for who has aligned their ESG priorities and sustainable priorities with their own and who is gonna help them with their own reporting of, you know, scope two and ultimately scope three reporting from greenhouse gas emissions and then the attracting and retaining talent. It's another element now of when you're bringing on new talent to your organization, they have a choice and they're thinking with their decision to accept a role or not within your organization of what your strategies are and do they align. So we're seeing those almost interchangeable in terms of priorities with, with the customers we're talking to. And it was a little surprising, cuz it, we thought initially this is really focused on investors attracting the investors, but it really has become quite a bit more than that. And it's been actually very interesting to see the development of that prioritization >>More comprehensive across the organization. Let's bring Dr. John Fry into the conversation and Terry your next. So stay tuned. Dr. Fry, can you talk about HPE and S H I partnering together? What are some of the key aspects of the relationship that help one another support and enable each other's aggressive goals where sustainability is concerned? >>Yeah, it's a great question. And one of the things about the sustainability domain in solving these climate challenges that we all have is we've got to come together and partner to solve them. No one company's going to solve them by themselves and for our collective customers the same way. From an HPE perspective, we bring the expertise on our products. We bring in sustainable it point of view, where we've written many white papers on the topic and even workbooks that help companies implement a sustainable it program. But our direct sales forces can't reach all of our customers. And in many cases we don't have the local knowledge that our business partners like Shi bring to the table. So they extend the reach, they bring their own expertise. Their portfolio that they offer to the customer is wider than just enterprise products. So by working together, we can do a better job of helping the customer meet their own needs, give them the right technology solutions and enhance that customer experience because they get more value from us collectively. >>It really is better together, which is in a very appropriate name for our segment here. Terry, let's bring you into the conversation. Talk to us about AMD. How is it helping customers to create that sustainable it strategy? And what are some of the differentiators that what AMD is doing that, that are able to be delivered through partners like Shi? >>Well, Lisa, you used the word enabling just a short while ago. And fundamentally AMD enables HPE and partners like Shi to bring differentiated solutions to customers. So in the data center space, we began our journey in 2017 with some fundamental design elements for our processor technology that were really keenly focused on improving performance, but also efficiency. So now the, the most common measure that we see for the types of customers that Charlie and John were talking about is really that measure of performance per wat. And you'll continue to see AMD enabled customers to, to try to find ways to, to do more in a sustainable way within the constraints that they may be facing, whether it's availability of power data center space, or just needing to meet overall sustainability goals. So we have skills and expertise and tools that we make available to HPE and two Shi to help them have even stronger differentiated conversations with customers. >>Sounds like to me, Terry, that it's, that AMD can be even more of an more than an enabler, but really an accelerator of what customers are able to do from a strategic perspective on sustainability. >>You you're right about that. And, and we actually have tools, greenhouse gas, TCO tools that can be leveraged to really quantify the impact of some of the, the new technology decisions that customers are making to allow them to achieve their goals. So we're really proud of the work that we're doing in partnership with companies like HPE and Shi >>Better together. As we said at the beginning in just a minute ago, Charlie, let's bring you back in, talk to us a little bit about what Shi is doing to leverage sustainable it and enable your customers to meet their sustainability goals and their initiatives. >>So for quite a while, we've had some offerings to help customers, especially in the end user compute side. A lot of customers were interested in, I've got assets for, you know, let's say a large sales force that had been carrying tablets or laptops and, you know, those need to be refreshed. What do I do with those? How do I responsibly retire or recycle those? And we've been offering solutions for that for quite some time. It's within the last year or two, when we started offering for them guarantees and assurances assurances of how they can, if that equipment is reusable by somebody else, how can we issue them? You know, credits for carbon credits for reuse of that equipment somewhere else. So it's not necessarily going to be e-waste, it's something that can be recycled and reused. We have other programs with helping extend the life of, of some systems where they look at well, I have a awful lot of data on these machines where historically they might want to just retire those because the, the, the sensitivity of the data needed to be handled very specifically. We can help them properly remove the sensitive data and still allow reuse of that equipment. So we've been able to come up with some creative solutions specifically around end user compute in the past, but we are looking to new ways now to really help extend that into data center infrastructure and beyond to really help with what are the needs, what are the, the best ways to help our customers handle the things that are challenging them. >>That's a great point that you bring up. Charlie and security kind of popped into my head here, John Saul's question for you when you're in customer conversations and you're talking about, or maybe they're talking about help us with waste reduction with recycling, where are you having those customer conversations? Cause I know sustainability is a board level, it's a C level discussion, but where are you having those conversations within the customer organization? >>Well, so it's a, it's a combination of organizations within the customer. These are these global organizations. Typically when we're talking about asset life cycle management, asset recovery, how do you do that in a sustainable green way and securely the customers we're dealing with? I mean, security is top sustainability is right up there too. O obviously, but Charlie touched on a lot of those things and these are global rollouts, tens of thousands of employees typically to, to have mobile devices, laptops, and phones, and so forth. And they often are looking for a true managed service around the world that takes into consideration things like the most efficient way to ship products to, to the employees. And how do you do that in a sustainably? You need to think about that. Does it all go to a central location or to each individual's home during the pandemic that made a lot of sense to do it that way? >>And I think the reason I wanted to touch on those things is that, well for, for example, one European pharmaceutical that states in their reports that they're already in scope one in scope two they're fully net zero at this point. And, and they say, but that only solves 3% of our overall sustainability goals. 97% is scope three, it's travel, it's shipping. It's, it's, it's all the, the, all these things that are out of their direct control a lot of times, but they're coming to us now as a, as a supplier and as, and, and we're filling out, you know, forms and RFPs and so forth to show that we can be a sustainable supplier in their supply chain because that's their next big goal >>Sustain sustainable supply chain. Absolutely. Yes. Dr. John Fry and Terry, I want to kind of get your perspectives. Charlie talked about from a customer requirements perspective, customers coming through RFP saying, Hey, we've gotta work with vendors who have clear sustainability initiatives that are well underway, HPE and AMD hearing the same thing Dr. Fry will start with you. And then Terry >>Sure, absolutely. We receive about 2,500 customer questionnaires just on sustainability every year. And that's come up from a few hundred. So yeah, absolutely accelerating. Then the conversations turn deeper. Can you help us quantify our carbon emissions and power consumption? Then the conversation has recently gone even further to when can HPE offer net zero or carbon neutral technology solutions to the customer so that they don't have to account for those solutions in their own carbon footprint. So the questions are getting more sophisticated, the need for the data and the accuracy of the data is climbing. And as we see potential regulatory disclosure requirements around carbon emissions, I think this trend is just gonna continue up. >>Yeah. And we see the same thing. We get asked more and more from our customers and partners around our own corporate sustainability goals. But the surveying that survey work that we've done with customers has led us to, you know, understand that, you know, approximately 75% of customers are gonna make sustainability goals, a key component of their RFIs in 2023, which is right around the corner. And, and, you know, 60% of those same customers really expect to have business level KPIs in the new year that are really related to sustainability. So this is not just a, a kind of a buzzword topic. This is, this is kind of business imperatives that, you know, the company, the companies like HPE and AMD and the partners like I, that really stand behind it and really are proactive in getting out in front of customers to help are really gonna be ahead of the game. >>That's a great point that you make Terry there that this isn't, we're not talking about a buzzword here. We're talking about a business imperative for businesses of probably all sizes across all industries and Dr. Far, you mentioned regulations. And something that we just noticed is that the S E C recently said, it's proposing some rules where companies must disclose greenhouse gas emissions. If they were, if that were to, to come into play, I'm gonna pun back to Charlie and John saws. How would Shi and, and frankly at HPE and AMD be able to help companies comply if that type of regulation were to be implemented. Charlie. >>Yeah. So we are in the process right now of building out a service to help customers specifically with that, with the reporting, we know reporting is a challenge. The scope two reporting is a challenge and scope three that I guess people thought was gonna be a ways out now, all of a sudden, Hey, if you have made a public statement that you're going to make an impact on your scope three targets, then you have to report on them. So that, that has become really important very quickly as word about this requirement is rumbling around there's concern. So we are actually working right now on something it's a little too early to fully disclose, but stay tuned, cuz we have something coming. That's interesting. >>Definitely PED my, my ears are, are, are perk here. Charlie, we'll stay tuned for that. Dr. Fry. Terry, can you talk about together with Shi HPE and AMD enabling customers to manage access to the da data obviously, which is critical and it's doing nothing but growing and proliferating key folks need access to it. We talked a little bit about security, but how are from a better together perspective, Dr. Fry will start with you, how are you really helping organizations on that sustainability journey to ensure that data can be accessible to those who need it when they need it? And at these days what it's real time requirements. >>Yeah. It's, it's an increasing challenge. In fact, we have changed the H HP story the way we talk about H HP's value proposition to talk about data first modernization. So how often do you collect data? Where do you store it? How do you avoid moving it? How do you make sure if you're going to collect data, you get insights from that data that change your business or add business value. And then how long do you retain that data afterward and all of that factors into sustainable it, because when I talk to technology executives, what they tell me again, and again, is there's this presumption within their user community, that storage is free. And so when, when they have needs for collecting data, for example, if, if once an hour would do okay, but the system would collect it once a minute, the default, the user asks for of course, once a minute. And then are you getting insights from that data? Or are we moving it that becomes more important when you're moving data back and forth between the public cloud or the edge, because there is quite a network penalty for moving that equipment across your network. There's huge power and carbon implications of doing that. So it's really making a better decision about what do we collect, why do we collect it, what we're gonna do with it when we collect and how we store it. >>And, and for years, customers have really talked about, you know, modernization and the need to modernize their data center. You know, I, I fundamentally believe that sustainability is really that catalyst to really drive true modernization. And as they think forward, you know, when we work with, with HPE, you know, they offer a variety of purpose-built servers that can play a role in, you know, specific customer workloads from the largest, super computers down to kind of general purpose servers. And when we work with partners like Shi, not only can they deliver the full suite of offerings for on premise deployments, they're also very well positioned to leverage the public cloud infrastructure for those workloads that really belong there. And, and that certainly can help customers kind of achieve an end to end sustainability goal. >>That's a great point that, that it needs to be strategic, but it also needs to be an end to end goal. We're just about out of time, but I wanted to give John saws the last word here, take us out, John, what are some of the things Charlie kind of teased some of the things that are coming out that piqued my interest, but what are some of the things that you are excited about as HPE AMD and Shi really help customers achieve their sustainability initiatives? >>Sure. Couple comments here. So Charlie, yeah, you touched on some upcoming capabilities that Shi will have around the area of monitoring and management. See, this is difficult for all customers to be able to report in this formal way. This is a train coming at everybody very quickly and they're not ready. Most customers aren't ready. And if we can help as, as a reseller integrator assessments, to be able to understand what they're currently running compare to different scenarios of where they could go to in a future state, that seems valuable if we can help in that way. That's, those are things that we're looking into specifically, you know, greenhouse gas, emissions, relevant assessments, and, and, and within the comments of, of, of Terry and, and John around the, the power per wat and the vast portfolio of, of technologies that they, that they had to address various workloads is, is fantastic. >>We'd be able to help point to technologies like that and move customers in that direction. I think as a, as an integrator and a technical advisor to customers, I saw an article on BBC this morning that I, I, I think if, if we think about how we're working with our customers and we can help them maybe think differently about how they're using their technology to solve problems. The BBC article mentioned this was Ethereum, a cryptocurrency, and they have a big project called merge. And today was a go live date. And BBC us news outlets have been reporting on it. They basically changed the model from a model called power of work, which takes a, a lot of compute and graphic, GPU power and so forth around the world. And it's now called power of stake, which means that the people that validate that their actions in this environment are correct. >>They have to put up a stake of their own cryptocurrency. And if they're wrong, it's taken from them. This new model reduces the emissions of their environment by 99 plus percent. The June emissions from Ethereum were, it was 120 telos per, per year, a Terra terat hours per year. And they reduced it actually, that's the equivalent of what the net Netherlands needed for energy, so comparable to a medium sized country. So if you can think differently about how to solve problems, it may be on-prem, it may be GreenLake. It may be, it may be the public cloud in some cases or other, you know, interesting, innovative technologies that, that AMD HPE, other partners that we can bring in along, along with them as well, we can solve problems differently. There is a lot going on >>The opportunities that you all talked about to really make such a huge societal impact and impact to our planet are exciting. We thank you so much for talking together about how HPE AMD and SSHA are really working in partnership in synergy to help your customers across every organization, really become much more focused, much more collaborative about sustainable it. Guys. We so appreciate your time and thank you for your insights. >>Thank you, Lisa. Thank you. My >>Pleasure. Thank you, Lisa. You're watching the cube, the leader in high tech enterprise coverage.

(futuristic music) >> Hey everyone. Lisa Martin here for theCUBE back with you, three guests join me. Dan Molina is here, the co-president and chief technology officer at NTH Generation. And I'm joined once again by Terry Richardson, North American channel chief for AMD and Dr. John Fry, chief technologist, sustainable transformation at HPE. Gentlemen, It's a pleasure to have you on theCUBE Thank you for joining me. >> Thank you, Lisa. >> Dan. Let's have you kick things off. Talk to us about how NTH Generation is addressing the environmental challenges that your customers are having while meeting the technology demands of the future. That those same customers are no doubt having. >> It's quite an interesting question, Lisa, in our case we have been in business since 1991 and we started by providing highly available computing solutions. So this is great for me to be partnered here with HPE and the AMD because we want to provide quality computing solutions. And back in the day, since 1991 saving energy saving footprint or reducing footprint in the data center saving on cooling costs was very important. Over time those became even more critical components of our solutions design. As you know, as a society we started becoming more aware of the benefits and the must that we have a responsibility back to society to basically contribute with our social and environmental responsibility. So one of the things that we continue to do and we started back in 1991 is to make sure that we're deciding compute solutions based on clients' actual needs. We go out of our way to collect real performance data real IT resource consumption data. And then we architect solutions using best in the industry components like AMD and HPE to make sure that they were going to be meeting those goals and energy savings, like cooling savings, footprint reduction, knowing that instead of maybe requiring 30 servers, just to mention an example maybe we're going to go down to 14 and that's going to result in great energy savings. Our commitment to making sure that we're providing optimized solutions goes all the way to achieving the top level certifications from our great partner, Hewlett Packard Enterprise. Also go deep into micro processing technologies like AMD but we want to make sure that the designs that we're putting together actually meet those goals. >> You talked about why sustainability is important to NTH from back in the day. I love how you said that. Dan, talk to us a little bit about what you're hearing from customers as we are seeing sustainability as a corporate initiative horizontally across industries and really rise up through the C-suite to the board. >> Right, it is quite interesting Lisa We do service pretty much horizontally just about any vertical, including public sector and the private sector from retail to healthcare, to biotech to manufacturing, of course, cities and counties. So we have a lot of experience with many different verticals. And across the board, we do see an increased interest in being socially responsible. And that includes not just being responsible on recycling as an example, most of our conversations or engagements that conversation happens, 'What what's going to happen with the old equipment ?' as we're replacing with more modern, more powerful, more efficient equipment. And we do a number of different things that go along with social responsibility and environment protection. And that's basically e-waste programs. As an example, we also have a program where we actually donate some of that older equipment to schools and that is quite quite something because we're helping an organization save energy, footprint. Basically the things that we've been talking about but at the same time, the older equipment even though it's not saving that much energy it still serves a purpose in society where maybe the unprivileged or not as able to afford computing equipment in certain schools and things of that nature. Now they can benefit and being productive to society. So it's not just about energy savings there's so many other factors around social corporate responsibility. >> So sounds like Dan, a very comprehensive end to end vision that NTH has around sustainability. Let's bring John and Terry into the conversation. John, we're going to start with you. Talk to us a little bit about how HPE and NTH are partnering together. What are some of the key aspects of the relationship from HPE's perspective that enable you both to meet not just your corporate sustainable IT objectives, but those of your customers. >> Yeah, it's a great question. And one of the things that HPE brings to bear is 20 years experience on sustainable IT, white papers, executive workbooks and a lot of expertise for how do we bring optimized solutions to market. If the customer doesn't want to manage those pieces himself we have our 'As a service solutions, HPE GreenLake. But our sales force won't get to every customer across the globe that wants to take advantage of this expertise. So we partner with companies like NTH to know the customer better, to develop the right solution for that customer and with NTH's relationships with the customers, they can constantly help the customer optimize those solutions and see where there perhaps areas of opportunity that may be outside of HPE's own portfolio, such as client devices where they can bring that expertise to bear, to help the customer have a better total customer experience. >> And that is critical, that better overall comprehensive total customer experience. As we know on the other end, all customers are demanding customers like us who want data in real time, we want access. We also want the corporate and the social responsibility of the companies that we work with. Terry, bringing you into the conversation. Talk to us a little about AMD. How are you helping customers to create what really is a sustainable IT strategy from what often starts out as sustainability tactics? >> Exactly. And to pick up on what John and and Dan were saying, we're really energized about the opportunity to allow customers to accelerate their ability to attain some of their more strategic sustainability goals. You know, since we started on our current data center, CPU and GPU offerings, each generation we continue to focus on increasing the performance capability with great sensitivity to the efficiency, right? So as customers are modernizing their data center and achieving their own digital transformation initiatives we are able to deliver solutions through HPE that really address a greater performance per watt which is a a core element in allowing customers to achieve the goals that John and Dan talked about. So, you know, as a company, we're fully on board with some very public positions around our own sustainability goals, but working with terrific partners like NTH and HPE allows us to together bring those enabling technologies directly to customers >> Enabling and accelerating technologies. Dan, let's go back to you. You mentioned some of the things that NTH is doing from a sustainability approach, the social and the community concern, energy use savings, recycling but this goes all the way from NTH's perspective to things like outreach and fairness in the workplace. Talk to us a little bit about some of those other initiatives that NTH has fired up. >> Absolutely, well at NTH , since the early days, we have invested heavily on modern equipment and we have placed that at NTH labs, just like HPE labs we have NTH labs, and that's what we do a great deal of testing to make sure that our clients, right our joint clients are going to have high quality solutions that we're not just talking about it and we actually test them. So that is definitely an investment by being conscious about energy conservation. We have programs and scripts to shut down equipment that is not needed at the time, right. So we're definitely conscious about it. So I wanted to mention that example. Another one is, we all went through a pandemic and this is still ongoing from some perspectives. And that forced pretty much all of our employees, at least for some time to work from home. Being an IT company, we're very proud that we made that transition almost seamlessly. And we're very proud that you know people who continue to work from home, they're saving of course, gasoline, time, traffic, all those benefits that go with reducing transportation, and don't get me wrong, I mean, sometimes it is important to still have face to face meetings, especially with new organizations that you want to establish trust. But for the most part we have become a hybrid workforce type of organization. At the same time, we're also implementing our own hybrid IT approach which is what we talk to our clients about. So there's certain workloads, there are certain applications that truly belong in in public cloud or Software as a Service. And there's other workloads that truly belong, to stay in your data center. So a combination and doing it correctly can result in significant savings, not just money, but also again energy, consumption. Other things that we're doing, I mentioned trading programs, again, very proud that you know, we use a e-waste programs to make sure that those IT equipment is properly disposed of and it's not going to end in a landfill somewhere but also again, donating to schools, right? And very proud about that one. We have other outreach programs. Normally at the end of the year we do some substantial donations and we encourage our employees, my coworkers to donate. And we match those donations to organizations like Operation USA, they provide health and education programs to recover from disasters. Another one is Salvation Army, where basically they fund rehabilitation programs that heal addictions change lives and restore families. We also donate to the San Diego Zoo. We also believe in the whole ecosystem, of course and we're very proud to be part of that. They are supporting more than 140 conservation projects and partnerships in 70 countries. And we're part of that donation. And our owner has been part of the board or he was for a number of years. Mercy House down in San Diego, we have our headquarters. They have programs for the homeless. And basically that they're servicing. Also Save a Life Foundation for the youth to be educated to help prevent sudden cardiac arrest for the youth. So programs like that. We're very proud to be part of the donations. Again, it's not just about energy savings but it's so many other things as part of our corporate social responsibility program. Other things that I wanted to mention. Everything in our buildings, in our offices, multiple locations. Now we turn into LED. So again, we're eating our own dog food as they say but that is definitely some significant energy savings. And then lastly, I wanted to mention, this is more what we do for our customers, but the whole HPE GreenLake program we have a growing number of clients especially in Southern California. And some of those are quite large like school districts, like counties. And we feel very proud that in the old days customers would buy IT equipment for the next three to five years. Right? And they would buy extra because obviously they're expecting some growth while that equipment must consume energy from day one. With a GreenLake type of program, the solution is sized properly. Maybe a little bit of a buffer for unexpected growth needs. And anyway, but with a GreenLake program as customers need more IT resources to continue to expand their workloads for their organizations. Then we go in with 'just in time' type of resources. Saving energy and footprint and everything else that we've been talking about along the way. So very proud to be one of the go-tos for Hewlett Packard Enterprise on the GreenLake program which is now a platform, so. >> That's great. Dan, it sounds like NTH generation has such a comprehensive focus and strategy on sustainability where you're pulling multiple levers it's almost like sustainability to the NTH degree ? See what I did there ? >> (laughing) >> I'd like to talk with all three of you now. And John, I want to start with you about employees. Dan, you talked about the hybrid work environment and some of the silver linings from the pandemic but I'd love to know, John, Terry and then Dan, in that order how educated and engaged are your employees where sustainability is concerned? Talk to me about that from their engagement perspective and also from the ability to retain them and make them proud as Dan was saying to work for these companies, John ? >> Yeah, absolutely. One of the things that we see in technology, and we hear it from our customers every day when we're meeting with them is we all have a challenge attracting and retaining new employees. And one of the ways that you can succeed in that challenge is by connecting the work that the employee does to both the purpose of your company and broader than that global purpose. So environmental and social types of activities. So for us, we actually do a tremendous amount of education for our employees. At the moment, all of our vice presidents and above are taking climate training as part of our own climate aspirations to really drive those goals into action. But we're opening that training to any employee in the company. We have a variety of employee resource groups that are focused on sustainability and carbon reduction. And in many cases, they're very loud advocates for why aren't we pushing a roadmap further? Why aren't we doing things in a particular industry segment where they think we're not moving quite as quickly as we should be. But part of the recognition around all of that as well is customers often ask us when we suggest a sustainability or sustainable IT solution to them. Their first question back is, are you doing this yourselves? So for all of those reasons, we invest a lot of time and effort in educating our employees, listening to our employees on that topic and really using them to help drive our programs forward. >> That sounds like it's critical, John for customers to understand, are you doing this as well? Are you using your own technology ? Terry, talk to us about from the AMD side the education of your employees, the engagement of them where sustainability is concerned. >> Yeah. So similar to what John said, I would characterize AMD is a very socially responsible company. We kind of share that alignment in point of view along with NTH. Corporate responsibility is something that you know, most companies have started to see become a lot more prominent, a lot more talked about internally. We've been very public with four key sustainability goals that we've set as an organization. And we regularly provide updates on where we are along the way. Some of those goals extend out to 2025 and in one case 2030 so not too far away, but we're providing milestone updates against some pretty aggressive and important goals. I think, you know, as a technology company, regardless of the role that you're in there's a way that you can connect to what the company's doing that I think is kind of a feel good. I spend more of my time with the customer facing or partner facing resources and being able to deliver a tool to partners like NTH and strategic partners like HPE that really helps quantify the benefit, you know in a bare metal, in terms of greenhouse gas emissions and a TCO tool to really quantify what an implementation of a new and modern solution will mean to a customer. And for the first time they have choice. So I think employees, they can really feel good about being able to to do something that is for a greater good than just the traditional corporate goals. And of course the engineers that are designing the next generation of products that have these as core competencies clearly can connect to the impact that we're able to make on the broader global ecosystem. >> And that is so important. Terry, you know, employee productivity and satisfaction directly translates to customer satisfaction, customer retention. So, I always think of them as inextricably linked. So great to hear what you're all doing in terms of the employee engagement. Dan, talk to me about some of the outcomes that NTH is enabling customers to achieve, from an outcomes perspective those business outcomes, maybe even at a high level or a generic level, love to dig into some of those. >> Of course. Yes. So again, our mission is really to deliver awesome in everything we do. And we're very proud about that mission, very crispy clear, short and sweet and that includes, we don't cut corners. We go through the extent of, again, learning the technology getting those certifications, testing those in the lab so that when we're working with our end user organizations they know they're going to have a quality solution. And part of our vision has been to provide industry leading transformational technologies and solutions for example, HPE and AMD for organizations to go through their own digital transformation. Those two words have been used extensively over the last decade, but this is a multi decade type of trend, super trend or mega trend. And we're very proud that by offering and architecting and implementing, and in many cases supporting, with our partners, those, you know, best in class IT cyber security solutions were helping those organizations with those business outcomes, their own digital transformation. If you extend that Lisa , a Little bit further, by helping our clients, both public and private sector become more efficient, more scalable we're also helping, you know organizations become more productive, if you scale that out to the entire society in the US that also helps with the GDP. So it's all interrelated and we're very proud through our, again, optimized solutions. We're not just going to sell a box we're going to understand what the organization truly needs and adapt and architect our solutions accordingly. And we have, again, access to amazing technology, micro processes. Is just amazing what they can do today even compared to five years ago. And that enables new initiatives like artificial intelligence through machine learning and things of that nature. You need GPU technology , that specialized microprocessors and companies like AMD, like I said that are enabling organizations to go down that path faster, right? While saving energy, footprint and everything that we've been talking about. So those are some of the outcomes that I see >> Hey, Dan, listening to you talk, I can't help but think this is not a stretch for NTH right? Although, you know, terms like sustainability and reducing carbon footprint might be, you know more in vogue, the type of solutions that you've been architecting for customers your approach, dates back decades, and you don't have to change a lot. You just have new kind of toys to play with and new compelling offerings from great vendors like HPE to position to your customers. But it's not a big change in what you need to do. >> We're blessed from that perspective that's how our founders started the company. And we only, I think we go through a very extensive interview process to make sure that there will be a fit both ways. We want our new team members to get to know the the rest of the team before they actually make the decision. We are very proud as well, Terry, Lisa and John, that our tenure here at NTH is probably well over a decade. People get here and they really value how we help organizations through our dedicated work, providing again, leading edge technology solutions and the results that they see in our own organizations where we have made many friends in the industry because they had a problem, right? Or they had a very challenging initiative for their organization and we work together and the outcome there is something that they're very, very proud of. So you're right, Terry, we've been doing this for a long time. We're also very happy again with programs like the HPE GreenLake. We were already doing optimized solutions but with something like GreenLake is helping us save more energy consumption from the very beginning by allowing organizations to pay for only what they need with a little bit of buffer that we talked about. So what we've been doing since 1991 combined with a program like GreenLake I think is going to help us even better with our social corporate responsibility. >> I think what you guys have all articulated beautifully in the last 20 minutes is how strategic and interwoven the partnerships between HP, AMD and NTH is what your enabling customers to achieve those outcomes. What you're also doing internally to do things like reduce waste, reduce carbon emissions, and ensure that your employees are proud of who they're working for. Those are all fantastic guys. I wish we had more time cause I know we are just scratching the surface here. We appreciate everything that you shared with respect to sustainable IT and what you're enabling the end user customer to achieve. >> Thank you, Lisa. >> Thanks. >> Thank you. >> My pleasure. From my guests, I'm Lisa Martin. In a moment, Dave Vellante will return to give you some closing thoughts on sustainable IT You're watching theCUBE. the leader in high tech enterprise coverage.

foreign [Music] Lisa Martin of the cube here hpe and AMD better together with Shi is the name of our segment and I'm here with four guests please welcome Charlie mulrooney Global pre-sales engineering manager at SHI John saw is also of shi joins us Global pre-sales Technical consultant and back with me are Terry Richardson North American Channel Chief and Dr John Fry Chief technologist of sustainable transformation at hpe welcome gang great to have you here all here Thank you Lisa thank you good to be here all right Charlie let's go ahead and start with you keeping the Earth sustainable and minimizing carbon emissions greenhouse gases is a huge priority for businesses right everywhere globally can you talk truly about what Shi is seeing in the marketplace with respect to sustainable I.T sure so starting about a year and a half two years ago we really noticed that our customers certainly our largest Enterprise customers were putting into their annual reports their Chairman's letters their SEC filings that they had sustainability initiatives ranging from achieving carbon neutral uh or carbon zero goals starting with 20 50 dates and then since then we've seen 20 40 and 2030 targets to achieve net neutrality and rfps rfis that we're Fielding certainly all now contain elements of that so this is certainly top of mind for our largest customers our Fortune 250 and Fortune 500 customers for sure where we're seeing an onslaught of requests for this we get into many conversations with the folks that are leading these efforts to understand you know here's what we have today what can we do better what can we do different to help make it an impact on those goals so making an impact top of Mind pretty much for everyone as you mentioned John Sal's let's bring you into the conversation now when you're in customer conversations what are some of the things that you talk about with respect to shi's approach to sustainability sustainable I.T are you seeing more folks that are implementing things tactically versus strategically what's going on in the customer space well so Charlie touched on something really important that you know the the wake-up moment for us was receiving you know proposal requests or customer meeting requests that were around sustainability and it was really around two years ago I suppose for the first time and those requests started coming from european-based companies because they had a bit of a head start uh over the U.S based global companies even um and what we found was that sustainability was already well down the road and that they were doing very interesting things to uh use renewable energy for data centers uh utilized they were already considering sustainability for new technologies as a high priority versus just performance costs and other factors that you typically had at the top so as we started working with them uh I guess that beginning was more tactical because we really had to find a way to respond uh we were starting to be asked about our own efforts and in regards to sustainability we have our headquarters in Somerset and our second Headquarters in Austin Texas um those are the gold certified we've been installing solar panels producing waste across the company recycling efforts and so forth charging stations for electric vehicles all that sort of thing to make our company more sustainable in in uh in our offices and in our headquarters um but it's a lot more than that and what we found was that we wanted to look to our vast number of supply of customers and partners we have over 30 000 partners that would work with globally and tens of thousands of customers and we wanted to find best practices and Technologies and services that we could uh talk about with these customers and apply and help integrate together as a as a really large Global uh reseller and integrator we can have a play there and bring these things together from multiple uh partners that we work with to help solve customer problems and so over time it's become more strategic and we've been uh as a company building the uh the the the forward efforts through organizing a true formal sustainability team and growing that um and then also reporting for CDP echovatus and so forth and it's really that all has been coming about in the last couple of years and we take it very seriously it sounds like it also sounds like from the customer's perspective they're shifting from that tactical maybe early initial approach to being more strategic to really enabling sustainable I.T across their organization and I imagine from a business driver's perspective John saws and Charlie are you hearing customers you talked about it being part of rfps but also where are customers in terms of we need to have a sustainable I.T strategy so that we can attract and retain the right investors we can attract and retain customers Charlie John what are your thoughts on that yeah that's top of mind with uh with all the folks that we're talking to uh I would say there's probably a three-way tie for the importance of uh attracting and retaining investors as you said plus customers customers are shopping their customers are shopping for who has aligned their ESG priorities in sustainable priorities uh with their own and who is going to help them with their own reporting of you know spoke to and ultimately scope three reporting from greenhouse gas emissions and then the attracting and retaining Talent uh it's another element now of when you're bringing on a new talent to your organization they have a choice and they're thinking with their decision to accept a role or not within your organization of what your strategies are and do they align so we're seeing those almost interchangeable in terms of priorities with with the customers we're talking to it was a little surprising because we thought initially this is really focused on investors attracting the investors but it really has become quite a bit more than that and it's been actually very interesting to see the development of that prioritization more comprehensive across the organization let's bring Dr John Fry into the conversation and Terry your neck so stay tuned Dr Frey can you talk about hpe and Shia partnering together what are some of the key aspects of the relationship that help one another support and enable each other's aggressive goals where sustainability is concerned yeah it's a great question and one of the things about the sustainability domain in solving these climate challenges that we all have is we've got to come together and partner to solve them no one company's going to solve them by themselves and for our Collective customers the same way from an hpe perspective we bring the expertise on our products we bring in a sustainable I.T point of view where we've written many white papers on the topic and even workbooks that help companies Implement a sustainable I.T program but our direct sales forces can't reach all of our customers and in many cases we don't have the local knowledge that our business partners like Shi bring to the table so they extend the reach they bring their own expertise their portfolio that they offer to the customer is wider than just Enterprise Products so by working together we can do a better job of helping the customer meet their own needs give them the right Technology Solutions and enhance that customer experience it's because they get more value from us collectively it really is better together which is a very appropriate name for our segment here Terry let's bring you into the conversation talk to us about AMD how is it helping customers to create that sustainable I.T strategy and what are some of the differentiators that what AMD is doing that that are able to be delivered through Partners like Shi well Lisa you use the word enabling um just a short while ago and fundamentally AMD enables hpe and partners like Shi to bring differentiated solutions to customers so in the data center space We Begin our journey in 2017 with some fundamental Design Elements for our processor technology that we're really keenly focused on improving performance but also efficiency so now the the most common measure that we see for the types of customers that Charlie and John were talking about was really that measure of performance per watt and you'll continue to see AMD enable um customers to to try to find ways to to do more in a sustainable way within the constraints that they may be facing whether it's availability of power data center space or just needing to meet overall sustainability goals so we have skills and expertise and tools that we make available to hpe and to Shi to help them have even stronger differentiated conversations with customers sounds like to me Terry that it's that AMD can be even more of an more than an enabler but really an accelerator of what customers are able to do from a strategic perspective on sustainability you're right about that and and we actually have tools greenhouse gas TCO tools that can be leveraged to really quantify the impact of some of the the new technology decisions that customers are making to allow them to achieve their goals so we're really proud of the work that we're doing in partnership with companies like hpe and Shi Better Together as we've said at the beginning and just a minute ago Charlie let's bring you back in talk to us a little bit about what Shi is doing to leverage sustainable I.T and enable your customers to meet their sustainability goals and their initiatives so for quite a while we've had uh some offerings to help customers especially in the end user compute side a lot of customers were interested in I've got assets for you know let's say a large sales force that had been carrying tablets or laptops and you know those need to be refreshed what do I do with those how do I responsibly retire or recycle those and we've been offering solutions for that for quite some time it's within the last year or two when we started offering for them guarantees and Assurance assurances of how they can if that equipment is reusable by somebody else how can we issue them you know credits for uh carving credits for reuse of that equipment somewhere else so it's not necessarily going to be E-Waste it's uh something that can be recycled and reused we have other programs with helping extend the life of of some systems where they look at boy I have an awful lot of data on these machines where historically they might want to just retire those because the the sensitivity of the data needed to be handled very specifically we can help them properly remove the sensitive data and still allow reuse of that equipment so we've been able to accomplish some Creative Solutions specifically around end user compute in the past but we are looking to new ways now to to really help extend that into Data Center infrastructure and Beyond to really help with what are the needs what are the the best ways to help our customers handle the things that are challenging them [Music] that's a great point that you bring up Charlie and the security kind of popped into my head here John saw his question for you when you're in customer conversations and you're talking about or maybe they're talking about help us with waste reduction with recycling where are you having those customer conversations I know sustainability is a board level it's a c-level discussion but where are you having those conversations within the customer organization well so it's a it's a combination of um organizations within the customer these are these Global organizations typically when we're talking about asset like cycle management asset recovery how do you do that in a sustainable Green Way and securely the customers we're dealing with I mean security is top sustainability is right up there too obviously but uh um Charlie touched on a lot of those things and these are Global rollouts tens of thousands of employees typically to to have mobile devices laptops and phones and so forth um and they often are looking for a true managed service around the world that takes into consideration things like the most efficient way to ship products to to the employees and how do you do that in a sustainable way you need to think about that does it all go to a central location um or to each individual's home during the pandemic that made a lot of sense to do it that way I think the reason I wanted to touch on those things is that well for for example one European pharmaceutical that the states and their reports that they are already in scope one in scope two they're fully uh Net Zero at this point and and they say but that only solves three percent of our overall sustainability goals uh 97 is scope three it's travel it's shipping it's it's uh it's all the all these things that are out of their direct control a lot of times but they're coming to us now as a as a supplier and ask and and we're filling out forms and rfps and so forth uh to show that we can be a sustainable supplier in their supply chain because that's their next big goal so sustainable supply chain absolutely Dr John Fry and Terry I want to kind of get your perspectives Charlie talked about from a customer requirements perspective customers coming through RFP saying hey we've got to work with vendors who have clear sustainability initiatives that are well underway hpe and AMD hearing the same thing Dr Fry will start with you and then Terry sure absolutely we receive about 2500 customer questionnaires just on sustainability every year and that's come up from a few hundred so yeah absolutely accelerating then the conversations turn deeper can you help us quantify our carbon emissions and power consumption then the conversation has recently gone even further to when can hpe offer Net Zero or carbon neutral Technology Solutions to the customer so that they don't have to account for those Solutions in their own carbon footprint so the questions are getting more sophisticated the need for the data and the accuracy of the data is climbing and as we see potential regulatory disclosure requirements around carbon emissions I think this trend is just going to continue up yeah and we see the same thing uh we get asked more and more from our customers and partners around our own corporate sustainability goals but the surveying that the survey work that we've done with customers has led us to you know understand that you know approximately 75 percent of customers are going to make sustainability goals a key component of their rfis in 2023 which is right around the corner and you know 60 of those same customers really expect to have business level kpis uh in the new year that are really related to sustainability so this is not just a a kind of a buzzword topic this is this is kind of business imperatives that you know the company the companies like hpe and AMD and the partners like Shi that really stand behind it and really are proactive in getting out in front of customers to help are really going to be ahead of the game that's a great point that you make Terry there that this isn't we're not talking about a buzzword here we're talking about a business imperative for businesses of probably all sizes across all Industries and Dr Farr you mentioned regulations and something that we just noticed is that the SEC recently said it's proposing some rules where companies must disclose greenhouse gas emissions um if they were if that were to to come into play I'm going to come back to Charlie and John saws how would Shi and frankly at hpe and AMD be able to help companies comply if that type of Regulation were to be implemented Charlie yeah so we are in the process right now of building out a service to help customers specifically with that with the reporting we know reporting is a challenge uh the scope 2 reporting is a challenge and scope three that I guess people thought was going to be a ways out now all of a sudden hey if you have made a public statement that you're going to make an impact on your scope three uh targets and you have to report on them so that that has become really important very quickly uh as word about this requirement is rumbling around uh there's concern so we are actually working right now on something it's a little too early to fully disclose but stay tuned because we have something coming that's interesting definitely peaked my ears are are parked here Charlie well stay tuned for that Dr Brian Terry can you talk about together with Shi hpe and AMD enabling customers to manage access to the data obviously which is critical and it's doing nothing but growing and proliferating key folks need access to it we talked a little bit about security but how are from a Better Together perspective Dr Fry will start with you how are you really helping organizations on that sustainability journey to ensure that data can be accessible to those who need it when they need it and these days what is real-time requirements yeah it's an increasing challenge in fact we have changed the HP Story the way we talk about hpe's value proposition to talk about data first modernization so how often do you collect data where do you store it how do you avoid moving it how do you make sure if you're going to collect data you get insights from that data that change your business or add business value and then how long do you retain that data afterward and all of that factors into sustainable I.T because when I talk to technology Executives what they tell me again and again is there's this presumption within their user community that storage is free and so when when they have needs for collecting data for example if if once an hour would do okay but the system would collect it once a minute the default the user asks for of course is once a minute and then are you getting insights from that data or are we moving it that becomes more important when you're moving data back and forth between the public cloud or the edge because there is quite a network penalty for moving that equipment across your network there's huge power and carbon implications of doing that so it's really making a better decision about what do we collect why do we collect it what we're going to do with it when we collect and how we store it and for years customers have really talked about you know modernization and the need to modernize their data center you know I fundamentally believe that sustainability is really that Catalyst to really Drive true modernization and as they think forward um you know when we work with with hpe you know they offer a variety of purpose-built servers that can play a role in you know specific customer workloads from the larger supercomputers down to kind of general purpose servers and when we work with Partners like Shi not only can they deliver the full Suite of um offerings for on-premise deployments they're also very well positioned to leverage the public Cloud infrastructure for those workloads that really belong there and that certainly can help customers kind of achieve an end-to-end sustainability goal that's a great point that that it needs to be strategic but it also needs to be an end-to-end goal we're just about out of time but I wanted to give John saws the last word here take us out John what are some of the things Charlie kind of teased some of the things that are coming out that piqued my interest but what are some of the things that you're excited about as hpe AMD and Shi really help customers achieve their sustainability initiatives sure um a couple of comments here um so Charlie yeah you touched on some upcoming capabilities uh that uh Shi will have around the area of monitoring and management see this is difficult for all customers to be able to report in this formal way this is a train coming at everybody very quickly and um they're not ready most customers aren't ready and if we can help um as as a reseller integrator assessments to be able to understand what they're currently running compared to different scenarios of where they could go to in a future state that seems valuable if we can help in that way that's those are things that we're looking into specifically uh you know greenhouse gas emissions relevant assessments and and um and what in the comments uh of Terry and John around the power per watt and um the vast um uh portfolio of technologies that they that they had to address various workloads is uh is fantastic we'd be able to help point to Technologies like that and move customers in that direction I think as a as an integrator and a technical advisor to customers I saw an article on BBC this morning that I I think if we think about how we're working with our customers and we can help them maybe think differently about how they're using their technology to solve problems um the BBC article mentioned this was ethereum a cryptocurrency and they have a big project called merge and today was a go live date and BBC US news outlets have been reporting on it they basically changed the model from a model called The Power of work which takes a a lot of compute and graphic GPU power and so forth around the world and it's now called a power of stake which means that the people that validate that their actions in this environment are correct they have to put up a stake of their own cryptocurrency and if they're wrong it's taken from them this new model reduces the emissions of their um uh environment by 99 plus percent the June emissions from ethereum were it was 120 uh terawatts per per year terawatt hours per year and they reduced it um actually that's the equivalent of what the Netherlands needed for energy so the comparable to a medium-sized country so if you can think differently about how to solve problems it may be on-prem it may be extremely it may be that may be the public cloud in some cases or other you know interesting Innovative Technologies that the AMD hpe other partners that we can bring in along along with them as well we can solve problems differently there is a lot going on the opportunities that you all talked about to really make such a huge societal impact and impact to our planet are exciting we thank you so much for talking together about how hpe AMD and sha are really working in partnership in Synergy to help your customers across every organization really become much more focused much more collaborative about sustainable I.T guys we so appreciate your time and thank you for your insights Thank you Lisa thank you my pleasure for my guests I'm Lisa Martin in a moment Dan Molina is going to join me he's the co-president and chief technology officer of nth generation you're watching the cube the leader in high tech Enterprise coverage [Music]

(upbeat music) >> Hey everyone. Lisa Martin here of theCUBE. I have three guests now here with me. Please welcome Dave Fafel, chief technology officer at WEI. And welcome back to the program, Terry Richardson, North American channel chief at AMD, and Dr. John Fry, chief technologist, sustainable transformation at HPE. Gentlemen, it's great to have you on the program. Thanks so much for hopping on. >> Thanks for having us. >> Thank you. >> (indistinct) >> So, Dave, let's start with you, a lot of acronyms here. Talk to us about WEI and its approach to sustainability. >> Yeah, absolutely, sure. So, WEI is a innovative, full service, customer-centric, IT solutions provider. We're experts in business technology improvement, in driving efficiency, helping our customers to optimize their IT environments. That's what we do. And of course, sustainability is really now part of the core function in architecting IT solutions these days. It has to be. I look at sustainability and I hear the word sustainability and I think efficiency. And that's the way that our organization designs solutions for our customers today. >> Talk about the impetus. You mentioned being customer centric you talked about efficiency, all incredibly important to all of us on this Zoom, but Dave, talk about the impetus for WEI to develop and implement this sustainability initiative. Well, I mean, so look, for WEI, it's part of our business model, it's part of our culture. So it's natural that that comes out in the solutions that we design for our customers, but we're trying to solve business problems for our customers, We're not just geeks building something really cool with the latest technology, we're trying to solve real world problems and sustainability addresses real world issues. And so, our customers are looking for us to help them either implement their sustainability programs, or to mature their sustainability programs. And IT has a big responsibility in that. And so, when we're working with them to solve these problems we're really solving that business problem, solving that sustainability, IT initiative that they have. >> And we're going to dig and unpack that in a little bit. John, I want to bring you into the conversation. HPE and AMD have been long partnering on advancing sustainability goals for quite a long time now. Can you talk about how HPE and WEI are partnering? What are some of the key aspects of the relationship that help support not only the goals that Dave talked about but HPE's sustainability goals? >> Yeah, absolutely. One of the things in sustainability is partnership is really leadership. No one company can do this by themselves, and customers really need that input and perspective from all of their partners as part of this process. So, for us as HPE, 65% of our carbon footprint, for example, is when our customers use our technology products. So, for us to lower our carbon footprint, it also requires us helping the customer do that. And that's where the power of the AMD and HPE relationship comes together, but we can't give our expertise widely to every customer in the world. And so, we use our channel partners like WEI to not only extend our reach, but they bring that deep knowledge of the customer and all of their operations across technology, even places where HPE does not offer that technology, in the client space, for example, or in the printer space. And so, what it allows us to do is develop better solutions for the customer. WEI has a deep relationship with the customer. They have a deep expertise in local nuances if there's regulations or local constraints. In fact, in many cities in the world, you can't, for example, build new data centers because of power infrastructure constraints. So, that's where we leverage partners like WEI to improve the customer experience and make sure that we give the best solutions to the customer. >> All about improving those customer experiences as demand for technology does nothing but increase. Terry, let's bring you into the conversation now. Speaking of customer centricity, we find that sustainability is very complicated, that a lot of large companies might have the resources to figure it out, but some of the smaller and mid-size companies might not quite have the boots on the street. What should some of the smaller organizations do, Terry, in your perspective to get started where sustainability is concerned? >> Well, I first off, appreciate the opportunity to be here and it's really terrific to have such a strong partnership with both HPE and WEI in order to deliver innovative solutions to customers. I think what AMD brings to the table is a real choice for customers that they haven't had. All of our personnel are really expert in articulating a differentiated value proposition that hits on a little bit what John talked about which is higher performance but with very, very efficient systems. And we've been offering those to the market since 2017 and we continued to get better. And now, there's an absolute opportunity to do more with same amount of servers, or do a workload with far fewer servers, that require far less energy. So, bringing in the AMD resources to assist the efforts of HPE and WEI, I would say, would be a good step for customers. >> Are there any Terry, sticking with you, any recommendations or tools particularly that you've seen really help customers get kicked off well, and strategically? >> Yeah, there actually are a couple that are readily available and I would encourage through WEI, customers take a close look. Two that really come to mind. We have a virtualization TCO tool that helps optimize configurations for virtual environments. And one of our newest tools is one that's focused on bare metal and greenhouse gas emissions TCO. So, really quantifying the impact to customers and expressed in terms that are familiar and help them achieve their sustainability initiatives. >> Excellent, that's great that those resources are available for customers, especially those smaller ones that might need a bit more guidance and handholding. Dave, let's come back to you. Let's now unpack the sustainability initiatives at WEI that you're really leveraging and implementing to meet the demands of customers and their future technology demands. >> Yeah, absolutely. Yeah, that's a great question, what we're getting to. So, look, we're going to combine, the advancements in technology from an AMD and from an HPE into an architecture that's really usable for a customer. So, 10 years ago, we were all looking at consolidation ratios for virtualization as one driver to a more efficient IT environment. And so, look, we've done this over the last decade, where we've added as many virtual machines to a server as we can get and as many containers to a physical machine as we can get, and now we've got to find other ways to drive efficiency. And so, when we see technology from AMD that's maybe having the socket count from a CPU perspective with a 30 plus percent reduction in power consumption and heat output, that's huge. So, we're architecting these solutions, using that best of breed technology but also implementing technology that was previously consumed more by larger enterprise customers for that small and medium customer base that you mentioned earlier. And that is implementing infrastructure as a service as a way to more efficiently utilize IT resources. So, we'll design the right systems, we'll put them into a consumption model that allows us to dial up and down when we need to, as opposed to having to build oversized environments that consume too much power, that produce too much heat and that aren't really driving toward those sustainability initiatives. So, we want to change not only the technology but also the models of which we consume IT. That's how we're driving that forward with customers today. >> And Dave, another question for you. How are you seeing from a cultural perspective this be adopted and accepted across the customer base? 'Cause change management is challenging but we all know sustainability is a focus of pretty much every business on the planet. >> It is, but fortunately we've got good partners like AMD and HPE, so they make it easy for the channel to implement these things. If you take a look at HPE's GreenLake solutions, for instance. These are tool sets that allow us to go and easily implement that for customers and reduce that change or cost of change for them. In fact, it actually allows them to take the models that they're currently used to and yet still leverage that new consumption model that I just referred to. >> Got it, awesome, thank you. John, let's go back to you. There's a tremendous opportunity here for customers from a sustainability standpoint, across every industry. And I was looking at some data that HPE shared that said for example, 25% of compute in data centers is comatose. First of all, I think the description is brilliant. What are some of the outcomes that customers can expect in working with HPE and AMD and WEI in terms of better leveraging their technology investments today and in the future? >> Yeah, it's a great question. And we do see a tremendous amount of equipment in the average data center that's not doing any useful work. And so, comatose is a great name for that. We also see a tremendous amount of equipment that's being dramatically underutilized as well. So, when the three companies come together and share that expertise with the customer and the customer follows through on that you can expect a whole lot of things. So, you reduce over-provisioning, you have the IT assets in your infrastructure doing useful work for you. The second thing you you tend to see is utilization levels going up. So, where the average utilization level across compute today even in a virtualized or containerized environment is about 30%. You see that almost doubling, for example, in good scenarios where the customer has that equipment doing a tremendous amount of additional work, keeping them from needing to add additional assets to the infrastructure. So, all of that drives cost savings, both CapEx and OPEX, cost savings opportunities. It drives efficiency savings. If you have less equipment being more well utilized and better managed, you tend not to have over temperature situations or equipment that goes down for no explainable reason that then drives staff work to go find out and fix workloads that go down. In fact, many of our customers are measured on service level agreements. They want to keep that infrastructure running all the time to keep their customers happy as well. And finally, one that sometimes is missed is employee satisfaction. Technology companies are having a tough enough time finding and attracting and retaining employees to start with but those employees want to see how what they're doing contributes to purpose. So, as our customers can use these employees to do more productive work, show them how it connects to the purpose of their company and show them how it makes the world a better place at the same time, they can do a better job of holding on to those employees that they so value. >> That's such a great point, John, that you bring up that employee retention but also talent attraction and retention for your customers. Dave, back to you. Are you seeing more and more customers come to WEI, saying, "We have sustainability initiatives. "We can only partner with companies that are also really focused on this because we need to make sure that our employees are satisfied and that we can attract and retain customers." Is that something that you're seeing an increase of? >> Yeah, absolutely. So very often, we're asked to explain how we're implementing sustainability in our business, that the partners that we work with are also doing the same and I'll give you an example of that. So, we've been talking about IT efficiency and good utilization of IT equipment but let's not forget that life cycles of IT equipment result in that equipment leaving a customer site eventually. So, we've got to be responsible in the way that we handle that. And so, this is the area where WEI has put together programs to connect the sustainability aspect of IT recycling, if you will, with the social aspect of corporate social responsibility. And that is, what do we do with this stuff? So, we offer programs to customers where we say, "Hey, look, let's take back some of that IT equipment, there's value in this." It may be that we need to go and recycle this in a responsible way. And we can extract valuable components out of this that result in funds to do something with. Well, what can we do with those funds? Can we put those towards social programs? So, this is where we, again, tie together sustainability and social responsibility. We've been talking about data centers but this also extends to other IT devices. So, if we're pulling back laptops, as an example, from a customer environment, well, those may still have a useful life someplace. Can we bring those to disadvantaged communities and utilize those for educational purposes and other things? Again, this is how WEI connects our customers with these opportunities to enhance their CSR programs. >> Tremendous opportunities there for customers across every industry. Dave, sticking with you for a second. From a differentiation perspective, talk about what the partnership with HPE and AMD delivers WEI from a unique value prop perspective. >> Yeah, so we touched on it a little bit already, and that is, you've got the incredible technology from AMD and from HPE that work seamlessly together but is also focused on driving down the cost of computing. I mean, just the overall efficiency built into design of these solutions makes it easy for an IT consultant like us to build an efficient architecture. But it's not just the technology. It's also the models, or the IT provisioning and consumption models that are important. And again, that's where the relationship between HPE and WEI comes together, because we get to leverage some of these other programs. I mentioned before GreenLake, as an example. This gives us the opportunity to build that infrastructure as service model for our customers who would otherwise maybe go out to a hyperscaler for a similar solution. But as we know, most of our customers even small and medium businesses, can't move everything out to the cloud. They have to use their own data centers. They have to keep data on site and on-prem. So, building that model for them drives efficiency and quite honestly, that's the thing that they're looking for, it's driving cost savings, it's driving efficiency, it's aiding their CSR initiatives. >> Got it. Let's chat now about the strategic versus the tactical. Terry, I would like to get your feedback and then John, yours as well. We talked a little bit about this already but how do you help advise organizations that might be in that tactical mode, approaching sustainability from a tactical mode and really up level that to a strategy that's around sustainable IT? Terry, what are some of the things that you're seeing in the marketplace? Well, at AMD we're fortunate to be passionate about partnerships and sustainability. We're fortunate to work with companies of all shapes and sizes and in different geographies around the world. Some are a little bit more advanced in the way they think about this, but it really is becoming a strategic imperative for companies. And I think certain companies don't know exactly how to proceed. So, the opportunity to educate and open their eyes to the way that you can do both, you can meet your IT goals and objectives, but also do it in a very socially responsible and sustainable way, to me is a win-win. And we welcome the opportunity to just have those conversations. I think some customers are not necessarily understanding how much IT can really contribute to their ability to meet their current and future sustainability goals. And we look forward to having as many conversations as possible 'cause it goes in the category of just the right thing to do. If you can power your IT and do things that are good for the planet and good for all. >> That's a great point. It really is the right thing to do. John, just question, last question for you, is similar to what I asked Terry, but I would like to know where are your customer conversations when it comes to really looking at IT as a big driver of sustainability? Who in the organization really needs to be the spearheads around that initiative? >> Yeah, great question. Often we see customers have one organization that sometimes is a sustainability organization. Sometimes the facility's a real estate organization or sometimes IT is spearheading this and often doing that in isolation. To your point, we really need to think about this as a sustainable IT strategy and get all the right organizations involved together. So, for example, for us, after seeing many customers that didn't know how to develop this strategy, we wrote a workbook called "Six Steps For Implementing A Sustainable IT Strategy." And the steps are things like figure out what your company goals already are that you've made public to your customers then grab the right stakeholders and bring them together. For example, you know you're going to have cost savings, so have the finance team in the room, You know this is going to save utilities, have the real estate team in the room. You know it's going to generate a sustainability benefit, have the sustainability team involved so that they can quantify the benefit in a meaningful manner. Have the communication and marketing teams because when companies implement a sustainable IT strategy they have a great story that they can then tell their customers about how they're doing a better job from an efficiency perspective and from an environmental perspective as well. So, when you bring all of those stakeholders together you can have a much broader and deeper strategy. It becomes a strategic imperative. And when your institutional investors, if you're publicly traded, or your customers come asking about your programs, you're ready to answer those questions in a credible manner. >> Sounds like it really needs to truly be a collaborative effort across the organization. You mentioned John's story and that goes back to employee retention, talent attraction and retention for your companies and your customers as well. We could go off on that but we're almost out of time. So, I want to go back to Dave to take us home here. You walked us through what WEI is doing from a sustainability initiative perspective, the impetus to develop that. What are some of the things that we can expect to see on the horizon from WEI where sustainability is concerned? What are you excited about? >> Well, that's a good question. So, we're excited about how we can continue to deploy those infrastructure as a service models. That's the next step in the direction. How do we automate these things, and then how do we quantify them? So, you've got to build the environment but then you've got to be able to measure it. And that's another area where WEI really adds value to this whole solution set is how are we measuring these things in the long term and developing a program that extends beyond just the implementation of this, but through its entire life cycle and the value of it? Because if you can quantify the value and if you can show what the savings really is and how it's helping customers meet their sustainability goals, well, guess what? They're going to want to implement more of this So, it's good business, and that's what we're excited about, is that next mile of implementation after we developed the initial architecture. >> That measurement is key. It sounds like then it really becomes a flywheel of sustainability. Gentlemen, thank you so much for joining me today talking about from your three perspectives and how you're partnering together to really enable businesses across any industry to develop a sustainable IT strategy that they can implement and then create a flywheel of optimization. We appreciate your insights and your time. >> Thank you. >> Thanks, Lisa. >> Thank you. >> All right, my pleasure for my guests, I'm Lisa Martin. In a moment, John and Terry and I are going to be joined by Charles Mulrooney, global presales engineering manager at SHI and John Sahs, global presales technical consultant at SHI. You're watching theCUBE, the leader in global tech coverage. (upbeat music)

(upbeat music) >> Sustainability has become one of the hottest topics, not just in enterprise tech, but across all industries. The relentless pace of technology improvement over the decades and orders of magnitude increases in density have created heat, power and cooling problems that are increasingly challenging to remediate. Intense efforts have been implemented over the years around data center design techniques to dissipate heat, use ambient air, liquid cooling and many other approaches that have been brought to bear to get power usage effectiveness, PUE, as close to one as possible. Welcome to Better Together Sustainability, presented by the CUBE and brought to you by Hewlett Packard Enterprise and AMD. In this program we'll lay out today's challenges and how leading companies are engineering solutions to the problems just introduced, along with some recommendations, best practices and resources as to how you can initiate or enhance your sustainability journey. First up to help us better understand this important topic are John Fry, senior technologist IT efficiency and sustainability at Hewlett Packard Enterprise and Terry Richardson, North America channel chief for AMD. Gents, welcome. >> Great to be here. >> (indistinct). >> John, let's start at the high level here. Why is sustainability such an important topic today? Why now? Why is it such a challenge for customers and, and how are you guys approaching the solutions? >> The topic has been an important topic for a number of years, but what we're seeing across the world is more and more corporations are putting in place climate targets and sustainability goals. And at the same time, boards and CEOs are starting to be asked about the topic as well, making this topic much more important for technology leaders across the globe. At the same time, technology leaders are fighting with space, power and cooling constraints that caused them to rethink their approach to IT. To get a better sense of how wide this challenge is, we did a survey last year and we asked 500 technology leaders across the globe if they were implementing sustainable IT goals and metrics and programs within their infrastructure. Personally, I thought the answer would be about 40% of them had these programs. Actually it turned out to be 96% of them. And so when we asked them why they were implementing these programs and what was the primary driver, what we heard from them was three things. Those of them that were the early adopters and the ones that move were moving the fastest told us they were putting these programs in place to attract and retain institutional investors. If they're a publicly traded company, their investors were already asking their boards, their CEOs, wanting to know what their company was doing to drive efficiency within their technology operations. Those companies in the middle, the ones that were just moving along at the same pace as many other companies around the world, told us they were putting these programs in place to attract and retain their customers. Customers are increasingly asking the companies they do business with about their sustainability aspirations specifically how technology contributes to their carbon emissions and their sustainability goals. And so these customers want to make sure that they can keep their own customers. And finally, a third group, the digital followers, that group of companies that's a little slower adopting programs, more conservative in nature. They said they were implementing these programs to attract and retain employees. In fact, over the last year or so, every customer we've talked to when they describe their pain points and their challenges that we can try to help them meet, has had a difficulty in finding employees. And so what we know is these younger employees coming into the workforce, if you can show them how what they are going to be doing connects to the purpose of their company and connects to making the world a better place, you can attract them easier and you can retain them longer. So a variety of business reasons why companies are looking at these programs, but what we know is when they implement these programs they often reduce over-provisioning. They save money, they have a lower environmental footprint, and again they have an easier time attracting and retaining employees. So for all of these reasons, driving sustainability into your IT operations is a great thing to do. >> Yeah, I never would've expected 96%. And of course, investors, customers and employees. I mean, this is the big three. Terry what's AMD's perspective on this topic? In other words, what do you bring to the table and the partnership? I mean, I know processors, but what's unique about AMD's contribution? >> Yeah. Thanks Dave. And, and John, great to be with you. Appreciate the opportunity and the partnership. You know, we too are very focused on sustainability and enjoy our partnership with HPE very much in this area. You know, since 2017, when AMD introduced its epic processor family, there's been a couple of core design elements in that technology. One has to do with performance. And the second has to do with efficiency. Both are critically important to today's topic of sustainability because increasingly, customers are understanding and measuring performance per watt and fortunately, AMD really excels in this area. So whether we're talking about the larger super computers in the world, or even general purpose servers, customers can fundamentally do more with fewer AMD servers than competitive alternatives. And so, so we, we really bring a technology element on the processor side, CPU and GPU, to play a role in delivering real ability for customers to meet some of their core sustainability goals. And of course, in partnership with HPE, together we have really a compelling story. >> Great. Thank you, Terry. And, and John, wonder if you could talk to the differentiation that you bring from HPE's perspective, the total package. >> Yeah, of course. The first thing as partnership. As Terry mentioned, AMD and HPE have been working together since HPE was founded actually, to drive power efficiency up to meet the demands of our customers. At the same time, as our customers have asked more and more questions around technology sustainability, we've realized that we needed to not only develop a point of view on that from an HPE perspective, but actually write the white papers that give the customer guidance for sustainable IT strategies, for tech refresh cycles, give them some guidance on what are the right questions to ask technology vendors when they're buying technology equipment. So a series of white papers and you might not appreciate why, but this is a topic that you can't go get a college degree in and frankly can't even buy a book on. So for customers to get that knowledge, they want to get it from experienced professionals around the globe. And in fact, in the survey that I mentioned earlier, we asked customers, where's the number one place that you expect to get your sustainable IT information from? And they said, our technology vendors. So for us, it's really about driving that point of view, sharing it with customers, helping customers get better and even pointing out some of the unintended consequences. So a great example, Dave, you mentioned PUE earlier. Many customers have been driving PUE down for a number of years, but often the way that they did that was optimizing the data center building infrastructure. They got PUE pretty low. Now, one of the things that happens and customers need to be aware of this, particularly if they're focused on PUE as their primary metric, is when they optimize their IT stack and make that smaller, PUE actually goes up. And at first they think, well, wait a minute, that metric is going in the wrong direction. But when you remember it's a ratio, if you get that IT stack component smaller, then you're driving efficiency even if PUE goes the wrong direction. So part of the conversation then is you might want to look at PUE internally, but perhaps you've outgrown PUE and now have an opportunity to look at other metrics like carbon emissions per workload, or or power consumption per piece of equipment or rack. So all of this drives back to that upward trajectory that Terry was talking about where customers are really interested in power performance. So as we share those stories with customers, share the expertise how to move along this journey, that really provides great differentiation for HPE and AMD together. >> So that's interesting. So PUE is not necessarily the holy grail metric. There are other metrics that you, you should look at. Number one, and number two the way you interpret PUE is changing for the better. So thank you for that context. I wonder Terry, do, do you have any like proof points or examples that you can share? >> Yeah, so one that immediately comes to mind that was a manifestation of some terrific collaboration between AMD and HPE was their recently announced implementation of the Frontier supercomputer. That was a project that we collaborated on for a long time. And, and where we ended up was turning over to the government a supercomputer that is currently the highest performing in the world, broke the exaFLOP barrier. And probably even more importantly is number one on the Green500 list of the top super computers. And, and together we enjoy favorable rankings in other systems, but that's the one that, that really stands out in terms of at scale implementation to shine really a spotlight on what we can do together. Certainly for other customers doesn't have to be the world's largest super computer. It's not uncommon that we see customers just kind of in general purpose business applications in their data centers to be able to do more with less, you know, meaning, you know, you know a third of the servers oftentimes delivering not only a very strong TCO but the environmental benefit that gets associated with significantly reduced energy that can be expressed in reduction in, in overall CO2 emissions and other, other ways to express the benefit, whether it's, you know the equivalent of, of planting you know, acres of forest or whatever. So we're really proud of the proof points that we have and and look forward to the opportunity to together explain this more fully to customers and partners. >> Right? So John, Terry sort of alluded to this being more broad based. I know HPE has a very strong focus on HPC. Sorry for all the acronyms, but high performance computing. But the, so this is more broad based than just the super computing business, right John? >> Yeah, absolutely. We see these performance benefits for customers and industry standard servers as well. In fact, many customers, that's the primary type of equipment they use and they want better power performance. They either want to as Terry alluded to, use less equipment to do the same amount of work, or if they've run into a space or power or cooling constraint in their data centers, they want to be able to increase workloads in the same footprint. So it allows them to take better use of their data centers. And for some customers even the data center enclosure that they started with they can actually use a much smaller amount of space. In fact, we have some that even move over to co-location facilities as they improve that performance per watt, and can do more work in the smaller space. So it starts an industry standard server, but increasingly we're seeing customers considering liquid cooling solutions and that generally moves them into the high performance compute space as well right now. So those performance improvements exist across that entire spectrum. >> So since you brought up liquid cooling John, I mean can you share any best practices? I mean, like what do you do with all that heated liquid? >> Yeah, it's a great, great question. And we have seen a lot more interest from customers in liquid cooling and there's a variety of things that you can do, but if you're considering liquid cooling the opportunities to think broader than just the IT stack. So if you're going to use a cooling loop anyhow and you're going to generate warm liquid coming off the it equipment as waste, think about what you can do with that. We have a, a government customer here in the United States that designed their high performance computer while they were designing the building it went in. So they're able to use that hot air, hot water, excuse me coming off the IT equipment to heat the entire building. And that provides a great use of that warm water. In many parts of the world, that warm water can either be used on a hot water utility grid or it can even be used on a steam grid if you can get it warm enough. Other places we're aware of customers (indistinct) and greenhouses next to data centers and using both the warm air and the warm water from the data center to heat the greenhouse as well. So we're encouraging customers to take a step back, look at the entire system, look at anything coming out of that system that once was waste and start to think about how can we use that what was waste now as an input to another process. >> Right, that's system thinking and some, some pragmatic examples there. Can, can you each summarize, maybe start Terry, with you AMD's and HPE's respective climate goals that may, Terry then John chime in please. >> Yeah, I'll go first. We actually have four publicly stated goals. The first one is I think very aggressive but we've got a track record of doing something similar in our client business. And, and so kind of goal number one is a 30 X increase in energy efficiency for AMD processors and accelerators powering servers for AI and HPC by 2025. The second is broad based across the corporation is a 50% absolute reduction in greenhouse gas emissions from AMD operations by 2030. And then the third is 100% of AMD manufacturing suppliers will have published greenhouse gas emissions reduction goals by 2025. And we've declared that 80% or greater of our manufacturing suppliers will source renewable energy by 2025. Those are the, those are the four big publicly stated goals and objectives that we have in this area. >> You know what I like about those Terry? A lot of, a lot of these sustainability goals these moonshot goals is like by 2050, it's like, okay. But I, I like the focus on '25 and then of course there's one in there at the end of the decade. All right, John, maybe you could share with us HPE's approach. >> Yeah, absolutely. And we've had almost two decades of emissions reduction goals and our current goals, which we accelerated by 10 years last year, are to be carbon new or excuse me, net zero by 2040. And that's a science based target-approved goal. In fact, one of the first in the world. And we're doing that because we believe that 2050 is too long to wait. And so how we reach that net zero goal by 2040, is by 2030, an interim step is to reduce our scopes one and two, our direct and energy related emissions by 70% from 2020. And that includes sourcing 100% renewable energy across all of our operations. At the same time, the bigger part of our footprint is in our supply chain and when our customers use our products, so we're going to leverage our as a service strategy HPE GreenLake and our energy efficient portfolio of products to reduce our scope three carbon emissions 42% over that 2020 baseline by 2030, and as with AMD as well, we have a goal to have 80% of our suppliers by spend have their own science based targets so that we know that their commitments are scientifically validated. And then the longer step, how we reach net zero by 2040 is by reducing our entire footprint scopes one, two and three by 90% and then balance the rest. >> Yeah. So again, I mean, you know 2030 is only eight years away, a little more. And so if, if, if you have a, a target of 2030 you have to figure out, okay, how are you going to get there? The, if you say, you know, longer, you know in the century you got this balloon payment, you know that you're thinking about. So, so great job, both, both companies and and really making more specific goals that we can quantify you know, year by year. All right, last question, John. Are there any resources that you can share to help customers, you know, get started maybe if they want to get started on their own sustainability strategy or maybe they're part way through and they just want to see how they're doing. >> Yeah, absolutely much of what Terry and I have talked about are available in an executive workbook that we wrote called "Six Steps For Implementing a Sustainable IT Strategy" and that workbook's freely available online and we'll post the URL so that you can get a copy of it. And we really developed that workbook because what we found is, although we had white papers on a variety of these topics, executives said we really need a little bit more specific steps to work through this and implement that sustainable IT strategy. And the reason for that, by the way is that so many of our customers when they start this sustainable IT journey, they take a a variety of tactical steps, but they don't have an overarching strategy that they're really trying to drive. And often they don't do things like bring all the stakeholders they need together. Often they make improvements without measuring their baseline first. So in this workbook, we lead them step by step how to gather the right resources internally, how to make the progress, talk about the progress in a credible way, and then make decisions on where they go next to drive efficiencies. >> Yeah, really that system thinking is, is, is critical. Guys. Thanks so much for your time. Really appreciate it. >> Thank you. >> Okay guys, thanks for your time today. I really appreciate it. In a moment, We're going to toss it over to Lisa Martin out of our Palo Alto studio and bring in Dave Faffel, chief technology officer at WEI, along with John and Terry, to talk about what WEI is doing in this space to address sustainability challenges. You're watching Better Together Sustainability brought to you by HPE and AMD in collaboration with the CUBE, your leader in enterprise and emerging tech coverage. (lilting music)

>>From around the globe. It's the cube with digital coverage, a BizOps manifesto unveiled brought to you by biz ops coalition. >>Hey, welcome back everybody. Jeff Frick here with the cube. Welcome back to our ongoing coverage of the biz ops manifesto. Unveil. Something has been in the works for a little while. Today's the formal unveiling, and we're excited to have three of the core founding members of the manifesto authors of the manifesto. If you will, uh, joining us again, we've had them all on individually. Now we're going to have a great power panel. First up. We're gonna have Mitt Kirsten returning he's the founder and CEO of Tasktop mic. Good to see you again. Where are you dialing in from? >>Great to see you again, Jeff I'm dialing from Vancouver, >>We're Canada, Vancouver, Canada. One of my favorite cities in the whole wide world. Also we've got Tom Davenport come in from across the country. He's a distinguished professor and author from Babson college, Tom. Great to see you. And I think you said you're at a fun, exotic place on the East coast >>Realm of Memphis shoes. That's on Cape Cod. >>Great to see you again and also joining surge Lucio. He is the VP and general manager enterprise software division at Broadcom surge. Great to see you again, where are you coming in from? >>Uh, from Boston right next to Cape Cod. >>Terrific. So welcome back, everybody again. Congratulations on this day. I know it's been a lot of work to get here for this unveil, but let's just jump into it. The biz ops manifesto, what was the initial reason to do this? And how did you decide to do it in a kind of a coalition, a way bringing together a group of people versus just making it an internal company, uh, initiative that, you know, you can do better stuff within your own company, surge, why don't we start with you? >>Yeah, so, so I think we were at a really critical juncture, right? Many, um, large enterprises are basically struggling with their digital transformation. Um, in fact, um, many recognized that, uh, the, the business side, it collaboration has been, uh, one of the major impediments, uh, to drive that kind of transformation. That, and if we look at the industry today, many people are, whether we're talking about vendors or, um, you know, system integrators, consulting firms are talking about the same kind of concepts, but using very different language. And so we believe that bringing all these different players together, um, as part of the coalition and formalizing, uh, basically the core principles and values in a BizOps manifesto, we can really start to F could have a much bigger movement where we can all talk about kind of the same concepts and we can really start to provide, could have a much better support for large organizations to, to transform. Uh, so whether it is technology or services or, um, or training, I think that that's really the value of bringing all of these players together, right. >>And mic to you. Why did you get involved in this, in this effort? >>So I've been closely involved the agile movement since it started two decades with that manifesto. And I think we got a lot of improvement at the team level, and I think that was just no. Did we really need to improve at the business level? Every company is trying to become a software innovator, trying to make sure that they can pivot quickly and the changing market economy and what everyone's dealing with in terms of needing to deliver value to customers sooner. However, agile practices have really focused on these metrics, these measures and understanding processes that help teams be productive. Those things now need to be elevated to the business as a whole. And that just hasn't happened. Uh, organizations are actually failing because they're measuring activities and how they're becoming more agile, how teams are functioning, not how much quickly they're delivering value to the customer. So we need to now move past that. And that's exactly what the manifesto provides. Right, >>Right, right. And Tom, to you, you've been covering tech for a very long time. You've been looking at really hard challenges and a lot of work around analytics and data and data evolution. So there's a definitely a data angle here. I wonder if you could kind of share your perspective of what you got excited to, uh, to sign onto this manifesto. >>Sure. Well, I have, you know, for the past 15 or 20 years, I've been focusing on data and analytics and AI, but before that I was a process management guy and a knowledge management guy. And in general, I think, you know, we've just kind of optimize that to narrow a level, whether you're talking about agile or dev ops or ML ops, any of these kinds of ops oriented movements, we're making individual project, um, performance and productivity better, but we're not changing the business, uh, effectively enough. And that's the thing that appealed to me about the biz ops idea, that we're finally creating a closer connection between what we do with technology and how it changes the business and provides value to it. >>Great. Uh, surge back to you, right? I mean, people have been talking about digital transformation for a long time and it's been, you know, kind of trucking along and then covert hit and it was instant Lightswitch. Everyone's working from home. You've got a lot more reliance on your digital tools, digital communication, uh, both within your customer base and your partner base, but also then your employees when you're, if you could share how that really pushed this all along. Right? Because now suddenly the acceleration of digital transformation is higher. Even more importantly, you got much more critical decisions to make into what you do next. So kind of your portfolio management of projects has been elevated significantly when maybe revenues are down, uh, and you really have to, uh, to prioritize and get it right. >>Yeah. Maybe I'll just start by quoting Satina Nello basically recently said that they're speeding the two years of digital preservation just last two months in any many ways. That's true. Um, but yet when we look at large enterprises, they're still struggling with a kind of a changes in culture. They really need to drive to be able to disrupt themselves. And not surprisingly, you know, when we look at certain parts of the industry, you know, we see some things which are very disturbing, right? So about 40% of the personal loans today are being, uh, origin data it's by fintechs, uh, of a like of Sophie or, uh, or a lending club, right? Not to a traditional brick and mortar for BEC. And so the, well, there is kind of a much more of an appetite and it's a, it's more of a survival type of driver these days. >>Uh, the reality is that's in order for these large enterprises to truly transform and engage on this digital transformation, they need to start to really align the business nightie, you know, in many ways and make cover. Does agile really emerge from the core desire to truly improve software predictability between which we've really missed is all the way we start to aligning the software predictability to business predictability, and to be able to have continual sleep continuous improvement and measurement of business outcomes. So by aligning that of these, uh, discuss inward metrics, that's, it is typically being using to business outcomes. We think we can start to really ELP, uh, different stakeholders within the organization to collaborate. So I think there is more than ever. There's an imperative to acts now. Um, and, and resolves, I think is kind of the right approach to drive that kind of transformation. Right. >>I want to follow up on the culture comment, uh, with you, Tom, because you've talked before about kind of process flow and process flow throughout a whore and an organization. And, you know, we talk about people process and tech all the time. And I think the tech is the easy part compared to actually changing the people the way they think. And then the actual processes that they put in place. It's a much more difficult issue than just the tech issue to get this digital transformation in your organization. >>Yeah. You know, I've always found that the soft stuff about, you know, the culture of a behavior, the values is the hard stuff to change and more and more, we, we realized that to be successful with any kind of digital transformation you have to change people's behaviors and attitudes. Um, we haven't made as much progress in that area as we might have. I mean, I've done some surveys suggesting that most organizations still don't have data driven cultures. And in many cases there is a lower percentage of companies that say they have that then, um, did a few years ago. So we're kind of moving in the wrong direction, which means I think that we have to start explicitly addressing that, um, cultural, behavioral dimension and not just assuming that it will happen if we, if we build system, if we build it, they won't necessarily come. Right. >>Right. So I want to go to you Nick. Cause you know, we're talking about workflows and flow, um, and, and you've written about flow both in terms of, um, you know, moving things along a process and trying to find bottlenecks, identify bottlenecks, which is now even more important again, when these decisions are much more critical. Cause you have a lot less, uh, wiggle room in tough times, but you also talked about flow from the culture side and the people side. So I wonder if you can just share your thoughts on, you know, using flow as a way to think about things, to get the answers better. >>Yeah, absolutely. And I'll refer back to what Tom has said. If you're optimized, you need to optimize your system. You need to optimize how you innovate and how you deliver value to the business and the customer. Now, what we've noticed in the data, since that we've learned from customers, value streams, enterprise organizations, value streams, is that when it's taking six months at the end to deliver that value with the flow is that slow. You've got a bunch of unhappy developers, unhappy customers when you're innovating half so high performing organizations, we can measure third and 10 float time and dates. All of a sudden that feedback loop, the satisfaction your developer's measurably goes up. So not only do you have people context, switching glass, you're delivering so much more value to customers at a lower cost because you've optimized for flow rather than optimizing for these other approximate tricks that we use, which is how efficient is my agile team. How quickly can we deploy software? Those are important, but they do not provide the value of agility of fast learning of adaptability to the business. And that's exactly what the biz ops manifesto pushes your organization to do. You need to put in place this new operating model that's based on flow on the delivery of business value and on bringing value to market much more quickly than you were before. Right. >>I love that. And I'm going back to you, Tom, on that to follow up. Cause I think, I don't think people think enough about how they prioritize what they're optimizing for. Cause you know, if you're optimizing for a versus B, you know, you can have a very different product that you kick out and let you know. My favorite example is with Clayton Christianson and innovator's dilemma talking about the three inch hard drive. If you optimize it for power, you know, is one thing, if you optimize it for vibration is another thing and sure enough, you know, they missed it on the poem because it was the, it was the game console, which, which drove that whole business. So when you, when you're talking to customers and we think we hear it with cloud all the time, people optimizing for cost efficiency, instead of thinking about it as an innovation tool, how do you help them kind of rethink and really, you know, force them to, to look at the, at the prioritization and make sure they're prioritizing on the right thing is make just said, what are you optimizing for? >>Oh yeah. Um, you have one of the most important aspects of any decision or, um, attempt to resolve a problem in an organization is the framing process. And, um, you know, it's, it's a difficult aspect of the decision to frame it correctly in the first place. Um, there, it's not a technology issue. In many cases, it's largely a human issue, but if you frame that decision or that problem incorrectly to narrowly say, or you frame it as an either or situation where you could actually have some of both, um, it, it's very difficult for the, um, process to work out correctly. So in many cases that I think we need to think more at the beginning about how we bring this issue or this decision in the best way possible before we charge off and build a system to support it. You know, um, it's worth that extra time to think, think carefully about how the decision has been structured, right >>Surgery. I want to go back to you and talk about the human factors because as we just discussed, you can put it in great technology, but if the culture doesn't adopt it and people don't feel good about it, you know, it's not going to be successful and that's going to reflect poorly on the technology, even if it had nothing to do with it. And you know, when you look at the, the, the core values, uh, of the Bezos manifesto, you know, a big one is trust and collaboration, you know, learn, respond and pivot. I wonder if you can share your thoughts on, on trying to get that cultural shift, uh, so that you can have success with the people or excuse me, with the technology in the process and helping customers, you know, take this more trustworthy and kind of proactive, uh, position. >>So I think, I think at the ground level, it truly starts with the realization that we're all different. We come from different backgrounds. Um, oftentimes we tend to blame the data. It's not uncommon my experiments that we spend the first 30 minutes of any kind of one hour conversation to debate the validity of the data. Um, and so, um, one of the first kind of, uh, probably manifestations that we've had or revelations as we start to engage with our customers is spike, just exposing, uh, high-fidelity data sets to different stakeholders from their different lens. We start to enable these different stakeholders to not debate the data. That's really collaborate to find a solution. So in many ways, when, when, when we think about kind of the types of changes we're trying to, to truly affect around data driven decision making, it's all about bringing the data in context, in the context that is relevant and understandable for, for different stakeholders, whether we're talking about an operator or develop for a business analyst. >>So that's, that's the first thing. The second layer I think, is really to provide context to what people are doing in their specific cycle. And so I think one of the best examples I have is if you start to be able to align business KPI, whether you are counting, you know, sales per hour, or the engagements of your users on your mobile applications, whatever it is, you can start to connect that PKI to the business KPI, to the KPIs that developers might be looking at, whether it is the number of defects or a velocity or whatever, you know, metrics that they are used to to actually track you start to, to be able to actually contextualize in what we are the effecting, basically a metric that is really relevant in which we see is that DC is a much more systematic way to approach the transformation than say, you know, some organizations kind of creating, uh, some of these new products or services or initiatives, um, to, to drive engagements, right? >>So if you look at zoom, for instance, zoom giving away a it service to, uh, to education, he's all about, I mean, there's obviously a marketing aspect in therapists. It's fundamentally about trying to drive also the engagement of their own teams. And because now they're doing something for good and the organizations are trying to do that, but you only can do this kind of things in a limited way. And so you really want to start to rethink how you connect to, everybody's kind of a business objective fruit data, and now you start to get people to stare at the same data from their own lens and collaborate on all the data. Right, >>Right. That's a good, uh, Tom, I want to go back to you. You've been studying it for a long time, writing lots of books and getting into it. Um, why now, you know, what w why now are we finally aligning business objectives with, with it objectives? You know, why didn't this happen before? And, you know, what are the factors that are making now the time for this, this, this move with the, uh, with the biz ops? >>Well, and much of the past, it was sort of a back office related activity. And, you know, it was important for, um, uh, producing your paychecks and, uh, um, capturing the customer orders, but the business wasn't built around it now, every organization needs to be a software business, a data business, a digital business, the auntie has been raised considerably. And if you aren't making that connection between your business objectives and the technology that supports it, you run a pretty big risk of, you know, going out of business or losing out to competitors. Totally. So, um, and, uh, even if you're in a, an industry that hasn't historically been terribly, um, technology oriented customer expectations flow from, uh, you know, the digital native, um, companies that they work with to basically every industry. So you're compared against the best in the world. So we don't really have the luxury anymore of screwing up our it projects or building things that don't really work for the business. Um, it's mission critical that we do that well. Um, almost every time, I just want to follow up by that, Tom, >>In terms of the, you've talked extensively about kind of these evolutions of data and analytics from artismal stage to the big data stage, the data economy stage, the AI driven stage and what I find diff interesting that all those stages, you always put a start date. You never put an end date. Um, so you know, is the, is the big data I'm just going to use that generically a moment in time finally here, where we're, you know, off mahogany row with the data scientists, but actually can start to see the promise of delivering the right insight to the right person at the right time to make that decision. >>Well, I think it is true that in general, these previous stages never seemed to go away. The, um, the artisinal stuff is still being done, but we would like for less than less of it to be artisinal, we can't really afford for everything to be artisinal anymore. It's too labor and time consuming to do things that way. So we shift more and more of it to be done through automation and B to be done with a higher level of productivity. And, um, you know, at some point maybe we reached the stage where we don't do anything artisanally anymore. I'm not sure we're there yet, but, you know, we are, we are making progress. Right, >>Right. And Mick, back to you in terms of looking at agile, cause you're, you're such a, a student of agile when, when you look at the opportunity with ops, um, and taking the lessons from agile, you know, what's been the inhibitor to stop this in the past. And what are you so excited about? You know, taking this approach will enable. >>Yeah. I think both Sergeant Tom hit on this is that in agile what's happened is that we've been measuring tiny subsets of the value stream, right? We need to elevate the data's there. Developers are working on these tools that delivering features that the foundations for, for great culture are there. I spent two decades as a developer. And when I was really happy is when I was able to deliver value to customers, the quicker I was able to do that the fewer impediments are in my way, that quicker was deployed and running in the cloud, the happier I was, and that's exactly what's happening. If we can just get the right data, uh, elevated to the business, not just to the agile teams, but really these values of ours are to make sure that you've got these data driven decisions with meaningful data that's oriented around delivering value to customers. Not only these legacies that Tom touched on, which has cost center metrics from an ITK, from where, for it being a cost center and something that provided email and then back office systems. So we need to rapidly shift to those new, meaningful metrics that are customized business centric and make sure that every development the organization is focused on those as well as the business itself, that we're measuring value and that we're helping that value flow without interruptions. >>I love that mic. Cause if you don't measure it, you can't improve on it and you gotta, but you gotta be measuring the right thing. So gentlemen, uh, thank you again for, for your time. Congratulations on the, uh, on the unveil of the biz ops manifesto and together this coalition >>Of, of, uh, industry experts to get behind this. And, you know, there's probably never been a more important time than now to make sure that your prioritization is in the right spot and you're not wasting resources where you're not going to get the ROI. So, uh, congratulations again. And thank you for sharing your thoughts with us here on the cube. Alright, so we had surge, Tom and Mick I'm. Jeff, you're watching the cube, it's a biz ops manifesto and unveil. Thanks for watching. We'll see you next time >>From around the globe. It's the cube with digital coverage of BizOps manifesto, unveiled brought to you by biz ops coalition and welcome back Friday, Jeff Frick here with the cube we're in our Palo Alto studios. And we'd like to welcome you back to our continuing coverage of biz ops manifesto, unveil exciting day to really, uh, kind of bring this out into public. There's been a little bit of conversation, but today's really the official unveiling and we're excited to have our next guest to share a little bit more information on it. He's Patrick tickle. He's a chief product officer for planned view. Patrick. Great to see you. Yeah, it's great to be here. Thanks for the invite. So why the biz ops manifesto, why the biz optical edition now when you guys have been at it, it's relatively mature marketplace businesses. Good. What was missing? Why, why this, uh, why this coalition? >>Yeah, so, you know, again, why is, why is biz ops important and why is this something I'm, you know, I'm so excited about, but I think companies as well, right. Well, you know, in some ways or another, this is a topic that I've been talking to, you know, the market and our customers about for a long time. And it's, you know, I really applaud, you know, this whole movement, right. And, um, in resonates with me, because I think one of the fundamental flaws, frankly, of the way we've talked about technology and business literally for decades, uh, has been this idea of, uh, alignment. Those who know me, I occasionally get off on this little rant about the word alignment, right. But to me, the word alignment is, is actually indicative of the, of the, of the flaw in a lot of our organizations and biz ops is really, I think now trying to catalyze and expose that flaw. >>Right. Because, you know, I always say that, you know, you know, alignment implies silos, right. Instantaneously, as soon as you say there's alignment, there's, there's obviously somebody who's got a direction and other people that have to line up and that, that kind of siloed, uh, nature of organizations. And then frankly, the passive nature of it. Right. I think so many technology organizations are like, look, the business has the strategy you guys need to align. Right. And, and, you know, as a product leader, right. That's where I've been my whole career. Right. I can tell you that I never sit around. I almost never use the word alignment. Right. I mean, whether I never sit down and say, you know, the product management team has to get aligned with Deb, right. Or the dev team has to get aligned with the delivery and ops teams. I mean, what I say is, you know, are we on strategy, right? >>Like we've, we have a strategy as a, as a full end to end value stream. Right. And that there's no silos. And I mean, look, every on any given day we got to get better. Right. But the context, the context we operate is not about alignment. Right. It's about being on strategy. And I think I've talked to customers a lot about that, but when I first read the manifesto, I was like, Oh yeah, this is exactly. This is breaking down. Maybe trying to eliminate the word alignment, you know, from a lot of our organizations, because we literally start thinking about one strategy and how we go from strategy to delivery and have it be our strategy, not someone else's that we're all aligning to it. And it's a great way to catalyze that conversation. That I've, it's been in my mind for years, to be honest. Right. >>So, so much to unpack there. One of the things obviously, uh, stealing a lot from, from dev ops and the dev ops manifesto from 20 years ago. And as I look through some of the principles and I looked through some of the values, which are, you know, really nicely laid out here, you know, satisfy customers, do continuous delivery, uh, measure, output against real results. Um, the ones that, that jumps out though is really about, you know, change, change, right? Requirements should change frequently. They do change frequently, but I'm curious to get your take from a, from a software development point, it's easy to kind of understand, right. We're making this widget and our competitors, beta widget plus X, and now we need to change our plans and make sure that the plus X gets added to the plan. Maybe it wasn't in the plan, but you talked a lot about product strategy. So in this kind of continuous delivery world, how does that meld with, I'm actually trying to set a strategy, which implies the direction for a little bit further out on the horizon and to stay on that while at the same time, you're kind of doing this real time continual adjustments. Cause you're not working off a giant PRD or MRD anymore. >>Yeah, yeah, totally. Yeah. You know, one of the terms, you know, that we use internally a lot and even with my customers, our customers is we talked about this idea of rewiring, right. And I think, you know, it's kind of a, now an analogy for transformation. And I think a lot of us have to rewire the way we think about things. Right. And I think at Planview where we have a lot of customers who live in that, you know, who operationalize that traditional PPM world. Right. And are shifting to agile and transforming that rewire is super important. And, and to your point, right, it's, you've just, you've got to embrace this idea of, you know, just iterative getting better every day and iterating, iterating, iterating as to building annual plans or, you know, I get customers occasionally who asked me for two or three year roadmap. >>Right. And I literally looked at them and I go, there's no, there's no scenario where I can build a two or three year roadmap. Right. You, you, you think you want that, but that's not, that's not the way we run. Right. And I will tell you the biggest thing that for us, you know, that I think is matched the planning, uh, you know, patents is a word I like to use a lot. So the thing that we've like, uh, that we've done from a planning perspective, I think is matched impedance to continuous delivery is instituting the whole program, implement, you know, the program, increment planning, capabilities and methodologies, um, in the scaled agile world. Right. And over the last 18 months to two years, we really have now, you know, instrumented our company across three value streams. You know, we do quarterly PI program increment 10 week planning, you know, and that becomes, that becomes the Terra firma of how we plant. >>Right. And it's, what are we doing for the next 10 weeks? And we iterate within those 10 weeks, but we also know that 10 weeks from now, we're going to, we're going to adjust iterate again. Right. And that shifting of that planning model, you know, to being as cross-functional is that as that big room planning kind of model is, um, and also, uh, you know, on that shorter increment, when you get those two things in place, all sudden the impedance really starts to match up, uh, with continuous delivery and it changes, it changes the way you plan and it changes the way you work. Right? >>Yeah. Their thing. Right. So obviously a lot of these things are kind of process driven, both within the values, as well as the principles, but there's a whole lot, really about culture. And I just want to highlight a couple of the values, right? We already talked about business outcomes, um, trust and collaboration, uh, data driven decisions, and then learn, respond and pivot. Right. A lot of those are cultural as much as they are process. So again, is it the, is it the need to really kind of just put them down on paper and you know, I can't help, but think of, you know, the hammering up the, uh, the thing in the Lutheran church with their, with their manifesto, is it just good to get it down on paper? Because when you read these things, you're like, well, of course we should trust people. And of course we need an environment of collaboration and of course we want data driven decisions, but as we all know saying it and living, it are two very, very different things. >>Yeah. Good question. I mean, I think there's a lot of ways you bring that to life you're right. And just hanging up, you know, I think we've all been through the hanging up posters around your office, which these days, right. Unless you're going to hang a poster and everybody's home office. Right. You can't even, you can't even fake it that you think that might work. Right. So, um, you know, you really, I think we've attacked that in a variety of ways. Right. And you definitely have to, you know, you've got to make the shift to a team centric culture, right. Empowered teams, you know, that's a big deal. Right. You know, a lot of, a lot of the people that, you know, we lived in a world of quote unquote, where we were lived in a deep resource management world for a long, long time. >>And right. A lot of our customers still do that, but you know, kind of moving to that team centric world is, uh, is really important and core the trust. Um, I think training is super important, right. We've, you know, we've internally, right. We've trained hundreds employees over the last a year and a half on the fundamentals really of safe. Right. Not necessarily, you know, we've had, we've had teams delivering in scrum and the continuous delivery for, you know, for years, but the scaling aspect of it, uh, is where we've done a lot of training and investment. Um, and then, you know, I think, uh, leadership has to be bought in. Right. You know? And so when we pie plan, you know, myself and Cameron and the other members of our leadership, you know, we're NPI planning, you know, for, for four days. Right. I mean, it's, it's, you've got to walk the walk, you know, from top to bottom and you've got to train on the context. Right. And then you, and then, and, and then once you get through a few cycles where you've done a pivot, right. Or you brought a new team in, and it just works, it becomes kind of this virtuous circle where he'll go, man, this really works so much better than what we used to do. Right. >>Right. The other really key principle to this whole thing is, is aligning, you know, the business leaders and the business prioritization, um, so that you can get to good outcomes with the development and the delivery. Right. And we, we know again, and kind of classic dev ops to get the dev and the production people together. So they can, you know, quickly ship code that works. Um, but adding the business person on there really puts, puts a little extra responsibility that they, they understand the value of a particular feature or particular priority. Uh, they, they can make the, the, the trade offs and that they kind of understand the effort involved too. So, you know, bringing them into this continuous again, kind of this continuous development process, um, to make sure that things are better aligned and really better prioritize. Cause ultimately, you know, we don't live in an infinite resources situation and people got to make trade offs. They got to make decisions as to what goes and what doesn't go in for everything that goes. Right. I always say you pick one thing. Okay. That's 99 other things that couldn't go. So it's really important to have, you know, this, you said alignment of the business priorities as well as, you know, the execution within, within the development. >>Yeah. I think that, you know, uh, you know, I think it was probably close to two years ago. Forester started talking about the age of the customer, right. That, that was like their big theme at the time. Right. And I think to me what that, the age of the customer actually translates to and Mick, Mick and I are both big fans of this whole idea of the project and product shift, mixed book, you know, it was a great piece on a, you're talking about, you know, as part of the manifesto is one of the authors as well, but this shift from project to product, right? Like the age of the customer, in my opinion, the, the embodiment of that is the shift to a product mentality. Right. And, and the product mentality in my opinion, is what brings the business and technology teams together, right? >>Once you, once you're focused on a customer experience is delivered through a product or a service. That's when I that's, when I started to go with the alignment problem goes away, right. Because if you look at software companies, right, I mean, we run product management models yeah. With software development teams, customer success teams, right. That, you know, the software component of these products that people are building is obviously becoming bigger and bigger, you know, in an, in many ways, right. More and more organizations are trying to model themselves over as operationally like software companies. Right. Um, they obviously have lots of other components in their business than just software, but I think that whole model of customer experience equaling product, and then the software component of product, the product is the essence of what changes that alignment equation and brings business and teams together because all of a sudden, everyone knows what the customer's experiencing. Right. And, and that, that, that makes a lot of things very clear, very quickly. >>Right. I'm just curious how far along this was as a process before, before COBIT hit, right. Because serendipitous, whatever. Right. But the sudden, you know, light switch moment, everybody had to go work from home and in March 15th compared to now we're in October and this is going to be going on for a while. And it is a new normal and whatever that whatever's going to look like a year from now, or two years from now is TBD, you know, had you guys already started on this journey cause again, to sit down and actually declare this coalition and declare this manifesto is a lot different than just trying to do better within your own organization. >>Yeah. So we had started, uh, you know, w we definitely had started independently, you know, some, some, you know, I think people in the community know that, uh, we, we came together with a company called lean kit a handful of years ago, and I give John Terry actually one of the founders LeanKit immense credit for, you know, kind of spearheading our cultural change and not, and not because of, we were just gonna be, you know, bringing agile solutions to our customers, but because, you know, he believed that it was going to be a fundamentally better way for us to work. Right. And we kind of, you know, we started with John and built, you know, out of concentric circles of momentum and, and we've gotten to the place where now it's just part of who we are, but, but I do think that, you know, COVID has, you know, um, I think pre COVID a lot of companies, you know, would, would adopt, you know, the would adopt digital slash agile transformation. >>Um, traditional industries may have done it as a reaction to disruption. Right. You know, and in many cases, the disruption to these traditional industries was, I would say a product oriented company, right. That probably had a larger software component, and that disruption caused a competitive issue, uh, or a customer issue that caused companies and tried to respond by transforming. I think COVID, you know, all of a sudden flatten that out, right. We literally all got disrupted. Right. And so all of a sudden, every one of us is dealing with some degree of market uncertainty, customer uncertainty, uh, and also, you know, none of us were insulated from the need to be able to pivot faster, deliver incrementally, you know, and operate in a different, completely more agile way, uh, you know, post COVID. Right. Yeah. That's great. >>So again, a very, very, very timely, you know, a little bit of serendipity, a little bit of planning. And, you know, as, as with all important things, there's always a little bit of lock in, uh, and a lot of hard work involved. So a really interesting thank you for, for your leadership, Patrick. And, you know, it really makes a statement. I think when you have a bunch of leaderships across an industry coming together and putting their name on a piece of paper, uh, that's aligned around us some principles and some values, which again, if you read them who wouldn't want to get behind these, but if it takes, you know, something a little bit more formal, uh, to kind of move the ball down the field, and then I totally get it and a really great work. Thanks for, uh, thanks for doing it. >>Oh, absolutely. No. Like I said, the first time I read it, I was like, yep. Like you said, this is all, it's all makes complete sense, but just documenting it and saying it and talking about it moves the needle. I'll tell you as a company, you gotta, we're pushing really hard on, uh, you know, on our own internal strategy on diversity and inclusion. Right. And, and like, once we wrote the words down about what, you know, what we aspire to be from a diversity and inclusion perspective, it's the same thing. Everybody reads the words that goes, why wouldn't we do this? Right. But until you write it down and kind of have again, a manifesto or a Terra firma of what you're trying to accomplish, you know, then you can rally behind it. Right. As opposed to it being something that's, everybody's got their own version of the flavor. Right. And I think it's a very analogous, you know, kind of, uh, initiative. Right. And, uh, and it's happening, both of those things right. Are happening across the industry these days. Right. >>And measure it too. Right. And measure it, measure, measure, measure, get a baseline. Even if you don't like to measure, even if you don't like what the, even if you can argue against the math, behind the measurement, measure it. And at least you can measure it again and you can, and you've got some type of a comp and that is really the only way to, to move it forward. We're Patrick really enjoyed the conversation. Thanks for, uh, for taking a few minutes out of your day. >>It's great to be here. It's an awesome movement and we're glad to be a part of it. >>All right. Thanks. And if you want to check out the biz ops, Manifesta go to biz ops, manifesto.org, read it. You might want to sign it. It's there for you. And thanks for tuning in on this segment will continuing coverage of the biz op manifesto unveil you're on the cube. I'm Jeff, thanks for watching >>From around the globe. It's the cube with digital coverage of biz ops manifesto unveiled brought to you by biz ops coalition. >>Hey, welcome back, everybody Jeffrey here with the cube. We're coming to you from our Palo Alto studios. And welcome back to this event is the biz ops manifesto unveiling. So the biz ops manifesto and the biz ops coalition had been around for a little while, but today's the big day. That's kind of the big public unveiling, or we're excited to have some of the foundational people that, you know, have put their, put their name on the dotted, if you will, to support this initiative and talk about why that initiative is so important. And so the next guest we're excited to have is dr. Mick Kirsten. He is the founder and CEO of Tasktop mic. Great to see you coming in from Vancouver, Canada, I think, right? Yes. Great to be here, Jeff. Thank you. Absolutely. I hope your air is a little better out there. I know you had some of the worst air of all of us, a couple, a couple of weeks back. So hopefully things are, uh, are getting a little better and we get those fires under control. Yeah. >>Things have cleared up now. So yeah, it's good. It's good to be close to the U S and it's going to have the Arabic cleaner as well. >>Absolutely. So let's, let's jump into it. So you you've been an innovation guy forever starting way back in the day and Xerox park. I was so excited to do an event at Xerox park for the first time last year. I mean, that, that to me represents along with bell labs and, and some other, you know, kind of foundational innovation and technology centers, that's gotta be one of the greatest ones. So I just wonder if you could share some perspective of getting your start there at Xerox park, you know, some of the lessons you learned and what you've been able to kind of carry forward from those days. >>Yeah. I was fortunate to join Xerox park in the computer science lab there at a fairly early point in my career, and to be working on open source programming languages. So back then in the computer science lab, where some of the inventions around programming around software development games, such as object programming, and a lot of what we had around really modern programming levels constructs, those were the teams I had the fortunate of working with, and really our goal was. And of course, there's, as, as you noticed, there's just this DNA of innovation and excitement and innovation in the water. And really it was the model that was all about changing the way that we work was looking at for how we can make it 10 times easier to white coat. But this is back in 99. And we were looking at new ways of expressing, especially business concerns, especially ways of enabling people who are wanting to innovate for their business to express those concerns in code and make that 10 times easier than what that would take. >>So we create a new open source programming language, and we saw some benefits, but not quite quite what we expected. I then went and actually joined Charles Stephanie, that former to fucking from Microsoft who was responsible for, he actually got Microsoft word as a sparking into Microsoft and into the hands of bill Gates and that company that was behind the whole office suite and his vision. And then when I was trying to execute with, working for him was to make PowerPoint like a programming language to make everything completely visual. And I realized none of this was really working, that there was something else, fundamentally wrong programming languages, or new ways of building software. Like let's try and do with Charles around intentional programming. That was not enough. >>That was not enough. So, you know, the agile movement got started about 20 years ago, and we've seen the rise of dev ops and really this kind of embracing of, of, of sprints and, you know, getting away from MRDs and PRDs and these massive definitions of what we're going to build and long build cycles to this iterative process. And this has been going on for a little while. So what was still wrong? What was still missing? Why the biz ops coalition, why the biz ops manifesto? >>Yeah, so I basically think we nailed some of the things that the program language levels of teams can have effective languages deployed to soften to the cloud easily now, right? And at the kind of process and collaboration and planning level agile two decades, decades ago was formed. We were adopting and all the, all the teams I was involved with and it's really become a self problem. So agile tools, agile teams, agile ways of planning, uh, are now very mature. And the whole challenge is when organizations try to scale that. And so what I realized is that the way that agile was scaling across teams and really scaling from the technology part of the organization to the business was just completely flawed. The agile teams had one set of doing things, one set of metrics, one set of tools. And the way that the business was working was planning was investing in technology was just completely disconnected and using a whole different set of measures. Pretty >>Interesting. Cause I think it's pretty clear from the software development teams in terms of what they're trying to deliver. Cause they've got a feature set, right. And they've got bugs and it's easy to, it's easy to see what they deliver, but it sounds like what you're really honing in on is this disconnect on the business side, in terms of, you know, is it the right investment? You know, are we getting the right business ROI on this investment? Was that the right feature? Should we be building another feature or should we building a completely different product set? So it sounds like it's really a core piece of this is to get the right measurement tools, the right measurement data sets so that you can make the right decisions in terms of what you're investing, you know, limited resources. You can't, nobody has unlimited resources. And ultimately you have to decide what to do, which means you're also deciding what not to do. And it sounds like that's a really big piece of this, of this whole effort. >>Yeah. Jeff, that's exactly it, which is the way that the agile team measures their own way of working is very different from the way that you measure business outcomes. The business outcomes are in terms of how happy your customers are, but are you innovating fast enough to keep up with the pace of a rapidly changing economy, roughly changing market. And those are, those are all around the customer. And so what I learned on this long journey of supporting many organizations transformations and having them try to apply those principles of agile and dev ops, that those are not enough, those measures technical practices, uh, those measured sort of technical excellence of bringing code to the market. They don't actually measure business outcomes. And so I realized that it really was much more around having these entwined flow metrics that are customer centric and business centric and market centric where we need it to go. Right. >>So I want to shift gears a little bit and talk about your book because you're also a bestselling author from project to product and, and, and you, you brought up this concept in your book called the flow framework. And it's really interesting to me cause I know, you know, flow on one hand is kind of a workflow and a process flow and, and you know, that's how things get done and, and, and embrace the flow. On the other hand, you know, everyone now in, in a little higher level existential way is trying to get into the flow right into the workflow and, you know, not be interrupted and get into a state where you're kind of at your highest productivity, you know, kind of your highest comfort, which flow are you talking about in your book? Or is it a little bit of both? >>That's a great question. It's not one I get asked very often cause to me it's absolutely both. So that the thing that we want to get, that we've learned how to master individual flow, that there's this beautiful book by me, how you teaches me how he does a beautiful Ted talk by him as well about how we can take control of our own flow. So my question with the book with question replies, how can we bring that to entire teams and really entire organizations? How can we have everyone contributing to a customer outcome? And this is really what if you go to the biz ops manifesto, it says, I focus on outcomes on using data to drive whether we're delivering those outcomes rather than a focus on proxy metrics, such as, how quickly did we implement this feature? No, it's really how much value did the customer go to the future? >>And how quickly did you learn and how quickly did you use that data to drive to that next outcome? Really that with companies like Netflix and Amazon have mastered, how do we get that to every large organization, every it organization and make everyone be a software innovator. So it's to bring that, that concept of flow to these end to end value streams. And the fascinating thing is we've actually seen the data. We've been able to study a lot of value streams. We see when flow increases, when organizations deliver value to a customer faster, developers actually become more happy. So things like that and point out promoter scores, rise, and we've got empirical data for this. So that the beautiful thing to me is that we've actually been able to combine these two things and see the results and the data that you increase flow to the customer. Your developers are more, >>I love it. I love it, right, because we're all more, we're all happier when we're in the flow and we're all more productive when we're in the flow. So I, that is a great melding of, of two concepts, but let's jump into the, into the manifesto itself a little bit. And you know, I love that you took this approach really of having kind of four key values and then he gets 12 key principles. And I just want to read a couple of these values because when you read them, it sounds pretty brain dead. Right? Of course. Right. Of course you should focus on business outcomes. Of course you should have trust and collaboration. Of course you should have database decision making processes and not just intuition or, you know, whoever's the loudest person in the room, uh, and to learn and respond and pivot. But what's the value of actually just putting them on a piece of paper, because again, this is not this, these are all good, positive things, right? When somebody reads these to you or tells you these are sticks it on the wall, of course. But unfortunately of course isn't always enough. >>No. And I think what's happened is some of these core principles originally from the agile manifesto in two decades ago, uh, the whole dev ops movement of the last decade of flow feedback and continue learning has been key. But a lot of organizations, especially the ones undergoing digital transformations have actually gone a very different way, right? The way that they measure value, uh, in technology and innovation is through costs for many organizations. The way that they actually are looking at that they're moving to cloud is actually as a reduction in cost. Whereas the right way of looking at moving to cloud is how much more quickly can we get to the value to the customer? How quickly can we learn from that? And how quickly can we drive the next business outcome? So really the key thing is, is to move away from those old ways of doing things of funding projects and cost centers, to actually funding and investing in outcomes and measuring outcomes through these flow metrics, which in the end are your fast feedback and how quickly you're innovating for your customer. >>So these things do seem very obvious when you look at them. But the key thing is what you need to stop doing to focus on these. You need to actually have accurate realtime data of how much value you fund to the customer every week, every month, every quarter. And if you don't have that, your decisions are not driven on data. If you don't know what your bottleneck is. And this is something that in decades of manufacturing, a car manufacturers, other manufacturers, master, they always know where the bottom back in their production processes. You ask a random CIO when a global 500 company where their bottleneck is, and you won't get a clear answer because there's not that level of understanding. So have to actually follow these principles. You need to know exactly where you fall. And I guess because that's, what's making your developers miserable and frustrated, then having them context, which I'm trash. So the approach here is important and we have to stop doing these other things, >>Right? There's so much there to unpack. I love it. You know, especially the cloud conversation because so many people look at it wrong as, as, as a cost saving a device, as opposed to an innovation driver and they get stuck, they get stuck in the literal. And I, you know, I think at the same thing, always about Moore's law, right? You know, there's a lot of interesting real tech around Moore's law and the increasing power of microprocessors, but the real power, I think in Moore's laws is the attitudinal change in terms of working in a world where you know that you've got all this power and what you build and design. I think it's funny to your, your comment on the flow and the bottleneck, right? Cause, cause we know manufacturing, as soon as you fix one bottleneck, you move to your next one, right? You always move to your next point of failure. So if you're not fixing those things, you know, you're not, you're not increasing that speed down the line, unless you can identify where that bottleneck is or no matter how many improvements you make to the rest of the process, it's still going to get hung up on that one spot. >>That's exactly it. And you also make it sound so simple, but again, if you don't have the data driven visibility of where the bottom line is, and these bottlenecks are adjusted to say, it's just whack-a-mole right. So we need to understand is the bottleneck because our security reviews are taking too long and stopping us from getting value for the customer. If it's that automate that process. And then you move on to the next bottleneck, which might actually be that deploying yourself into the cloud was taking too long. But if you don't take that approach of going flow first, rather than again, that sort of cost reduction. First, you have to think of that approach of customer centricity and you only focused on optimizing costs. Your costs will increase and your flow will slow down. And this is just one of these fascinating things. Whereas if you focus on getting back to the customer and reducing your cycles on getting value, your flow time from six months to two weeks or two, one week or two event, as we see with, with tech giants, you actually can both lower your costs and get much more value that for us to get that learning loop going. >>So I think I've seen all of these cloud deployments and one of the things that's happened that delivered almost no value because there was such big bottlenecks upfront in the process and actually the hosting and the AP testing was not even possible with all of those inefficiencies. So that's why going float for us rather than costs where we started our project versus silky. >>I love that. And, and, and, and it, it begs repeating to that right within the subscription economy, you know, you're on the hook to deliver value every single month because they're paying you every single month. So if you're not on top of how you're delivering value, you're going to get sideways because it's not like, you know, they pay a big down payment and a small maintenance fee every month, but once you're in a subscription relationship, you know, you have to constantly be delivering value and upgrading that value because you're constantly taking money from the customer. So it's such a different kind of relationship than kind of the classic, you know, big bang with a maintenance agreement on the back end really important. Yeah. >>And I think in terms of industry shifts that that's it that's, what's catalyzed. This interesting shift is in this SAS and subscription economy. If you're not delivering more and more value to your customers, someone else's and they're winning the business, not you. So one way we know is to delight our customers with great user experiences. Well, that really is based on how many features you delivered or how much, how big, how many quality improvements or scalar performance improvements you delivered. So the problem is, and this is what the business manifesto, as well as the full frame of touch on is if you can't measure how much value you delivered to a customer, what are you measuring? You just backed again, measuring costs and that's not a measure of value. So we have to shift quickly away from measuring cost to measuring value, to survive in the subscription economy. >>We could go for days and days and days. I want to shift gears a little bit into data and, and, and a data driven, um, decision making a data driven organization cause right day has been talked about for a long time, the huge big data meme with, with Hadoop over, over several years and, and data warehouses and data lakes and data oceans and data swamps, and can go on and on and on. It's not that easy to do, right? And at the same time, the proliferation of data is growing exponentially. We're just around the corner from, from IOT and 5g. So now the accumulation of data at machine scale, again, this is going to overwhelm and one of the really interesting principles, uh, that I wanted to call out and get your take right, is today's organizations generate more data than humans can process. So informed decisions must be augmented by machine learning and artificial intelligence. I wonder if you can, again, you've got some great historical perspective, um, reflect on how hard it is to get the right data, to get the data in the right context, and then to deliver it to the decision makers and then trust the decision makers to actually make the data and move that down. You know, it's kind of this democratization process into more and more people and more and more frontline jobs making more and more of these little decisions every day. >>Yeah. I definitely think the front parts of what you said are where the promises of big data have completely fallen on their face into the swamps as, as you mentioned, because if you don't have the data in the right format, you've cannot connect collected at the right way. You want that way, the right way you can't use human or machine learning effectively. And there've been the number of data warehouses in a typical enterprise organization. And the sheer investment is tremendous, but the amount of intelligence being extracted from those is, is, is a very big problem. So the key thing that I've noticed is that if you can model your value streams, so yes, you understand how you're innovating, how you're measuring the delivery of value and how long that takes. What is your time to value these metrics like full time? You can actually use both the intelligence that you've got around the table and push that down as well, as far as getting to the organization, but you can actually start using that those models to understand and find patterns and detect bottlenecks that might be surprising, right? >>Well, you can detect interesting bottlenecks when you shift to work from home. We detected all sorts of interesting bottlenecks in our own organization that were not intuitive to me that had to do with, you know, more senior people being overloaded and creating bottlenecks where they didn't exist. Whereas we thought we were actually an organization that was very good at working from home because of our open source roots. So that data is highly complex. Software value streams are extremely complicated. And the only way to really get the proper analyst and data is to model it properly and then to leverage these machine learning and AI techniques that we have. But that front part of what you said is where organizations are just extremely immature in what I've seen, where they've got data from all their tools, but not modeled in the right way. Right, right. >>Right. Well, all right. So before I let you go, you know, let's say you get a business leader, he buys in, he reads the manifesto, he signs on the dotted line and he says, Mick, how do I get started? I want to be more aligned with, with the development teams. You know, I'm in a very competitive space. We need to be putting out new software features and engaging with our customers. I want to be more data-driven how do I get started? Well, you know, what's the biggest inhibitor for most people to get started and get some early wins, which we know is always the key to success in any kind of a new initiative. >>Right? So I think you can reach out to us through the website, uh, there's the manifesto, but the key thing is just to get you set up it's to get started and to get the key wins. So take a probably value stream that's mission critical. It could be your new mobile and web experiences or, or part of your cloud modernization platform or your analytics pipeline, but take that and actually apply these principles to it and measure the end to end flow of value. Make sure you have a value metric that everyone is on the same page on the people, on the development teams, the people in leadership all the way up to the CEO. And one of the, what I encourage you to start is actually that content flow time, right? That is the number one metric. That is how you measure it, whether you're getting the benefit of your cloud modernization, that is the one metric that Adrian Cockcroft. When the people I respect tremendously put into his cloud for CEOs, the metric, the one, the one way to measure innovation. So basically take these principles, deploy them on one product value stream, measure, sentiment, flow time, and then you'll actually be well on your path to transforming and to applying the concepts of agile and dev ops all the way to, to the business, to the way >>You're offering model. >>Well, Mick really great tips, really fun to catch up. I look forward to a time when we can actually sit across the table and, and get into this. Cause I just, I just love the perspective and, you know, you're very fortunate to have that foundational, that foundational base coming from Xerox park and they get, you know, it's, it's a very magical place with a magical history. So to, to incorporate that into, continue to spread that well, uh, you know, good for you through the book and through your company. So thanks for sharing your insight with us today. >>Thanks so much for having me, Jeff. >>All right. And go to the biz ops manifesto.org, read it, check it out. If you want to sign it, sign it. They'd love to have you do it. Stay with us for continuing coverage of the unveiling of the business manifesto on the cube. I'm Jeff. Rick. Thanks for watching. See you next time >>From around the globe. It's the cube with digital coverage of biz ops manifesto unveiled brought to you by biz ops coalition. >>Hey, welcome back everybody. Jeff Frick here with the cube come due from our Palo Alto studios today for a big, big reveal. We're excited to be here. It's the biz ops manifesto unveiling a thing's been in the works for awhile and we're excited to have our next guest. One of the, really the powers behind this whole effort. And he's joining us from Boston it's surge, Lucio, the vice president, and general manager enterprise software division at Broadcom surge. Great to see you. >>Hi, good to see you, Jeff. Glad to be here. >>So you've been in this business for a very long time. You've seen a lot of changes in technology. What is the biz ops manifesto? What is this coalition all about? Why do we need this today and in 2020? >>Yeah. So, so I've been in this business for close to 25 years, right? So about 20 years ago, the agile manifesto was created. And the goal of the agile manifesto was really to address the uncertainty around software development and the inability to predict the efforts to build software. And, uh, if you, if you roll that kind of 20 years later, and if you look at the current state of the industry, uh, the product, the project management Institute, estimates that we're wasting about a million dollars, every 20 seconds in digital transformation initiatives that do not deliver on business results. In fact, we were recently served a third of the, uh, a number of executives in partnership with Harvard business review and 77% of those executives think that one of the key challenges that they have is really at the collaboration between business and it, and that that's been kind of a case for, uh, almost 20 years now. >>Um, so the, the, the key challenge we're faced with is really that we need a new approach and many of the players in the industry, including ourselves, I've been using different terms, right? Some are being, are talking about value stream management. Some are talking about software delivery management. If you look at the site, reliability engineering movement, in many ways, it embodies a lot of these kind of concepts and principles. So we believed that it became really imperative for us to crystallize around, could have one concept. And so in many ways, the, uh, the BizOps concept and the business manifesto are bringing together a number of ideas, which have been emerging in the last five years or so, and, and defining the key values and principles to finally help these organizations truly transform and become digital businesses. And so the hope is that by joining our forces and defining public key principles and values, we can help the industry, uh, not just, uh, by, you know, providing them with support, but also, uh, tools and consulting that is required for them to truly achieve the kind of transformation that everybody's seeking. >>Right, right. So COVID now we're six months into it, approximately seven months into it. Um, a lot of pain, a lot of bad stuff still happening. We've got a ways to go, but one of the things that on the positive side, right, and you've seen all the memes and social media is, is a driver of digital transformation and a driver of change. Cause we had this light switch moment in the middle of March and there was no more planning. There was no more conversation. You've suddenly got remote workforces, everybody's working from home and you got to go, right. So the reliance on these tools increases dramatically, but I'm curious, you know, kind of short of, of the beginnings of this effort in short of kind of COVID, which, you know, came along unexpectedly. I mean, what were those inhibitors because we've been making software for a very long time, right? The software development community has, has adopted kind of rapid change and, and iterative, uh, delivery and, and sprints, what was holding back the connection with the business side to make sure that those investments were properly aligned with outcomes. >>Well, so, so you have to understand that it is, is kind of a its own silos. And traditionally it has been treated as a cost center within large organizations and not as a value center. And so as a result could have a traditional dynamic between it and the business is basically one of a kind of supplier up to kind of a business. Um, and you know, if you, if you go back to, uh, I think you'll unmask a few years ago, um, basically at this concept of the machines to build the machines and you went as far as saying that, uh, the machines or the production line is actually the product. So, um, meaning that the core of the innovation is really about, uh, building, could it be engine to deliver on the value? And so in many ways, you know, we have missed on this shift from, um, kind of it becoming this kind of value center within the enterprises. >>And, and he talks about culture. Now, culture is a, is a sum total of beavers. And the reality is that if you look at it, especially in the last decade, uh, we've agile with dev ops with, um, I bring infrastructures, uh, it's, it's way more volatile today than it was 10 years ago. And so the, when you start to look at the velocity of the data, the volume of data, the variety of data to analyze this system, um, it's, it's very challenging for it to actually even understand and optimize its own processes, let alone, um, to actually include business as sort of an integral part of kind of a delivery chain. And so it's both kind of a combination of, of culture, um, which is required as well as tools, right? To be able to start to bring together all these data together, and then given the volume variety of philosophy of the data, uh, we have to apply some core technologies, which have only really, truly emerged in the last five to 10 years around machine learning and analytics. And so it's really kind of a combination of those freaks, which are coming together today to really help organizations kind of get to the next level. Right, >>Right. So let's talk about the manifesto. Let's talk about, uh, the coalition, uh, the BizOps coalition. I just liked that you put down these really simple, you know, kind of straightforward core values. You guys have four core values that you're highlighting, you know, business outcomes, over individual projects and outputs, trust, and collaboration, oversight, load teams, and organizations, data driven decisions, what you just talked about, uh, you know, over opinions and judgment and learned, respond and pivot. I mean, surgery sounds like pretty basic stuff, right? I mean, aren't, isn't everyone working to these values already. And I think he touched on it on culture, right? Trust and collaboration, data driven decisions. I mean, these are fundamental ways that people must run their business today, or the person that's across the street, that's doing it. It's going to knock them out right off their blog. >>Yeah. So that's very true. But, uh, so I'll, I'll mention in our survey, we did, uh, I think about six months ago and it was in partnership with, uh, with, uh, an industry analyst and we serve at a, again, a number of it executives to understand how many we're tracking business outcomes I'm going to do with the software executives. It executives we're tracking business outcomes. And the, there were less than 15% of these executives were actually tracking the outcomes of a software delivery. And you see that every day. Right? So in my own teams, for instance, we've been adopting a lot of these core principles in the last year or so, and we've uncovered that 16% of our resources were basically aligned around initiatives, which are not strategic for us. Um, I take, you know, another example, for instance, one of our customers in the, uh, in the airline industry and Harvard, for instance, that a number of, uh, um, that they had software issues that led to people searching for flights and not returning any kind of availability. >>And yet, um, you know, the, it teams, whether it's operations, software environments were completely oblivious to that because they were completely blindsided to it. And so the connectivity between kind of the inwards metrics that RT is using, whether it's database time, cycle time, or whatever metric we use in it are typically completely divorced from the business metrics. And so at its core, it's really about starting to align the business metrics with what the, the software delivery chain, right? This, uh, the system, which is really a core differentiator for these organizations. It's about connecting those two things and, and starting to, um, infuse some of the agile culture and principles. Um, that's emerged from the software side into the business side. Um, of course the lean movement and other movements have started to change some of these dynamic on the, on the business side. And so I think this, this is the moment where we are starting to see kind of the imperative to transform. Now, you know, Covina obviously has been a key driver for that. The, um, the technology is right to start to be able to weave data together and really kind of, uh, also the cultural shifts, uh, Prue agile through dev ops through, uh, the SRE movement, uh frulein um, business transformation, all these things are coming together and that are really creating kind of the conditions for the BizOps manifesto to exist. >>So, uh, Clayton Christianson, great, uh, Harvard professor innovator's dilemma might still my all time favorite business books, you know, talks about how difficult it is for incumbents to react to, to disruptive change, right? Because they're always working on incremental change because that's what their customers are asking for. And there's a good ROI when you talk about, you know, companies not measuring the right thing. I mean, clearly it has some portion of their budget that has to go to keeping the lights on, right. That that's always the case, but hopefully that's an, an ever decreasing percentage of their total activity. So, you know, what should people be measuring? I mean, what are kind of the new metrics, um, in, in biz ops that drive people to be looking at the right things, measuring the right things and subsequently making the right decisions, investment decisions on whether they should do, you know, move project a along or project B. >>So there, there are only two things, right? So, so I think what you're talking about is portfolio management, investment management, right. And, um, which, which is a key challenge, right? Um, in my own experience, right? Uh, driving strategy or a large scale kind of software organization for years, um, it's very difficult to even get kind of a base data as to who is doing what, uh, um, I mean, some of our largest customers we're engaged with right now are simply trying to get a very simple answer, which is how many people do I have and that specific initiative at any point in time, and just tracking that information is extremely difficult. So, and again, back to a product project management Institute, um, there, they have estimated that on average, it organizations have anywhere between 10 to 20% of their resources focused on initiatives, which are not strategically aligned. >>So, so that's one dimensional portfolio management. I think the key aspect though, that we are, we're really keen on is really around kind of the alignment of a business metrics to the it metrics. Um, so I'll use kind of two simple examples, right? And my background is around quality and I've always believed that the fitness for purpose is really kind of a key, um, uh, philosophy if you will. And so if you start to think about quality as fitness for purpose, you start to look at it from a customer point of view, right. And fitness for purpose for a core banking application or mobile application are different, right? So the definition of a business value that you're trying to achieve is different. Um, and so the, and yeah, if you look at our, it, operations are operating there, we're using kind of a same type of, uh, kind of inward metrics, uh, like a database off time or a cycle time, or what is my point of velocity, right? >>And so the challenge really is this inward facing metrics that it is using, which are divorced from ultimately the outcome. And so, you know, if I'm, if I'm trying to build a poor banking application, my core metric is likely going to be uptight, right? If I'm trying to build a mobile application or maybe your social, a mobile app, it's probably going to be engagement. And so what you want is for everybody across it, to look at these metric and what are the metrics within the software delivery chain, which ultimately contribute to that business metric. And some cases cycle time may be completely irrelevant, right? Again, my core banking app, maybe I don't care about cycle time. And so it's really about aligning those metrics and be able to start to, um, Charles you mentioned, uh, around the, the, um, uh, around the disruption that we see is, or the investors is the dilemma now is really around the fact that many it organizations are essentially applying the same approaches of, for innovation, like for basically scrap work, then they would apply to kind of over more traditional projects. And so, you know, there's been a lot of talk about two-speed it, and yes, it exists, but in reality are really organizations, um, truly differentiating, um, all of the operate, their, their projects and products based on the outcomes that they're trying to achieve. And this is really where BizOps is trying to affect. >>I love that, you know, again, it doesn't seem like brain surgery, but focus on the outcomes, right. And it's horses for courses, as you said, this project, you know, what you're measuring and how you define success, isn't necessarily the same as, as on this other project. So let's talk about some of the principles we talked about the values, but, you know, I think it's interesting that, that, that the BizOps coalition, you know, just basically took the time to write these things down and they don't seem all that super insightful, but I guess you just got to get them down and have them on paper and have them in front of your face. But I want to talk about, you know, one of the key ones, which you just talked about, which is changing requirements, right. And working in a dynamic situation, which is really what's driven, you know, this, the software to change in software development, because, you know, if you're in a game app and your competitor comes out with a new blue sword, you got to come out with a new blue sword. >>So whether you had that on your Kanban wall or not. So it's, it's really this embracing of the speed of change and, and, and, and making that, you know, the rule, not the exception. I think that's a phenomenal one. And the other one you talked about is data, right? And that today's organizations generate more data than humans can process. So informed decisions must be generated by machine learning and AI, and, you know, in the, the big data thing with Hadoop, you know, started years ago, but we are seeing more and more that people are finally figuring it out, that it's not just big data, and it's not even generic machine learning or artificial intelligence, but it's applying those particular data sets and that particular types of algorithms to a specific problem, to your point, to try to actually reach an objective, whether that's, you know, increasing the, your average ticket or, you know, increasing your checkout rate with, with, with shopping carts that don't get left behind in these types of things. So it's a really different way to think about the world in the good old days, probably when you got started, when we had big, giant, you know, MRDs and PRDs and sat down and coded for two years and came out with a product release and hopefully not too many patches subsequently to that. >>It's interesting. Right. Um, again, back to one of these surveys that we did with, uh, with about 600, the ITA executives, and, uh, and, and we, we purposely designed those questions to be pretty open. Um, and, and one of them was really wrong requirements and, uh, and it was really a wrong, uh, kind of what do you, what is the best approach? What is your preferred approach towards requirements? And if I were to remember correctly, over 80% of the it executives set that the best approach they'll prefer to approach these core requirements to be completely defined before software development starts, let me pause there we're 20 years after the agile manifesto, right? And for 80% of these idea executives to basically claim that the best approach is for requirements to be fully baked before salt, before software development starts, basically shows that we still have a very major issue. >>And again, our hypothesis in working with many organizations is that the key challenge is really the boundary between business and it, which is still very much contract based. If you look at the business side, they basically are expecting for it deliver on time on budget, right. But what is the incentive for it to actually delivering on the business outcomes, right? How often is it measured on the business outcomes and not on an SLA or on a budget type criteria? And so that's really the fundamental shift that we need to, we really need to drive up as an industry. Um, and you know, we, we talk about kind of this, this imperative for organizations to operate that's one, and back to the, the, um, you know, various Doris dilemna the key difference between these larger organization is, is really kind of, uh, if you look at the amount of capital investment that they can put into pretty much anything, why are they losing compared to, um, you know, startups? What, why is it that, uh, more than 40% of, uh, personal loans today or issued not by your traditional brick and mortar banks, but by, um, startups? Well, the reason, yes, it's the traditional culture of doing incremental changes and not disrupting ourselves, which Christiansen covered the length, but it's also the inability to really fundamentally change kind of a dynamic picture. We can business it and, and, and partner right. To, to deliver on a specific business outcome. >>All right. I love that. That's a great, that's a great summary. And in fact, getting ready for this interview, I saw you mentioning another thing where, you know, the, the problem with the agile development is that you're actually now getting more silos. Cause you have all these autonomous people working, you know, kind of independently. So it's even a harder challenge for, for the business leaders to, to, as you said, to know, what's actually going on, but, but certainly I w I want to close, um, and talk about the coalition. Um, so clearly these are all great concepts. These are concepts you want to apply to your business every day. Why the coalition, why, you know, take these concepts out to a broader audience, including either your, your competition and the broader industry to say, Hey, we, as a group need to put a stamp of approval on these concepts, these values, these principles. >>So first I think we, we want, um, everybody to realize that we are all talking about the same things, the same concepts. I think we were all from our own different vantage point, realizing that things after change, and again, back to, you know, whether it's value stream management or site reliability engineering, or biz ops, we're all kind of using slightly different languages. Um, and so I think one of the important aspects of BizOps is for us, all of us, whether we're talking about, you know, consulting agile transformation experts, uh, whether we're talking about vendors, right, provides kind of tools and technologies or these large enterprises to transform for all of us to basically have kind of a reference that lets us speak around kind of, um, in a much more consistent way. The second aspect is for, to me is for, um, DS concepts to start to be embraced, not just by us or trying, or, you know, vendors, um, system integrators, consulting firms, educators, thought leaders, but also for some of our old customers to start to become evangelists of their own in the industry. >>So we, our, our objective with the coalition needs to be pretty, pretty broad. Um, and our hope is by, by starting to basically educate, um, our, our joint customers or partners, that we can start to really foster these behaviors and start to really change some of dynamics. So we're very pleased at if you look at, uh, some of the companies which have joined the, the, the, the manifesto. Um, so we have vendors such as desktop or advance, or, um, uh, PagerDuty for instance, or even planned view, uh, one of my direct competitors, um, but also thought leaders like Tom Davenport or, uh, or cap Gemini or, um, um, smaller firms like, uh, business agility, institutes, or agility elf. Um, and so our goal really is to start to bring together, uh, fall years, people would have been LP, large organizations, do digital transformation vendors. We're providing the technologies that many of these organizations use to deliver on this digital preservation and for all of us to start to provide the kind of, uh, education support and tools that the industry needs. Yeah, >>That's great surge. And, uh, you know, congratulations to you and the team. I know this has been going on for a while, putting all this together, getting people to sign onto the manifesto, putting the coalition together, and finally today getting to unveil it to the world in, in a little bit more of a public, uh, opportunity. So again, you know, really good values, really simple principles, something that, that, uh, shouldn't have to be written down, but it's nice cause it is, and now you can print it out and stick it on your wall. So thank you for, uh, for sharing this story and again, congrats to you and the team. >>Thank you. Thanks, Jeff. Appreciate it. >>Oh, my pleasure. Alrighty, surge. If you want to learn more about the BizOps manifest to go to biz ops manifesto.org, read it and you can sign it and you can stay here for more coverage. I'm the cube of the biz ops manifesto unveiled. Thanks for watching. See you next >>From around the globe. It's the cube with digital coverage of this ops manifesto unveiled brought to you by bill. >>Hey, welcome back, everybody Jeffrey here with the cube. Welcome back to our ongoing coverage of the biz ops manifesto unveiling. It's been in the works for awhile, but today's the day that it actually kind of come out to the, to the public. And we're excited to have a real industry luminary here to talk about what's going on, why this is important and share his perspective. And we're happy to have from Cape Cod, I believe is Tom Davenport. He is a distinguished author and professor at Babson college. We could go on, he's got a lot of great titles and, and really illuminary in the area of big data and analytics Thomas. Great to see you. >>Thanks Jeff. Happy to be here with you. >>Great. So let's just jump into it, you know, and getting ready for this. I came across your LinkedIn posts. I think you did earlier this summer in June and right off the bat, the first sentence just grabbed my attention. I'm always interested in new attempts to address longterm issues, uh, in how technology works within businesses, biz ops. What did you see in biz ops, uh, that, that kind of addresses one of these really big longterm problems? >>Well, yeah, but the longterm problem is that we've had a poor connection between business people and it people between business objectives and the, it solutions that address them. This has been going on, I think since the beginning of information technology and sadly it hasn't gone away. And so biz ops is a new attempt to deal with that issue with, you know, a new framework, eventually a broad set of solutions that increase the likelihood that we'll actually solve a business problem with an it capability. >>Right. You know, it's interesting to compare it with like dev ops, which I think a lot of people are probably familiar with, which was, you know, built around, uh, agile software development and a theory that we want to embrace change that that changes. Okay. Uh, and we want to be able to iterate quickly and incorporate that. And that's been happening in the software world for, for 20 plus years. What's taken so long to get that to the business side, because as the pace of change has changed on the software side, you know, that's a strategic issue in terms of execution on the business side that they need now to change priorities. And, you know, there's no PRDs and MRDs and big, giant strategic plans that sit on the shelf for five years. That's just not the way business works anymore. It took a long time to get here. >>Yeah, it did. And you know, there have been previous attempts to make a better connection between business and it, there was the so called alignment framework that a couple of friends of mine from Boston university developed, I think more than 20 years ago, but you know, now we have better technology for creating that linkage. And the, you know, the idea of kind of ops oriented frameworks is pretty pervasive now. So I think it's time for another serious attempt at it. Right. >>And do you think doing it this way, right. With the, with the biz ops coalition, you know, getting a collection of, of, of kind of likeminded individuals and companies together, and actually even having a manifesto, which we're making this declarative statement of, of principles and values, you think that's what it takes to kind of drive this kind of beyond the experiment and actually, you know, get it done and really start to see some results in, in, uh, in production in the field. >>I think certainly, um, no one vendor organization can pull this off single handedly. It does require a number of organizations collaborating and working together. So I think our coalition is a good idea and a manifesto is just a good way to kind of lay out what you see as the key principles of the idea. And that makes it much easier for everybody to understand and act on. >>I think it's just, it's really interesting having, you know, having them written down on paper and having it just be so clearly articulated both in terms of the, of the values as well as, as the, uh, the principles and the values, you know, business outcomes matter trust and collaboration, data driven decisions, which is the number three or four, and then learn, respond and pivot. It doesn't seem like those should have to be spelled out so clearly, but, but obviously it helps to have them there. You can stick them on the wall and kind of remember what your priorities are, but you're the data guy. You're the analytics guy, uh, and a big piece of this is data and analytics and moving to data-driven decisions. And principle number seven says, you know, today's organizations generate more data than humans can process and informed decisions can be augmented by machine learning and artificial intelligence right up your alley. You know, you've talked a number of times on kind of the mini stages of analytics. Um, and how has that's evolved over, over time, you know, as you think of analytics and machine learning, driving decisions beyond supporting decisions, but actually starting to make decisions in machine time. What's that, what's that thing for you? What does that make you, you know, start to think, wow, this is, this is going to be pretty significant. >>Yeah. Well, you know, this has been a longterm interest of mine. Um, the last generation of AI, I was very interested in expert systems. And then, um, I think, uh, more than 10 years ago, I wrote an article about automated decision-making using what was available then, which was rule-based approaches. Um, but you know, this addresses an issue that we've always had with analytics and AI. Um, you know, we, we tended to refer to those things as providing decision support. The problem is that if the decision maker didn't want their support, didn't want to use them in order to make a decision, they didn't provide any value. And so the nice thing about automating decisions, um, with now contemporary AI tools is that we can ensure that data and analytics get brought into the decision without any possible disconnection. Now, I think humans still have something to add here, and we often will need to examine how that decision is being made and maybe even have the ability to override it. But in general, I think at least for, you know, repetitive tactical decisions, um, involving a lot of data, we want most of those, I think to be at least recommended if not totally made by an algorithm or an AI based system, and that I believe would add to the quality and the precision and the accuracy of decisions and in most organizations, >>No, I think, I think you just answered my next question before I, before Hey, asked it, you know, we had dr. Robert Gates on a former secretary of defense on a few years back, and we were talking about machines and machines making decisions. And he said at that time, you know, the only weapon systems, uh, that actually had an automated trigger on it were on the North Korea and South Korea border. Um, everything else, as you said, had to go through a sub person before the final decision was made. And my question is, you know, what are kind of the attributes of the decision that enable us to more easily automated? And then how do you see that kind of morphing over time, both as the data to support that as well as our comfort level, um, enables us to turn more and more actual decisions over to the machine? >>Well, yeah, it's suggested we need, um, data and, um, the data that we have to kind of train our models has to be high quality and current. And we, we need to know the outcomes of that data. You know, um, most machine learning models, at least in business are supervised. And that means we need to have labeled outcomes in the, in the training data. But I, you know, um, the pandemic that we're living through is a good illustration of the fact that, that the data also have to be reflective of current reality. And, you know, one of the things that we're finding out quite frequently these days is that, um, the data that we have do not reflect, you know, what it's like to do business in a pandemic. Um, I wrote a little piece about this recently with Jeff cam at wake forest university, we called it data science quarantined, and we interviewed with somebody who said, you know, it's amazing what eight weeks of zeros will do to your demand forecast. We just don't really know what happens in a pandemic. Um, our models maybe have to be put on the shelf for a little while and until we can develop some new ones or we can get some other guidelines into making decisions. So I think that's one of the key things with automated decision making. We have to make sure that the data from the past and that's all we have of course, is a good guide to, you know, what's happening in the present and the future as far as we understand it. Yeah. >>I used to joke when we started this calendar year 2020, it was finally the year that we know everything with the benefit of hindsight, but it turned out 20, 20 a year. We found out we actually know nothing and everything thought we knew, but I wanna, I wanna follow up on that because you know, it did suddenly change everything, right? We got this light switch moment. Everybody's working from home now we're many, many months into it, and it's going to continue for a while. I saw your interview with Bernard Marr and you had a really interesting comment that now we have to deal with this change. We don't have a lot of data and you talked about hold fold or double down. And, and I can't think of a more, you know, kind of appropriate metaphor for driving the value of the BizOps when now your whole portfolio strategy, um, these to really be questioned and, and, you know, you have to be really, uh, well, uh, executing on what you are, holding, what you're folding and what you're doubling down with this completely new environment. >>Well, yeah, and I hope I did this in the interview. I would like to say that I came up with that term, but it actually came from a friend of mine. Who's a senior executive at Genpact. And, um, I, um, used it mostly to talk about AI and AI applications, but I think you could, you could use it much more broadly to talk about your entire sort of portfolio of digital projects. You need to think about, well, um, given some constraints on resources and a difficult economy for a while, which of our projects do we want to keep going on pretty much the way we were and which ones are not that necessary anymore? You see a lot of that in AI, because we had so many pilots, somebody told me, you know, we've got more pilots around here than O'Hare airport and AI. Um, and then, but the ones that involve double down they're even more important to you. They are, you know, a lot of organizations have found this out in the pandemic, on digital projects. It's more and more important for customers to be able to interact with you, um, digitally. And so you certainly wouldn't want to, um, cancel those projects or put them on hold. So you double down on them and get them done faster and better. >>Right, right. Uh, another, another thing that came up in my research that you quoted, um, was, was from Jeff Bezos, talking about the great bulk of what we do is quietly, but meaningfully improving core operations. You know, I think that is so core to this concept of not AI and machine learning and kind of the general sense, which, which gets way too much buzz, but really applied right. Applied to a specific problem. And that's where you start to see the value. And, you know, the, the BizOps, uh, manifesto is, is, is calling it out in this particular process. But I'd love to get your perspective as you know, you speak generally about this topic all the time, but how people should really be thinking about where are the applications where I can apply this technology to get direct business value. >>Yeah, well, you know, even talking about automated decisions, um, uh, the kind of once in a lifetime decisions, uh, the ones that, um, ag Lafley, the former CEO of Procter and gamble used to call the big swing decisions. You only get a few of those. He said in your tenure as CEO, those are probably not going to be the ones that you're automating in part because, um, you don't have much data about them. You're only making them a few times and in part, because, um, they really require that big picture thinking and the ability to kind of anticipate the future, that the best human decision makers, um, have. Um, but, um, in general, I think where they are, the projects that are working well are, you know, when I call the low hanging fruit ones, the, some people even report to it referred to it as boring AI. >>So, you know, sucking data out of a contract in order to compare it to a bill of lading for what arrived at your supply chain companies can save or make a lot of money with that kind of comparison. It's not the most exciting thing, but AI, as you suggested is really good at those narrow kinds of tasks. It's not so good at the, at the really big moonshots, like curing cancer or, you know, figuring out well what's the best stock or bond under all circumstances or even autonomous vehicles. Um, we, we made some great progress in that area, but everybody seems to agree that they're not going to be perfect for quite a while. And we really don't want to be driving around on them very much unless they're, you know, good and all kinds of weather and with all kinds of pedestrian traffic and you know, that sort of thing, right? That's funny you bring up contract management. >>I had a buddy years ago, they had a startup around contract management and was like, and this was way before we had the compute power today and cloud proliferation. I said, you know, how, how can you possibly build software around contract management? It's language, it's legal, ease. It's very specific. And he's like, Jeff, we just need to know where's the contract. And when does it expire? And who's the signatory. And he built a business on those, you know, very simple little facts that weren't being covered because their contracts contractor in people's drawers and files and homes, and Lord only knows. So it's really interesting, as you said, these kind of low hanging fruit opportunities where you can extract a lot of business value without trying to, you know, boil the ocean. >>Yeah. I mean, if you're Amazon, um, uh, Jeff Bezos thinks it's important to have some kind of billion dollar projects. And he even says it's important to have a billion dollar failure or two every year. But I think most organizations probably are better off being a little less aggressive and, you know, sticking to, um, what AI has been doing for a long time, which is, you know, making smarter decisions based on, based on data. >>Right? So Tom, I want to shift gears one more time before, before we let you go on on kind of a new topic for you, not really new, but you know, not, not a, the vast majority of, of your publications and that's the new way to work, you know, as, as the pandemic hit in mid March, right. And we had this light switch moment, everybody had to work from home and it was, you know, kind of crisis and get everybody set up. Well, you know, now we're five months, six months, seven months. A number of companies have said that people are not going to be going back to work for a while. And so we're going to continue on this for a while. And then even when it's not what it is now, it's not going to be what it was before. So, you know, I wonder, and I know you, you, uh, you teased, you're working on a new book, you know, some of your thoughts on, you know, kind of this new way to work and, and the human factors in this new, this new kind of reality that we're kind of evolving into, I guess. >>Yeah. I missed was an interest of mine. I think, um, back in the nineties, I wrote an article called, um, a coauthored, an article called two cheers for the virtual office. And, you know, it was just starting to emerge. Then some people were very excited about it. Some people were skeptical and, uh, we said two cheers rather than three cheers because clearly there's some shortcomings. And, you know, I keep seeing these pop up. It's great that we can work from our homes. It's great that we can accomplish most of what we need to do with a digital interface, but, um, you know, things like innovation and creativity and certainly, um, uh, a good, um, happy social life kind of requires some face to face contact every now and then. And so I, you know, I think we'll go back to an environment where there is some of that. >>Um, we'll have, um, times when people convene in one place so they can get to know each other face to face and learn from each other that way. And most of the time, I think it's a huge waste of people's time to commute into the office every day and to jump on airplanes, to, to, um, give every little, um, uh, sales call or give every little presentation. Uh, we just have to really narrow down what are the circumstances where face to face contact really matters. And when can we get by with, with digital, you know, I think one of the things in my current work I'm finding is that even when you have AI based decision making, you really need a good platform in which that all takes place. So in addition to these virtual platforms, we need to develop platforms that kind of structure the workflow for us and tell us what we should be doing next, then make automated decisions when necessary. And I think that ultimately is a big part of biz ops as well. It's not just the intelligence of an AI system, but it's the flow of work that kind of keeps things moving smoothly throughout your organization. >>Yeah. I think such, such a huge opportunity as you just said, cause I forget the stats on how often we're interrupted with notifications between email texts, Slack, a sauna, Salesforce, the list goes on and on. So, you know, to put an AI layer between the person and all these systems that are begging for attention, and you've written a book on the attention economy, which is a whole nother topic, we'll say for another day, you know, it really begs, it really begs for some assistance because you know, you just can't get him picked, you know, every two minutes and really get quality work done. It's just not, it's just not realistic. And you know what? I don't think that's a feature that we're looking for. I agree. Totally. Alright, Tom. Well, thank you so much for your time. Really enjoyed the conversation. I gotta dig into the library. It's very long. So I might start at the attention economy. I haven't read that one in to me. I think that's the fascinating thing in which we're living. So thank you for your time and, uh, great to see you. >>My pleasure, Jeff. Great to be here. >>All right. Take care. Alright. He's Tom I'm Jeff. You are watching the continuing coverage of the biz ops manifesto and Vale. Thanks for watching the cube. We'll see you next time.

>>From around the globe. It's the cube with digital coverage, a BizOps manifesto unveiled brought to you by biz ops coalition. >>Hey, welcome back everybody. Jeff Frick here with the cube. Welcome back to our ongoing coverage of the biz ops manifesto. Unveil. Something has been in the works for a little while. Today's the formal unveiling, and we're excited to have three of the core of founding members of the manifesto authors of the manifesto. If you will, uh, joining us again, we've had them all on individually. Now we're going to have a great power panel first up. We're gab Mitt, Kirsten returning he's the founder and CEO of Tasktop mic. Good to see you again. Where are you dialing in from? >>Great to see you again, Jeff I'm dialing from Vancouver, >>We're Canada, Vancouver, Canada. One of my favorite cities in the whole wide world. Also we've got Tom Davenport come in from across the country. He's a distinguished professor and author from Babson college, Tom. Great to see you. And I think you said you're at a fun, exotic place on the East coast >>Realm of Memphis shoe sits on Cape Cod. >>Great to see you again and also joining surge Lucio. He is the VP and general manager enterprise software division at Broadcom surge. Great to see you again, where are you coming in from? >>Uh, from Boston right next to kickoff. >>Terrific. So welcome back, everybody again. Congratulations on this day. I know it's, it's been a lot of work to get here for this unveil, but let's just jump into it. The biz ops manifesto, what was the initial reason to do this? And how did you decide to do it in a kind of a coalition, a way bringing together a group of people versus just making it an internal company, uh, initiative that, you know, you can do better stuff within your own company, surge, why don't we start with you? >>Yeah, so, so I think we were at a really critical juncture, right? Many, um, large enterprises are basically struggling with their digital transformation. Um, in fact, um, many recognize that, uh, the, the business side, it collaboration has been, uh, one of the major impediments, uh, to drive that kind of transformation. And if we look at the industry today, many people are, whether we're talking about vendors or, um, you know, system integrators, consulting firms are talking about the same kind of concepts, but using very different language. And so we believe that bringing all these different players together, um, as part of the coalition and formalizing, uh, basically the core principles and values in a BizOps manifesto, we can really start to F could have a much bigger movement where we can all talk about kind of the same concepts and we can really start to provide, could have a much better support for large organizations to transform. Uh, so whether it is technology or services or, um, we're training, I think that that's really the value of bringing all of these players together, right. >>And Nick to you, why did you get involved in this, in this effort? >>So Ben close and follow the agile movement since it started two decades ago with that manifesto. >>And I think we got a lot of improvement at the team level, and I think as satisfies noted, uh, we really need to improve at the business level. Every company is trying to become a software innovator, uh, trying to make sure that they can adapt quickly and the changing market economy and what everyone's dealing with in terms of needing to deliver the customer sooner. However, agile practices have really focused on these metrics, these measures and understanding processes that help teams be productive. Those things now need to be elevated to the business as a whole. And that just hasn't happened. Uh, organizations are actually failing because they're measuring activities and how they're becoming more agile, how teams are functioning, not how much quickly they're delivering value to the customer. So we need to now move past that. And that's exactly what the that's manifested provides. Right, >>Right, right. And Tom, to you, you've been covering tech for a very long time. You've been looking at really hard challenges and a lot of work around analytics and data and data evolution. So there's a definitely a data angle here. I wonder if you could kind of share your perspective of what you got excited to, uh, to sign onto this manifesto. >>Sure. Well, I have, you know, for the past 15 or 20 years, I've been focusing on data and analytics and AI, but before that I was a process management guy and a knowledge management guy. And in general, I think, you know, we've just kind of optimized that to narrow a level, whether you're talking about agile or dev ops or ML ops, any of these kinds of ops oriented movements, we're making individual project, um, performance and productivity better, but we're not changing the business, uh, effectively enough. And that's the thing that appealed to me about the biz ops idea that we're finally creating a closer connection between what we do with technology and how it changes the business and provides value to it. >>Great. Uh, surge back to you, right? I mean, people have been talking about digital transformation for a long time and it's been, you know, kind of trucking along and then covert hit and it was instant lights, which everyone's working from home. You've got a lot more reliance on your digital tools, digital communication, uh, both within your customer base and your partner base, but also then your employees when you're, if you could share how that really pushed this all along. Right? Because now suddenly the acceleration of digital transformation is higher. Even more importantly, you got much more critical decisions to make into what you do next. So kind of your portfolio management of projects has been elevated significantly when maybe revenues are down, uh, and you really have to, uh, to prioritize and get it right. >>Yeah. Maybe I'll just start by quoting Satina Nello basically recently said that they're speeding the two years of digital preservation just last two months in any many ways. That's true. Um, but, but yet when we look at large enterprises, they're >>Still struggling with the kind of a changes in culture that they really need to drive to be able to disrupt themselves. And not surprisingly, you know, when we look at certain parts of the industry, you know, we see some things which are very disturbing, right? So about 40% of the personal loans today, or being, uh, origin data it's by fintechs, uh, of a like of Sophie or, uh, or a lending club, right? Not to a traditional brick and mortar for BEC. And so the, well, there is kind of a much more of an appetite and it's a, it's more of a survival type of driver these days. Uh, the reality is that's in order for these large enterprises to truly transform and engage with this digital transformation, they need to start to really align the business. And it, you know, in many ways, uh, make covered that agile really emerged from the core desire to truly improve software predictability between which we've really missed is all that we, we start to aligning the software predictability to business predictability and to be able to have continual sleep continuous improvement and measurement of business outcomes. So by aligning kind of these, uh, kind of inward metrics, that's, it is typically being using to business outcomes. We think we can start to really ELP different stakeholders within the organization to collaborate. So I think there is more than ever. There's an imperative to act now. Um, and, and resolves, I think is kind of the right approach to drive that transformation. Right. >>I want to follow up on the culture comment, uh, with Utah, because you've talked before about kind of process flow and process flow throughout a whore and an organization. And, you know, we talk about people process and tech all the time. And I think the tech is the easy part compared to actually changing the people the way they think. And then the actual processes that they put in place. It's a much more difficult issue than just the tech issue to get this digital transformation in your organization. >>Yeah. You know, I've always found that the soft stuff about, you know, the culture of the behavior, the values is the hard stuff to change and more and more, we, we realized that to be successful with any kind of digital transformation you have to change people's behaviors and attitudes. Um, we haven't made as much progress in that area as we might have. I mean, I've done some surveys suggesting that, um, most organizations still don't have data-driven cultures. And in many cases there is a lower percentage of companies that say they have that then, um, did a few years ago. So we're kind of moving in the wrong direction, which means I think that we have to start explicitly addressing that, um, cultural, behavioral dimension and not just assuming that it will happen if we, if we build a system, >>If we build it, they won't necessarily come. Right. >>Right. So I want to go to, to you Nick cause you know, we're talking about workflows and flow, um, and, and you've written about flow both in terms of, um, you know, moving things along a process and trying to find bottlenecks, identify bottlenecks, which is now even more important again, when these decisions are much more critical. Cause you have a lot less, uh, wiggle room in tough times, but you also talked about flow from the culture side and the people side. So I wonder if you can just share your thoughts on, you know, using flow as a way to think about things, to get the answers better. >>Yeah, absolutely. And I'll refer back to what Tom has said. If you're optimized, you need to optimize your system. You need to optimize how you innovate and how you deliver value to the business and the customer. Now, what we've noticed in the data, since that we've learned from customers, value streams, enterprise organizations, value streams, is that when it's taking six months at the end to deliver that value with the flow is that slow. You've got a bunch of unhappy developers, unhappy customers when you're innovating house. So high performing organizations we can measure at antenna flow time and dates. All of a sudden that feedback loop, the satisfaction, your developers measurably, it goes up. So not only do you have people context, switching glass, you're delivering so much more value to customers at a lower cost because you've optimized for flow rather than optimizing for these, these other approximate tricks that we use, which is how efficient is my adult team. How quickly can we deploy software? Those are important, but they do not provide the value of agility of fast learning of adaptability to the business. And that's exactly what the biz ops manifesto pushes your organization to do. You need to put in place this new operating model that's based on flow on the delivery of business value and on bringing value to market much more quickly than you were before. Right. >>I love that. And I'm gonna back to you Tom, on that to follow up. Cause I think, I don't think people think enough about how they prioritize what they're optimizing for, because you know, if you're optimizing for a versus B, you know, you can have a very different product that, that you kick out. And, you know, my favorite example is with Clayton Christianson and innovator's dilemma talking about the three inch hard drive, if you optimize it for power, you know, is one thing, if you optimize it for vibration is another thing and sure enough, you know, they missed it on the poem because it was the, it was the game console, which, which drove that whole business. So when you're talking to customers and we think we hear it with cloud all the time, people optimizing for a cost efficiency, instead of thinking about it as an innovation tool, how do you help them kind of rethink and really, you know, force them to, to look at the, at the prioritization and make sure they're prioritizing on the right thing is make just that, what are you optimizing for? >>Oh yeah. Um, you have one of the most important aspects of any decision or attempt to resolve a problem in an organization is the framing process. And, um, you know, it's, it's a difficult aspect to have the decision to confirm it correctly in the first place. Um, there, it's not a technology issue. In many cases, it's largely a human issue, but if you frame >>That decision or that problem incorrectly to narrowly say, or you frame it as an either or situation where you could actually have some of both, um, it, it's very difficult for the, um, process to work out correctly. So in many cases, I think we need to think more at the beginning about how we bring this issue or this decision in the best way possible before we charge off and build a system to support it. You know, um, it's worth that extra time to think, think carefully about how the decision has been structured. Right, >>Sir, I want to go back to you and talk about the human factors because as we just discussed, you can put it in great technology, but if the culture doesn't adopt it and people don't feel good about it, you know, it's not going to be successful and that's going to reflect poorly on the technology, even if that had nothing to do with it. And you know, when you look at the, the, the, the core values, uh, of the Bezos manifesto, you know, a big one is trust and collaboration, you know, learn, respond, and pivot. Wonder if you can share your thoughts on, on trying to get that cultural shift, uh, so that you can have success with the people, or excuse me, with the technology in the process and helping customers, you know, take this more trustworthy and kind of proactive, uh, position. >>So I think, I think at the ground level, it truly starts with the realization that we're all different. We come from different backgrounds. Uh, oftentimes we tend to blame the data. It's not uncommon my experiments that we spend the first 30 minutes of any kind of one hour conversation to debate the validity of the data. Um, and so, um, one of the first kind of, uh, probably manifestations that we've had or revelations as we start to engage with our customers is spoke just exposing, uh, high-fidelity data sets to different stakeholders from their different lens. We start to enable these different stakeholders to not debate the data. That's really collaborate to find a solution. So in many ways, when, when, when we think about kind of the types of changes we're trying to, to truly affect around data driven decision making, he told about bringing the data in context and the context that is relevant and understandable for, for different stakeholders, whether we're talking about an operator or develop for a business analyst. >>So that's, that's the first thing. The second layer I think, is really to provide context to what people are doing in their specific silo. And so I think one of the best examples I have is if you start to be able to align business KPI, whether you are counting, you know, sales per hour, or the engagements of your users on your mobile applications, whatever it is, you can start to connect that PKI to business KPI, to the KPIs that developers might be looking at, whether it is all the number of defects or velocity or whatever over your metrics that you're used to, to actually track you start to be able to actually contextualize in what we are, the effecting, basically a metric of that that is really relevant. And then what we see is that this is a much more systematic way to approach the transformation than say, you know, some organizations kind of creating some of these new products or services or initiatives, um, to, to drive engagements, right? >>So if you look at zoom, for instance, zoom giving away a it service to, uh, to education, he's all about, I mean, there's obviously a marketing aspect in there, but it's, it's fundamentally about trying to drive also the engagement of their own teams. And because now they're doing something for good and many organizations are trying to do that, but you only can do this kind of things in the limited way. And so you really want to start to rethink how you connect to, everybody's kind of a business objective fruit data, and now you start to get people to stare at the same data from their own lens and collaborate on all the data. Right, >>Right. That's a good, uh, Tom, I want to go back to you. You've been studying it for a long time, writing lots of books and getting into it. Um, why now, you know, what, why, why now are we finally aligning business objectives with, with it objectives? You know, why didn't this happen before? And, you know, what are the factors that are making now the time for this, this, this move with the, uh, with the biz ops? >>Well, and much of a past, it was sort of a back office related activity. And, you know, it was important for, um, uh, producing your paychecks and, uh, capturing the customer orders, but the business wasn't built around it now, every organization needs to be a software business, a data business, a digital business, the auntie has been raised considerably. And if you aren't making that connection between your business objectives and the technology that supports it, you run a pretty big risk of, you know, going out of business or losing out to competitors. Totally. So, um, and even if you're in, uh, an industry that hasn't historically been terribly, um, technology oriented customer expectations flow from, uh, you know, the digital native, um, companies that they work with to basically every industry. So you're compared against the best in the world. So we don't really have the luxury anymore of screwing up our it projects or building things that don't really work for the business. Um, it's mission critical that we do that well. Um, almost every time, I just want to fall by that, Tom, >>In terms of the, you've talked extensively about kind of these evolutions of data and analytics from artismal stage to the big data stage, the data economy stage, the AI driven stage and what I find diff interesting that all those stages, you always put a start date, you never put an end date. Um, so you know, is the, is the big data I'm just going to use that generically a moment in time finally here where we're, you know, off mahogany row with the data scientists, but actually can start to see the promise of delivering the right insight to the right person at the right time to make that decision. >>Well, I think it is true that in general, these previous stages never seemed to go away. The, um, the artisinal stuff is still being done, but we would like for less and less of it to be artisinal, we can't really afford for everything to be artisinal anymore. It's too labor and, and time consuming to do things that way. So we shift more and more of it to be done through automation and B to be done with a higher level of productivity. And, um, you know, at some point maybe we reached the stage where we don't do anything artisanally anymore. I'm not sure we're there yet, but we are, we are making progress. Right. >>Right. And Mick, back to you in terms of looking at agile, cause you're, you're such a student of agile. When, when you look at the opportunity with biz ops and taking the lessons from agile, you know, what's been the inhibitor to stop this in the past. And what are you so excited about? You know, taking this approach will enable. >>Yeah. I think both search and Tom hit on this is that in agile what's happened is that we've been measuring tiny subsets of the value stream, right? We need to elevate the data's there. Developers are working on these tools that delivering features that the foundations for for great culture are there. I spent two decades as a developer. And when I was really happy is when I was able to deliver value to customers, the quicker I was able to do that the fewer impediments are in my way, that quicker was deployed and running in the cloud, the happier I was, and that's exactly what's happening. If we can just get the right data, uh, elevated to the business, not just to the agile teams, but really this, these values of ours are to make sure that you've got these data driven decisions with meaningful data that's oriented around delivering value to customers. Not only these legacies that Tom touched on, which has cost center metrics. So when, from where for it being a cost center and something that provided email and then back office systems. So we need to rapidly shift to those new, meaningful metrics that are customized business centric and make sure that every development the organization is focused on those as well as the business itself, that we're measuring value. And that will help you that value flow without interruptions. >>I love that mic. Cause if you don't measure it, you can't improve on it and you gotta, but you gotta be measuring the right thing. So gentlemen, uh, thank you again for, for your time. Uh, congratulations on the, uh, on the unveil of the biz ops manifesto and bringing together this coalition, uh, of, of, uh, industry experts to get behind this. And, you know, there's probably never been a more important time than now to make sure that your prioritization is in the right spot and you're not wasting resources where you're not going to get the ROI. So, uh, congratulations again. And thank you for sharing your thoughts with us here on the cube. >>Thank you. >>Alright, so we had surge Tom and Mick I'm. Jeff, you're watching the cube. It's a biz ops manifesto unveil. Thanks for watching. We'll see you next time >>From around the globe. It's the cube with digital coverage of biz ops manifesto unveiled brought to you by biz ops coalition. >>Hey, welcome back. Variety. Jeff Frick here with the cube. We're in our Palo Alto studios, and we'd like to welcome you back to our continuing coverage of biz ops manifesto unveil some exciting day to really, uh, kind of bring this out into public. There's been a little bit of conversation, but today's really the official unveiling and we're excited to have our next guest is share a little bit more information on it. He's Patrick tickle. He's a chief product officer for planned view. Patrick. Great to see you. >>Yeah, it's great to be here. Thanks for the invite. So why >>The biz ops manifesto, why the biz ops coalition now when you guys have been at it, it's relatively mature marketplace businesses. Good. What was missing? Why, why this, why this coalition? >>Yeah. So, you know, again, why is, why is biz ops important and why is this something that I'm, you know, I'm so excited about, but I think companies as well, right? Well, no, in some ways or another, this is a topic that I've been talking to the market and our customers about for a long time. And it's, you know, I really applaud this whole movement. Right. And, um, it resonates with me because I think one of the fundamental flaws, frankly, of the way we have talked about technology and business literally for decades, uh, has been this idea of, uh, alignment. Those who know me, I occasionally get off on this little rant about the word alignment, right. But to me, the word alignment is, is actually indicative of the, of the, of the flaw in a lot of our organizations and biz ops is really, I think now trying to catalyze and expose that flaw. >>Right. Because, you know, I always say that, you know, you know, alignment implies silos, right. Instantaneously, as soon as you say there's alignment, there's, there's obviously somebody who's got a direction and other people that have to line up and that kind of siloed, uh, nature of organizations then frankly, the passive nature of it. Right. I think so many technology organizations are like, look, the business has the strategy you guys need to align. Right. And, and, you know, as a product leader, right. That's where I've been my whole career. Right. I can tell you that I never sit around. I almost never use the word alignment. Right. I mean, whether, you know, I never sit down and say, you know, the product management team has to get aligned with dev, right. Or the dev team has to get aligned with the delivery and ops teams. I mean, what I say is, you know, are we on strategy, right? >>Like we've, we have a strategy as a, as a full end to end value stream. Right. And that there's no silos. And I mean, look, every on any given day we got to get better. Right. But the context, the context we operate is not about alignment. Right. It's about being on strategy. And I think I've talked to customers a lot about that, but when I first read the manifesto, I was like, Oh yeah, this is exactly. This is breaking down. Maybe trying to eliminate the word alignment, you know, from a lot of our organizations, because we literally start thinking about one strategy and how we go from strategy to delivery and have it be our strategy, not someone else's that we're all aligning to. And I, and it's a great way to catalyze that conversation that I've, it's been in my mind for years, to be honest. Right. >>So, so much to unpack there. One of the things obviously, uh, stealing a lot from, from dev ops and the dev ops manifesto from 20 years ago. And, and as I look through some of the principles and I looked through some of the values, which are, you know, really nicely laid out here, you know, satisfy customer, do continuous delivery, uh, measure, output against real results. Um, the ones that, that jumps out though is really about, you know, change, change, right? Requirements should change frequently. They do change frequently, but I'm curious to get your take from a, from a software development point, it's easy to kind of understand, right. We're making this widget and our competitors, beta widget plus X, and now we need to change our plans and make sure that the plus X gets added to the plan. Maybe it wasn't in the plan, but you talked a lot about product strategy. So in this kind of continuous delivery world, how does that meld with, I'm actually trying to set a strategy, which implies the direction for a little bit further out on the horizon and to stay on that while at the same time, you're kind of doing this real time continual adjustments because you're not working off a giant PRD or MRD anymore. >>Yeah, yeah, totally. Yeah. You know, one of the terms, you know, that we use internally a lot and even with my customers, our customers is we talk about this idea of rewiring, right. And I think, you know, it's kind of a, now an analogy for transformation. And I think a lot of us have to rewire the way we think about things. Right. And I think at Planview where we have a lot of customers who live in that, you know, who operationalize that traditional PPM world. Right. And are shifting to agile and transforming that rewire is super important. And, and to your point, right, it's, you've just, you've got to embrace this idea of, you know, just iterative getting better every day and iterating, iterating, iterating as opposed to building annual plans or, you know, I get customers occasionally who asked me for two or three year roadmap. >>Right. And I literally looked at them and I go, there's no, there's no scenario where I can build a two or three year roadmap. Right. You, you, you think you want that, but that's not, that's not the way we run. Right. And I will tell you the biggest thing that for us, you know, that I think is matched the planning, uh, you know, patents is a word I like to use a lot. So the thing that we've like, uh, that we've done from a planning perspective, I think is matched impedance to continuous delivery is instituting the whole program, implement, you know, the program, increment planning, capabilities, and methodologies, um, in the scaled agile world. Right. And over the last 18 months to two years, we really have now, you know, instrumented our company across three value streams. You know, we do quarterly PI program increment 10 week planning, you know, and that becomes, that becomes the Terra firma of how we plan. >>Right. And it's, what are we doing for the next 10 weeks? And we iterate within those 10 weeks, but we also know that 10 weeks from now, we're gonna, we're gonna adjust iterate again. Right. And that shifting of that planning model to, you know, to being as cross-functional is that as that big room planning kind of model is, um, and also, uh, you know, on that shorter increment, when you get those two things in place, also the impedance really starts to match up, uh, with continuous delivery and it changes, it changes the way you plan and it changes the way you work. Right? >>Yeah. Their thing. Right. So obviously a lot of these things are kind of process driven, both within the values, as well as the principles, but there's a whole lot, really about culture. And I just want to highlight a couple of the values, right? We already talked about business outcomes, um, trust and collaboration, uh, data driven decisions, and then learn, respond and pivot. Right. A lot of those are cultural as much as they are process. So again, is it the, is it the need to really kind of just put them down on paper and, you know, I can't help, but think of, you know, the hammer and up the, a, the thing in the Lutheran church with it, with their manifesto, is it just good to get it down on paper? Because when you read these things, you're like, well, of course we should trust people. And of course we need an environment of collaboration and of course we want data driven decisions, but as we all know saying it and living, it are two very, very different things. >>Yeah. Good question. I mean, I think there's a lot of ways to bring that to life you're right. And just hanging up, you know, I think we've all been through the hanging up posters around your office, which these days, right. Unless you're going to hang a poster in everybody's home office. Right. You can't even, you can't even fake it that you think that might work. Right. So, um, you know, you really, I think we've attacked that in a variety of ways. Right. And you definitely have to, you know, you've got to make the shift to a team centric culture, right. Empowered teams, you know, that's a big deal. Right. You know, a lot of, a lot of the people that, you know, we lived in a world of quote, unquote work. We lived in a deep resource management world for a long, long time, and right. >>A lot of our customers still do that, but, you know, kind of moving to that team centric world is, uh, is really important and core to the trust. Um, I think training is super important, right. I mean, we've, you know, we've internally, right. We've trained hundreds employees over the last a year and a half on the fundamentals really of safe. Right. Not necessarily, you know, we've had, we've had teams delivering in scrum and the continuous delivery for, you know, for years, but the scaling aspect of it, uh, is where we've done a lot of training investment. Um, and then, you know, I think a leadership has to be bought in. Right. You know? And so when we pie plan, you know, myself and Cameron and the other members of our leadership, you know, we're NPI planning, you know, for, for four days. Right. I mean, it's, it's, you've got to walk the walk, you know, from top to bottom and you've got to train on the context. Right. And then you, and then, and, and then once you get through a few cycles where you've done a pivot, right. Or you brought a new team in, and it just works, it becomes kind of this virtuous circle where he'll go, man, this really works so much better than what we used to do. Right. >>Right. The other really key principle to this whole thing is, is aligning, you know, the business leaders and the business prioritization, um, so that you can get to good outcomes with the development and the delivery. Right. And we know again, and kind of classic dev ops to get the dev and the production people together. So they can, you know, quickly ship code that works. Um, but adding the business person on there really puts, puts a little extra responsibility that they, they understand the value of a particular feature or particular priority. Uh, they, they can make the, the, the trade offs and that they kind of understand the effort involved too. So, you know, bringing them into this continuous again, kind of this continuous development process, um, to make sure that things are better aligned and really better prioritize. Cause ultimately, you know, we don't live in an infinite resources situation and people gotta make trade offs. They gotta make decisions as to what goes and what doesn't go in for everything that goes. Right. I always say you pick one thing. Okay. That's 99 other things that couldn't go. So it's really important to have, you know, this, you said alignment of the business priorities as well as, you know, the execution within, within the development. >>Yeah. I think that, you know, uh, you know, I think it was probably close to two years ago. Forester started talking about the age of the customer, right. That, that was like their big theme at the time. Right. And I think to me what that, the age of the customer actually translates to and Mick, Mick and I are both big fans of this whole idea of the project, the product shift, mixed book, you know, it was a great piece on a, you're talking to Mick, you know, as part of the manifesto is one of the authors as well, but this shift from project to product, right? Like the age of the customer, in my opinion, the, the, the embodiment of that is the shift to a product mentality. Right. And, and the product mentality in my opinion, is what brings the business and technology teams together, right? >>Once you, once you're focused on a customer experience, that's delivered through a product or a service that's when I that's, when I started to go with the alignment problem goes away, right. Because if you look at software companies, right, I mean, we run product management models, you know, with software development teams, customer success teams, right. That, you know, the software component of these products that people are building is obviously becoming bigger and bigger, you know, in an, in many ways, right. More and more organizations are trying to model themselves over as operationally like software companies. Right. Um, they obviously have lots of other components in their business than just software, but I think that whole model of customer experience equaling product, and then the software component of product, the product is the essence of what changes that alignment equation and brings business and teams together because all of a sudden, everyone knows what the customer's experiencing. Right. And, and that, that, that makes a lot of things very clear, very quickly. >>Right. I'm just curious how far along this was as a process before, before covert hit, right. Because serendipitous, whatever. Right. But th the sudden, you know, light switch moment, everybody had to go work from home and in March 15th compared to now, we're in October, and this is going to be going on for a while, and it is a new normal and whatever that whatever's going to look like a year from now, or two years from now is TBD, you know, had you guys already started on this journey cause again, to sit down and actually declare this coalition and declare this manifesto is a lot different than just trying to do better within your own organization. >>Yeah. So we had started, uh, you know, w we definitely had started independently, you know, some, some, you know, I think people in the community know that, uh, we, we came together with a company called lean kit a handful of years ago, and I give John Terry actually one of the founders leaned to immense credit for, you know, kind of spearheading our cultural change and not, and not because of, we were just going to be, you know, bringing agile solutions to our customers, but because, you know, he believed that it was going to be a fundamentally better way for us to work. Right. And we kind of, you know, when we started with John and built, you know, out of concentric circles of momentum and, and we've gotten to the place where now it's just part of who we are, but, but I do think that, you know, COVID has, you know, um, I think pre COVID a lot of companies, you know, would, would adopt, you know, the, you would adopt digital slash agile transformation. >>Um, traditional industries may have done it as a reaction to disruption. Right. You know, and in many cases, the disruption to these traditional industries was, I would say a product oriented company, right. That probably had a larger software component, and that disruption caused a competitive issue or a customer issue that caused companies and tried to respond by transforming. I think COVID, you know, all of a sudden flatten that out, right. We literally all got disrupted. Right. And, and so all of a sudden, every one of us is dealing with some degree of market uncertainty, customer uncertainty, uh, and also know none of us were insulated from the need to be able to pivot faster, deliver incrementally, you know, and operate in a different, completely more agile way, uh, you know, post COVID. Right. Yeah. That's great. >>So again, a very, very, very timely, you know, a little bit of serendipity, a little bit of, of planning. And, you know, as, as with all important things, there's always a little bit of luck and a lot of hard work involved. So a really interesting thank you for, for your leadership, Patrick. And, you know, it really makes a statement. I think when you have a bunch of leaderships across an industry coming together and putting their name on a piece of paper, uh, that's aligned around us some principles and some values, which again, if you read them who wouldn't want to get behind these, but if it takes, you know, something a little bit more formal, uh, to kind of move the ball down the field, and then I totally get it and a really great work. Thanks for, uh, thanks for doing it. >>Oh, absolutely. No. Like I said, the first time I read it, I was like, yeah, like you said, this is all, this all makes complete sense, but just documenting it and saying it and talking about it moves the needle. I'll tell you as a company, you gotta, we're pushing really hard on, uh, you know, on our own internal strategy on diversity inclusion. Right? And, and like, once we wrote the words down about what, you know, what we aspire to be from a diversity and inclusion perspective, it's the same thing. Everybody reads the words and goes, why wouldn't we do this? Right. But until you write it down and kind of have again, a manifesto or a Terrafirma of what you're trying to accomplish, you know, then you can rally behind it. Right. As opposed to it being something that's, everybody's got their own version of the flavor. Right. And I think it's a very analogous, you know, kind of, uh, initiative, right. And, uh, and this happening, both of those things, right. Are happening across the industry these days. Right. >>And measure it too. Right. And measure it, measure, measure, measure, get a baseline. Even if you don't like to measure, even if you don't like what the, even if you can argue against the math, behind the measurement, measure it, and at least you can measure it again and you can, and you've got some type of a comp and that is really the only way to, to move it forward. Well, Patrick really enjoyed the conversation. Thanks for, uh, for taking a few minutes out of your day. >>It's great to be here. It's an awesome movement and we're glad >>That'd be part of it. All right. Thanks. And if you want to check out the biz ops, Manifesta go to biz ops, manifesto.org, read it. You might want to sign it. It's there for you. And thanks for tuning in on this segment will continuing coverage of the biz op manifesto unveil here on the cube. I'm Jeff, thanks for watching >>From around the globe. It's the cube with digital coverage of biz ops manifesto unveiled brought to you by biz ops coalition. >>Hey, welcome back, everybody Jeffrey here with the cube. We're coming to you from our Palo Alto studios. And welcome back to this event is the biz ops manifesto unveiling. So the biz ops manifesto and the biz ops coalition had been around for a little while, but today's the big day. That's kind of the big public unveiling or excited to have some of the foundational people that, you know, have put their, put their name on the dotted, if you will, to support this initiative and talk about why that initiative is so important. And so the next guest we're excited to have is dr. Mick Kirsten. He is the founder and CEO of Tasktop mic. Great to see you coming in from Vancouver, Canada, I think, right? Yes. Thank you. Absolutely. I hope your air is a little better out there. I know you had some of the worst air of all of us, a couple, a couple of weeks back. So hopefully things are, uh, are getting a little better and we get those fires under control. Yeah. >>Things have cleared up now. So yeah, it's good. It's good to be close to the U S and it's going to have the Arabic cleaner as well. >>Absolutely. So let's, let's jump into it. So you you've been an innovation guy forever starting way back in the day and Xerox park. I was so excited to do an event at Xerox park for the first time last year. I mean, that, that to me represents along with bell labs and, and some other, you know, kind of foundational innovation and technology centers, that's gotta be one of the greatest ones. So I just wonder if you could share some perspective of getting your start there at Xerox park, you know, some of the lessons you learned and what you've been able to kind of carry forward from those days. >>Yeah. I was fortunate to join Xerox park in the computer science lab there at a very early point in my career, and to be working on open source programming languages. So back then in the computer science lab, where some of the inventions around programming around software development teams, such as object oriented programming, and a lot of what we had around really modern programming levels constructs, those were the teams I have the fortune of working with, and really our goal was. And of course there's as, as you know, uh, there's just this DNA of innovation and excitement and innovation in the water. And really it was the model back then was all about changing the way that we work, uh, was looking at for how we could make it 10 times easier to write code. But this is back in 99. And we were looking at new ways of expressing, especially business concerns, especially ways of enabling people who are, who want to innovate for their business to express those concerns in code and make that 10 times easier than what that would take. >>So we create a new open source programming language, and we saw some benefits, but not quite quite what we expected. I then went and actually joined Charles Stephanie, that former to fucking Microsoft who was responsible for, he actually got Microsoft word as a spark and into Microsoft and into the hands of bill Gates on that company. I was behind the whole office suite and his vision. And then when I was trying to execute with, working for him was to make PowerPoint like a programming language, make everything completely visual. And I realized none of this was really working in that there was something else, fundamentally wrong programming languages, or new ways of building software. Like let's try and do with Charles around intentional programming. That was not enough. >>That was not enough. So, you know, the agile movement got started about 20 years ago, and we've seen the rise of dev ops and really this kind of embracing of, of, of sprints and, you know, getting away from MRDs and PRDs and these massive definitions of what we're going to build and long build cycles to this iterative process. And this has been going on for a little while. So what was still wrong? What was still missing? Why the BizOps coalition, why the biz ops manifesto? >>Yeah, so I basically think we nailed some of the things that the program language levels of teams can have effective languages deployed soften to the cloud easily now, right? And at the kind of process and collaboration and planning level agile two decades, decades ago was formed. We were adopting and all the, all the teams I was involved with and it's really become a self problem. So agile tools, agile teams, agile ways of planning, uh, are now very mature. And the whole challenge is when organizations try to scale that. And so what I realized is that the way that agile was scaling across teams and really scaling from the technology part of organization to the business was just completely flawed. The agile teams had one set of doing things, one set of metrics, one set of tools. And the way that the business was working was planning was investing in technology was just completely disconnected and using a whole different set of advisors. >>Interesting. Cause I think it's pretty clear from the software development teams in terms of what they're trying to deliver. Cause they've got a feature set, right. And they've got bugs and it's easy to, it's easy to see what they deliver, but it sounds like what you're really honing in on is this disconnect on the business side, in terms of, you know, is it the right investment? You know, are we getting the right business ROI on this investment? Was that the right feature? Should we be building another feature or should we building a completely different product set? So it sounds like it's really a core piece of this is to get the right measurement tools, the right measurement data sets so that you can make the right decisions in terms of what you're investing, you know, limited resources. You can't, no one has unlimited resources and ultimately have to decide what to do, which means you're also deciding what not to do. And it sounds like that's a really big piece of this, of this whole effort. >>Yeah. Jeff, that's exactly it, which is the way that the agile team measures their own way of working is very different from the way that you measure business outcomes. The business outcomes are in terms of how happy your customers are, but are you innovating fast enough to keep up with the pace of a rapidly changing economy, rapidly changing market. And those are, those are all around the customer. And so what I learned on this long journey of supporting many organizations transformations and having them try to apply those principles of agile and dev ops, that those are not enough, those measures technical practices, those measured sort of technical excellence of bringing code to the market. They don't actually measure business outcomes. And so I realized that it really was much more around having these entwined flow metrics that are customer centric and business centric and market centric where we need it to go. Right. >>So I want to shift gears a little bit and talk about your book because you're also a bestselling author, a project, a product, and, and, and you, you brought up this concept in your book called the flow framework. And it's really interesting to me cause I know, you know, flow on one hand is kind of a workflow and a process flow and, and you know, that's how things get done and, and, and embrace the flow. On the other hand, you know, everyone now in, in a little higher level existential way is trying to get into the flow right into the workflow and, you know, not be interrupted and get into a state where you're kind of at your highest productivity, you know, kind of your highest comfort, which flow are you talking about in your book or is it a little bit about, >>Well, that's a great question. It's not what I get asked very often. Just to me, it's absolutely both. So that the thing that we want to get to, we've learned how to master individual flow. That is this beautiful book by me, how he teaches me how he does a beautiful Ted talk by him as well about how we can take control of our own flow. So my question with the book with project replies, how can we bring that to entire teams and really entire organizations? How can we have everyone contributing to a customer outcome? And this is really what if you go to the biz ops manifesto, it says, I focus on outcomes on using data to drive whether we're delivering those outcomes rather than a focus on proxy metrics, such as, how quickly did we implement this feature? No, it's really how much value did the customer go to the feature and how quickly did you learn and how quickly did you use that data to drive to that next outcome? >>Really that with companies like Netflix and Amazon have mastered, how do we get that to every large organization, every it organization and make everyone be a software innovator. So it's to bring that co that concept of flow to these entwined value streams. And the fascinating thing is we've actually seen the data. We've been able to study a lot of value streams. We see when flow increases, when organizations deliver value to a customer faster, developers actually become more happy. So things like the employee net promoter scores rise, and we've got empirical data for this. So the beautiful thing to me is that we've actually been able to combine these two things and see the results in the data that you increase flow to the customer. Your developers are more happy. >>I love it, right, because we're all more, we're all happier when we're in the flow and we're all more productive when we're in the flow. So I, that is a great melding of, of two concepts, but let's jump into the, into the manifesto itself a little bit. And, you know, I love that, you know, took this approach really of having kind of four key values and then he gets 12 key principles. And I just want to read a couple of these values because when you read them, it sounds pretty brain dead. Right? Of course. Right. Of course you should focus on business outcomes. Of course you should have trust and collaboration. Of course you should have database decision making processes and not just intuition or, you know, whoever's the loudest person in the room, uh, and to learn and respond and pivot. But what's the value of actually just putting them on a piece of paper, because again, this is not this, these are all good, positive things, right? When somebody reads these to you or tells you these are sticks it on the wall, of course. But unfortunately of course isn't always enough. >>No. And I think what's happened is some of these core principles originally from the agile manifesto two decades ago, uh, the whole dev ops movement of the last decade of flow feedback and continue learning has been key. But a lot of organizations, especially the ones that are undergoing digital transformations have actually gone a very different way, right? The way that they measure value in technology and innovation is through costs for many organizations. The way that they actually are looking at that they're moving to cloud is actually as a reduction in cost. Whereas the right way of looking at moving to cloud is how much more quickly can we get to the value to the customer? How quickly can we learn from that? And how quickly can we drive the next business outcome? So really the key thing is, is to move away from those old ways of doing things, a funny projects and cost centers, uh, to actually funding and investing in outcomes and measuring outcomes through these flow metrics, which in the end are your fast feedback and how quickly you're innovating for your customer. >>So these things do seem, you know, very obvious when you look at them. But the key thing is what you need to stop doing to focus on these. You need to actually have accurate realtime data of how much value your phone to the customer every week, every month, every quarter. And if you don't have that, your decisions are not driven on data. If you don't know what your boggling like is, and this is something that in decades of manufacturing, a car manufacturers, other manufacturers, master, they always know where the bottom back in their production processes. You ask a random CIO when a global 500 company where their bottleneck is, and you won't get a clear answer because there's not that level of understanding. So let's, you actually follow these principles. You need to know exactly where you fall. And I guess because that's, what's making your developers miserable and frustrated around having them context, which on thrash. So it, the approach here is important and we have to stop doing these other things, >>Right? There's so much there to unpack. I love it. You know, especially the cloud conversation, because so many people look at it wrong as, as, as a cost saving device, as opposed to an innovation driver and they get stuck, they get stuck in the literal and the, and you know, I think at the same thing, always about Moore's law, right? You know, there's a lot of interesting real tech around Moore's law and the increasing power of microprocessors, but the real power, I think in Moore's laws is the attitudinal change in terms of working in a world where you know that you've got all this power and what you build and design. I think it's funny to your, your comment on the flow and the bottleneck, right? Cause, cause we know manufacturing, as soon as you fix one bottleneck, you move to your next one, right? You always move to your next point of failure. So if you're not fixing those things, you know, you're not, you're not increasing that speed down the line, unless you can identify where that bottleneck is or no matter how many improvements you make to the rest of the process, it's still going to get hung up on that one spot. >>That's exactly it. And you also make it sound so simple, but again, if you don't have the data driven visibility of where that bottom line is, and these bottlenecks are adjusted to say defense just whack them. All right. So we need to understand is the bottleneck because our security reviews are taking too long and stopping us from getting value for the customer. If it's that automate that process. And then you move on to the next bottleneck, which might actually be that deploying yourself into the cloud. It's taking too long. But if you don't take that approach of going flow first, rather than again, that sort of cost reduction. First, you have to think of the approach of customer centricity and you only focused on optimizing costs. Your costs will increase and your flow will slow down. And this is just one of these fascinating things. >>Whereas if you focus on getting closer to the customer and reducing your cycles out on getting value, your flow time from six months to two weeks or two, one week or two event, as we see with the tech giants, you actually can both lower your costs and get much more value for us to get that learning loop going. So I think I've, I've seen all these cloud deployments and one of the things happened that delivered almost no value because there was such big bottlenecks upfront in the process and actually the hosting and the AP testing was not even possible with all of those inefficiencies. So that's why going float us rather than costs when we started our project versus silky. >>I love that. And, and, and, and it, it begs repeating to that right within the subscription economy, you know, you're on the hook to deliver value every single month because they're paying you every single month. So if you're not on top of how you're delivering value, you're going to get sideways because it's not like they pay a big down payment and a small maintenance fee every month. But once you're in a subscription relationship, you know, you have to constantly be delivering value and upgrading that value because you're constantly taking money from the customer. So it's such a different kind of relationship than kind of the classic, you know, big bang with a maintenance agreement on the back end really important. Yeah. >>And I think in terms of industry shifts that that's, it that's, what's catalyzed. This industry shift is in this SAS and subscription economy. If you're not delivering more and more value to your customers, someone else's, and they're winning the business, not you. So, one way we know is to delight our customers with great user experience as well. That really is based on how many features you delivered or how much, how much, how many quality improvements or scalar performance improvements we delivered. So the problem is, and this is what the business manifesto, as well as the flow frame of touch on is if you can't measure how much value you deliver to a customer, what are you measuring? You just backed again, measuring costs, and that's not a measure of value. So we have to shift quickly away from measuring costs to measuring value, to survive. And in the subscription economy, >>We could go for days and days and days. I want to shift gears a little bit into data and, and a data driven decision making a data driven organization cause right day has been talked about for a long time, the huge big data meme with, with Hadoop over, over several years and, and data warehouses and data lakes and data oceans and data swamps. And you can go on and on and on. It's not that easy to do, right? And at the same time, the proliferation of data is growing exponentially. We're just around the corner from, from IOT and five G. So now the accumulation of data at machine scale, again, is this gonna overwhelm? And one of the really interesting principles, uh, that I wanted to call out and get your take right, is today's organizations generate more data than humans can process. So informed decisions must be augmented by machine learning and artificial intelligence. I wonder if you can, again, you've got some great historical perspective, um, reflect on how hard it is to get the right data, to get the data in the right context, and then to deliver it to the decision makers and then trust the decision makers to actually make the data and move that down. You know, it's kind of this democratization process into more and more people and more and more frontline jobs making more and more of these little decisions every day. >>Yeah. I definitely think the front parts of what you said are where the promises of big data have completely fallen on their face into the swamps as, as you mentioned, because if you don't have the data in the right format, you've cannot connect, collected that the right way you want it, that way, the right way you can't use human or machine learning on it effectively. And there've been the number of data where, how has this in a typical enterprise organization and the sheer investment is tremendous, but the amount of intelligence being extracted from those is, is, is a very big problem. So the key thing that I've noticed is that if you can model your value streams, so you actually understand how you're innovating, how you're measuring the delivery of value and how long that takes, what is your time to value through these metrics like full time? >>You can actually use both the intelligence that you've got around the table and push that down as well, as far as getting to the organization, but you can actually start using that those models to understand and find patterns and detect bottlenecks that might be surprising, right? Well, you can detect interesting bottlenecks when you shift to work from home. We detected all sorts of interesting bottlenecks in our own organization that were not intuitive to me that have to do with, you know, more senior people being overloaded and creating bottlenecks where they didn't exist. Whereas we thought we were actually an organization that was very good at working from home because of our open source roots. So the data is highly complex. Software value streams are extremely complicated. And the only way to really get the proper analysts and data is to model it properly and then to leverage these machine learning and AI techniques that we have. But that front part of what you said is where organizations are just extremely immature in what I've seen, where they've got data from all their tools, but not modeled in the right way. Right, right. >>Right. Well, all right. So before I let you go, you know, let's say you get a business leader. He, he buys in, he reads the manifesto, he signs on the dotted line and he says, Mick, how do I get started? I want to be more aligned with the, with the development teams. I know I'm in a very competitive space. We need to be putting out new software features and engage with our customers. I want to be more data-driven how do I get started? Well, you know, what's the biggest inhibitor for most people to get started and get some early wins, which we know is always the key to success in any kind of a new initiative. >>Right? So I think you can reach out to us through the website, uh, for the manifesto. But the key thing is just, it's definitely set up it's to get started and to get the key wins. So take a product value stream. That's mission critical if it'd be on your mobile and web experiences or part of your cloud modernization platform where your analytics pipeline, but take that and actually apply these principles to it and measure the end to end flow of value. Make sure you have a value metric that everyone is on the same page on, but the people on the development teams that people in leadership all the way up to the CEO, and one of the, where I encourage you to start is actually that end to end flow time, right? That is the number one metric. That is how you measure it, whether you're getting the benefit of your cloud modernization, that is the one metric that when the people I respect tremendously put into his cloud for CEOs, the metric, the one, the one way to measure innovation. So basically take these principles, deploy them on one product value stream measure, Antonin flow time, uh, and then you'll actually be well on your path to transforming and to applying the concepts of agile and dev ops all the way to, to the, to the way >>You're offering model. >>Well, Mick really great tips, really fun to catch up. I look forward to a time when we can actually sit across the table and, and get into this. Cause I just, I just love the perspective and, you know, you're very fortunate to have that foundational, that foundational base coming from Xerox park and they get, you know, it's, it's a very magical place with a magical history. So to, to incorporate that into, continue to spread that well, uh, you know, good for you through the book and through your company. So thanks for sharing your insight with us today. >>Thanks so much for having me, Jeff. Absolutely. >>All right. And go to the biz ops manifesto.org, read it, check it out. If you want to sign it, sign it. They'd love to have you do it. Stay with us for continuing coverage of the unveiling of the business manifesto on the cube. I'm Jeff. Rick. Thanks for watching. See you next time >>From around the globe. It's the cube with digital coverage, a biz ops manifesto unveiled brought to you by biz ops coalition. >>Hey, welcome back. You're ready. Jeff Frick here with the cube for our ongoing coverage of the big unveil. It's the biz ops manifesto manifesto unveil. And we're going to start that again from the top three And a Festo >>Five, four, three, two. >>Hey, welcome back everybody. Jeff Frick here with the cube come to you from our Palo Alto studios today for a big, big reveal. We're excited to be here. It's the biz ops manifesto unveiling a thing's been in the works for a while and we're excited to have our next guest. One of the, really the powers behind this whole effort. And he's joining us from Boston it's surge, Lucio, the vice president, and general manager enterprise software division at Broadcom surge. Great to see you. >>Hi, good to see you, Jeff. Glad to be here. >>Absolutely. So you've been in this business for a very long time. You've seen a lot of changes in technology. What is the biz ops manifesto? What is this coalition all about? Why do we need this today and in 2020? >>Yeah. So, so I've been in this business for close to 25 years, right? So about 20 years ago, the agile manifesto was created. And the goal of the agile manifesto was really to address the uncertainty around software development and the inability to predict the efforts to build software. And, uh, if you, if you roll that kind of 20 years later, and if you look at the current state of the industry of the product, the project management Institute, estimates that we're wasting about a million dollars, every 20 seconds in digital transformation initiatives that do not deliver on business results. In fact, we were recently served a third of the, a, a number of executives in partnership with Harvard >>Business review and 77% of those executives think that one of the key challenges that they have is really the collaboration between business and it, and that that's been kind of a case for, uh, almost 20 years now. Um, so the, the, the key challenge that we're faced with is really that we need a new approach. And many of the players in the industry, including ourselves have been using different terms, right? Some are being, are talking about value stream management. Some are talking about software delivery management. If you look at the site, reliability engineering movement, in many ways, it embodies a lot of these kind of concepts and principles. So we believed that it became really imperative for us to crystallize around, could have one concept. And so in many ways, the, a, the BizOps concept and the BizOps manifesto are bringing together a number of ideas, which has been emerging in the last five years or so, and, and defining the key values and principles to finally help these organizations truly transform and become digital businesses. And so the hope is that by joining our forces and defining public key principles and values, we can help the industry, uh, not just, uh, by, you know, providing them with support, but also tools and consulting that is required for them to truly achieve the kind of transformation that everybody's taking. >>Right. Right. So COVID now we're six months into it, approximately seven months into it. Um, a lot of pain, a lot of bad stuff still happening. We've got a ways to go, but one of the things that on the positive side, right, and you've seen all the memes and social media is, is a driver of digital transformation and a driver of change. Cause we had this light switch moment in the middle of March, and there was no more planning. There was no more conversation. You've suddenly got remote workforces, everybody's working from home and you got to go, right. So the reliance on these tools increases dramatically, but I'm curious, you know, kind of short of, of the beginnings of this effort in short of kind of COVID, which, you know, came along unexpectedly. I mean, what were those inhibitors because we've been making software for a very long time, right? The software development community has, has adopted kind of rapid change and, and iterative, uh, delivery and, and sprints, what was holding back the connection with the business side to make sure that those investments were properly aligned with outcomes. >>Well, so, so you have to understand that it is, is kind of a its own silos. And traditionally it has been treated as a cost center within large organizations and not as a value center. And so as a result, kind of a, the traditional dynamic between it and the business is basically one of a kind of supplier up to kind of a business. Um, and you know, if you go back to, uh, I think you'll unmask a few years ago, um, basically at this concept of the machines to build the machines and you went as far as saying that, uh, the, the machines or the production line is actually the product. So, uh, meaning that the core of the innovation is really about, uh, building, could it be engine to deliver on the value? And so in many ways, you know, we, we have missed on this shift from, um, kind of it becoming this kind of value center within the enterprises and end. >>He talks about culture. Now, culture is a, is a sum total of behaviors. And the reality is that if you look at it, especially in the last decade, uh, we've agile with dev ops with, um, I bring infrastructures, uh, it's, it's way more volatile today than it was 10 years ago. And so the, when you start to look at the velocity of the data, the volume of data, the variety of data to analyze the system, um, it's, it's very challenging for it to actually even understand and optimize its own processes, let alone, um, to actually include business as sort of an integral part of kind of a delivery chain. And so it's both kind of a combination of, of culture, um, which is required, uh, as well as tools, right? To be able to start to bring together all these data together, and then given the volume of variety of philosophy of the data. Uh, we have to apply some core technologies, which have only really, truly emerged in the last five to 10 years around machine learning and analytics. And so it's really kind of a combination of those freaks, which are coming together today, truly out organizations kind of get to the next level. Right, >>Right. So let's talk about the manifesto. Let's talk about, uh, the coalition, uh, the BizOps coalition. I just liked that you put down these really simple, you know, kind of straightforward core values. You guys have four core values that you're highlighting, you know, business outcomes, over individual projects and outputs, trust, and collaboration, oversight, load teams, and organizations, data driven decisions, what you just talked about, uh, you know, over opinions and judgment and learned, respond and pivot. I mean, surgery sounds like pretty basic stuff, right? I mean, aren't, isn't everyone working to these values already. And I think he touched on it on culture, right? Trust and collaboration, data driven decisions. I mean, these are fundamental ways that people must run their business today, or the person that's across the street, that's doing it. It's going to knock them out right off their block. >>Yeah. So that's very true. But, uh, so I'll, I'll mention an hour survey. We did, uh, I think about six months ago and it was in partnership with, uh, with, uh, an industry analyst and we serve at a, again, a number of it executives to understand only we're tracking business outcomes. I'm going to get the software executives, it executives we're tracking business outcomes. And the, there were less than 15% of these executives were actually tracking the outcomes of the software delivery. And you see that every day. Right? So in my own teams, for instance, we've been adopting a lot of these core principles in the last year or so, and we've uncovered that 16% of our resources were basically aligned around initiatives, which are not strategic for us. Um, I take another example, for instance, one of our customers in the, uh, in the airline industry and Harvard, for instance, that a number of, uh, um, that they had software issues that led to people searching for flights and not returning any kind of availability. >>And yet, um, you know, the it teams, whether it's operation software environments were completely oblivious to that because they were completely blindsided to it. And so the connectivity between kind of the inwards metrics that RT is using, whether it's database time, cycle time, or whatever metric we use in it are typically completely divorced from the business metrics. And so at its core, it's really about starting to align the business metrics with the, the, the software delivery chain, right? This, uh, the system, which is really a core differentiator for these organizations. It's about connecting those two things and starting to, um, infuse some of the agile culture and principles. Um, that's emerged from the software side into the business side. Um, of course the lean movement and other movements have started to change some of these dynamics on the business side. And so I think this, this is the moment where we are starting to see kind of the imperative to transform. Now, you know, Covina obviously has been a key driver for that. The, um, the technology is right to start to be able to weave data together and really kind of, uh, also the cultural shifts, uh, Prue agile through dev ops through, uh, the SRE movement, uh frulein um, business transformation, all these things are coming together and that are really creating kind of the conditions for the BizOps manifestor to exist, >>Uh, Clayton Christianson, great, uh, Harvard professor innovator's dilemma might steal my all time. Favorite business books, you know, talks about how difficult it is for incumbents to react to, to disruptive change, right? Because they're always working on incremental change cause that's what their customers are asking for. And there's a good ROI when you talk about, you know, companies not measuring the right thing. I mean, clearly it has some portion of their budget that has to go to keeping the lights on, right. That that's always the case, but hopefully that's an ever decreasing percentage of their total activity. So, you know, what should people be measuring? I mean, what are kind of the new metrics, um, in, in biz ops that drive people to be looking at the right things, measuring the right things and subsequently making the right decisions, investment decisions on whether they should do, you know, move project a along or project B. >>So there, there are only two things, right? So, so I think what you're talking about is portfolio management, investment management, right. And, um, which, which is a key challenge, right? Um, in my own experience, right? Uh, driving strategy or a large scale kind of software organization for years, um, it's very difficult to even get kind of a base data as to who is doing what, uh, um, I mean, some of our largest customers we're engaged with right now are simply trying to get a very simple answer, which is how many people do I have and that specific initiative at any point in time and just tracking that information is extremely difficult. So, and, and again, back to a product project management Institute, um, they're, they've estimated that on average, it organizations have anywhere between 10 to 20% of their resources focused on initiatives, which are not strategically aligned. >>So that's one dimension on portfolio management. I think the key aspect though, that we are really keen on is really around kind of the alignment of a business metrics to the it metrics. Um, so I'll use kind of two simple examples, right? And my background is around quality. And so I've always believed that fitness for purpose is really kind of a key, um, uh, philosophy if you will. And so if you start to think about quality as fitness for purpose, you start to look at it from a customer point of view, right. And fitness for purpose for core banking application or mobile application are different, right? So the definition of a business value that you're trying to achieve is different. Um, and so the, and yet, if you look at our, it, operations are operating, they were using kind of a same type of, uh, kind of inward metrics, uh, like a database of time or a cycle time, or what is my point of velocity, right? >>And, uh, and so the challenge really is this inward facing metrics that it is using, which are divorced from ultimately the outcome. And so, you know, if I'm, if I'm trying to build a poor banking application, my core metric is likely going to be uptime, right? If I'm trying to build a mobile application or maybe your social mobile app, it's probably going to be engagement. And so what you want is for everybody across it, to look at these metric, and what's hard, the metrics within the software delivery chain, which ultimately contribute to that business metric and some cases cycle time may be completely irrelevant, right? Again, my core banking app, maybe I don't care about cycle time. And so it's really about aligning those metrics and be able to start to differentiate, um, the key challenges you mentioned, uh, around the, the, um, uh, around the disruption that we see is, or the investors is the dilemma now is really around the fact that many it organizations are essentially applying the same approaches of, for innovation, right, for basically scrap work, then they would apply to kind of over more traditional projects. And so, you know, there's been a lot of talk about two-speed it, and yes, it exists, but in reality are really organizations, um, truly differentiating, um, all of the operate, their, their projects and products based on the outcomes that they're trying to achieve. And this is really where BizOps is trying to affect. >>I love that, you know, again, it doesn't seem like brain surgery, but focus on the outcomes, right. And it's horses for courses, as you said, this project, you know, what you're measuring and how you define success, isn't necessarily the same as, as on this other project. So let's talk about some of the principles we've talked about the values, but, you know, I think it's interesting that, that, that the BizOps coalition, you know, just basically took the time to write these things down and they don't seem all that, uh, super insightful, but I guess you just gotta get them down and have them on paper and have them in front of your face. But I want to talk about, you know, one of the key ones, which you just talked about, which is changing requirements, right. And working in a dynamic situation, which is really what's driven, you know, this, the software to change in software development, because, you know, if you're in a game app and your competitor comes out with a new blue sword, you've got to come out with a new blue sword. >>So whether you had that on your Kanban wall or not. So it's, it's really this embracing of the speed of change and, and, and, and making that, you know, the rule, not the exception. I think that's a phenomenal one. And the other one you talked about is data, right? And that today's organizations generate more data than humans can process. So informed decisions must be generated by machine learning and AI, and, you know, in the, the big data thing with Hadoop, you know, started years ago, but we are seeing more and more that people are finally figuring it out, that it's not just big data, and it's not even generic machine learning or artificial intelligence, but it's applying those particular data sets and that particular types of algorithms to a specific problem, to your point, to try to actually reach an objective, whether that's, you know, increasing the, your average ticket or, you know, increasing your checkout rate with, with, with shopping carts that don't get left behind and these types of things. So it's a really different way to think about the world in the good old days, probably when you got started, when we had big, giant, you know, MRDs and PRDs and sat down and coded for two years and came out with a product release and hopefully not too many patches subsequently to that. >>It's interesting. Right. Um, again, back to one of these surveys that we did with, uh, with about 600, the ITA executives, and, uh, and, and we, we purposely designed those questions to be pretty open. Um, and, and one of them was really role requirements and, uh, and it was really a wrong kind of what do you, what is the best approach? What is your preferred approach towards requirements? And if I remember correctly over 80% of the it executives set that the best approach they'll prefer to approach is for requirements to be completely defined before software development starts. Let me pause there where 20 years after the agile manifesto, right? And for 80% of these idea executives to basically claim that the best approach is for requirements to be fully baked before salt, before software development starts, basically shows that we still have a very major issue. >>And again, our hypothesis in working with many organizations is that the key challenge is really the boundary between business and it, which is still very much contract based. If you look at the business side, they basically are expecting for it deliver on time on budget, right. But what is the incentive for it to actually delivering all the business outcomes, right? How often is it measured on the business outcomes and not on an SLA or on a budget type criteria. And so that, that's really the fundamental shift that we need to, we really need to drive up as an industry. Um, and you know, we, we talk about kind of this, this imperative for organizations to operate that's one, and back to the innovator's dilemma. The key difference between these larger organization is, is really kind of a, if you look at the amount of capital investment that they can put into pretty much anything, why are they losing compared to, um, you know, startups? What, why is it that, uh, more than 40% of, uh, personal loans today or issued not by your traditional brick and mortar banks, but by, um, startups? Well, the reason, yes, it's the traditional culture of doing incremental changes and not disrupting ourselves, which Christiansen covered at length, but it's also the inability to really fundamentally change kind of a dynamic picture. We can business it and, and, and partner right. To, to deliver on a specific business outcome. Right. >>I love that. That's a great, that's a great summary. And in fact, getting ready for this interview, I saw you mentioning another thing where, you know, the, the problem with the agile development is that you're actually now getting more silos because you have all these autonomous people working, you know, kind of independently. So it's even a harder challenge for, for the business leaders to, to, to, as you said, to know, what's actually going on, but, but certainly I w I want to close, um, and talk about the coalition. Um, so clearly these are all great concepts. These are concepts you want to apply to your business every day. Why the coalition, why, you know, take these concepts out to a broader audience, including your, your competition and, and the broader industry to say, Hey, we, as a group need to put a stamp of approval on these concepts, values, these principles. >>So, first I think we, we want, um, everybody to realize that we are all talking about the same things, the same concepts. I think we were all from our own different vantage point, realizing that, um, things after change, and again, back to, you know, whether it's value stream management or site reliability engineering, or biz ops, we're all kind of using slightly different languages. Um, and so I think one of the important aspects of BizOps is for us, all of us, whether we're talking about, you know, consulting agile transformation experts, uh, whether we're talking about vendors, right, provides kind of tools and technologies, or these large enterprises to transform for all of us to basically have kind of a reference that lets us speak around kind of, um, in a much more consistent way. The second aspect is for, to me is for, um, these concepts to start to be embraced, not just by us or trying, or, you know, vendors, um, system integrators, consulting firms, educators, thought leaders, but also for some of our old customers to start to become evangelists of their own in the industry. >>So we, our, our objective with the coalition needs to be pretty, pretty broad. Um, and our hope is by, by starting to basically educate, um, our, our joint customers or partners, that we can start to really foster these behaviors and start to really change, uh, some of dynamics. So we're very pleased at if you look at, uh, some of the companies which have joined the, the, the, the manifesto. Um, so we have vendors and suggest desktop or advance, or, um, uh, PagerDuty for instance, or even planned view, uh, one of my direct competitors, um, but also thought leaders like Tom Davenport or, uh, or cap Gemini or, um, um, smaller firms like, uh, business agility, institutes, or agility elf. Um, and so our, our goal really is to start to bring together, uh, thought leaders, people who have been LP, larger organizations do digital transformation vendors, were providing the technologies that many of these organizations use to deliver on these digital preservation and for all of us to start to provide the kind of, uh, education support and tools that the industry needs. Yeah, >>That's great surge. And, uh, you know, congratulations to you and the team. I know this has been going on for a while, putting all this together, getting people to sign onto the manifesto, putting the coalition together, and finally today getting to unveil it to the world in a little bit more of a public, uh, opportunity. So again, you know, really good values, really simple principles, something that, that, uh, shouldn't have to be written down, but it's nice cause it is, and now you can print it out and stick it on your wall. So thank you for, uh, for sharing this story. And again, congrats to you and the team. Thank you. Appreciate it. My pleasure. Alrighty, surge. If you want to learn more about the biz ops, Manifesta go to biz ops manifesto.org, read it, and you can sign it and you can stay here for more coverage. I'm the cube of the biz ops manifesto unveiled. Thanks for watching. See you next time >>From around the globe. It's the cube with digital coverage of this ops manifesto unveiled and brought to you by >>This obstacle volition. Hey, welcome back, everybody Jeffrey here with the cube. Welcome back to our ongoing coverage of the biz ops manifesto unveiling. It's been in the works for awhile, but today's the day that it actually kind of come out to the, to the public. And we're excited to have a real industry luminary here to talk about what's going on, why this is important and share his perspective. And we're happy to have from Cape Cod, I believe is Tom Davenport. He's a distinguished author and professor at Babson college. We could go on, he's got a lot of great titles and, and really illuminary in the area of big data and analytics Thomas. Great to see you. >>Thanks Jeff. Happy to be here with you. >>Great. So let's just jump into it, you know, and getting ready for this. I came across your LinkedIn posts. I think you did earlier this summer in June and right off the bat, the first sentence just grabbed my attention. I'm always interested in new attempts to address longterm issues, uh, in how technology works within businesses, biz ops. What did you see in biz ops, uh, that, that kind of addresses one of these really big longterm problems? >>Well, yeah, but the longterm problem is that we've had a poor connection between business people and it people between business objectives and the, it solutions that address them. This has been going on, I think since the beginning of information technology and sadly it hasn't gone away. And so biz ops is a new attempt to deal with that issue with a, you know, a new framework, eventually a broad set of solutions that increase the likelihood that will actually solve a business problem with an it capability. >>Right. You know, it's interesting to compare it with like dev ops, which I think a lot of people are probably familiar with, which was, you know, built around, uh, agile software development and a theory that we want to embrace change that that changes. Okay. And we want to be able to iterate quickly and incorporate that. And that's been happening in the software world for, for 20 plus years. What's taken so long to get that to the business side, because as the pace of change has changed on the software side, you know, that's a strategic issue in terms of execution, the business side that they need now to change priorities. And, you know, there's no PRDs and MRDs and big, giant strategic plans that sit on the shelf for five years. That's just not the way business works anymore. It took a long time to get here. >>Yeah, it did. And, you know, there had been previous attempts to make a better connection between business and it, there was the so called strategic alignment framework that a couple of friends of mine from Boston university developed, I think more than 20 years ago, but you know, now we have better technology for creating that linkage. And the, you know, the idea of kind of ops oriented frameworks is pretty pervasive now. So I think it's time for another serious attempt at it. >>And do you think doing it this way, right. With the, with the BizOps coalition, you know, getting a collection of, of, of kind of likeminded individuals and companies together, and actually even having a manifesto, which we're making this declarative statement of, of principles and values, you think that's what it takes to kind of drive this kind of beyond the experiment and actually, you know, get it done and really start to see some results in, in, uh, in production in the field. >>I think certainly no one vendor organization can pull this off single handedly. It does require a number of organizations collaborating and working together. So I think our coalition is a good idea and a manifesto is just a good way to kind of lay out what you see as the key principles of the idea. And that makes it much easier for everybody to understand and act on. >>I, I think it's just, it's really interesting having, you know, having them written down on paper and having it just be so clearly articulated both in terms of the, of the values as well as, as the, uh, the principles and the values, you know, business outcomes matter trust and collaboration, data-driven decisions, which is the number three of four, and then learn, respond and pivot. It doesn't seem like those should have to be spelled out so clearly, but, but obviously it helps to have them there. You can stick them on the wall and kind of remember what your priorities are, but you're the data guy. You're the analytics guy, uh, and a big piece of this is data and analytics and moving to data driven decisions. And principle number seven says, you know, today's organizations generate more data than humans can process and informed decisions can be augmented by machine learning and artificial intelligence right up your alley. You know, you've talked a number of times on kind of the mini stages of analytics. Um, and how has that evolved over over time, you know, as you think of analytics and machine learning, driving decisions beyond supporting decisions, but actually starting to make decisions in machine time. What's that, what's that thing for you? What does that make you, you know, start to think, wow, this is this going to be pretty significant. >>Yeah. Well, you know, this has been a longterm interest of mine. Um, the last generation of AI, I was very interested in expert systems. And then, um, I think, uh, more than 10 years ago, I wrote an article about automated decision-making using what was available then, which was rule-based approaches. Um, but you know, this addresses an issue that we've always had with analytics and AI. Um, you know, we, we tended to refer to those things as providing decision support, but the problem is that if the decision maker didn't want their support, didn't want to use them in order to make a decision, they didn't provide any value. And so the nice thing about automating decisions, um, with now contemporary AI tools is that we can ensure that data and analytics get brought into the decision without any possible disconnection. Now, I think humans still have something to add here, and we often will need to examine how that decision is being made and maybe even have the ability to override it. But in general, I think at least for, you know, repetitive tactical decisions, um, involving a lot of data, we want most of those, I think to be at least, um, recommended if not totally made by an algorithm or an AI based system. And that I believe would add to, um, the quality and the precision and the accuracy of decisions and in most organizations, >>No, I think, I think you just answered my next question before I, before I asked it, you know, we had dr. Robert Gates on the former secretary of defense on a few years back, and we were talking about machines and machines making decisions. And he said at that time, you know, the only weapon systems, uh, that actually had an automated trigger on it were on the North Korea and South Korea border. Um, everything else, as you said, had to go through a sub person before the final decision was made. And my question is, you know, what are kind of the attributes of the decision that enable us to more easily automated? And then how do you see that kind of morphing over time, both as the data to support that as well as our comfort level, um, enables us to turn more and more actual decisions over to the machine? >>Well, yeah, as I suggested we need, um, data and the data that we have to kind of train our models has to be high quality and current, and we need to know the outcomes of that data. You know, um, most machine learning models, at least in business are supervised. And that means we need to have labeled outcomes in the, in the training data. But I, you know, um, the pandemic that we're living through is a good illustration of the fact that, that the data also have to be reflective of current reality. And, you know, one of the things that we're finding out quite frequently these days is that, um, the data that we have do not reflect, you know, what it's like to do business in a pandemic. Um, I wrote a little piece about this recently with Jeff cam at wake forest university, we call it data science quarantined, and we interviewed with somebody who said, you know, it's amazing what eight weeks of zeros will do to your demand forecast. We just don't really know what happens in a pandemic. Um, our models maybe have to be put on the shelf for a little while and until we can develop some new ones or we can get some other guidelines into making decisions. So I think that's one of the key things with automated decision making. We have to make sure that the data from the past and that's all we have of course, is a good guide to, you know, what's happening in the present and the future as far as we understand it. >>Yeah. I used to joke when we started this calendar year 2020, it was finally the year that we know everything with the benefit of hindsight, but I turned down 20, 20 a year. We found out we actually know nothing and everything and thought we knew, but I want to, I want to follow up on that because you know, it did suddenly change everything, right? We've got this light switch moment. Everybody's working from home now we're many, many months into it, and it's going to continue for a while. I saw your interview with Bernard Marr and you had a really interesting comment that now we have to deal with this change. We don't have a lot of data and you talked about hold fold or double down. And, and I can't think of a more, you know, kind of appropriate metaphor for driving the value of the biz ops when now your whole portfolio strategy, um, these to really be questioned and, and, you know, you have to be really, uh, well, uh, executing on what you are, holding, what you're folding and what you're doubling down with this completely new environment. >>Well, yeah, and I hope I did this in the interview. I would like to say that I came up with that term, but it actually came from a friend of mine. Who's a senior executive at Genpact. And, um, I, um, used it mostly to talk about AI and AI applications, but I think you could, you could use it much more broadly to talk about your entire sort of portfolio of digital projects. You need to think about, well, um, given some constraints on resources and a difficult economy for a while, which of our projects do we want to keep going on pretty much the way we were and which ones are not that necessary anymore? You see a lot of that in AI, because we had so many pilots, somebody told me, you know, we've got more pilots around here than O'Hare airport and, and AI. Um, and then, but the ones that involve doubled down, they're even more important to you. They are, you know, a lot of organizations have found this out, um, in the pandemic on digital projects, it's more and more important for customers to be able to interact with you, um, digitally. And so you certainly wouldn't want to cancel those projects or put them on hold. So you double down on them and get them done faster and better. Right, >>Right. Uh, another, another thing that came up in my research that, that you quoted, um, was, was from Jeff Bezos, talking about the great bulk of what we do is quietly, but meaningfully improving core operations. You know, I think that is so core to this concept of not AI and machine learning and kind of the general sense, which, which gets way too much buzz, but really applied right. Applied to a specific problem. And that's where you start to see the value. And, you know, the, the BizOps, uh, manifesto is, is, is calling it out in this particular process. But I'd love to get your perspective as you know, you speak generally about this topic all the time, but how people should really be thinking about where are the applications where I can apply this technology to get direct business value. >>Yeah, well, you know, even talking about automated decisions, um, uh, the kind of once in a lifetime decisions, uh, the ones that, um, ag Lafley, the former CEO of Procter and gamble used to call the big swing decisions. You only get a few of those. He said in your tenure as CEO, those are probably not going to be the ones that you're automating in part because, um, you don't have much data about them. You're only making them a few times and in part, because, um, they really require that big picture thinking and the ability to kind of anticipate the future, that the best human decision makers, um, have. Um, but, um, in general, I think where they, I, the projects that are working well are, you know, what I call the low hanging fruit ones, the, some people even report to it referred to it as boring AI. >>So, you know, sucking data out of a contract in order to compare it to a bill of lading for what arrived at your supply chain companies can save or make a lot of money with that kind of comparison. It's not the most exciting thing, but AI, as you suggested is really good at those narrow kinds of tasks. It's not so good at the, at the really big moonshots, like curing cancer or, you know, figuring out well what's the best stock or bond under all or even autonomous vehicles. Um, we, we made some great progress in that area, but everybody seems to agree that they're not going to be perfect for quite a while, and we really don't want to be driving around on, um, and then very much unless they're, you know, good and all kinds of weather and with all kinds of pedestrian traffic and you know, that sort of thing, right? >>That's funny you bring up contract management. I had a buddy years ago, they had a startup around contract management and I've like, and this was way before we had the compute power today and cloud proliferation. I said, you know, how can you possibly build software around contract management? It's language, it's legal, ease. It's very specific. And he's like, Jeff, we just need to know where's the contract. And when does it expire? And who's the signatory. And he built a business on those, you know, very simple little facts that weren't being covered because their contracts are in people's drawers and files and homes. And Lord only knows. So it's really interesting, as you said, these kind of low hanging fruit opportunities where you can extract a lot of business value without trying to, you know, boil the ocean. >>Yeah. I mean, if you're Amazon, um, uh, Jeff Bezos thinks it's important to have some kind of billion dollar project. And he even says it's important to have a billion dollar failure or two every year. But I think most organizations probably are better off being a little less aggressive and, you know, sticking to, um, what AI has been doing for a long time, which is, you know, making smarter decisions based on, based on data. >>Right? So Tom, I want to shift gears one more time before, before we let you go on, on kind of a new topic for you, not really new, but you know, not, not a, the vast majority of, of your publications and that's the new way to work, you know, as, as the pandemic hit in mid March, right. And we had this light switch moment, everybody had to work from home and it was, you know, kind of crisis and get everybody set up. Well, you know, now we're five months, six months, seven months. A number of companies have said that people are not going to be going back to work for a while. And so we're going to continue on this for a while. And then even when it's not what it is now, it's not going to be what it was before. So, you know, I wonder, and I know you, you, uh, you teased, you're working on a new book, you know, some of your thoughts on, you know, kind of this new way to work and, and, and the human factors in this new, this new kind of reality that we're kind of evolving into, I guess. >>Yeah. I missed was an interest of mine. I think, um, back in the nineties, I wrote an article called, um, a coauthored, an article called two cheers for the virtual office. And, you know, it was just starting to emerge. Then some people were very excited about it. Some people were skeptical and, uh, we said two cheers rather than three cheers because clearly there's some shortcomings. And, you know, I keep seeing these pop up. It's great that we can work from our homes. It's great that we can, most of what we need to do with a digital interface, but, um, you know, things like innovation and creativity, and certainly, um, uh, a good, um, happy social life kind of requires some face to face contact every now and then. And so I, you know, I think we'll go back to an environment where there is some of that. >>Um, we'll have, um, times when people convene in one place so they can get to know each other face to face and learn from each other that way. And most of the time, I think it's a huge waste of people's time to commute into the office every day and to jump on airplanes, to, to, um, give every little, um, uh, sales call or give every little presentation. Uh, we just have to really narrow down what are the circumstances where face to face contact really matters. And when can we get by with digital? You know, I think one of the things in my current work I'm finding is that even when you have AI based decision making, you really need a good platform in which that all takes place. So in addition to these virtual platforms, we need to develop platforms that kind of structure the workflow for us and tell us what we should be doing next, then make automated decisions when necessary. And I think that ultimately is a big part of biz ops as well. It's not just the intelligence of an AI system, but it's the flow of work that kind of keeps things moving smoothly throughout your organization. >>I think such, such a huge opportunity as you just said, cause I forget the stats on how often we're interrupted with notifications between email texts, Slack, a sauna, Salesforce, the list goes on and on. So, you know, to put an AI layer between the person and all these systems that are begging for attention, you've written a book on the attention economy, which is a whole nother topic, we'll say for another day, you know, it, it really begs, it really begs for some assistance because you know, you just can't get him picked, you know, every two minutes and really get quality work done. It's just not, it's just not realistic. And you know what? I don't think that's a feature that we're looking for. >>I agree. Totally >>Tom. Well, thank you so much for your time. Really enjoyed the conversation. I got to dig into the library. It's very long. So I might start at the attention economy. I haven't read that one. And to me, I think that's the fascinating thing in which we're living. So thank you for your time and, uh, great to see you. >>My pleasure, Jeff. Great to be here. >>All right. He's Tom I'm Jeff. You are watching the continuing coverage of the biz ops manifesto and Vail. Thanks for watching the cube. We'll see you next time.

>>from around the globe. It's the Cube with digital coverage of biz ops Manifesto unveiled. Brought to you by Biz Ops Coalition >>Hey, welcome back Variety. Jeff Freak here with the Cube were Palo Alto studios. And we like to welcome you back to our continuing coverage of biz. Opps manifesto. Unveil. Exciting day to really, uh, kind of bring this out into public. There's been a little bit of conversation, but today is really the official unveiling, and we're excited to have our next guest to share a little bit more information on it. He's Patrick Tickle. He's a chief product officer for plan view. Patrick, great to see you. Yeah, it's great to be here. Thanks for the invite. So why the biz? Opps manifesto? Why the bizarre coalition? Now, when you guys have been added, it's relatively mature marketplace. Business is good. What was missing? Why? Why this? Why this coalition? >>Yeah, so you know, again, Why? Why is bizarre is important. And why is this something I'm you know, I'm so excited about, but I think companies as well, right? Well, no. In some ways or another, this is a topic that I've been talking to you know the market in our customers about for a long time. And it's, you know, I really applaud, you know, this whole movement, right? And, um, it resonates with me because I think one of the fundamental flaws, frankly, of the way we have talked about technology and business literally for decades has been this idea of alignment. Those who know me, I occasionally get off on this little rant about the word alignment. Right? But to me, the word alignment is actually indicative of the of the of the flaw in a lot of our organizations. And biz ops is really, I think, now, trying to catalyze and expose that flaw, right? Because, you know, I I always say that, you know, you know, alignment implies silos right the instantaneously with soon as you say, there's alignment. There's there's obviously somebody who's got a direction and other people that have tow line up and that that kind of siloed, uh, nature of organizations. And then, frankly, the passive nature of I think so many technology organizations like look, the business has the strategy. You guys need to align right and and, you know, is a product leader right that's what I've been my whole career, right? I can tell you that I never sit around. I almost never used the word alignment, right. I mean, whether you know, I never sit down and say, you know, the product management team has to get aligned with death, right? Or the Dev team has to get aligned with the delivery and ops teams. I mean, what I say is, are we on strategy? Right? Like we have a strategy, a zey full end to end value stream, right, and that there's no silos, and I mean, look, every on any given day, we got to get better, right? But the context, the context we operate is not about alignment, right? It's about being on strategy. And I think I've talked to customers a lot about that. But when I first read the manifesto, I was like, Oh, you know, this is exactly this. Is breaking down maybe trying to eliminate the word alignment, you know, from a lot of our organizations, because we literally start thinking about one strategy and how we go from strategy to delivery and have it be our strategy, not someone else's, that we're all aligning to it. And it's a great way to catalyze. You know, that conversation that I've It's been in my mind for years, to be honest, >>right? So, so much to unpack there. One of the things, obviously, uh, stealing a lot from from Dev Ops and the Dev Ops manifesto from 20 years ago. And and as I looked through some of the principles and I looked through some of the values which are, you know, really nicely laid out here, you know, satisfied customers do continues delivery, uh, measure output against riel results. Um, the ones that that jumps out that was really about, you know, change change, right requirements should change frequently. They do change frequently, but I'm curious to get your take from A from a software development point. It's easy to kind of understand, right? We're making this widget, and our competitors made a widget plus X, and now we need to change our plans and make sure that the plus X gets added to the plan. Maybe it wasn't in the plan. You talked a lot about product strategy. So in this kind of continuous delivery world, how does that meld with? I'm actually trying to set a strategy which implies a direction for a little bit further out on the horizon. And to stay on that while at the same time you're kind of doing this real time, continual adjustments because you're not working off a giant PRD or M R d anymore. Yeah, >>totally. Yeah. You know, one of the terms you know, that we use internally a lot on even with my customers, our customers is we talked about this idea rewiring right, and I think you know. So it's kind of an analogy for transformation, and I think a lot of us have to rewire the way we think about things right. And I think it planned view where we have a lot of customers who live in that you know who operationalized that traditional ppm world right and are shifting toe agile and transforming that rewire super important and and to your point right, it's You've just you've got to embrace this idea of, you know, just iterative getting better every day and iterating iterating iterating as opposed to building annual plans. Or, you know, I get customers occasionally. Who asked me for two or three year roadmap right and I literally looked at them and I go There is No There is no scenario where I could build a two or three year roadmap. Right? You you think you want that? But that's not That's not the way we run, right. And I will tell you the biggest thing that for us, you know, that I think is matched the planning. You know, impedance is a word I like to use a lot. So the thing that we've like that we've done from a planning perspective, I think is matched impedance to continuous delivery is instituting the whole program. Implement the program in current planning capabilities and methodologies. Um, in the scaled, agile world, right. And over the last 18 months to two years, we really have now, you know, instrumented our company across three value streams. You know, we do Corley p I program increment 10 week planning, you know, And that becomes that becomes the terra firma of how we plan, right? And it's what are we doing for the next 10 weeks? And we iterated within those 10 weeks. But we also know that 10 weeks from now we're gonna we're gonna just generate again, right and that shifting of that planning model, you know, to being is cross functional. Is that as that big room planning kind of model is, um and also, you know, on that shorter increments. Um, when you get those two things in place also, the impedance really starts to match up with continuous delivery, and it changes. It changes the way you plan. And it changes the way you work, right? >>The other thing. Right. So obviously a lot of these things are kind of process driven both within the values as well as the principles. But there's a whole lot really about culture, and I just wanna highlight a couple of the values, right? We already talked about business outcomes, um, trust and collaboration, a data driven decisions and then learned responded Pivot, right. A lot of those air cultural as much as they are processed. So again, is that the Is that the need to really kind of just put them down on paper? And you know, e can't help but think of, you know, the hammer and up the thing in the Lutheran church with it with their manifesto. Is it just good to get it down? on paper, because when you read these things, you're like, Well, of course we should trust people. And, of course, we need an environment of collaboration. And, of course, we want data driven decisions. But as we all know, saying it and living it are two very, very different things. >>Yeah, good question. I mean, I think there's a lot of ways to bring that to life. You're right. And just hanging up. You know, I think we've all been through the hanging up posters around your office, which these days, right, Unless you're gonna hang a poster and everybody's home office, right, you can't even you can't even fake it that you think that might work, right? So, um, you know, you really, I think we have attacked that in a variety of ways, right? And you definitely have to, you know, you've got to make the shift to a team centric culture, right? Empowered teams. You know, that's a big deal, right? You know, a lot of a lot of the people that you know, we lived in a world of unquote where we lived in a deep resource management world for a long, long time and write a lot of our customers still do that, but, you know, kind of moving to that team centric world is eyes really important and court of the trust. I think training is super important, right? We've, you know, we've internally, right. We've trained hundreds employees over the last year and a half on the fundamentals. Really of safe, right? Not necessarily. You know, we've had we've had teams delivering and scrum and continuous delivery for, you know, for years. But this scaling aspect of it eyes where we've done a lot of training investment on Ben. You know, I think leadership has to be bought in, right, you know? And so we p I plan, you know, myself and camera and the other members are leadership, you know, we're in p I planning, you know, for for four days, right? I mean, you've gotta walk the walk, you know, from top to bottom. And you've got a train on the context, right? And then you and then and then once you get through a few cycles where you've done a pivot, right or you brought a new team in and it just works, it becomes kind of this virtuous circle where people go. Man, this really works so much better than what we used to dio, >>right? Right. Theater Really key principle to this whole thing is is aligning the business leaders and the business prioritization s so that you can get to good outcomes with the development and and the delivery, right? And we know again and kind of classic dev ops to get the Dev and the production people together so they can, you know, quickly ship code that works. Um, but adding the business person on there really puts puts a little extra responsibility that they they understand the value of a particular feature, a particular priority. Uh, they can make the trade offs and that they kind of understand the effort involved too. So, you know, bringing them into this continuous again kind of this continuous development process, Um, to make sure that things were better aligned and really better Prioritize, because ultimately, you know, we don't live in an infinite resource is situation and and people got to make tradeoffs. They gotta make decisions, is toe what goes and what doesn't go on for everything that goes right. I always say you pick one thing Okay, that's 99 other things that couldn't go. So it's really important to have you know, this you said alignment of the business priorities as well as you know, the execution within. Within the development. >>Yeah, I think that, you know, You know, I think it was probably close to two years ago, Forrester started talking about the age of the customer, right? That was like their big theme at the time, right? And I think to me what that the age of the customer actually translates to. And Mick, Mick and I are both big fans of this whole idea of the project. The product shift mixed book, you know, is a great piece on your talking assed part of the manifesto is one of the authors as well. But this shift from project to product, right? Like the age of the customer, in my opinion, the mhm, the embodiment that is the shift to a product mentality, right? And? And the product mentality, in my opinion, is what brings the business and technology teams together, right? Once, once you're focused on a customer experience is delivered through a product or service. That's when I That's when I start to go. The alignment problem goes away. Right? Because if you look at software companies, right, I mean, we run product management models with software development teams, customer success teams, right? That, you know, the software component of these products that people are building is obviously becoming bigger and bigger, you know, and in many ways, right. More more organizations, air trying to model themselves over as operationally like software companies, Right? They obviously have lots of other components in their business than just software. But I think that whole model of customer experience equaling product and then the software component of product the product is the essence of what changes that alignment equation and brings business and teams together. Because also, everyone knows what the customers experiencing, right, And that that that makes a lot of things very clear very quick, >>right? I'm just curious how far along this was as a process before, before Cove, it hit right, because serendipitous. Whatever. Right? But the sudden, you know, light switch moment. Everybody had to go work from home in March 15th. Compared to now, we're in October on. This is gonna be going on for a while and it is a new normal and whatever that whatever is gonna look like a year from now or two years from now is T v D. You know, had you guys already started on this journey because again, to sit down and actually declare this coalition and declare this manifesto is a lot different than just trying to do better within your own organization. Yeah, >>So we had started, you know, we definitely had started independently. You know, some some. You know, I think people in the community know that we we came together with a company called Link It Handful years ago. And I give John Terry, actually one of the founders link it immense credit for, you know, kind of spearheading our cultural change. And not and not because of we're just gonna be, you know, bringing agile solutions to our customers. But because, you know, he believed that it was gonna be a fundamentally better way for us to work, right. And we kind of, you know, and we started with John and built, you know, centric circles, momentum. And we've gotten to the place where now it's just part of who we are, but but I do think that you know, Cove it has. You know, I think pre Cove in a lot of companies, you know, would would adopt, you know, the would adopt digital slash agile transformation. Um, traditional industries may have done it as a reaction to disruption. Right, You know, And in many cases, though, the disruption to these traditional industries was, I would say, a product oriented company, right that probably had a larger software component, and that disruption caused a competitive issue or a customer issue that cause companies to try to respond by transforming. I think co vid, you know, all sudden flatten that out, right? We literally all got disrupted, right? And and so all of a sudden, every one of us is dealing with some degree of market uncertainty customer uncertainty on doll. So none of us are insulated from the need to be able to pivot faster, deliver incrementally, you know, and operating a different, completely more agile way. Uh, you know, Post Cove it right? >>Yeah, that's great. So again, very, very, very timely. You know, a little bit of serendipity, a little bit of planning and, you know, a zoo with all important things There's always a little bit of locking a a lot of hard work involved. So really interesting. Thank you for for your leadership, Patrick. And, you know, it really makes a statement. I think when you have a bunch of leaderships across an industry coming together and putting their name on a piece of paper, that's a line around us, um, principles and some values, which again, if you read them, who wouldn't want to get behind these? But if it takes, you know, something a little bit more formal, uh, to kind of move the ball down the field, and then I totally get it. And, uh, really great work. Thanks for Thanks for doing it. >>Oh, absolutely. No. Like I said, the first time I read it, I was like, Yeah, like you said, this is all this all makes complete sense, but just documenting it and saying it and talking about it moves the needle. I'll tell you, as a company, we were pushing really hard on, uh, you know, on our own internal strategy on diversity inclusion, right. And and like once we wrote the words down About what? You know what we aspire to be from a diversity and inclusion perspective. It's the same thing. Everybody reads the words and goes, Why wouldn't we do this right? But until you write it down and kind of have again, you know, a manifesto or a terra firma of what you're trying to accomplish, you know, Then you can rally behind right, as opposed to it being, you know, something that's everybody's got their own version of the flavor, right? And I think it's a very analogous, you know, kind of initiative. And, uh, it's happening. Both of those things right are happening across the industry these days, >>right and measure it to write and measure it. Measure, measure, get a baseline even if you don't like the measure, even if you don't like what the Even if you can argue against the math behind the measurement, measure it, and at least you could measure it again. And you've got some type of a compound that is really the only way toe to move it forward with. Patrick really enjoyed the conversation. Thanks for for taking a few minutes out of your day. It's great to >>be here. It's an awesome movement, and we're glad to be part of it. All >>right. Thanks. And if you want to check out the biz ops manifesto goto biz Opps manifesto dot org's read it. You might want to sign it there for you. And thanks for tuning in on this segment. We'll continuing coverage of the bizarre manifesto unveiled here on the Cube. I'm Jeff. Thanks for watching.

>>from around the globe. It's the Cube with digital coverage of biz ops Manifesto unveiled Brought to you by Biz Ops Coalition >>Hey, welcome back Variety. Jeff Freak here with the Cube were Palo Alto Studios, and we like to welcome you back to our continuing coverage of biz. Opps manifesto Unveil. Exciting day to really, uh, kind of bring this out into public. There's been a little bit of conversation, but today is really the official unveiling, and we're excited to have our next guest to share a little bit. More information on it. He's Patrick Tickle. He's a chief product officer for plan view. Patrick, great to see you. Yeah, >>it's great to be here. Thanks for the invite. And it's Yeah, exciting day. It's fund a great topic to talk about, right? So before we >>jump into the manifesto, let's for people that aren't as familiar with plan view. Give us kind of the quick overview of what you guys are all about. Yeah, >>so plan, view. You know, we've We've been around for 30 years. The company on we've traditionally lived. We live in the strategy to delivery space. You know, people eso all about planning and connecting that all the way to delivery. You know, historically, a lot of people know us as having lived is the best breed leader in the world of ppm or project portfolio management. But you know, what's interesting about this conversation, in some ways is over The last couple of years, we've been through a massive transformation of our own and really, you know, added the whole world of agile transformation not just to who we are internally, but to the products and solutions we offer. So we now really spanned the world of the world of strategy and work, whether it's agile, traditional, uh, in ways that we never have before. And it's a super exciting time, right? >>And it's really interesting with Cove. It obviously a lot of challenges and and still tough times and dark some dark days ahead. But there's certain businesses, certain industries that are getting a little bit of a tailwind. So I assume that's really helping you guys. As you know now, you've got remote and distributed teams that need more organization and better tooling toe actually get stuff done. So I assume you guys businesses probably little bit on an uptake over the last several months. Yeah, >>that's that is absolutely true, right? I have that conversation all the time, right? I mean, these days, you know, strategy and delivery are pretty dynamic environments, right? And not just in terms of not just in terms of setting strategy and, you know, determining how to deliver. But, I mean, with teams being completely distributed, you know, uh, it's created a whole, as we all know, right? A whole new way of working. But our tool set really is kind of built. Turns out it was kind of built for purpose, you know, for this kind of environment. And it's created, like, very, very interesting time for playing you in for all of our customers. >>Right? And I think your upper right corner in the Gartner Magic Quadrant all that good, positive stuff. And >>you've been at this for a while. >>So why the biz? Opps manifesto? Why the bizarre coalition? Now, when you guys have been at it, it's relatively mature marketplace. Business is good. What was missing? Why? Why this? Why this coalition? >>Yeah, So you know, again, Why? Why is bizarre is important. And why is this something I'm you know I'm so excited about, but I think companies as well, right? Well, no. In some ways or another, this is a topic that I've been talking to, you know, the market in our customers about for a long time. And it's, you know, I really applaud, you know, this whole movement, right? And, um, it resonates with me because I think one of the fundamental flaws, frankly, of the way we have talked about technology and business literally for decades has been this idea of alignment. Those who know me, I occasionally get off on this little rant about the word alignment. Right? But to me, the word alignment is actually indicative of the of the of the flaw in a lot of our organizations. And biz ops is really, I think, now, trying to catalyze and expose that flaw, right, because, you know, I I always say that, you know, you know, alignment implies silos right the instantaneously with soon as you say, there's alignment. There's there's obviously somebody who's got a direction and other people that have tow line up and that that kind of siloed, uh, nature of organizations and then, frankly, the passive nature of right? I think so. Many technology organizations, like look, the business has the strategy. You guys need to align, right and and, you know, as a product leader, right? That's what I've been my whole career. Right? I can tell you that I never sit around. I almost never use the word alignment, right? I mean, whether you know, I never sit down and say, you know, the product management team has to get aligned with death, right? Or the Dev team has to get aligned with the, you know, delivery and ops teams. I mean, what I say is, are we on strategy? Right? Like we we have a strategy as a as a full end to end value stream, right, and that there's no silos, and I mean, look, every on any given day, we got to get better, right? But the context, the context we operate is not about alignment, right? It's about being on strategy. And I think I've talked to customers a lot about that. But when I first read the manifesto, I was like, Oh, you know, this is exactly this is breaking down maybe trying to eliminate the word alignment, you know, from a lot of our organizations because we literally start thinking about one strategy and how we go from strategy to delivery and have it be our strategy, not someone else's, that we're all aligning to it. And it's a great way to catalyze. You know, that conversation that I've has been in my mind for years be honest, >>right? So, So much to unpack there. One of the things, obviously, uh, stealing a lot from from Dev Ops in the Dev Ops Manifesto from 20 years ago. And as I looked through some of the principles and I looked through some of the values which are, you know, really nicely laid out here, you know, satisfied customer do continues delivery measure output against riel results. Um, the the ones that that jumps out, though, is really about, you know, change change. Right requirements should change frequently. They do change frequently, but I'm curious to get your take from a from a software development point. It's easy to kind of understand, right? We're making this widget, and our competitors made a widget plus X, and now we need to change our plans and make sure that the the plus X gets added to the plan. Maybe it wasn't in the plan. You talked a lot about product strategy. So in this kind of continuous delivery world, how does that meld with? I'm actually trying to set a strategy which implies a direction for a little bit further out on the horizon. And to stay on that while at the same time you're kind of doing this real time, continual adjustments because you're not working off a giant PRD or M R D anymore? Yeah, >>totally. Yeah. You know, one of the terms you know, that we use internally a lot on even with my customers, our customers is we talked about this idea of rewiring, right, and I think you know. So it's kind of an analogy for transformation, and I think a lot of us have to rewire the way we think about things right. And I think it plan view where we have a lot of customers who live in that you know who operationalized that traditional ppm world right and are shifting toe agile and transforming that rewire super important and to your point, right, it's you've just you've got to embrace this idea of, you know, just iterative getting better every day. And Iterating Iterating Iterating as opposed to building annual plans. Or, you know, I get customers occasionally. Who asked me for two or three year roadmap? Right? And I literally looked at them and I go, There's no, there's no scenario where I could build a two or three year roadmap, right? You you think you want that? But that's not That's not the way we run, right. And I will tell you the biggest thing that for us, you know, that I think is matched the planning. You know, impedance is a word I like to use a lot. So the thing that we've like that we've done from a planning perspective, I think is matched impedance to continuous delivery is instituting the whole program. Implement the program increments, planning capabilities and methodologies. Um, in the scaled, agile world, right. And over the last 18 months to two years, we really have now, you know, instrumented our company across three value streams. You know, we do quarterly p I program increment 10 week planning, you know, And that becomes that becomes the terra firma of how we plan, right? And it's what are we doing for the next 10 weeks, and we iterated within those 10 weeks. But we also know that 10 weeks from now we're gonna we're gonna just reiterate again, right? And that shifting of that planning model, you know, to being is cross functional. Is that as that big room planning kind of model is, um And also, you know, on that shorter increments when you get those two things in place. Also, the impedance really starts to match up with continuous delivery, and it changes. It changes the way you plan, and it changes the way you work, right? Thea? Other >>thing. Right. So obviously a lot of these things, that kind of process driven both within the values as well as the principles. But there's a whole lot really about culture, and I just want to highlight a couple of the values, right? We already talked about business outcomes, um, trust and collaboration, a data driven decisions and then learned responded pivot, right. A lot of those air cultural as much as they are processed. So again, is that Is that the need to really kind of just put them down on paper? And you know e can't help but think of you know, the hammering up the thing in the Lutheran church with it with their manifesto. Is it just good to get it down on paper? Because when you read these things, you're like, Well, of course we should trust people. And, of course, we need an environment of collaboration. And, of course, we want data driven decisions. But as we all know, saying it and living it are two very, very different things. >>Yeah, good question. I mean, I think there's a lot of ways to bring that to life. You're right. And just hanging up. You know, I think we've all been through the hanging up posters around your office, which these days, right, Unless you're gonna hang a poster and everybody's home office, right, you can't even you can't even fake it that you think that might work, right? So, um, you know, you really, I think we have attacked that in a variety of ways, right? And you definitely have to, you know, you've got to make the shift to a team centric culture, right? Empowered teams. You know, that's a big deal, right? You know, a lot of a lot of the people that, you know, we lived in a world of quote unquote, where we lived in a deep resource management world for a long, long time and write a lot of our customers still do that. But, you know, kind of moving to that team centric world is eyes really important and court of the trust. I think training is super important, right? We've, you know, we've internally, right. We've trained hundreds employees over the last year and a half on the fundamentals. Really of safe, right? Not necessarily. You know, we've had we've had teams delivering and scrum and continuous delivery for, you know, for years. But this scaling aspect of it eyes where we've done a lot of training investment on Ben. You know, I think leadership has to be bought in, right, you know? And so we p I plan, you know, myself and camera and the other members are leadership, you know, we're in p I planning, you know, for for four days, right? I mean, you've gotta walk the walk, you know, from top to bottom. And you've got a train on the context, right? And then you and then and then once you get through a few cycles where you've done a pivot, right? Or you brought a new team in and it just works. It becomes kind of this virtuous circle where he will go. Man, this really works so much better than what we used to dio, >>right? Right. Theater, Really key principle to this whole thing is is aligning the business leaders and the business prioritization s so that you can get to good outcomes with the development and and the delivery right? And we know again and kind of classic dev ops to get the Dev and the production people together so they can, you know, quickly ship code that works. Um, but adding the business person on there really puts puts a little extra responsibility that they they understand the value of a particular feature, a particular priority. Uh, they can make the trade offs and that they kind of understand the effort involved too. So, you know, bringing them into this continuous again kind of this continuous development process, Um, to make sure that things were better aligned and really better Prioritize, because ultimately, you know, we don't live in an infinite resource. Is situation and and people got to make tradeoffs. They gotta make decisions, is toe what goes and what doesn't go on for everything that goes right, I would say you pick one thing. Okay, That's 99 other things that couldn't go. So it's really important to have you know, this you said alignment of the business priorities as well as you know, the execution within, Within the development. >>Yeah, I think that, you know, You know, I think it was probably close to two years ago, Forrester started talking about the age of the customer, right? That was like their big theme at the time, right? And I think to me what that the age of the customer actually translates to. And Mick, Mick and I are both big fans of this whole idea of the project. The product shift mixed book, you know, is a great piece on your talking. A za part of the manifesto is one of the authors as well. But this shift from project to product, right? Like the age of the customer, in my opinion that that the embodiment of that is the shift to a product mentality, right? And the product mentality, in my opinion, is what brings the business and technology teams together. Right once, once you're focused on a customer experience that's delivered through a product or a service, that's when I that's when I start to go. The alignment problem goes away right? Because if you look at software companies, right, I mean, we run product management models with software development teams, customer success teams, right that, you know, the software component of these products that people are building is obviously becoming bigger and bigger, you know, and in many ways, right, more, more organizations are trying to model themselves over as operationally like software companies, right? They obviously have lots of other components in their business than just software. But I think that whole model of customer experience equaling product and then the software component of product the product is the essence of what changes that alignment equation and brings business and teams together because all sudden, everyone knows what the customers experiencing right, and and that that that makes a lot of things very clear very quickly, right? >>I'm just curious how far along this waas as a process before, before Cove it hit right because serendipitous, whatever right, but the sudden, you know, light switch moment. Everybody had to go work from home in March 15th. Compared to now, we're in October on. This is gonna be going on for a while, and it is a new normal and whatever that whatever is gonna look like a year from now or two years from now is T B d. You know, had you guys already started on this journey because again, to sit down and actually declare this coalition and declare this manifesto is a lot different than just trying to do better within your own organization. Yeah, >>So we had started, you know, we definitely had started independently. You know, some some. You know, I think people in the community know that we we came together with a company called Link It Handful years ago. And I give John Terry, actually one of the founders link it immense credit for, you know, kind of spearheading our cultural change. And not and not because of, we're just gonna be, you know, bringing agile solutions to our customers. But because, you know, he believed that it was gonna be a fundamentally better way for us to work, right? And we kind of, you know, And we started with John and built, you know, centric circles momentum. And we've gotten to the place where now it's just part of who we are. But But I do think that you know, Cove it has. You know, I think pre Cove in a lot of companies, you know, would would adopt, you know, the would adopt digital slash agile transformation. Um, traditional industries may have done it as a reaction to disruption. Right, You know, and in many cases, the disruption to these traditional industries was, I would say, a product oriented company, right that probably had a larger software component, and that disruption caused a competitive issue or a customer issue that cause companies to try to respond by transforming. I think co vid, you know, all sudden flatten that out, right? We literally all got disrupted, right? And and so all of a sudden, every one of us is dealing with some degree of market uncertainty. Customer uncertainty on also, none of us are insulated from the need to be able to pivot faster, deliver incrementally, you know, and operating a different, completely more agile way. Uh, you know, Post Cove it, right? >>Yeah, that's great. So again, very, very, very timely. You know, a little bit of serendipity, a little bit of planning and, you know, a zoo with all important things. There's always a little bit of luck and a and a lot of hard work involved. So really interesting. Thank you for for your leadership, Patrick. And, you know, it really makes a statement. I think when you have a bunch of leaderships across an industry coming together and putting their name on a piece of paper, that's a line around us, um, principles and some values, Which again, if you read them, who wouldn't want to get behind these? But if it takes, you know, something a little bit more formal, uh, to kind of move the ball down the field, and then I totally get it. And, uh, really great work. Thanks for Thanks for doing it. >>No, absolutely. No. Like I said, the first time I read it, I was like, Yeah, like you said, this is all this all makes complete sense, but just documenting it and saying it and talking about it moves the needle. I'll tell you, as a company, we were pushing really hard on, uh, you know, on our own internal strategy on diversity inclusion, right? And and like once we wrote the words down About what? You know what we aspire to be from a diversity and inclusion perspective. It's the same thing. Everybody reads the words and goes, Why wouldn't we do this right? But until you write it down and kind of have again, you know, a manifesto or a terra firma of what you're trying to accomplish, you know, Then you can rally behind right, as opposed to it being, you know, something that's everybody's got their own version of the flavor, right? And I think it's a very analogous, you know, kind of initiative. And, uh, it's happening. Both of those things right are happening across the industry these days, >>right? And measure it to write and measure it. Measure, measure, get a baseline even if you don't like the measure, even if you don't like what the Even if you can argue against the math behind the measurement, measure it, and at least you could measure it again. And you've got some type of a compound that is really the only way toe to move it forward with Patrick really enjoyed the conversation. Thanks for for taking a few minutes out of your day. It's great to >>be here. It's an awesome movement, and we're glad to be part of it. All >>right, Thanks. And if you want to check out the biz ops manifesto goto biz ops manifesto dot org's read it. You might want to sign it there for you. And thanks for tuning in on this segment. We'll continuing coverage of the bizarre manifesto unveiled here on the Cube. I'm Jeff. Thanks for watching.