In complex processes, no one person knows what happens in every operation. But a visual model can create an easy reference that incorporates the input of many experts. Learn more about Enact
The process model, if you can imagine, I use a quick little example of building a cake, but think about building a car or an airplane or something much more complex than a cake. The process model has many, many operations that feed into each other, so it just expands until it gets huge. No one knows what happens in each one of these operations to get to the end product but someone might have an idea that they know there’s a paint shop, there’s a welding area, there’s a place where we do turn some aluminum into round stuff and they can build the skeleton of this model and then go to those expert say “well here’s the hole where we need your expertise to fill in what exactly happens in this operation.” What features are important to me in this operation where, what items do you want to collect to ensure that that operation is doing, what’s it’s supposed to do that the transformation is occurring as you need and so it’s a great for maybe one person to own the process model up from a high level but then go into the process experts in each one of those operation boxes to really dial in what’s going on and then as the process models are being used and data being collected. You know we gain new knowledge and so we may modify and alter these models. And if a company makes the same product in multiple locations you build a model one time and then it’s reusable and scalable across every place that makes a similar product and there may be hundreds of thousands of UPCs or products that go through a single model. Enact being a collaborative tool, some discoveries are made, and we can make small tweaks over time to the model, and the company as a whole benefits from these tweaks and alterations and improvements and in the process model.