Wireframes
Userflow
Information architecture
Affinity mapping
User Testing
Contextual Enquiry
the challenge was
totally deep
We went on to understand few aspects of investigation, what are the stages of solving the cases, how is the time distribution for that in the current system and how an ideal system will lookfrom user's point of view.
One clear indication was that, the time spent on understanding the data was more than ideal. Leading to that we went to understand what and point hold value for the investigator.
Further contextual enquiries led us to find out various data points which help investigator to decide the risk factors of the cases and which things to look at.
There are many false positives cases detected by system and it takes some time to understand those, which in return increases the average TAT for cases.
System is just for getting data, actual investigation takes place out of the application.
User also uses other tools like excel to sort data, note book to keep notes.
Every case has different set of data that concludes the result sometime it may be directly relevant and sometime user has dive deep.
For new users the learning curve was more stiff and the probable reasons were complexity and heuristics of the product.
Traversing through cases or finding the cases is challenging in the existing product
Sometimes while doing investigation user miss-places data, it take immense concentration & tracking when dealing with sophisticated cases.
There are 2 levels of investigators, Junior (L1) investigator & senior investigator (L2).
are curated
consolidated
with testings