In my last article, I helped you make preparations for testing your solution properly. Just having a brief glance and thinking “it looks good” is not enough. You really have to “live” the process to see if you have translated your requirements correctly.
So here we go!
Step 5. Run the process as it should run
That means you enter an item in the correct way, assign everything to yourself if appropriate, and click on OK at the right moment. Look out for the following:
- Are the fields in a logical order? (The process starts at the top and ends at the bottom.)
- Are the column names, the choice values and a description/instruction correct and easy to understand for your audience?
- Are the correct columns mandatory – or not?
- When you click OK or Save, is the next screen you see logical and expected? (For instance, do you go to “New Requests” or a “Thank You” page?)
- Do you receive a notification from an alert or workflow? If you use workflow, are the subject line and body text of the email meaningful, and is the attached link accessible?
- Is the newly submitted request shown in the desired way on the library/list and on any page? (E.g., does it go into the view “New Requests” and not into “Completed Requests”?)
Make a note of all things that are incorrect, not meaningful or that could be improved or that you would like to add/remove.
Now, switch to a different role and do the next step in the process. Start from the notification or the workflow or wherever you need to start from.
The second and last step is to look at the input as the IT manager.
- For CRM: You will now act as the distribution manager, add information and assign it to Quality Assurance.
CRM step 2: Distribution department receives entry from Customer Services, then hands it over to Quality Assurance.
Repeat for the other steps (where appropriate) and make notes of everything you want to discuss.
Step 6. Repeat with different scenarios
Run the different scenarios you have created in step 2 and see if it still works as planned. For these different scenarios, use different values than you used before and/or reject an item if in your first scenario you first approved one. Make notes.
Step 7. Hack the process
If you have found a showstopper in steps 5 or 6 (such as an error message) skip step 7.
But if things are working through step 6, now make some deliberate mistakes and see how that gets handled. Think about mistakes that you or your colleagues may make. Enter values that are not allowed. Forget to fill a mandatory field. What happens? Is it visually clear that the process is not going well? Do you get enough information about the problem and how to solve it? Make notes.
Up next: Feedback and finalization
In the next article I will discuss giving feedback, finalizing and implementation.
In the meantime, if you have suggestions or additions, please let me know!