Here's a genericized story for an issue I'm curious about:
A secure website for ACME Company has a
table of thousands of widget orders in an "initial" status that need to be processed online.
Dozens of ACME Company staff will be accessing the website at the same time to grab widget orders and process them. As such, once a person grabs an order to work on, they are the only person who can work the "checked out" order.
While they have the widget order checked out, they may change the status of the order, in which case the widget order moves to a new status outside of the "initial" queue, or they may alogether leave the order (for any reason) to get the next available order, or if they stay on the page too long, their user session may time-out with their item still checked out, but nothing else changed.
From the perspective of a user going through the queue of items, what features can be added to make this workflow process as user-friendly as possible?
For example: what would you do in the case where the user has checked out an item and then their session times out? Should they be forced to work on that item next? How would you transition from one-checked out order to the next: would you give them filters to slice up their options of buckets to grab from next? etc...
Any pointer to resources on this topic would be helpful, as my googling up to this point has not yielded meaningful results.