Showing posts with label executive. Show all posts
Showing posts with label executive. Show all posts

Saturday, August 15, 2020

The Portfolio Management Dream: How to Stop it from Becoming a Nightmare!

To get to the web page of the radio show, click here.

To download the mp3 file, click here.

To subscribe to the podcast on iTunes, click here.

This transcription was completed through an automated service.  Please excuse any typos or misrepresented words.

VoiceAmerica  0:04  
One problem facing people at many levels of business is how to make time for a work life and a personal life. Do you find that one seems to keep getting in the way of the other? This is the work life balance with Rick Morris. Even if you're not involved in the business world, you'll have a lot to gain by tuning into today's show. Now, here's your host, Rick Morris.

Rick A. Morris  0:26  
And welcome to another edition of the work life balance on this Friday afternoon. So excited to have you guys along. And, you know, I've been very, very blessed with this radio show been blessed by you as an audience. And because of that, we're now booked out to the end of the year, which is really, really cool. It's the first time in the five years that I've done the show that we've been booked out that far in advance and that's a testament to you guys and a testament to the quality of people that are wanting to come on and talk to us about the work life balance. But having said all that it's been a little while since just I've been with you. So I thought I would take the opportunity today and just talk through some of the things that's happening here in our lives and then go through one of my, my newest content deliveries that we're talking about, which is called a portfolio management dream, and how to stop that from becoming a nightmare. So just, you know, on the personal front, there's there's a ton of activity that's been going on, you know, COVID has impacted us all. And being a serial entrepreneur and somebody who works from home. My consulting business, really just kind of went away, and so did the speaking business. And so I was faced, you know, in February in March of looking at my pipeline projections and just seeing them go down to nothing, almost. And so it's always time to pivot in I always say, these are the times that make the entrepreneur and these are the times that we really need to focus on what's important, but it's also not the time to take a break, I think The people that are working the hardest right now to reinvent and reinvigorate are the ones that are going to come out of COVID just fine. So to that end, we've started actually three different companies. Right now one super excited about we're calling milestone melodies. We're actually making custom songs. So we've got an entire group of Nashville Songwriters, musicians in really looking to create a unique, I hate to even say gift but a unique moment or so it could be, you know, wedding, anniversary, birthday, anything like that. And we're creating custom music fully produced. So there's a couple of other groups out there that do that, but they don't have the production level or certainly the talent that's available to us in Nashville. So super excited about that. There'll be probably a whole show, I'll bring the CO owners, which is Jennifer McGill, who's former Mickey Mouse Club, and Jeff bohannan is her Ben who does a lot of the production as well and we'll have them on and talk about their why and that business that's going to be really cool. We started a new organization as well called social RX which is spinning up which is more of a prescription for social media and how to do social media total Social Media Marketing Agency. And of course, you know, the pm tribe has been going on but the latest announcement is radio MMC, which you can go to radio MMC calm, but it is now a radio station that's internet based, that plays solely music of those artists and people that are connected to the 90s version of the Mickey Mouse Club. So that just launched this week. It actually launched August 12. So we're super excited about that. You can go to radio MMC comm and check that out. So let's get into today's topic. So in my consulting career and working with a lot of organizations, I've worked with almost 150 or so organizations now implementing what we call project portfolio management software. In the sole reason that most organizations buy this level of software in they can spend anywhere from, you know, 20,000 a year up to 200 $300,000 a year. So, I know several clients that have millions of dollars

invested in a platform like this, but they all buy it so that they can generally make better decisions when it comes to portfolio management. And so for those of my audience that may not fully understand what portfolio management really is, it is managing the entire project inventory for an organization in managing that to strategy as well as cost. And so the first question I always like to ask when we're doing any kind of portfolio management work is, are you picking projects based on what you can spend, or what your resources can realistically achieve? So let's explain that most organizations have some sort of capital budget planning process. Guess what they do? Is that the beat, you know, somewhere in September, October, they start a list and they essentially just say, hey, what are other projects that we need to complete next year? And this huge list? And they asked about how much is that going to cost? And then, of course, that list gets sent up somewhere, and, you know, goes through some magic formula, and essentially, they pick the project. And we've done a whole series on, you know, making sure that projects aligned to strategy and all those other things. So we won't get into that at this point. But my question is, is during that process? How do we ensure that when we pick all these projects, that we have a reasonable staff to be able to complete all those projects? And I would say between 90 and 95% of companies out there, have some sort of an idea. They'll say, you know, how many resources do you think you'll use? How many hours do you think this will be? Some kind of rough estimate? But it really doesn't timescale those estimates and show how the resources are being utilized whether or not they're gonna be overloaded or have enough time to actually complete the project work. So that's a huge question. And so as organizations start to become aware of this need, or really want to start to understand, and especially I think now in terms of COVID, you know, with reduced staffed and work at home and all those things, that it's forcing all these companies to challenge all their assumptions. And I wonder what that process is like if you don't have something that's automated, or something that can assist you in understanding that. And it's far too complex to keep this kind of information in your head or even via a spreadsheet. Because the moment you finish the spreadsheet, it's out of date. So essentially, an organization then has this dream, that they're going to buy some portfolio management software, and off they go. So what I want to do is talk through kind of three different Dreams. And then the nightmares that I see get created through those dreams. And then I'll finish this episode with some practical tips and tricks from a real world perspective. So that's what we're doing today. So the first dream is again, they buy a piece of software, it automatically somehow ranks projects through data, and then automatically communicate that information through the enterprise. So everybody knows the ranking of the projects and whether or not we have enough people to do them. And off we go. Now it's true. Most of the software on the market can do that. But here's how these things become nightmares very, very quickly. First and foremost, the first mistake most people do when they're looking at implementing a system like this any kind of automation system really, is they overcomplicate the software. When you start to see the potential of what software can automate, you start picking more and more and more processes to bring in and then essentially becomes this huge behemoth that takes forever to test for everything. Training is so disruptive to the enterprise. It's just too big. And so, by overcomplicate I can tell you I can't tell you how many times that when we we sold the software, we started working with the organization, we had something very simple like we want to do portfolio management. By the end, what you're arguing about is these 30 reports that nobody's going to read. And it's about colors and fonts and things, things like to me that I'm sure they matter to some people, but at the end of the day, those aren't decision making things. And those aren't things that really are driving those types of decisions. So becomes way over complicated. We're trying to do way too much and bite off more than we can chew. I think that second thing is that while this software does rank things, it has to have the data underneath to rank them. So for instance, if I want to know whether or not I have the resources available to do this project, and I have to have some sort of thought of what type of resources I need for how long and And how much of them that I need. So for instance, any 50% of a project manager for six months, and then that has to be compared with all the existing projects, and those have to have at least some sort of resource estimation.

Beyond that, a lot of people like to look at return on investment, net present value and, and total costs and things like that. But if we're not inputting that data consistently, in the system, then when it ranks the projects, it's ranking based on incomplete data. I think the third major thing that I see when people buy the software is that computers and software aren't going to replace human conversation. So for instance, one of the big ones is like, Okay, if I input my resources there, I want to be notified every time somebody updates a resource in the system. And I really see you know, do you do you really want to be notified because at some point, the These notifications is just going to clog your email box, and nobody's really going to want to look through them, and then it's going to lose its effectiveness and value anyway. So why would you want to be notified? And ultimately, the conversation comes down? Well, I don't want, you know, project manager or somebody going in there and messing up my resource forecast. So I get that. But even if they do, right, the system isn't going to prevent that or being notifying you isn't going to prevent that there's still got to be some sort of human conversation. There's still has to be talking that goes on and you know, jacking for the best resources for a project and no system, no matter how well automated or how well crafted is going to replace human conversation. And also the whole notification thing. Well, I see value in that being notified immediately. Whenever I'm talking to somebody in a meeting and they say something like that. I say, okay, hang on real quick. You just got notified. What are you going to do with it? Now that you've been notified, what's the next step? You're in a meeting You don't have the access to the data. So now it's just another email in your box that you got to get back to. So why couldn't we just create something like a weekly digest that says, you know, here's all the things you said you cared about, you know that, that if they were updated or changed in the system you wanted to know. But we give that to you in a consolidated format that says like, here's all the resource changes, here's all the project date changes, here's all the issue updates, you know, those types of things. But kind of a weekly digest instead of notifying you every time something like that happens. And most of my clients will take that option. But the point being is you lose the effectiveness of the software. If you overcomplicated, you don't have complete data. And you think that this system is going to replace the human conversations that are necessary to move business along. So that's how dream number one becomes nightmare. Number one. So we're going to go through a couple more of these. I've got two more dreams and nightmares to talk about and then we'll get into some practical tips but we're going to take a break right here. Are you listening to Rick Moore's on the work life balance?

VoiceAmerica  12:05  
Are you aware that 80% of project management executives do not know how their projects align with their company's business strategy? Are you aware that businesses identified capturing time and costs against projects as their biggest project management challenge? Are you aware that 44% of project managers use no software? Even though Price Waterhouse Coopers found that the use of commercially available project management software increases performance and satisfaction? Now, imagine that you could have the ease of entry like a spreadsheet and a software tool set up and running within two to four weeks. Imagine within two weeks being able to see clearly where all of your resource conflicts are. Well, you don't have to imagine because PD ware has already created it. pd ware can give you real time access to KPIs easily updated views of what your teams are working on. And immediate feedback to some of project management's toughest questions like when can we start this project. What happens if we delay this project? Can we do this in time? How does this new project impact our current portfolio? Find us at PDX where calm at imagine not manually compiling endless reports again, are you getting the most out of your project management software. In many cases, it is not the software that is failing, but the implementation limitations or processes surrounding the use of that software. r squared can analyze your current use and help improve your return on investment. r squared can also suggest the best software for your organization and goals and assist in the selection implementation and training. Allow r square to ensure that you are getting the value of your investment. Visit r squared consulting.com today

