
Scott Berkun look at the myth behind discoverability. According to him, a prioritization of how to think about the relative importance of tasks and features is based upon:
1. Things most people do, most often.
2. Things most people do, somewhat often.
3. Things some people do, most often.
4. Things some people do, somewhat often.
5. Things few people do, most often.
6. Things few people do, somewhat often.
Another thing that Scott misses out in this list is to find out how many users will perform the task. This is very important of your application supports multiple roles. In that case each of the above questions have to be factored by the number of users using the feature. And if the ultimate prioritization can be done when the feature is used by your primary persona or role...
[via Emergic]
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| 1 | 2 | |||||
| 3 | 4 | 5 | 6 | 7 | 8 | 9 |
| 10 | 11 | 12 | 13 | 14 | 15 | 16 |
| 17 | 18 | 19 | 20 | 21 | 22 | 23 |
| 24 | 25 | 26 | 27 | 28 | 29 | 30 |
![]() |
![]() |
![]() |
![]() |
||||
![]() |
![]() |
![]() |
![]() |
||||
![]() |
![]() |
![]() |
![]() |
||||
![]() |
![]() |
![]() |
![]() |
||||
![]() |
![]() |
![]() |
![]() |