series – in the final article in their series on lean process development, the authors discuss what it takes to get started with their 6con process development model.
words: eric ethington and matt zayko
“reasoning draws a conclusion, but does not make the conclusion certain, unless the mind discovers it by the path of experience.” – roger bacon
as with any new model or framework, the most difficult part is knowing where or how to start. in this article, we will provide some guidance on setting off down your own unique path to building traction to integrate process development earlier in the overall development cycle.
what is your current condition?
the best place to start is to deeply understand your current situation and to gain alignment on the current challenges or problems you are facing. use a recently launched process to map out the steps taken to develop it from beginning to end. this will allow your organization to truly grasp the reality of how well it designs new processes. this reflection and learning will be highly valuable, because as time passes we tend to forget many of the critical items and to connect cause and effect of certain decisions.
what is the capability of the recently launched process?
as part of this reflection with a recently launched process or one that is close to launching, use a standard score card to collect data and facts about the capability that is currently being experienced. in the confirm section of our book, we introduced a standard qualification score card, which is a great template to use. with clear data collection assignments for every team member, this is an effective means to objectively understand the true process capability. as you gain experience in process development, this score card should be changed to better support your unique circumstances. nevertheless, it is a good place to start.
example score card for launch process readiness
how much waste and cost could have been avoided with better upfront process design?
with the reflection and learning that the team gathers, it is also important to capture and summarize the tangible waste, customer impact, delays, and costs that could have been avoided with proper, upfront process design. this is a valuable insight into the cost of poor process design, which can be used to help justify the earlier investment in new process development resources.
what are your key enablers for lean process creation?
before the team jumps to designing their shared vision for how to do future process development work, they will need to challenge their existing mental models. successful process design teams incorporate a handful of key enablers into their way of working. these questions help to determine the enablers for your own situation:
- what is the system architect or chief process engineer role for your organization? who should have this role?
- what is the operational declaration? how is this different from the charter? who owns it?
- how will you gain alignment on how the actual work will be organized to provide the value, from idea to production start? (product & process development value stream map)
- where will you use “set-based” design concepts to maximize the learning early on during the study phase? how will you identify and manage knowledge gaps to de-risk the back end?
- where will you use the obeya space for effective visual management to see abnormal from normal?
- what are the key milestone integration points? what are the design review types during the development of your new product?
- what is the management system routine for plan-do-check-adjust (pdca) when developing a new product?
how will your leadership team support, engage, and learn with the team?
as noted in our planet lean article series, it is not enough for the leadership team to “declare” their desires, but rather they will need to actively engage and tangibly support the process design team during this pivotal time. great process creation includes a clear, cadenced role for leadership with regular engagements and a clear escalation path for highlighting and resolving issues.
***
in conclusion, change is not easy in any organization, and big change is even more difficult. if you are able to align the team around a shared reason for needing to change, however, that is a great place to start. this could be related to a need to reduce process development lead-times drastically for a customer, improve process readiness at the start of production, or another urgent need. once you have this alignment, start to build momentum by setting aggressive goals and targets in order to be the best in your industry from the customer’s perspective. avoid getting paralyzed by indecision or caught up in a cycle of trying to “boil the ocean” of problems or challenges that face your organization.
for more details, please visit
the authors
eric ethington is a senior lean coach and program manager, lean product and process development, at the lean enterprise institute.
matt zayko is lean leader at ge hitachi nuclear energy.