Are there studies that prove overall user performance degradation when interacting with Task-Based/Driven UIs in complex enterprise web applications and domains?
Considering, multi-step Delivery Order creation which involves
- setting up Customer,
- multiple Consignments etc
each including multiple Items, where each consignment could be collected (Pick-Up) at different locations (vendors) by different delivery sub-contractors.
And finally where all consignments could be routed to different hubs and delivered to the Consignee by different delivery sub-contractors/own drivers. Also, probably collection from Consignee could be involved. All this is still a single Delivery Order which is considered to be closed only when all sub-routines/orders are closed.
I just described some dummy complex process which starts with the simple task from the user perspective - "Create Delivery Order" and this routine could be done like 20-30 times per every operator (user) per day. (I'm intentionally excluding things like automation).
I see, how it can be split in dozens of component frames (views/tasks)... but I have a feeling that in comparison to traditional form and grid (CRUD) heavy applications it could be much slower creation process for the advanced enterprise users. Also, I imagine that deep branching out of the main task could confuse the user a lot.
Are there any studies about the balance of Task-Based UIs and traditional UIs in complex domains?