from the boardroom to you voice America business network.

You want to tuned into the work life balance to reach Rick A. Morris or his guest today, we'd love to have you call into the program at 1-866-472-5790. Again, that's 1-866-472-5790. If you'd rather send an email, Rick can be reached at our Morris at r squared consulting.com. Now back to the work life balance.

Rick A. Morris  14:25  
And we're back to the work life balance on this Friday afternoon. We're talking about the portfolio management dream and how to stop that from becoming a nightmare. So this really comes from years and years of experience doing portfolio management working with organizations. The first one that we covered was, you know, buying software that we think is going to solve all the problems and while software does accelerate a lot of the decisions and makes a lot of the decisions easier. Certainly we have the ability to mess up how we implement the software and thereby make the nightmare happen. So our second dream that I want to talk about is where people will convene a PMO. And ultimately a portfolio management committee. The dream is that we're going to get the executives in the room, we're going to give them some criteria, they're going to look at all of our projects, and rank them with only one number one.

Not like one, a, one, B, one C, one D, but truly have a number one project. You know, a lot of times when when I'm starting the consulting with an organization, I'll ask them, who do you think is making the strategic decisions of the company? And of course, you know, they say, well, we do, right. We're the Executive Council, we do, and I'll say, Okay, do you have a prioritized list of projects that's, that's actually accessible, and everybody understands where they fit? And if the answer's no, then I said, well, you're really not making the strategic decisions. And they asked me how that can be. And I said, because what you're doing is essentially by not having a prioritized list of projects. You're deferring the decision. And that decision will continue to get deferred until it has to be made, which is generally at the lowest level. So for instance, it's it's not you making the strategic decision. It's that database administrator who just got asked to do three different things. Whatever they choose to do first is now the number one priority, at least to them. And of course, if everybody's operating that way, then you've got 500 priorities being worked on, and no consolidated effort towards that major project. And so how you combat that is then how do you decide what's the number one project and most people will do that through a council. So that's the dream is that we're going to convene this council. They're going to make decisions. We're going to have a prioritized list of projects and how we go. Now the first qualifier I want to give before I get into the nightmares, those one of the biggest things that I look at from a maturity perspective of not only Portfolio Management Council, but the project management office, the PMO, I was asked how many projects did Did you kill in flight or cancel outright as part of this committee? And if the answer is that they haven't, then they're not a very mature committee. Because the committee is just now becoming a rubber stamp or roadmap through in order to, you know, greenlight the project. But if they're really not stopping projects, or looking at projects that are performing poorly in them from that point, then they're not really making these portfolio management type decisions. That's really the goal. The goal shouldn't be which project should we approve? It really should be which projects aren't worth our time are we not going to do so how these then councils become a nightmare is first, how do you actually come up with a ranking for a project. And so what they'll do is they'll design a formula to rank projects, right the but then the argument then becomes about the formula. So instead of deciding you This project should be higher than this project we're arguing about, you know what, that ROI should be five times the revenue coming in or, you know, the NPV should be two times as important as the overall cost, you know, things of that sort. And the reason that that that formula becomes an argument is because based on the ranking of using the formula, the projects that they felt were most important, weren't showing up. So the answer must be let's tweak the formula so that we can get the expected result versus taking a really hard look at the what, what the formulas doing. So that's one way it can become an absolute nightmare. The second one and this one, this one I see more often than anything is that the council itself breaks down. So the decisions are really hard to make, but then that's why it's part of an Executive Council. The executives are there to make really hard decisions, and a very hard decision is we're going to do this Project and not do that project. And so I was contracted for for a government agency. And they had eight divisions that were using a centralized it. And everybody was upset that it wasn't doing the projects fast enough and wasn't producing enough so on and so forth, because everybody had a number one, and it was just bogged down. And my my challenge to them was, Why does it have to make the decision because at the end of the day, it for the most part, for the most part, I know I'm being generous here. So please don't be offended. But for the most part, it doesn't care what project we're doing. What we care about is that we have enough time to do that project with quality and be able to to put out the best results possible. But whether we do project a or project B really doesn't matter because we're going to end up doing them both. It's just give us the time to complete project day before we move on to project beat. So I worked with the the eight divisions and I can to counsel with them. And one of the first things I had them do was I asked them to come up with a list of criteria they feel they would need to have answered, in order for them to make a decision as to which project was going to be number one versus number two. And so we worked for weeks on that all kinds of data points, they were saying, and all this other stuff. When we were done with this exercise, the first thing I asked them to do was let's go ahead and rank our existing projects against this criteria. So that, you know, we could just see how it works, right kind of a test case. And they couldn't answer. They didn't have enough information to answer all the things that they say we're required in order to get a project approved to their Council. And I remember saying, doesn't that scare you? It doesn't scare you as the slightest bit that you're saying this is the minimum information you need in order to be able to rank a project. You can't produce that information for projects that are running right now. How does like how does Does that make you guys feel? And so what ended up happening is that it was too hard to get the data that they wanted. So we suggested to pare down the form and they disagree. They're like, no, we're just gonna disband the council. So it was a perfect example for me. And I've seen many organizations do that, that the decisions are that difficult. And in light of making the difficult decision or showing some leadership and taking that on, the response was simply we're going to push the decision back down to it and then we're going to yell at them if they're not making the decision we want them to make and that's essentially what I see in a ton of organizations.

The third one is nightmares is kind of the same under the same thing, but you can never make a decision due to insufficient data. So really nightmare. Scenario number two in this dream is is where they just the decisions too hard to make they disband but The third one is insufficient data. What this one really is, is what I call the decision delay tactic. So this is when they say, okay, we do want this set of information, go get it, you provide that information. Of course, a lot of people are doing this in spreadsheets, and it takes a ton of time to compile the information. And then somebody else on the council will say, Well, I really need to understand this piece of data in order for us to make these decisions. So obviously, you can't make the decision in that meeting. So you send everybody off, they create the new data point, they load it all up, they bring it back into the organization and somebody who go you know, that's really good, but now that I'm seeing that I want to know this piece of information. And while they say they do want to know it, it takes a lot of maturity in in somebody who's running the process to go, that's great. We'll rearrange the projects when we have that information, but we need to rank these projects based on the information we have today. That way, you have that opportunity to go ahead and start making some of the key decisions that need to be made. And you're not pushing it off. Just because of a data point. When you start to feel that kind of happening, that's when you want to challenge the organization or the council itself, to start to really come to terms with this decision has to be made. And it has to be made for the betterment of our people. And we talked about that for just a second. You know, decision making is what I feel the executives are paid the amount that they're paid for that that's that is their job is to make decisions. And but if you look at it from a human nature perspective, human nature says we don't really like or want to make tough decisions and a tough decision means it's not a compromise. Generally, somebody wins, somebody loses. And so when you're trying to maintain relationships, and you're trying to You know, make everybody happy and lead an organization successfully, those decisions are really hard to make. And I am not undermining that by any mean. But at the same time, no decision means the decision becomes deferred to a lower level. And so that now falls to your middle management, middle management doesn't make it that it falls down to your people and your people end up making strategic decisions, just for the mere fact that nobody else would. And so I just want you to think through that. And think about just something simple. Like if you're, you're asking for a team to collaborate on, you know, some copy that was being written an email was going to go out or a newsletter or something of that sort of something as simple as that. You ever send that email out and says, Hey, you know, provide me feedback. And you just don't get any information. Then of course, once it's published, everybody has their feedback ready for you? Well, some of these decisions That that are being deferred could cost millions upon millions upon millions of dollars. I remember

working with a bank, and they had something that they call this security scan. And it was supposed to just scan to see if any ports were open and they would close them before you know this, this thing would go into production. And there was there was a couple of projects that went out where a port was open, and it left them vulnerable to some sort of attack or hacking or something of that sort. And the CIO just came down with fury just beat everybody up around them. And so, next thing you know, as a project manager, when you go to do a security scan, they say, well, the security scan teams really overloaded. We said why they said well, we require three security scans for every project. I was like, what does that mean? And they said well, we got to scan it when the it is done building the server, we have to scan it after the vendors installed. software and we have to scan it after user acceptance testing, so that we can confirm if any ports were open. And if the ports were open, who, who opened them. And so then it became 10 days to schedule a security scan 10 days to perform it and 10 days to get the results. So you're looking at 90 business days or four and a half months, just so that we could say whether or not ports were open and who was to blame. And that was the kind of key thing see the executive needed to know who and was blowing everybody up, not the fact that the ports were open, but who did it. And so the question became, who made the decision to do three security scans? Well, nobody did. So the security scan team did, because they didn't want to get yelled at because they didn't know who opened the port. And so the question becomes, well, what was more important than the fact that we caught a port and we closed it before it went live? Or is it more important to know Who opened the port so we can yell at him and blame him. And when when I finally challenged the executive with that information, the answer was clear that no, we just want to make sure the ports are closed. But my that was a perfect example of how every single project in that bank, for as long as those process were in play, we're getting delayed by up to two and a half to three months. For no logical business reason, other than we wanted to know who to blame. That's a perfect example of when an executive decides to blow something up or yell at somebody or not make the the decision, how it gets hand checked down, and other people will then make the decision in absence. So that's our dream number two convenient counsel and make decisions and how those become nightmares. We're going to come back with nightmare number three right after this break and listening to Rick Morris and the work life balance.

