First post here, but long time reader. I've had a look around, but couldn't find anything that exactly answered my question, so I'll jump in...
Here's my scenario:
Our business has a web app, used by engineers in the construction industry. A part of the app allows engineers to report issues from site, both to notify subscription groups, and to enable management to take ownership of the issue.
- User selects from three top-level categories
- New screen: User photographs the issue
- New screen: User tags image (effectively a subcategory of the top-level category)
- User taps 'Send' -- Photo then broadcasted to subscription group dependent on subcategory
The correct tag/subcategory is not always chosen by the operative. Probably a quarter of the time, they choose the accursed 'Other' category.
Office users then spend time moving issues out of 'Other' and into the correct tag/subcategory.
There appears to be the added problem that field engineers expect some of the tags/subcategories to be under one top-level category, when in fact they are under a different one. So, they select the 'Other' option!
Granted, this idea of choosing a top-level category, taking a photo, and then tagging with a more granular subcategory is pretty poor design. My first thoughts are to scrap the top level categories altogether, and replace with a single 'Report an issue' option. Or, at least to bring the top-level categories onto the same page as the bottom-level tags / subcategories.
I just wondered if anybody had any other ideas on how to improve this design? If anybody has any examples to hand, it'd be really useful.
Thanks in advance.