Context
The Short Rescheduler is one of the modules that integrate the MES (Manufacturing Execution System), a system that monitors, manages, and optimizes metallurgical production processes. The goal of this module is to serve as an editor for the critical production schedule (which is very close to being executed), replacing, grouping, and splitting production orders.
At the beginning of May, we conducted a 5-day workshop at the Belo Horizonte office, followed by another week remotely, to define the first steps of the Short Rescheduler and some other MES modules together with the Product Owners (POs) and technical leaders. The workshop lasted two weeks, during which we defined the workflow and scope of each module, as well as the ideation and subsequently a "MVP" of the Short Rescheduler.
Data Flow / Product Vision
The first thing we did was understand the data flow of the Short Rescheduler, where the biggest challenge was figuring out how to handle the movements of job orders and their division. This data flow helps everyone involved, as it provides a good starting point for our user flow for us and the Product Owners, and assists developers in structuring the database.
Is/Is Not - Does/Does Not
After understanding the data flow, we conducted an Is/Is Not - Does/Does Not exercise to define the scope of the module in question, as there were other products in the workshop that dealt with the same data but had different objectives.

Crazy 8's
At this stage, we conducted a Crazy 8's session to generate ideas for the user flow and even the main layout of the module. The process also helped us understand the expectations of the POs and technical leaders regarding the product's layout.

Ideation Process
With all this material in hand, we conducted a more free-form ideation process, led by the design team. The goal was to structure an initial user flow, following the data flow, respecting the product's scope, and aligning with the possible user flows and layouts presented in the Crazy 8's.
Prototyping
At the end of these two weeks, we had three more weeks to deliver the first prototypes, covering a significant portion of the user flow discussed in the workshop. The prototype is available here.

Conclusion
The workshop was crucial in defining the scope of the Short Rescheduler and other MES modules. This first version was presented and well-received by stakeholders and the module's initial clients. We are now working on new features and improvements for the next version of the Short Rescheduler.