VoiceAmerica  27:57  
Are you frustrated with the overall productivity Have your project management processes Do you lack consistency and project delivery? Our squared consulting provides end to end services to assist companies of all sizes in realizing and improving the value of project management. Whether you want to build a project management office train project managers for learn how to bring the oversight and governance to your project processes, r squared has tailored best practices to help you in all areas of project management, visit r squared consulting.com. At the work life balance, we like to ask simple questions to our executives and portfolio managers. Are you picking your projects based on what the organization can spend? Or is it based on what your resources can realistically achieve? This question is not answered properly can cause great strain on your staff limiting the return on investment. When creating project selection criteria. Does your organization attempt to understand the amount of resources needed to complete the work? Is this done in spreadsheets or in a while level. What if we told you there was a simple and easy solution that was built with resource planning in mind? We call it resource first from PD where resource first was built with resource planning as its foundation. We have years of experience that proves before a company fine tunes its project and portfolio management processes without a process for resource planning. The best processes and algorithms can fall flat resources should be first when deciding the strategy of taking an organization forward. Find out more at PD were calm. Put your people first with resource first from PD where join us at PDX were calm.

When it comes to business,

you'll find the experts here

voice America business network.

You are tuned in to the work life balance to reach Rick A. Morris or his guest today. We'd love to have you call into the program at 186 64725790 Again, that's 1-866-472-5790. If you'd rather send an email, Rick can be reached at r Morris at r squared consulting.com. Now back to the work life balance.

Rick A. Morris  30:17  
And we're back to the work life balance on this Friday afternoon talking about the portfolio management dream, how to stop them from becoming a nightmare. So we've covered two dreams already. Let's get into the third one and then we're going to get into tips and tricks that I have several clients that pay big money to hear so that's that's what's coming. So hang on with us and we'll get into some tips and tricks on some practices that are surprisingly successful. So dream number three is to institute a gating process. So, gating process is a series of gates where you want to have some sort of check where a project goes from initiation into planning, planning and execution, execute In closing, so on so forth, the goal is to validate that the team itself is ready that all the due diligence has been done. And we really understand what we're getting ourselves involved with. It's also, though should be a key point in which we look at the project and decide whether or not to continue the project. So it's not just a rubber stamp. So a lot of organizations, again, state that they want that they state that they want some sort of gating process, they want some control. They want to make sure that everybody's thought through everything that they're supposed to do. But the reality of the situation is it becomes a process for the sake of process. And before I get into that, let me explain that like, for instance, for instance, one of the biggest process I think, is misused in project management is that of lessons learned. Not saying that lessons learned is invaluable. It's just that people haven't really thought through the process. So then it just becomes something that we do for the sake to say that we did add a checkbox for the PMO that says yes, we completed the lessons learned what I mean is most of the time lessons learned is handled with the project team. It's tracked in some sort of spreadsheet and then it goes out to like a SharePoint site. And then the intent is that all the project managers are supposed to read all of the lessons learned so that we can plan for that and avoid making the same mistake twice now in theory, phenomenal. But we do have a system of how do we take those lessons learned and actionable so that people can really learn? haven't thought through how to do that, then we're just doing a bunch of wasted effort. So again, it's it's not that lessons learned is invaluable. It's just the process in which we do it. If you want a great system of how you can actually turn lessons learned into a real risk assessment I suggest my book project management that works I have an entire chapter devoted to how you take the lessons learned turn that into a questionnaire that can that is in central English for Your project managers to be able to answer and then it tells you what to plan into the project based on how they answered that questionnaire. And it's all based on lessons learned. But coming back then to gating, right, a lot of people end up having gates, just for a process I had of Fortune 50 client I worked with. And when we calculated the cost of their gating process, it was $18 million. It cost them to run their gating process per year $18 million.

And so

that became a great test case for the nightmares that we talked about. So nightmare number one is that gates become really complex and they use too much time. In this case, it would take 88 hours for a project manager to gather all of the data. And of course, then there's all these rules that come with it, right? So you got to fill out this massive PowerPoint, you get to go query all these different systems and you get all this information and You're supposed to have that done a week ahead of the meeting, so that the committee can review it. Well, of course, the committee is going to be reviewing like seven or eight projects, they did not look at all of those spreadsheets, they didn't read all that document beforehand, which is what they're supposed to do for the coming to the meeting. So when they get in the meeting, you end up just, you know, rattling off a bunch of information, and then you get a rubber stamp, and off you go. So we've got to make sure that when you're looking at a gating process, that it's not complex, it's super easy to kind of get through but you have the right amount of control within it. The second big nightmare that comes with the gating process comes around, again, decisions not being made. So you present it and then they defer decision in the gate because they want more information or they don't understand. And so therefore, the project essentially goes on hold until you can go through that next gate. Even more so. You know, when you when you have the council that's looking at the gating, a lot of times they'll say well You know, we're only going to meet every other Tuesday, something of that sort, which means if I'm ready to go through a gate, I've got to wait until a certain amount of time, so I can go present and get a rubber stamp and move forward. So that's another huge nightmare that we see when we're looking at the gating process. But the biggest one and my challenge to this fortune 50 client, my challenge to most of my clients is, once we understand what the total cost of the gating process is, then what is the value of doing that? Can we attribute the value? Did we cancel a project? Did we save a project that was gonna lose a ton of money? And, and, you know, revamp them? And when we start looking at processes like this, you know, some of these are very necessary. Some of these are regulatory, and that's fine. But the question becomes, is the value does the value outweigh the cost or is the cost tremendously outweighing the value? So in the case of that fortune 50 client, my question is, can we address Repeat like 35 to $40 million of gains from running this $18 million process. Because if not, then we need to kill the process and reinvent it. Right. And, and that's so I don't understand why it's so scary for organizations, but they're like, Oh, no, we got to do gating. Okay, but the gating hasn't produced any kind of results for your organization the way that you've chosen to do it. So why do it? Well, because, you know, we have to or because, you know, an audit finding or because, you know, our consultant said, so something of that sort, but making sure that we're getting twice the value out. If not, then everybody needs to be re diverted to revenue generating activities instead of these activities that are just clogging up the wheel and not producing results. So that that's how that becomes a nightmare. Number three, so let's get into some tips then for dreams instead of nightmares. So those are the things that can go wrong. Based on the assumptions that most organizations make,

so how do we how do we make these things, actual dreams? How do we make this stuff come true? So my first tip is that all of these things work gating works, project management software and how that work, you know, that works. Having a portfolio decision committee, it works, but they all have to start simple and then become built upon. So for instance, in the project management world, focus on each one of your roles kind of doing one thing, well, I call this the three rings of focus. So the three rings of focus is okay, I want portfolio, our project managers to write a good schedule. I want resource managers to give me utilization statistics, at the minimum Give me the percentage of resources used against the project over a length of time. And the team members just validate those assumptions. They can do that through time tracking or just validating the percentages that They're their resource manager put in. If each one of those roles just focuses on doing those things, well, then you have all of the pillars that you need to make great portfolio management decisions. We'll know how well the projects are trending, what percentage of resources are available to take on the next project. And we'll understand that the resources know where they're supposed to be and what they're supposed to be doing. And so if we do that, then it works. Once you have that down, then you can start to add onto some automation and some workflows and notifications and all those other things that a system can provide. But what I end up seeing happening more than anything, is when you overcomplicate it, then you stent, you start to doubt the tool and not the implementation of the tool or the configuration of the tool. And then it just becomes this large time tracking kind of database Whenever you try to use the data as a point of decision, people don't trust the data so they don't do it. That's, that's horrible. So, they are all of these things work, but they need to be kept simple and they need to be built upon. Under that same kind of tip though, I want you to have the concept of enter once use many. So I I see a lot of organizations who like one time tracking in their portfolio management tool resource management tool, but then they also have SAP or some other HR kind of tracking system in which they have to answer time so now it becomes duplicate entry of time. That's the biggest thing I always caution my my companies and clients to look at is to say, we need a time tracking system of record. And then whatever other system needs that information, we can feed it. So generally that means the portfolio management software is the best place to track time because it's generally at a lower level. When you're looking at like SAP and HR systems. They just kind of want time rolled up to the front project level, not necessarily at the task level. And then of course, you've got you know, just number of hours worked PTO time, that kind of stuff, you can roll that up and send that to other systems. In the same with like financials. So if you're running SAP financials, then let's not create a whole separate tracking spreadsheet in our portfolio management system. Let's find a way a way to feed the relevant information from the system of record into this, you know, into the system where you want to use the data but not have any kind of duplicate entry. All of the all of the systems now have open API's, they're super easy to start to integrate with. And there's ways that you can design that process so that you're entering once and using many. That's a huge tip. Think through the process. From your resource perspective, think through the process of the people that you're asking to do. You know, the so yes, you want the information to make better decisions. But if we make it cumbersome to enter it in or they're entering it in, twice, it's To lower the quality, then you're going to be into the nightmare of the data quality doesn't add up. So therefore we don't trust it. And now we're just doing again process for the sake of process. Very, very important that a well designed thought process of implementation of what's the system of record? What's the information do we need? What are we going to ask our people to do? And how are we going to utilize that data? That's how you prevent that from becoming a nightmare. So I've got four more tips that I'm going to share with you when we come back, but we're going to take our final break right here you're listening to Rick Morris and the work life balance.

VoiceAmerica  41:38  
Are you aware that 80% of project management executives do not know how their projects align with their company's business strategy? Are you aware that businesses identified capturing time and costs against projects as their biggest project management challenge? Are you aware that 44% of project managers use no software even though PricewaterhouseCoopers found that they use commercially available project management software increases performance and satisfaction. Now imagine that you could have the ease of entry like a spreadsheet and a software tool set up and running within two to four weeks. Imagine within two weeks being able to see clearly where all of your resource conflicts are. Well, you don't have to imagine because PD ware has already created PD where can give you real time access to KPIs easily updated views of what your teams are working on, and immediate feedback to some of project management's toughest questions. Like when can we start this project? What happens if we delay this project? Can we do this in time? How does this new project impact our current portfolio? Find us at PDX were calm and imagine not manually compiling endless reports again, Are you frustrated with the overall productivity of your project management processes? Do you lack consistency and project delivery? r squared consulting provides end to end services to assist companies of all sizes sizes and realizing and improving the value of project management. Whether you want to build a project management office, train project managers, or learn how to bring the oversight and governance to your project processes, r squared has tailored best practices to help you in all areas of project management, visit r squared consulting.com.

