Learning Release

Challenge

I am a member of the Production Planning and Control department of the  company where I work - our challenge is to improve workflow (activities and  projects) for better machine product distribution and raw material savings. The  scope of the project includes the quality, production, warehouse and procurement  departments. The project is limited to internal resources (ie budget and employee  time). The project should not exceed 30 business days and the solution should  include a uniform distribution of working hours among team members. We'll focus  on trying to figure out what our team members, as well as key stakeholders in the  Production Planning and Control (PPC) department, find ineffective or  problematic about workflow and product scheduling.

Selection

The team has gone through a lot of activities and training with design thinking  tools, so it's ready to try out the learning launch tool. Generally speaking, the  launch of learning is an experiment designed to quickly test an idea and a  prototype, which we jointly created to improve the capacity of the production flow.

Application

In our first learning release, focused on the structure / execution of our  programming tasks, you can see if we could structure our tasks, projects and  processes to tailor Scrum project management methods to our work (eg,  scheduled time, meetings). revisions, etc.) This proves our structure assumption  and execution were the main causes of our workflow challenge. Our team  underwent a two-day training with a Scrum project management coach. We then  went through five workshops to structure our tasks and processes more quickly.  These two sessions take place within a period of three and a half weeks. We  hope to produce a document with a clear description of our new, more  streamlined processes / workflows.

In our second learning release, we focused on getting information about our tasks  and using it. This tested our assumption that our task priority was the main cause  of our workflow challenge. Our team has completed an anonymous survey in the  manufacturing sector. Because the surveys include questions about our  proposed new process, understanding the process and prioritizing tasks and  feelings about change were carried out within a week.

Insight

By applying a start-up learning tool, our team identified our assumptions and  designed releases to test these assumptions. In addition, we think about the  expected results, hoping to find a more effective way to improve workflow and  our team and key parts needed to open a new priority for tasks and processes.  The result was expected by the team, but with some different suggestions than  we imagined, or that will be good for the team and the improvement project. In  the future, a team will review this insight and incorporate it into future release  projects with production suggestions as a continuous improvement project.

Insights are particularly important at this stage, as releases come before a full  implementation on the design thinking timeline.

Approach

The team has gone through many activities and training with design thinking tools  and is at this stage of the timeline, the launch of learning is a useful tool. Just as  in the future, as a work of continuous improvement, our team needs to review the  information in our two releases and incorporate future release projects, adding  as anonymous research suggestions to the project that can approach in a  customized way for the full release. on the production line.

