We have a module in an application where users define time periods for different criteria that will be used later to filter some lists.
By default each criterion applies any time. Its validity can be limited by both restricting the time periods where it applies, and adding exclusion time periods. Already-defined periods of applying and excluding can be edited or deleted.
The current interface is as follow:
download bmml source – Wireframes created with Balsamiq Mockups
Users find it difficult to understand the logic of "application" vs "exclusion" time periods, which I totally understand. I can't find a solution to simplify the interface while keeping all the existing possibilities.
What can be done to improve the user's experience here?
Answer
I'm not sure I fully understand your use case, but it sounds like users need to clearly see the results of their restrictions and exceptions. I'm focusing a little bit on how to see the outcome as feedback.
Forcing them to read and calculate dates (and proportional allocations) seems to add to their workload. They also might have to look at periods across each criterion as well.
Could you have a visualization that aids in showing them as they add criteria?
A heatmap example:
Github is an example of showing a years worth of data. At a glance, you can see periods of activity.
Don't make them read; provide visuals in tandem.
If there's another state (i'm not too clear on this): that of unrestricted and undeclared time, the heatmap can show these gaps as well.
No comments:
Post a Comment