When it comes to business, you'll find the

experts here voice America business network.

You are tuned in to the work life balance. To reach Rick Morris or his guest today we'd love to have you call into the program at 1-866-472-5790. Again, that's 1-866-472-5790 if you'd rather send an email Rick can be reached at our Morris at r squared consulting.com. Now back to the work life balance.

Rick A. Morris  44:00  
And we're back to the work life balance on this Friday afternoon, the final segment as we go through my tips now for how to keep your portfolio dream from becoming a nightmare. So we already talked about, you know, keeping things simple, the three rings of focus and enter once use many. Here's a very, very popular one we talked about earlier in the nightmare about how when you create a ranking algorithm to rank your projects, that a lot of the arguments become about the algorithm and not the projects themselves. So what I do is I find the five or six pieces of information that they're saying is important. So you know, ROI, NPV, total resource utilization, length of project, those types of things. And I rank all the projects by single statistic, each one so if there's five things I five separate lists and then I look for essentially the waterline or you know what we think we can do 30 projects, so which projects appear in the top 30 and all five of those categories. And generally there's about 10 to 12. In doing so, then we can say those 10 to 12 are in, regardless of who you know, if you think ROI is more important, or if you think total utilization is more important doesn't matter. That's it. And so now we're just we've made our decisions on the top 12 right out of the gate. And now we just start talking about the bottom 18. At that point, it moves things along a lot faster. And even if we come to a stalemate on the bottom 18 we still have ranked the top 12 and off we go. So that's a huge point in time saver for a lot of portfolio committees. probably my biggest tip that's utilized and in most of my most of my clients companies. The next one is what I call the 10% rule. This one, this one is is huge, especially when you start talking about lowering the amount of gates and things like that that you need. So essentially, the 10% rule works this way. So when you pitch a project and you have an initial budget, you automatically get 10% of that budget approved to go plan the project to really go plan out how much this thing is going to cost. And then if you're within 10%, plus or minus of your original estimate, you're automatically approved to go into execution. So the beauty of that is it's reducing the amount of gates that are just rubber stamp, and now gates just become about the outliers. But also it gives you the ability to move things along very, very quickly. So for an example, if it's a million dollar project, you get $100,000. To go plant it, you find out it's going to be a you know, 1,000,001 point 5 million, and then that means you you've got the green light to go into execution. So that's a very, very popular one as well. I've seen several organizations streamline their processes to where the only the gates that you're talking About are falling outside of that 10%. So therefore, there's real decisions starting to get made as to whether or not that project still valuable enough or whether it's still worth enough to go after.

And my next tip can go hand in hand with the 10% rule. And this is pmis term. It comes from the Pim Bock. And it's one that I remember kind of having a reaction when I first saw it, but once I saw one of these inaction, it's called a board. And that sounds horrible. But it essentially, is that the committee is convened to shoot down the project. And if you can, if you can then get the project through that committee, then it's a really good project to do. But otherwise, if it's a flimsy project, it's a pet project is one that's not really going to generate ROI, that kind of stuff. Those get cancelled and shut down in this committee. So the intent isn't to come to the committee to approve the intent is for the committee to come in and decline And make the sale of that project be so good, that it's irresistible. And we have to do this project. It's just it's a little bit of a flip of connotation, but it really is, is a powerful tool to say, you know, we understand we have limited resources, we understand we have limited budget, we're going to make sure that we're not going to waste any of those on projects that don't deserve, really to be considered by our staff. And my final tip, in this series is to talk about, again, value. If a process doesn't provide double the value, then it's time to redesign the process. And that really goes for any of our processes. It's amazing how much money that that I call low hanging fruit is available when I go into a consulting client. And all I have to do is looking at the processes that they're doing and question why do we have that process And I'll tell you that 90% of the time I'm talking 90% of the time, people will tell me Well, that's just the way it's always been done here. And that's that I hate that statement. Because that's not true. It's not the way it's always been done there. It was just the way that you were trained and you've never questioned or look to improve the process sense. And so when you're when you're looking at a process, I'll give you a perfect example something a question I asked a client that they'd never been asked before is that they, they deal with a lot of regulatory a lot of regulatory projects and regulatory generally means you have to do it, or there at least has some consequences for not doing it could be loss of reputation could be a financial fine in most times. It's a financial fine. But there was a new regulation came out everybody scrambling the project was gonna cost about $200,000 do and my question was, what's the fine? I go? What do you mean? I said, Well, we're doing this to avoid a fine, what's the fine, the fine was $10,000 For the first year, and I was like, Look, this is obviously a project we need to tackle, but it's going to be a nightmare to try to tackle it now. So why are we going to spend $200,000 to avoid 10? Where we'll just take the $10,000 lump. And now we don't have to do it as an emergency project, and it's gonna cost you no way less to do. And that's what we did. But nobody had ever really asked that question to the client before like, Alright, so that caused me and my portfolios when when I have a checkbox that says this is critical, or it's regulatory, like I want to see, like, Where's the regulation, I show me the document, show me the phrase, and show me the fine so that we understand that this is good business for us to do. So, if a process doesn't give you double that value, then it's time to absolutely redesign the process. So that's how we make portfolio management dreams. actually become dreams and avoid nightmares. If If you have any questions about any of those, you can reach me at r Morris at r squared consulting COMM The software that I recommend that you use right now, if you're looking at any kind of portfolio management type software is a company called PD where it is the first one that was built with resource planning in mind and makes the resource planning essentially the power of a project portfolio management tool with the ease of a spreadsheet, it's really really cool software, really inexpensive, and does a phenomenal job.

Coming up next week, we're going to start a series of entrepreneurs and real entrepreneurs. And we're going to have john tablets on who is the founder of books, which is Bo u q s and it is one of the fastest growing flower retailers out there, the largest company and one of the biggest successes ever to come out of shark tank and just a phenomenal entrepreneurial stories. So we're going to be visiting with john. Next week, and we've got tons of those coming up. We've got Wes, who actually was our reschedule. We missed an appointment before but he's a marketing guru got Travis Bell coming up. And just on and on Adam Mendler. Steve gave it tours. And then even if you missed last week, a fascinating conversation that we had with Doug vermeeren who's is considered the the modern day, Napoleon Hill. He's He's interviewed over 300 of the most successful people in the world, and is gleaned insights. And he talked to us about his movie, how thoughts become things so that was last week's episode. If you missed it, you definitely want to go back and catch that one. Otherwise, gang, we thank you so much for always being a part of the show, always the feedback that I get on social media and via email. I certainly appreciate it. So keep that coming. And until next Friday, we hope that you live here. Your own work life balance will talk to you that

VoiceAmerica  53:06  
thank you for joining us this week. The work life balance with Rick Morris can be heard live every Friday at 2pm pacific time and 5pm eastern time on The Voice America business channel. Now that the weekend is here, it's time to rethink your priorities and enjoy it. We'll see you on our next show.

Transcribed by https://otter.ai

Saturday, May 9, 2020

The Inevitable Collapse of Agile - David Stackleather

To get to the web page of the radio show, click here.

To download the mp3 file, click here.

To subscribe to the podcast on iTunes, click here.

This transcription was completed through an automated service.  Please excuse any typos or misrepresented words.

VoiceAmerica  0:04  
One problem facing people at many levels of business is how to make time for a work life and a personal life. Do you find that one seems to keep getting in the way of the other? This is the work life balance with Rick Morris. Even if you're not involved in the business world, you'll have a lot to gain by tuning into today's show. Now, here's your host, Rick Morris.

Rick A. Morris  0:26  
And welcome to another edition of the work life balance. Very excited to have everybody along. You know, I think it's still just really, really crazy times. I know a lot of the states in the United States are starting to kind of think about reopening and reintegration and you know, it's it's just been a crazy moment, but I had a moment of reflection this morning. I had a chance to join a mastermind with several of the john Maxwell team members. And really, you know, I think the the entire part of us being quarantine for that matter is that we really It's allowed me to focus more on connection versus distraction. Right, this is kind of the key thing that came out, I think, because I was traveling so much and because I was going all over the world and, and literally would lose two days a week to travel, there was just tons of distraction that I wouldn't allow that connection piece to always go and now that I'm kind of forced to stay in one spot, it's really been something to focus more on connection with people and so I challenge you to reach out and connect call three or four people today and just you know, maybe past clients or people that you haven't gotten, gotten in touch with recently and just have an opportunity to reach out to them. You know, I've got some some very special people in my life that that provides that connection that really just amplifies my energy and so I urge you to find the same. We also want to announce if you haven't had a chance to come join us at the pm tribe calm please do as for my project managers that are listening out there my agile lists that are listening out there. We wanted to create a community that did more than just deliver content, we wanted to deliver direct mentorship. So it's led by six of the brightest minds that we know in project management and agile and each one of us have lanes in which we have calls every week, the calls are recorded, but you have the ability to call into to the mentor and ask anything you want to ask and deal with any issue that you want to deal with. And we've got some phenomenal mentors, john Steinbeck, Colin Ellis, Peter Taylor, Elizabeth Heron, Elena Hill, and myself. And so it's just a great community of people that are really driven to watch you grow in and master your influence to be able to really do the job that we were intended to do. So that's at the pm tribe calm come join us over there. So we're going to get to our guests today. Our guest is is I'm really excited about this. He's an independent management consultant. And he's focused on unraveling track troubled large scale projects and helping organizations transformation into high performing and adaptable companies. In short, his mission is to help teams and organizations become better, better in the sense of increased teamwork, increased flow, increased learning and increased passion about their mission. Most companies today are run based on flawed and outdated assumptions about how people work their best. These assumptions around the structure work methods and management got us far during the Industrial Revolution. But those same approaches no longer work. The good news is we know what works now. And the challenge is that it's not easy or intuitive to get there and so we're going to talk to this gentleman who brings us this this great knowledge His name's David stack leather, David, how you doing, sir?

