Process validation made easy


Share on LinkedIn

We’ve explained our approach to process validation in several earlier posts on this blog and have focused on our ability to enable our Process TestLab [1] customers to experience their process designs before they are actually implemented.

The effect is overwhelming: Whereas before people had to struggle with interpreting abstract process models, now they can understand the logic and dynamics of a design by working ‘in’ the process rather than by looking at the model. Imagine taking the design template of a new car for a test drive and you get the general idea.

But how does process validation at the Process TestLab work?

Let’s take the most common case that a project team has developed a new process which needs to be validated before it goes into the next phase. Our approach makes it very easy:

  1. Process design models and descriptions are sent to the Process TestLab
  2. At the Process TestLab, we transfer your process designs onto our validation system. This usually takes only a few days.
  3. Next, we set up a temporary validation environment at the clients site. Not to worry, all it amounts to is a room into which we place our validation server and a network of terminals. Setup usually takes no more than a couple of hours.
  4. Then the actually process validation by the client takes place. Every participant is assigned a process role (e.g. sales rep., clearance team member etc.). Our validation system then generates process instances and the server routes the instances from participant to participant, following the logic as described in the process design. The participants can work on the assigned tasks, enter data, in fact they can do everything necessary to evaluate the process logic.
    Our job at this stage is simple. We just guide the validation team through the process and record any upcoming discussions. After all, our clients are the experts on their own processes.
  5. During the validation runs, we automatically record the audit trail of the process and add any comments made by the participants. This way, our clients receive a complete documentation on what aspects of a process may require changes and in which context these items came up.
  6. Finally, we dismantle the validation environment and generate the final validation report for our clients.

Thus, with a minimal amount of time spent, our clients

  • have validated their processes by having actually worked in them instead of only looking at the description,
  • have avoided the pitfall of interpretation,
  • have jointly identified areas to sign off on and areas that require additional work,
  • have created a group consensus on the process design.

Our approach lets our clients quickly ensure the integrity, workability and above all usability of a process design without them having to it implement it on their IT. As we all know, this helps avoid unnecessary costs [2] and helps reduce the time needed to implement and roll out the process. Best of all, as quick as our validation process is, you can use the Process TestLab in parallel to your projects. It doesn’t even conflict with your project schedule. And thanks to our mobile validation enviroment, we can support our clients anywhere in the world.

Republished with author's permission from original post.


Please use comments to add value to the discussion. Maximum one link to an educational blog post or article. We will NOT PUBLISH brief comments like "good post," comments that mainly promote links, or comments with links to companies, products, or services.

Please enter your comment!
Please enter your name here