5.2 Quick Hits vs. DMAIC

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 3 minutes
Video Transcription
Hi, guys. Welcome to quick hits. Quick Hits vs DM AIC. I'm Catherine Nick Iver, and today we're going to understand the difference between a quick hit in a domestic project. So you may have been asking yourself in the last module, If we're in the quick hit section of the course, why are we going over the domestic framework? And it's because
I was at a very high level.
You need to understand the D make framework toe help you decide whether or not your project or your work is going to be a quick hitter a domestic, so the rest of this section will be focused on true quick hits. But I wanted to make sure that you had the information you needed to be prepared to make a decision. Whether or not
the work you want to do is a quick hit or a domestic project.
from the beginning, what is a quick hit? So if you remember way, way back at the beginning of the course, we were talking about the differences between the lean and Six Sigma and that one of the strengths that Six Sigma brings to Lena's structure and then one of the strengths that lean brings to six Sigma
its flexibility. Ah, quick. It is the most tangible evidence of that flexibility. It is a process improvement project that doesn't utilize
the domestic methodology. So we talked about it is a very lean concept rather than a six segments concept, as you are doing a quick it. Or as you were trying to decide if the work that you want to do is a quick it, there are some general guidelines to keep in mind. Um,
if this is going to be work that we can be completed in less than a month,
Um, if your project is going to be what you anticipate to be a 6 to 8 week project, this is going to be a good candidate for a domestic project because you do want that structure to help keep you on track and keep you working towards milestones and deliver Bols or as they call them and lean six Sigma toll gates.
Um, it's not gonna be cross functional. So if you need
someone from human resource is and finance of stakeholders, you're not gonna want to do a quick it quick hit projects don't have stick holder analysis, and they don't usually usually do a sigh pock model at the beginning. So identifying your suppliers in your customers. If you think you're going to need a representative
from your supplier in either your internal or your external customer,
you need to do it to make project. And the reason why is because of the more robust communication structure and reporting structure. When you start pulling people from other departments, you're going to want to be accountable to those departments for what is the benefit for them. Lending them. Your resource is
the last aspect is measurable, so there are going to be a couple of aspects with in lean or within lean six Sigma that you don't have tohave measures for. But because this is a very quantitative discipline, we do want to have a baseline
and an improved state to show what was the benefit in doing this work.
Ideally, when you do this work, you're going tohave a benefit, and if you don't have a benefit, you're going to go back to the drawing board and try and figure out a solution that will. So you do wanna have a baseline and an improved measure for these. If you don't, this is either something to consider. Is it just do it
or potentially. This isn't a good candidate for a process improvement project or process improvement work as a whole.
A couple of things that are really important. We're talking about the differences between quick hits and Jamaica. Really, really fast Run through this quick. It can be done without a formal project, so we mean not necessarily Chartered
doesn't necessarily have ongoing meetings with set delivery bols and time frames. It can be done informally and when I say
can be done informally. This can be something that can happen at your regular staff meetings or a group of water coolers. You want to make sure that you do have some structure still, so there's some tools that will teach you specifically P. D. C. A. Which is two modules from now. If you're antsy to know,
Um, but really, what
a quick hit looks at is a low hanging fruit, something that you can look at. You can see the waist which will go through the eight waist shortly, um, and identify if I do this, this should happen. This is going to be one of your major key takeaways from yellow Belt.
When you are finished with this course,
you, the participant will or you the student will be able to do quick hit projects independently without a lean six Sigma coach or facilitator.
Um, now, if we look at DM, AIC projects their chartered by a sponsor and we use the phrase charter. When we get to the defining phase of the pores will go into more depth about what is a charter and what does that mean? But basically, for today, chartered by a sponsor means that somebody in some level of leadership
I told you,
you need to work on this project.
Don't make project has clear objectives. So if you think about a quick hit being and formally we want Thio, decrease our cycle time or how long it takes us to get work done, a domestic
goal would be we're going to decrease our cycle time by 10% by the end of Q three. So much more prescribed and what it is. The outcomes of the projects are.
And then, of course, Domenic follows that prescribed methodology we talked about in the last module. The defying measure, Analyze, improve and control phases.
When we're talking about quick hits, they still need to be documented. Ideally, they used the P. D. C A cycle. So a couple of modules coming up quick hits junior tohave the minimum details documented. They need a problem statement or business case in a current state.
These can be used interchangeably for this coat for the scope of a quick hit. But what you really want is
why am I working on this? And what is the beginning measured? But that's where you want to come from. With your problem statement, you're gonna want to document your intervention. So how did you respond to this problem statement in a way that you think that improved it, and then you're gonna wanna document your outcomes. So I have this problem statement. I did these activities,
and this is how it's improved or maybe hasn't improved. And we go back to the drawing board and we look for another solution.
One of the things that I tell organizations that I'm coaching on developing performance improvement or process improvement Continuous improvement up operational excellence up X. Moving forward is to set up a library
In this case, it's better to over document than under document because you want to know
the historical context. So six months from now, you don't go back to doing it the way you were, because nobody knew what the problem statement wasn't what the benefit was from doing your intervention. So having a repositories where you can keep track of your quick hits and your project charters is going to be very helpful for your organization to evolve.
And if we think back to your organizational maturity model,
pushing into more projects, structured work and towards that seeking perfection that level five
All right. So when we think about the difference between a quick hit and a DM AIC, quick hits are very important to this idea of kaizen or this culture of continuous improvement, where employees are empowered to identify ways or non value, add in their workplace
and react to it and respond and
improve upon it. It does need to be recorded and celebrated for the contribution. So remember, you're gonna wanna have your problem statement your interventions and your outcomes and store it somewhere where people can view them. One of the things that I recommend for companies that are trying to get excitement
about their performance improvement program
is circulating the quick hit documents so you can show that you are empowering your employees to react and respond to their workplace by saying, Look, this is what I did. This is how it improved. All right, guys, thank you so much. And I look forward to seeing you in our next module standard work.
Up Next