David Stackleather  3:37  
I'm good. Rick, how are you doing?

Rick A. Morris  3:38  
Doing fantastic. And you know, when I asked for a topic for the show, you know, the inevitable collapse of agile and so boy already I can feel the Agile is just, you know, just breathing heavy. Like, don't don't mess with my method. Don't you touch my standup right. Don't mess with my sprint. But let's talk about that. Right agile is is such a big buzzword and It's It's, you know something I looking at you on the screen here. I'm not going to guess age or judge age. But we've been through the ITIL. We've been through the Six Sigma craze. We've been through all the latest fads and things and, and so when when I first heard of agile, I thought it was a fad. I was like, man, they may even be around in two years, but right, it's hanging on. So talk to me. But why did you come up with that as a title? Why do you see it as an inevitable collapse of Agile?

David Stackleather  4:25  
Well, I, my early career, my first professional job was in when TQM was coming into the

Rick A. Morris  4:34  
TQM I'm certified baby.

David Stackleather  4:36  
Yeah, and process reengineering. And Mike hammer. And there was an executive at the company I worked for who was big into process reengineering. And I was kind of picked from the bowels of the organization as maybe I had an interest in that skill there. And so those things I was really passionate about that did a lot of work within the company I worked for with our clients, kind of an internal consulting company learned a lot traveled the world. And I still believe in all that stuff. I still believe in TPM. And I still believe in process reengineering in the in the right context. But it became clearer and clearer to me that there's a more fundamental issue that even if you have the recipe, even if you have the quote unquote, solution, there's a bigger issue and trying to accomplish that in larger organizations. And my most recent experience in a large scale agile transformation, were a very old school organization in the insurance space, which is famous for not wanting to change for some good reasons and some bad and looking at even an organization that wanted to go through the transformation and needed to go through a transformation. How much kind of nonsense there was within that structure and nonsense internally generated but a lot of nonsense externally generated from consulting firms. A lot of people who really had no idea really what they were talking about, but they had a certification over weekend and suddenly they felt they could suggest how an organization that is a multi billion dollar, billion dollar organization is going to operate and appreciating the complexities of that, you know, because it's not a machine that we're dealing with. And I've dealt in manufacturing environments, and those are also extremely complicated. But when you get humans involved in the situation, it's really complicated and the context is key. And so the more that I look at specifically agile, which I'm a big believer in the foundational principles of agile, I think this is the right direction, but the industry around it and what's being sold is is doesn't kind of hue to those standards. I don't believe and just like frankly, if we're speaking, you know, honestly, the T QM days, the process reengineering days, the Six Sigma days, whatever fad, you can mention the outcomes, I think we're generally disappointing to the various Businesses that implemented them not that there weren't successes. And I think we're seeing that now in the Agile space as well.

Rick A. Morris  7:06  
Well, so let's back that up and deconstruct it a little bit first, whether it's t qm ITIL, agile, Six Sigma, it's all plan, do check act. I mean, Pim Bach is doing that, is doing that. I mean, it's, it's all we're gonna plan, we're going to do it, then we've got a measure, and then we're going to act upon those measurements and deviations right there. Right? Plan, do check act. So that's why I always considered a fad. But I think my biggest determining factor of whether or not I really believe in what's going on, is whether is the first step that suggested and if the first step is suggested is we got to train everybody in the organization in new in new words and a new lingo. Right, then you're selling training, you're not selling a product because honestly, if you do it well, you don't really have to put anybody through training. It's just you just change the underlying structure and say, This is the way it's going to be done here.

David Stackleather  7:53  
Is that fair to say? No, I think the way that I I look at these I question, especially with the Large scale frameworks and I use safe as an example not because I have any particular issue with safe, but that's the most popular one. And I asked myself, what's being sold there? What's the business model and the business model is a certification business model. And it's a consulting, business model implementation business model, but really from the the large scale frameworks being sold. It's really the revenue stream is certification, which is why you pick just about any of the frameworks, or any of the organizations providing certification. And when I first got involved in the Agile space, there were a couple you know, you had your product owner and your Scrum Master certification, you know, there was a handful. Now, there's a dozen or more for most of these. Yeah, I mean, it's just it which is is kind of crazy in a lot of ways. And so just like any other business, they're coming out with new models all the time because they want to create new features and new models they can sell and that's really exciting. It's not fundamentally about improving an organization, it's about selling the training and all the kind of add on processes. And I think you're right in the executive or a leader will see that as you know, I call it installing the agile, you know, I want to buy the agile and install the Agile as if they're buying a printer or something. Right. And because of the way it's structured and sold, it kind of looks like that. And it seems very scientific, and it seems very official, and it's very expensive, and very time consuming. And by the time you get through all this certification and relabeling and all this process, a couple of things happen either it fizzles out, and people just still use the same terms but they're not really acting in that way. or an organization will try to fool itself because once you've spent millions of dollars implementing something, you can't really admit that it didn't. It didn't work. And so now you're you're, you're kind of forced to set to say that it did work or move on and Forget about it because you don't want to admit that you spent a huge amount of money doing something that didn't work.

Rick A. Morris  10:04  
Now Dean leffingwell is is a friend of the show and he's endorsed books that we've done. We wrote a book called agile Almanac, which was scaling all the different types of agile methodologies to the to the bigger scale. he endorsed that book, wonderful person, but the certifications coming out too fast. I mean, I was certified I think in four Dotto, and it's already up to five. And that was just a few years right and your certifications no longer valid because I decided I wanted to change the model. And the reason why I changed the model is because I'm getting feedback that it doesn't work right. So it's it's, it's this constant thing, but to be fair, one of the things that you said was was Tiki and and all these things were six sigma t qm, although they seem not to work in what I think happens is I think they do work I think, I think in their purest form when when, you know, the Toyota way, right, that was the big thing. Everybody wouldn't read that book and try to implement it like Toyota did. But it did work for Toyota. It was it was amazing what they did, but I love the way that you said the install methodology. So just go get me that no, that was a whole culture built and we've got a top down and everybody was no knowing what was happening. And so I want to get some of your feedback we're about to go to break here and I want to start talking about what you call the Agile industrial complex but to leave the listeners with something here as well as one of the biggest things that I see in failures of Agile is that we don't change the methodology the executives and I see this I have a lot of coaches on the line as well that a lot of john Maxwell team coaches and when when you approach an executive they go Okay, yeah, my team needs coaching. They're like no, no, we're starting with you. Oh, no, I'm fine. I'm good. I'd you know that my team needs that I'm you don't have to talk to me. And so I'm watching you know, a team base agile get started, but still being requested waterfall reports. So when is it going to be done? how much it's going to cost, which means the organization hasn't bought in, right? And so now you've spent all this money on training, you've got this agile team running and now when you're trying to then quantify it back up to the executives They don't, they don't that coach has never done it in a large scale like that insurance company there's the person that got sort of certification hasn't led anything on a large scale where the less transform a business right So, lots to talk about lots to unpack we'll get into the Agile industrial complex you're listening to David stack leather and Rick Moore's and the work life balance.

VoiceAmerica  12:27  
Are you frustrated with the overall productivity of your project management processes? Do you lack consistency and project delivery? Our squared consulting provides end to end services to assist companies of all sizes in realizing and improving the value of project management. Whether you want to build a project management office, train project managers or learn how to bring the oversight and governance to your project processes. r squared has tailored best practices to help you in all areas of project management, visit r squared consulting.com Are you getting the most out of your project management software. In many cases, it is not the software that is failing, but the implementation limitations or processes surrounding the use of that software. r squared can analyze your current use and help improve your return on investment. r squared can also suggest the best software for your organization and goals and assist in the selection implementation and training. Allow r squared to ensure that you are getting the value of your investment visit r squared consulting.com today from the boardroom to you, voice America business network.

You are tuned in to the work life balance to reach Rick A. Morris or his guest today we'd love to have you call into the program at 1-866-472-5790. Again, that's 1866 For 725790 if you'd rather send an email, Rick can be reached at our Morris at r squared consulting.com. Now back to the work life balance.

Rick A. Morris  14:12  
And we're back to the work life balance on this Friday afternoon visiting with David stack leather. David is talking about the inevitable collapse of agile. So that obviously piqued my interest. And I'm excited to have you aboard the show. One of the things that you brought up in in some of the pre interviews is you talked about the Agile industrial complex, can you can you describe what that is and what you're talking about there.

