Recently, I purchased an e-bike for myself. Before purchasing, I made a so-called “evaluation” to decide which model to buy by reading catalogs carefully, search reviews on the Web, or going to a bicycle shop to actually straddle ones”. Even I did so, I still have a feeling of regrets that “its weight is a bit too heavy”, “would have been better with the wheels a little bigger”, and so on.
“Evaluation” is important, isn’t it? “Evaluation” is also important in selecting a workflow system. I would like to make a “cool evaluation”.
Based on the case of Questetra BPM Suite, I would like to introduce a “cool evaluation method”. Please read this by all means as it will be helpful also for workflow systems in general!
Reactions of customers over “evaluation”
I often hear from the customers who applied to our Starter Plan that;
“Evaluation work itself seems to be tough.”
Organizing those customer voices, their questions can be classified into the following.
2. Haven’t got skills to write Workflow diagrams.
3. Can’t be sure if the created Apps would fit with the practical work.
4. Whether there will be a backlash of general users against the implementation, due to their inexperience.
In this article, I would like to focus on “1. Don’t know what steps one should take for making an evaluation for the introduction of a product.”
Grasp the features of a Workflow system!
Evaluation steps may differ depending on the functions and characteristics of the provided service. It is necessary to grasp the features and the characteristics of service provisioning and select the most suitable “evaluation method”.
For Questetra BPM Suite, those are;
* Designing of input form is easy.
* Workflow diagram works as business rules of a system as it is.
* All manipulations are solely browser operation.
* Available for trial immediately for free (up to 10 users, without any functional limitation).
“Practical evaluation” is suitable for making good use of these characteristics for evaluation.
That is, it is “to proceed evaluation while creating and running workflows little by little”. I summarized those steps more in details, below figure.
Recommended! “Stepwise evaluation/Practice”
STEP 0 (Organize current business challenges) and STEP 1 (Comprehension of the functional overview) are preparatory steps. Regarding STEP0, it is essential without concerning whether you use Questetra BPM Suite or not.
If you can roughly match the functional requirement in STEP1, go to STEP2 (prototype evaluation). Try designing business Apps and run it actually.
You can download the sample Apps from the “Workflow Sample site”, modify and use it so that you will be able to progress more efficiently.
In “Work Request Flow is the Basic of Workflow”, for example, the workflows of work implemented by email and documents in various companies are realized, and we recommend it for prototype evaluation. You can also search for the type of business operation you want to apply from the search window, and try it out on the relevant operations.
For the cloud-type workflow system of these days, “free trial” is becoming almost commonplace. In addition, there is something similar in the feature. I can say that it is also a good evaluation method that once you evaluate Questetra and compare it with other systems.
Next time, I will solve your worries about “Haven’t got skills to write Workflow diagrams”.
1 thought on “Cool Evaluation Method for Workflow Systems (1)”
Pingback: Cool Evaluation Method for Workflow Systems (3) - Questetra