Every dollar spent on transformation without a result is a dollar at risk. Fix the costliest problem first, in a slice small enough to measure in 90-days. This way your money follows proven value instead of a projection.
Video Transcript
Len Greski
If you can address those high frequency problems, you’ll get a lot of leverage in improving the performance of your business without having to immediately fix everything.
I make such a big deal about monetizing the value of work in my most recent writing. But that fixing your own stuff, I like to call it get off the Pareto chart where Pareto chart is a common graphic that shows problems by frequency in categories of problems, how frequently they occur, relative to a cumulative percentage of all problems where the idea is like the Pareto principle that 20% of the things cause 80% of the problems.
If you can address those high frequency problems, you’ll get a lot of leverage in improving the performance of your business without having to immediately fix everything.
When you focus on fixing your own stuff, other executives aren’t going to get angry because you’re admitting their performance improvements needed in your area. In fact, a lot of your colleagues will be happy to point out where your problems are. If you can enlist them in helping you resolve the problems so that you’re not on the Pareto chart anymore, then you have the ability to influence other stakeholders.
Stacy Gordon
Sure. I think that’s a foundational message that most executives should live by get your house in order and by doing that, you’ll lead by example and you can be more impactful again at your boundaries or beyond your own job.
So with that said, there’s got to be people listening today that have a budget problem right now that probably have taken away some tips from our conversation and are wondering where do they start? How do they change the culture? Is it a cultural change or can it be a small change, kind of like what you were just talking about to really start to see the impact of a value engineering analysis within their own organization?
Len Greski
Well, culture is never the right place to start because culture is an effect, not a cause. As a sociologist, I define culture as a set of shared beliefs and practices that make up the informal rules for how people in a group interact. And because it’s informal, it’s something that takes shape over time and is caused by other things.
So I always start with there are two primary drivers of change in life. One is a compelling vision and the second is pain. There are not many compelling visions. The second driver of change is pain.
People, when they feel enough pain, when the severity of their pain exceeds the fear of change, then they’re ready to have an admission of need. And today there are a few compelling visions.
And in fact, the most commonly used business example of vision is John F. Kennedy’s goal to send a human being to the moon by the end of the 1960s. Yet the reality is that was actually a response to pain, the pain of having been beaten in space by the Sputnik satellite in October 1957. So if even the shining example of vision is actually a response to pain, then you’re more likely to make change happen when the pain is sufficient to create an admission of need.
And my server story about the obfuscated infrastructure costs is a really good example of pain driven change because my company was six months into planning for a corporate split and every dollar of cost in the parent company was going to be allocated to one of the two resulting companies.
And the CIO of my division, the business unit that I was currently then working in, had been bragging about how his IT expense as a percentage of sales was only 1.5%. And in a manufacturing business, that’s really good. But since the infrastructure was centralized across all the business units, those costs weren’t charged to his budget.
And I was like the proverbial prophet out in the desert in a hair shirt yelling sinners repent, repeatedly warning my manager about an incoming tsunami of infrastructure costs. And I was basically ignored until month 11 of a 12 month divestiture process where my boss’s boss was told to absorb hundreds of millions of dollars of infrastructure costs into his budget, moving his IT as a percent of sales metric from 1.5% to 3.9%.
And all of a sudden the “time I had been wasting” on understanding our cost structure wasn’t so wasteful anymore. And so there’s a piece of being able to see where the puck is going to know where the pain will be to be prepared with a solution. And all of a sudden, my math was instrumental in taking scores of millions of dollars of costs out of various cost structures in that business unit.
Stacy Gordon
Is there a part of… You do a great job all the time of breaking things down and this seems like it could be an extraordinary large undertaking, but can one person start small, like a cross-functional team of one small pain point to start exercising those muscles on how to think differently? I mean, could change start to happen as small as that?
Len Greski
Absolutely. I mean, in fact, at LiminalArc, when we work with our clients, we very frequently structure change, whether it’s in an organization or product development or building a business capability into vertical slices so that you can deliver meaningful units of value every 90 days, like I discuss in the new software economics where you want to be able to make work small enough so that you can deliver a unit of business value no less frequently than every 90 days, generate value and then use the value generated to fund the next thing you want to change.
It’s a good risk mitigation tool as well because you can only spend so much money in 90 days, whereas if you have a 24 month project plan and if you don’t know that what you’re doing isn’t going to work until month 23, you’ve got a lot more risk hanging out there.