David Stackleather  14:33  
So this is the most visible aspect of this are the certification organizations, you know, the scrum.org and the scrum Alliance, and then some of the framework vendors safe and less than those kind of things. And that's even in the past couple of years that's kind of exploded. Even from a framework perspective. We have Nexus and others that have popped up and you know, I think as we talked about Before the break, a lot of this stuff is based on the same set of principles. It's just kind of a re mixing of it doesn't really bring anything new. And so this creates this process where there's an industry that's selling something to people. And there are multiple customers in the industry, which is kind of the complexity of it. The certification is one component of it. And those customers are employees, and folks who want to get into a job or a career. And the certification is just like in you know, the project management space, you had PMP certification, this is like that, but just worse than that, there's so many more. And the employees and the workers feel they have to become certified so you have a ready made audience. Hiring managers are part of this as a customer of this complex because hiring managers are looking to hire a fairly complicated skill set and a lot of these roles are Scrum masters and amazingly complicated skill set to hire for. And so as a hiring manager, it's much easier for me to simply Do you have a CSM and then I'll hire a CSM. And then, you know, just like in the old days where nobody got fired for buying IBM, you could say, well, nobody gets fired because you hired a CSM, they were certified, but nobody knows really what that means being certified. And you have executives who are for various reasons, some of them real, the performance of their organization isn't where it should be. And they're looking to change or they just want to be in on the latest fad to tell their friends that, hey, I'm an agile organization now. And so they want something to buy and install. And a lot of these large frameworks that come along with the certifications is something they can buy and feel that they can install. And what's what's fascinating, you said something before the break about, you know, it does work in certain contexts and stuff. And you mentioned Toyota and I totally agree. Now, the interesting thing is there's only one Toyota in the universe, right? And so the you know, the context is key there and in Toyota the, you know, executives were really bought in and continue to be really bought into the concepts and the philosophy behind it and the culture and that organization has built up over time. But you can't simply say to a, you know, a financial services firm be like Toyota, that just doesn't really work. And so a lot of this, this industrial complex is really about selling pieces of this to different customers. But it's not about fundamental transformation, because you can't, you can't just buy that in a box and install it.

Rick A. Morris  17:29  
Now, they, but they're sold it, that they're sold, what they they're sold a bill of goods, you write this, you will get this

David Stackleather  17:36  
there sold this as a bot and the more you know, kind of the more complicated it looks, the more pieces the more titles, all that stuff, the more it kind of makes sense to the existing narrative, which is really a false narrative, but they you know, they think there's just some tweak and it from an executive standpoint, they're really saying I want somebody else to change, I'm not going to change so give me something that I can install that will have these other people change. I think there's also something that's happened recently, a couple things that's happened recently. And by recently, maybe in the last decade. One is that you have a lot of executives and organizations that have found themselves in a position where they have to understand technology. Because their business, everybody relies on technology. You know, when I was in the financial services space, you would have executives talk about, I don't really care what happens in the technology department. And you know, I tried to tell them, if the technology stops working, this organization dies in 24 hours, right. And so there's no distinction between the business and the technology nowadays, but you have a lot of executives who this is new for them, and a lot of them don't really want to be involved in to the degree that they need to be. And so this this kind of scratches an itch to say I can, instead of understanding really what's going on there and be a part of that solution in the context of my organization and change myself and change how my my leadership team operates. I'll just buy this box of gizmos and have you guys install it. And it'll just it'll change the organization. But it fundamentally is an impossible ask. The other thing that's happened, you know, in the past maybe three or four years, I would guess is the very large consulting houses have come into this, they see this, the buzz generate, and large organizations, you know, on the kind of late adopters. And so that's an opportunity for them to just kind of, here's all the people, we're going to sell you thousands of hours of very expensive consulting folks to go in and transform your organization. And all they're doing is implementing the box of gizmos that you buy from the framework, implementing it without context within the organization. And they'll spend several years doing that. But fundamentally, your organization won't change because the culture didn't change the way the leadership operated, didn't change. And unfortunately, eventually all the employees will figure that out much quicker than the leadership And they'll become kind of upset that this is another fake change, which is probably one in a long series of fake changes within most organizations not all I mean, I want to be careful that there are there are definitely organizations out there that are trying to change and leaders that are trying to change but if you look at a percentage of organizations, I think that's a pretty small percentage.

Rick A. Morris  20:21  
And so so it's some it's important for us then to focus on the why of the change the one of the big things and misconceptions of Agile is if I install it will be faster. It's just it's it's, it's no different than saying I'm going to hire a personal trainers so that I can run faster, or that the day that you hire the trainer, you're running faster, right? That's Yeah, months of hard work and months of transformation in changing. And so I think the other thing is, is if if you're going to agile because you're having delivery problems and a lack of trust in the team and a lack of leadership, agile is only going to exacerbate that it's only going to make it worse because It requires more trust and more cohesive team units and stuff to be really effective. Right. But I recently had a client that that was sold the safe bill of goods essentially they wouldn't say but almost every single one of their projects is commercial off the shelf installations. Hmm. So now you're at the mercy of the vendor, and they're trying to be agile, and they're trying to do pies and it wasn't working for them. And I always said, so just don't do that ceremony. Right? Oh, well, you know, it's prescribed is what moves. But we have to recognize that these are just like the Pim Bock if you look at PMI in the pen back then that was a methodology but that doesn't mean I do every single one of those processes for every single project methodology. This isn't a doctor prescribing a treatment. If you don't do the treatment, you're gonna die. Right? This is this is somebody going you know, you may want to eat a couple less potatoes a rake, just gotta lay off the potatoes like a little bit there. Right? That's more of what it is. So So why, why is that difficult though for executive To just comprehend why we see it because we've been through it all. Yeah. Why? Why are these executives just buying it?

David Stackleather  22:08  
Well, I think part of it is that, especially in large organizations with a big hierarchy, most executives don't interact with the people who are at the interface to their customers. So I read somewhere, I wish I knew who had written it. But they said, there's a developer, a programmer has more in common with this with the CEO than any kind of mid manager does, right? Because they both just want to get something done at the end of the day. But most CEOs don't talk with the developers who are writing the software for their customers. And don't sit down and listen to what their problems are. And therefore, they have all this middle layer, this information that's being kind of squeezed the value before it gets into a PowerPoint and it gets into the boardroom. And the middle layers that are squeezing that information out are not doing it maliciously. They're been trained through the culture to do that. To what to expect, how to communicate. The one that I always kind of laugh at is I'm always admonished for providing too much detail to executives. You know, they don't want to go into that detail and say, Well, I understand they don't want to have a five hour long, you know, speech about something. But these are smart people. I mean, these are these are not dummies, why are we dumbing down everything? Why don't we have real conversations about real problems at the interface of the customers, which is the only relevant interface in an organization. And so I think that, because the executives and leaders have separated themselves, they don't go and sit down with developers and customer service people and the guy at the dock, unloading the boxes. All these folks know exactly where the problems are. And they'll tell you now, they may not tell you in the you know, most flowery language, they may not be polite about it, but they'll tell you what the issue is and you should be thankful if that's the case, but too many executive Don't do that. And I've seen in my career, a couple who are really good at that, and would know what was going on and could could interface with the organization at all levels in a way that made sense. But most are just kind of trapped in their daily meeting structure and PowerPoint decks, which there's no info. There's no valid information coming from that process.

Rick A. Morris  24:21  
yet. Carly Fiorina actually attributes a lot of her success, who first female CEO of a tech giant HP, to the fact that she would, she talked to everybody, she'd sit down with anybody and hear them out and got her best ideas from the lower level. There's the thing that I've done, I've dubbed it the fuzzy middle layer, you're talking about the middle layers, I call them fuzzy because that's where stuff just gets fuzzy. Right? But it's interesting, I was part of a project at at CAA, where we were developing an application on top of clarity ppm. So your total project portfolio management's got all of your statuses. And we built an app for an iPad, where you could do your strategy, but then you could tie your Strategy directly to the project. So you could see in a dashboard, how it was beautiful, but it bombed because it bypassed the middle layer, because it was getting the project managers were inputting data directly into the system. And that was feeding right up to the strategic plan, right. And there was no context being given by the fuzzy middle layer. And so it caused a lot of concern. Right. And so the project managers loved it. The executives loved it. The fuzzy middle layer, hated it. Really interesting to watch. Yeah, but why do we Why do we think executives stay so far removed? I've met with CIOs that literally just they're like, they like us. They like us, these consultants who will give them that level of data because we're the only people giving them real actionable data in the system. How do you How can they not see that culture getting for?

David Stackleather  25:52  
Well, they, you know, a part of it and happens over time. And so it's it's the old boiling frog problem. It's not a quick thing these cultures are generated over time. And it makes sense. It's logical that as, especially as an organization grows, you're like, Well, when I have, you know, 10 people in a room, and we're a little 10 person company, we don't have a lot of hierarchy. We're just in a room, we're talking, everything's flowing. If we have 1000 people in the organization, as the leader of the organization, I think, well, just mathematically, I can't deal with 2000 people. So it makes sense for me to create a hierarchy, rather than creating kind of a network process, which is a structure that you might want to look at, rather than a hierarchy. But the default is, well, I have a problem. So I need to hire a role. I need to have somebody to manage these people. And before long, you have all these structures. And there are a couple of things that happen, I think, to most executives, one is they get into a cadence, it's the you know, the old maker versus manager proc process where you know, managers can split their time in half hour increments, but if you actually build anything for a living, that's not possible you need to have long periods of time, financially. interrupted, you know, programmers don't develop software and half hour increments, right. And so they get into this cadence where it kind of makes sense you're having these meetings, you're think you're getting the information, it's very quick to fool yourself, that you have some line on what's really happening because that data is all being translated based on what the middle layer thinks you want to hear. And that middle layer is watching the executives reaction really, really closely. And so I think what a lot of executives don't realize is when they have a reaction, that's maybe a poor reaction, or they push back against something or they complain about something that that almost has a 10 x effect on the reaction of the middle layer, and it just makes the situation worse. And I've seen that time and time again, with like executive reaction in a meeting where somebody's presenting some data, which is valid and it's not good data. It's not good information. We'd rather not to be that way. And the executive reacts and I don't like this And the reaction is kind of a 10 x effect to the middle managers, and therefore the next meeting is even more watered down. For sure. And, you know, one of the things that has amazed me, especially in large, very large, like financial services organizations is the disconnect in, in opinion between the executives on what they think the worker level in the organization is, how good they are, versus how good they really are. And so they have an opinion that will our programmers aren't very good. That's why our software kind of goes down or whatever. And if you sit down and talk to the developers, you know, you're like, these are really smart people. These guys know what's going on. And you're lucky to have this kind of staff but the executives have never really talked to them and interacted with them and understand how many of their decisions which they don't even understand the impact of their decisions, kind of causes problems within the systems of the organization. They kind of they kind of lay the groundwork for their own torture in the future, but they just don't realize it. Because fundamentally, they're talking to people because they think that as an executive, my job is to sit in meetings and listen to PowerPoints and issue directives and that sort of thing rather than get lazy, right? You get lazy and you get used to that process. You know, we're all human. We get used to that this is kind of nice coming into the office, having my coffee, having somebody come and you know, give me a PowerPoint deck me making some kind of pontificating on it. The other thing that's dangerous let's let's pause right there because what I'd like to do is give some tips and tricks around kind of preventing this happen, but we do need to get to a break really quickly and we'll get it right on the other side of these commercials listening to Rick Morrison the work life balance.

