Experience the power of a deal management platform for R&D

How to create outlook signature

[Music] [Applause] welcome to the cure process optimization path application demo today we're going to walk through the creation of a quick win project we'll start this by selecting create a project on the menu the create project button and it's going to ask you for a title for your project give it a name that is descriptive and it makes sense to you the app is going to walk us through a series of simple questions to help you build your your project next is going to ask you what type of path you want to take in this case we're going to do a quick win basic improvement project we're going to start this process by defining your project you'll notice here on this screen we'll just name this process a common name that's used to describe the work that's done in the in the workplace you'll notice across the top of the screen we've got a map of the process optimization path what's my opportunity what's my process what's causing my problem what's my solution you're going through here and answering some basic questions to build a charter the definition of your project it's asking you what your process does give it a description of how it takes inputs and creates the outputs so a few words to describe what's actually happening you'll have a process owner we've talked about earlier the person that manages are responsible for the process all the things that are critical to define what we're doing why we're doing it and who's involved you may have a team if you do uh we'll list those here often a quick win project can be an individual project so you may not so that's why it's optional you'll notice we're typing in the email addresses that will become parent later as we finalize this those individuals will be invited to join you in this project so by hitting next uh the application is building your project charter here's a description of the project if it's all in order you hit next confirmation to invite your team members and you're on to the improvement process next stage what's my process so here you're going to identify uh how the work is actually done we're going to use a swimlane process map to do that well you'll notice we're filling out the swim lanes now the swim lanes are the roles or people involved in in the process roles functions are individuals it starts out with three you could have two to seven we see typically normally two three or four is enough to kind of describe most processes that we've been working on next you're going to actually outline the process steps as they're currently performed in the workplace we'll start with a reasonably detailed process map 7-15 steps no need to go into much more detail at this point you want to build this with your team try to capture as accurate as possible what's happening you review that with team members other subject matter experts as well this will be a key foundation for our improvement in your project we'll use this as the basis of the analysis going forward as well as generating improvements uh to improve this process so this will change or may change over time as you make improvements to your flow you'll continue to outline this with the steps that each of the functions perform in the in that process now i'm going to make sure that the process flow is clear we're going to do that with the arrows these snap in place arrows to kind of go from one step to the next to really outline how the the work flows from step to step and through the various uh functions involved so this process map is exportable you can print this out and share that with the team members and stakeholders for their review and feedback once you complete this process map it takes you to the next step which is the process walk again a further understanding of what's going on in the current process by walking that process and identifying opportunities for improvement so this process map is kind of a planning phase to make that happen so as we go to the next step and we do the process walk we're actually going to document our observations so as you watch this screen and you'll notice the inputs here the team is walking the process whether it's a physical process or a virtual process walking through the steps of the process identifying opportunities for improvement using the eight wastes or other process complexities that are listed in in the drop down we're going to categorize those by these categories you see here and we're also going to prioritize them by the impact they have on the process high medium or low based on the impact they have on the process relative to the problem we're trying to solve and if you need any notes to further clarify this you've got a space to capture that there this will be your log if you will of all the observations we'll do a few here in the demo but you may have numerous you want to capture as many as you can and then you want to prioritize these so we work on the most important opportunities first the application is going to carry these forward into two different branches uh one we'll talk about in just a moment if you've got a disorganization opportunity that where the chances to re reorganize and improve that organization can drive improvement the process that's a specific path then it'll be another path where we do a root cause analysis to help us get down to a specific level of detail and the app will take care of that for you as we go forward when we go to the next step which will be what's causing my problem but first capture all your opportunities here with enough detail as you notice disorganization was a key category that's the one will take us to the 5s the organization step and we put a note that the the staff is frustrated with this so the app recognizes that so the next thing we're going to do is go to a tool called the 5s but before we do that we're going to talk about baselining this process so before we start making any changes we're going to take a snapshot here we upload a photo of the workplace in this case since we identified this organization we'll take a picture of that workstation and load that here this will be used later in a before and after comparison now we'll move on to the 5s i mentioned before this is a part of the uh uh a tool uh technique for uh addressing uh process or disorganization uh to help it uh be uh better organized more intuitive to the process uh and the people that work in the process and to facilitate process flow the 5s gets its name because there's five steps in the methodology it's basically sort which we're talking about here straighten shine standardize and sustain five five steps that you'll go through to address a specific disorganized area in the sort step what we typically do is look at all the items in the workplace and decide if they need to stay if they're vital to the work or if they're unnecessary or excessive and we'll sort those out some things are obvious and we'll take those away either discard them or put them in another spot others we have questions about so we're going to do something called a 5s red tag there we're going to say all right we're not sure just in case we might need it we're going to move those to a special area mark them with a red tag and we're going to observe those if we need them we'll bring them back in and we'll find a way to put them back into the process in a more organized way or if we find we don't need them they'll be discarded or stored somewhere else and so you agree as a team you know what that those items are how long they need to be in in that red tag quarantine area it's usually a few days uh you don't want to make it excessive and you'll manage that so this is the the area where you log these and manage these items we'll complete those you may have numerous items in your red tag we'll kind of complement document those as many as we need and then we're ready to move on to the next step you would continue on with your 5s that's one path the other path i alluded to is the root cause analysis so here is the is just that we call it the five wise for the other opportunities that were identified in the process walk those are carried forward into this five why discussion here we're going to be asking the question why to go from a higher level kind of issue a problem to try to get down to a root cause in other words something that's very specific that's verifiable and that's actionable we'll call that a root cause so what you're seeing here is kind of the questioning process the team or the project leader is going through asking the question why and kind of responding uh with an answer the decision on the right is one of three choices continue ask more wise or a note i've gone far enough i've got to a root cause or nope i've got to a dead end so this does not take me where i can get to anything i can act on so that's kind of a dead end we'll go through the other opportunities and address those so we'll complete this questioning process sometimes it may take one or two sometimes it may take five or six questions five wise is the common label for this technique that you'll see in a lot of the literature so again asking the question why do you get to a level that you and the team agree that you've reached a root cause and you can actually do something about this will be the basis of focus if you will when we move on to the solution phase you'll notice as we walk through this one of the things we've done is done a logic check so we've kind of walked through the the the questioning process so to finalize this we'll go to this right side and kind of read through those questions and make sure that logic makes sense there's no holes if we agree then we're ready to move on to the solution phase so the apps takes us to the final phase of the process what's my solution for each of those root causes that were identified you may have two you may have uh you know ten it's asking you for your quick win ideas and so we'd suggest you generate as many ideas as you can thinking about quick wins and the criteria around a quick win and then put your best into this uh into this form and analysis as you put these ideas in you're going to screen them one more time to make sure they meet the quick win criteria you must answer yes for all these uh it must be a solution that meets all this criteria otherwise it's not a quick win so you may want to capture that idea so you have it in your in your documentation and it may be a great idea to pass on to a larger project that takes more time because we're saying basically if it's if it doesn't meet this criteria it's either too risky takes too long needs a little bit more analysis in the process so we don't have control over it so it needs to go somewhere else if it's a good idea more on that later but here we're going to just focus on the ones that we do identify as quick wins here we've identified a couple uh we click yes and go the next thing would happen in your project is you would actually develop an implementation plan implement those quick wins finish your 5s and here we do the after picture upload that into the process so that same photo we did earlier in the before we'll repeat that in the after so we have that before and after comparison going forward that's really the last step of the improvement side of it now we're going to actually talk about controlling this process sustaining it and closing it out so it's going to ask much like we did in the charter a few simple questions uh that we answer uh and then we'll have to actually have our stakeholders our process owner or supervisor review these uh and make sure they meet their uh their understanding and approval and that gives us the means to close this project out and start to wrap up the the activity uh we'll identify our sponsor if they're not only on the team they're gonna be tagged for this process owner you'll recognize the names we'll ask them to kind of agree or disagree if they disagree then there's more work for we need to do and we'll close that loop and do that work once we've completed that and hit next then we've got a handoff summary which just documents for the record you know what we've done the improvements that we made or the results that we received the controls we put in place and the agreement of our process owner and supervisor that those are satisfactory that we have actually completed what we said we've completed so we'll enter that here once that's done as we move on and we've agreed that it's complete we move on to the next phase of the process and actually the final step which is a project summary so again the app is moving this through the the process optimization path quick wind path in this case and here's our project summary it's the story of the project from the beginning uh the project name the process uh what the process is intended to do our team the opportunities we found the improvements that we've made and the results all in a nice summary this is exportable as well uh as you complete this as we all agree then basically you've completed your project that's logged in your system congratulations you've just completed your quick win project you're recognized and for you you've just completed your uh your tour of cures process optimization path quick win project well done