Operationally Defining

Video Activity
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *

Already have an account? Sign In »

9 hours 53 minutes
Video Transcription
Hi, guys. Welcome back. I'm Katherine McKeever, and today we're gonna go over operationally defining value at so we have been talking about voice of voice, of the customer, voice of the business voice of the process. So now we're gonna talk about defining the value, add from an operational perspective.
So you you remember in yellow Belt with the quite a bit of conversation around
value add and non value add. And as we do our process mapping, making sure that we look at every single step on determine if it is a value add or a non value add step. If this isn't sounding familiar, you should go back to your yellow belt course and review the modules on value. Add non value add.
You're going to need it for this module.
So if we think back to our history of, um, models, we know that the Toyota production system is basically the forefather of Lean and Six Sigma as we understand it today.
So I actually wanted to go over a passage that I highlighted out of the Toyota production system when I was learning my lean and six Sigma because it felt so powerful to me.
So the first part is it is irresponsible to allow non value adding work to continue,
period. There's no caveat, There's no but there's no except when
just a flat statement for the organization. It is irresponsible to keep non value add work going
the next one jumps out. It jumped out at me a lot, too, because it says this is disrespectful to the employees and compromises our competitive position, period. So if you remember back to Yellow Belt when we were going through the waist down time
and we talked quite a bit about the controversial eighth waste the waste of in select
this is where I pulled together that this is very important that we need to make sure that we are valuing our employees. In addition to that culture of kaizen. Where we talked about employee collaboration is one of the three things that you need to have to have your culture of ongoing continuous improvement.
The last statement is by ensuring that all work is value added. We build employment security into the production system, so this is really interesting, especially if you think about today's day and age where people don't stay at jobs between what? A production system
not only said, let's value our employees,
but let's build a workplace where our employees feel that they have security. This later becomes a giving their best to the organization, fully participating in the culture of kaizen. So this is an aspect of cultural piece.
If you remember, Dr Demming was considered a folklore hero because he said that high quality ultimately creates jobs.
This is where you see some of that manifesting
so with that. So when we talk about value at a non value, add what we didn't yellow boat was at the process level. We looked at every single step, and we said, Is this value add? Is this non value at Does this meet the three criteria customers willing to pay for It
is not rework and fundamentally transforms the product or service at some level.
Now we're gonna talk about operational value, add which is where we're going to step it up a level on. We're going to look at the entire value stream. So if you think about the process level work that we did in Yellow Belt is a silo. It is one chunk. If you remember when we did our sigh pock lecture.
We said that a value stream is basically sigh pox stacked on top of each other
so that we now understand how are outputs and suppliers become inputs and customers for the next chunk of the organization of the next chunk of the value stream. So operationally thinking about value add is thinking about that big picture. How do the silos interconnect
with each other so that we have a cohesive understanding of our organization?
This requires the insight of the voice off. So when we talked about it at a process level in our yellow boat, we said, We need to understand what the customer wants Now I'm saying we need to not only understand the customer, but also the business and the process,
because these become factors as we're starting to articulate what is value add
at our organization level or about Eastern.
So the way that you think about this is the value proposition. So if you remember when we were talking about our customers, we said that a customer need is what initiates the relationship between a customer and an organization.
The value proposition is articulating that customers need or being able to say definitively, This is what my company does for our customers. So we're going to do an imaginary Sai Buri one This is I've entirely made up for I've made this up. I'm not speaking for them.
But we're going to say that the cyber is value prop, maybe
to provide high quality economical training. So pretty straightforward. Sounds a lot like a mission statement. If you think about it as an organization that has your mission vision values painted on the wall, you wanted to be fairly straightforward. This is why customers come to cyber. This is why you the student, come here
because you want the best education.
Ah, a reasonable price or free. Um
so with that now we have to ask ourselves, Why do we care? Why does it matter? So remember, I just I just talked about how this articulates our what starts that relationship. What do we bring to our customers that meets their need? This now gives us context for our larger organization. This gives us
the framework that we need to make decisions as to whether or not
steps that we do in our process. Our value add at an organizational level rather than just a process level. So we're going to go through the classic classic Example of this. Eso are classic argument is the Q A department
from a process level value and non value add an eight waste perspective. The Q A department is entirely entirely non value. Add. It exists to confirm that we do, in fact, do our jobs.
And the argument back would be if you build a process that doesn't allow for defects, you have no reason
to need to do quality assurance or auditing because you know there are not defects in your process. So at that level it's totally non value add. But when we look at it in an organization or value stream level, let's think back to the CyberRays value proposition of high quality economical training.
What may be high quality for me as a lean six Sigma class may not necessarily be high quality for your cybersecurity, Um, class. So now you're Q. A department is knitting together multiple, different processes, so the process for lean six sigma compared to the process for cybersecurity,
you have a Q A department, that kind of
bridges, both of those So it, in fact, while at a process level, is non value, Add at an organization level is value add. So as you are going through your work as a greenbelt doing your current state process map
evaluating whether or not each of the steps are value add non value add. I expect you to have this organizational context because you have heard
the voice of the business, the voice of the process, and ask yourselves before we say this is non value add and we're gonna cut it out. Is this value add from an operation standpoint? So from a bigger picture. So we need to consider that before we hack these things out
so really, really quickly to kind of pull you guys back to value at non value add what are the three criteria for an activity to be value? Add
Okay, I am hoping that you said customers willing to pay for it must change the product in some way and must not be reworked. So remember, from Yellow Belt, if this all sounds unusual, go back and check your value at non value at these, this definition is still very relevant
to the work that you're going to do is a greenbelt. We've just added to it and said, Not only do you need to look at it from a process step perspective,
you also need to look at it from an organization perspective. It's very helpful when you have all of the key stakeholders on your team to make sure that you get that viewpoint. But so today we went over operationally defining value. Add so that big picture definition, how we use the voices of
to come to whether or not we do or don't need to do activities
and our next lecture. We're going to go over the house of quality or quality functional deployment, and I will see you guys there.
Up Next