VoiceAmerica  29:44  
Are you frustrated with the overall productivity of your project management processes? Do you lack consistency and project delivery? Our squared consulting provides end to end services to assist companies of all sizes in realizing and improving the value You have project management. Whether you want to build a project management office, train project managers, or learn how to bring the oversight and governance to your project processes. r squared has tailored best practices to help you in all areas of project management, visit r squared consulting.com. Are you getting the most out of your project management software? In many cases, it is not the software that is failing, but the implementation limitations or processes surrounding the use of that software. r squared can analyze your current use and help improve your return on investment. r squared can also suggest the best software for your organization and goals and assist in the selection implementation and training. Allow r squared to ensure that you are getting the value of your investment visit r squared consulting.com today it comes to business you'll find the experts here voice America Business Network.

You are tuned in to the work life balance to reach Rick A. Morris or his guest today, we'd love to have you call into the program at 1-866-472-5790. Again, that's 1-866-472-5790 if you'd rather send an email Rick can be reached at our Morris at r squared consulting.com. Now back to the work life balance.

Rick A. Morris  31:31  
And we're back to the work life balance on this Friday afternoon. Afternoon. We're visiting with David stack leather and talking about agile and how you what we may see as the inevitable collapse of agile and right before break. We were talking about 10 executives being removed. And you made a really good point, Dave, in talking saying that. There's opinions that are that are different in the opinion of the developers, the executives are is really based on that fuzzy middle layer that we're talking about. I always like that as executives when I go When I say well, who's who do you think makes the strategic decisions of this company? And you know, of course, well, I do, you know, this is what I get paid for, and I go, so do you have a prioritized list of projects? And are you resourced against those? And they go, No, I go, well, then you're not making the strategic, you may make the strategic direction, you're not making the strategic decisions, because the person that is that DBA in the corner that just got asked for things to do. And because there's no clear direction on what I should do, first, they're making the strategic decisions of what they're doing. And I've got 884 different strategic decisions being made a day. So that's, that's, it's an interesting concept, but how do we what are some tips and tricks to kind of help that or how do you deal with those opinions?

David Stackleather  32:44  
So So one, and you know, agile really helps in this way, which if if executives and leaders would accept this is the idea that if you operate off a prioritized backlog of things that you're working and whatever the granularity of the backlog is, you know, But certainly at a higher level about what the outcomes are you need for your business. And the idea of forcing that prioritization. So you don't have 10 number ones, which is usually in large enterprise, everything is important, we need to have 10 number ones. And, you know, the way that I describe it to them is Look, when you when you come into work in the morning, you have to get dressed, and you have to get your your set appearance to show up at work. All that stuff's important, your pants are important, your shirts important, everything's important, but you have to have a priority to get it done. You can't do it all at the same time. And so that's fundamentally the same way that we have to operate in these these projects on these efforts. One is to to the one decision is what is the most important thing at this moment in time and if you can, as a leader make that decision, then you need to figure out what information who do I need to talk to, because I think a lot of organizations kind of outsource that work just like you're describing to the to the layers the programmers and the DBAs in the to mid level managers to make those decisions, and there's 1000 decisions happening. And probably with most organizations 60% of the work is not really relevant to the success of the organization. It's kind of busy work, it'll be thrown away, or it doesn't really matter at the end of the day, but leaders are not making those decisions, because they're not having a hard discussion about prioritization, which is hard. I mean, I admit it, you have to make decisions about what you won't do, and what you will do. And that list should be fairly small, and it can change over time. But too many love to pass that

Rick A. Morris  34:33  
it's there.

David Stackleather  34:34  
Right? But that's the you know, as you just described, that somebody is making a decision. And they're making that decision for you. And you've just outsourced that decision to somebody you don't know. And you don't know why they're making that decision. And most likely, the decisions are not going to be consistent for delivery of some value that the organization needs, which is why you have so many organizations spending what seems like more and more money. Especially on technology efforts, but they see what they get more or less and less value out of the other end. And there's lots of reasons for that. But one, I think, is because of this lack of really, if you're an executive, the one thing you need to do is prioritize what's important to the organization, what what really needs to happen? And what are the goals of the organization and have a feedback loop to understand if you've if you need to change your decision, and very, very few leaders have that process. But the Agile kind of guides the way if you if you just take the kind of baseline agile of a prioritized backlog that concept and approach can help quite a bit, but too many don't want to have those difficult discussions because it is difficult. But let's Yeah,

Rick A. Morris  35:42  
let's talk about that first and prioritize backlog and I'll give you an example working with an executive recently. It first of all, the term agile coach, I hate that it's so why because I am an agile coach. But I don't, I don't install teams and I don't do whatever do is I work with executives to teach them how to think in an agile format? So for instance, you build me a data warehouse. Okay, well, that's fine. But what are we going to do with it? Well, you know, I don't know, I just need all my data in one place. And I'll tell you, no, that's not what we're going to build. And so I was doing this with an organization. And it's like, so what are we trying to get at? Well, we feel like we need to do local market plans. Okay, great. So how's the local market plan work? Well, we get our 50 accounts, and we get information. So great, let's, let's take six people, we'll do 300 accounts, we'll clean them up. We'll do this all manually to see if we're going to get a benefit. Before we go by Big Data Warehouse. I just kept asking questions. So I was like, so why can't we just take the 50 accounts and finally got the executive to go, Well, how do I know those are the best 50 accounts? And I was like, there's your first agile question, right? How do we know? And what are we going to use? So what are we going to use to determine it comes back? I don't know. That's why I needed their data warehouse to give me all the data and I was like, even if you have all the data, you're not going to know so Let's start here. And that's what an agile coach should really do is really force you to the value conversation and asking really good questions to be answered versus, well, I want to build a data warehouse and we're agile, so I should get it in six months instead of a year.

David Stackleather  37:14  
Right? Yeah. And I think it's, it's interesting, because as you're describing that, you know, if you take, take it out of the Agile coach or an external party, like yourself having that conversation and put an employee in that chair, they wouldn't get past the third question, right? What you know, they would just kind of be like, Okay, I'm done talking about this, just do what I told you to do. I have another meeting to go to. And so, you know, I think too many. I give you an example, a personal example, I've had somebody who's worked for me three companies over my career. And this individual will tell me when he thinks I'm going loopy, in a nanosecond, a very straightforward and sometimes it can be a frustrating conversation. You know, it's like he keeps pushing, pushing, pushing I've always valued that you have to have have to have people in the organization or people that you trust to be able to push back on the process or ask the 20 questions until you get to something that makes sense. And too often, executives or even mid level managers don't want to allow that. They have a very short fuse for that. And I think because it's part of it is because of the internal PR machine in your head that a lot of managers have when they're not involved in the day to day, and occasionally they'll come up on a situation. And they'll say, they'll make a comment, oh, you should do it this way. Or have you thought about that? And they're right, and the employee says, Oh, we didn't think about that. Sorry. And what people don't realize is the manager or the executive in their head, the PR machine in their head is saying, oh, you're a genius. Look, you just figured something out. You're a genius. You're a genius. And it plays in their head continuously and then they they end up believing their own internal PR when it's not just because you don't not involved and you just showed up and you saw it from a different angle and you made it statement and it seemed like you're a genius, but it's just the context of where you're coming from. It's not that you have any greater knowledge than your employees. And so I think they train, you know, and we all do this get trained over time, if we're not actively pushing back against this process, where we're shutting down the conversation that is so critical. But But oddly enough, we'll let an external party do it. If you bring in an external consultant, you'll let them get away with all kinds of stuff. Not always. There's always Oh,

Rick A. Morris  39:29  
yeah, I've been I've been escorted out a building. Yeah.

David Stackleather  39:32  
I mean, you have to kind of judge the context. But you can get away with a lot more as an external party and ask more uncomfortable questions and just about any employee in the organization, and that shouldn't be that way. Right? I mean, from because there's a lot of good knowledge in organizations that they're missing.

Rick A. Morris  39:50  
So we've got a couple of minutes left about two to three minutes left in this segment, what should executives really be focused on if agile is not going to work? What What should work what should they be? focused on.

David Stackleather  40:00  
So I think they shouldn't be focused on, you know, implementing a framework or having everybody get certified. They need to not that these things are not useful. These components of what we call agile are very useful. But executives to understand what's the context of their organization? What's the culture of their organization? What is the the goal, the optimizing goal of the structure of the organization? What do they need? What problem do they need to solve in the next several years, five years, and look at maybe tactics or structures that they can implement and test and have a feedback process but not to buy something that they're going to install? A large framework, starting to change titles, get people certified, really until you as a leader say, what are we trying to accomplish? And how should we change our work and there's a lot in Agile that'll inform on that and it's very valuable, but you shouldn't be your first step should not be to call up a consulting firm and say I want to buy the agile and to install the agile, because that's all that's inevitably going to fail. And most organizations, that's what they're doing. But the hard work is to understand your organization, go talk to the developers, figure out really what you really want to accomplish as an organization, maybe you don't have a problem as an organization, frankly, you might be working just fine. And agile is not the right thing to implement. And so that's the real process is to have those discussions and questions at all levels, not just in the boardroom.

Rick A. Morris  41:33  
I think I think one of my biggest suggestions I gave when we start talking about agile as if we're going to deploy agile, you need to start deploying agile yourself as an executive even in the way that you're bringing in people. So what's the value that you're going to negotiate in versus, you know, and that's my frustration with some of the big firms and in Look, they some of the big firms do a lot of great work. They do, to be fair, but then, you know, we have our run ins as consultants. I you know, I was an expert of this software for 20 years I was there when it was built. And I'm working with the lady that actually wrote the financial calculation portion. We're trying to solve something for a client and it's not working the way we want. And this guy comes in, sits down with the software for two minutes, and it gets a meeting with the CIO. And now I'm having to sit with the CIO, because this guy thinks he solved the problem. It's taking a Nic. Again, this is not I wouldn't suggest this. But again, I was an external consultant was frustrated. Plus, I'm Italian. I said, Look, I read all about your business on Wikipedia last night, I know how to solve all your problems. And the guy goes, What are you talking about? I said, that's what this joker just did here. I mean, you've got the people who wrote the software in the building. Let us finish this out. Right. He has no idea what he's talking about. But unfortunately, that's what we deal with in the consultant game. Right?

Unknown Speaker  42:44  
Yeah, absolutely. Yeah.

Rick A. Morris  42:47  
So we're going to go ahead and take our final break right here. We're going to come back with David's deck later, we're going to find out how to get in touch with them, as well as what are some of the best advice he's ever received. Stay tuned right here. You're listening to Rick Morris and the work life balance.

VoiceAmerica  43:04  
When it comes to business, you'll find the experts here, voice America business network. Are you getting the most out of your project management software? In many cases, it is not the software that is failing, but the implementation limitations or processes surrounding the use of that software. r squared can analyze your current use and help improve your return on investment. r squared can also suggest the best software for your organization and goals and assist in the selection implementation and training. Allow r squared to ensure that you are getting the value of your investment visit r squared consulting.com today. Are you frustrated with the overall productivity of your project management processes? Do you lack consistency and project delivery? r squared consulting provides end to end services to assist companies of all sizes in realizing and improving the value of project management. Whether you want to build a project management office, train project managers, or learn how to bring the oversight and governance to your project processes, r squared has tailored best practices to help you in all areas of project management, visit r squared consulting.com.

You are tuned in to the work life balance to reach Rick A. Morris or his guest today we'd love to have you call into the program at 1-866-472-5790. Again, that's 1-866-472-5790 if you'd rather send an email Rick can be reached at our Morris at r squared consulting.com Now back to the work life balance.

Rick A. Morris  44:50  
And we're back to the work life balance our final segment this Friday afternoon still visiting with David stack leather David what company did your own consultant you have your own firm Yeah, I have my own, you know, one man operation called scale frameworks kind of as a joke about the Agile frameworks. Well done. I like that.

Unknown Speaker  45:11  
I was I was available

Rick A. Morris  45:14  
right out of people get in touch with you, how do they find you?

David Stackleather  45:18  
So the easiest way to get in touch with me is either at David at scaled framework comm if you want to shoot me an email or I'm on LinkedIn, at LinkedIn slash stack leather linkedin.com slash stack leather. I'm only one of two David stack leather so you'll quickly find out which one it is the other ones my dad, he works for the federal government, that's not me.

Rick A. Morris  45:39  
Well, what would you say is your your ideal client?

David Stackleather  45:42  
My ideal client is someone, a leader in an organization who really wants to make change. Who sees that the situation is changing maybe in their industry, they're not delivering as they they used to. They're not satisfying their customers. They don't really know What the what the gears are how the thing needs to change, but are open to anything and open to dealing directly with people who do the work open to changing hope and open to being in very uncomfortable situations. And those are the best, like if we can just have a real conversation and maybe it gets a little heated but we're okay at the end of the day, we're moving forward and trying to do the best thing for the organization and and the folks that rely on that organization, both employees and customers. That's the best situation I really get energized by those kind of situations. I'm not really big on politics and hierarchy and let's talk about the org charts and that sort of thing. That's, that's not really something that I was interested in.

Rick A. Morris  46:46  
So what some of the best advice you've ever received.

David Stackleather  46:48  
So probably the you know, as similar to the kind of the internal PR machine I as I mentioned before the break I had an executive that I worked for for quite some time and he Told me during a dinner or something, always remember, you're not a genius, which is shocking to have somebody about seven rungs above you on the org chart. And we talked quite a bit about that. And what he had said was that there's so much information there's the world is so complicated in a lot of ways you can't possibly know everything, you have to rely on other people. You have to be open to new information. And no matter how smart you are, how smart you think you are, you have to know and believe that you're not a genius. And you're not always going to have the answer. And for two reasons, one is because you're not always going to have the answer. The second is even if you have the answer, other people have an ability to kind of mess that up for you. And so you have to make sure that everybody's on board and nobody likes to work or deal with somebody who thinks they're a genius. It's annoying. And so I think I'm very smart. I have an ego like anyone else, but I try to actively tamp that down. I think it's important especially the highest You are up in a hierarchy, the more kind of good luck you've had in your life about moving into a position, having the right education, having the right parents, whatever the situation is, is having a little humility and understanding that the world is very complex. And you don't have all the answers. But if you get enough people together and have a good conversation, you can probably find a good solution. And that's the best advice. And I've tried to increasingly improve on that over the years, this probably was 20 years ago when I heard this message. And that's, you know, led me down a good path. I think over time, where I can I can at least be proud of what I've done. And I'm not ashamed of anything that I've done in my my career.

Rick A. Morris  48:46  
Do you have any final thoughts or things that you'd like to share with the audience?

David Stackleather  48:50  
Well, I would just say that especially if you're involved in an agile transformation, if you've got your CSM, if you're in an organization that uses is kind of struggling is to kind of throw away the idea about the certifications and go back to the the actual underlying data. And what I mean by the underlying data or the underlying information is the the old stuff like Deming, the number of times that I'm in a room of executives and ask them if anybody know who Edwards Deming is. And I get maybe one hand at a 40 cola. You know, it makes me really sad. And this is what I mean about this. We know what to do in these organizations. We know how people work we know how leaders and people on the factory floor or the call center floor ideas that really operate but we need to go back to this information so kind of throw away the new website stuff and go back to the lemmings and McGregor it's not hard to find all these people. And and you'll be surprised when you read the kind of the old knowledge that we've known about this for quite some time. We have a lot of ideas, but I think focus needs to really go back and read that stuff and understand it the intent behind it, rather than kind of taking a, you know, pre written, pre installed framework or set of tactics, and try to shove them in the context of your organization, because it's just, it's just going to be frustrating. All the way around.

Rick A. Morris  50:18  
Yeah, and, again, there's gonna be something else that comes behind agile, it's gonna be the, in fact, I already heard of one friend of mine just went to Rome to get certified in this thing. And but essentially, when he described it to me, I was like, so tell me how that's different from my toe. Right? Well, this one's different because you're, there's chargebacks they're really trying to use a cost center. And I was like, right, that's exactly what I was doing. And everybody, everybody froze at the time that you were trying to do that configuration to the CMDB. Right. There was always the, the one piece of thing and there always seems to be one piece of thing and in this case, it's it's agile is the right level development of when you throw something into poi. That's always the one thing that people seem to miss. That's And strategy over versus functionality or requests or business questions, right? In this one, right, it was a CMDB. So now they've tried to figure out how to do it without a CMDB. And therefore, it's Yeah, it's it's frustrating.

David Stackleather  51:14  
Yeah, well, that goes to it's, it's a business model, and they're not realize this, they're constructing a product to sell, which means you have to change something, and you've got to have something to sell. And now you're just re, for the most part, you're rehashing old stuff in a new format with new fonts and, you know, fancy website, but fundamentally, you're not really selling anything new. And fundamentally, people can't buy something and install it and change their organizations and that that deep giveaway just is not really possible.

Rick A. Morris  51:45  
So I've had to I've had to learn how to develop analogies that I do a lot of stuff on resource management, understanding the utilization of our people and it doesn't have to be hard takes five minutes a week per person, you know, per manager really to do. But I always love We don't have time to do resource management. I'm like, well, that's like saying you're too fat to diet. It just there's nothing there. That makes sense. It's Yeah, it is what it is. Right? Well, David, I've appreciated your time partner, I appreciate you coming on the show and sharing your expertise with us. And we wish you luck in the future. Thank you very much. I've enjoyed it. And so for everybody else hanging on, we're going to have West bush on the show next week. Wes is a best selling author of product lead growth, these renowned product lead growth pioneer, it says in his bio, he's ridiculously tall, so we're gonna have to figure out what that means. But looking forward to have Wes on the show. We've got some great guests lined up. We're actually I think, booked out into July now for the show. So we've got a lot of great information coming up. We'd love for you guys to give us feedback. You can do so at Rick A. Morris on Twitter. You can find me on LinkedIn and Facebook at Rick A. Morris, and you can always send an email to our Morris at r squared consulting comm or Rick at Rick A. Morris calm and until next Friday. We hope that you live your own work life balance and stay tuned right here to voice them. America business for our next fantastic show.

VoiceAmerica  53:06  
Thank you for joining us this week. The work life balance with Rick Morris can be heard live every Friday at 2pm pacific time and 5pm eastern time on The Voice America business channel. Now that the weekend is here, it's time to rethink your priorities and enjoy it. We'll see you on our next show.