asmecher
commented
9 years ago Our goal is to keep the tasks list short and friendly; if we have 100 tasks either it's an unusual case or we've done something wrong. (Think of a post-it note metaphor: yes, you can write a book on them, but you're doing it wrong.)
The task list is attempting to answer the question: what do I have to do right now?
For more comprehensive listings, the dashboard is intended for this. It's trying to answer the question: what's active in the press/journal? What is its rough progress at a glance?
A landing page for tasks would be fine, but does mean a longer interaction in terms of time cost to actually get to an outstanding task.
NateWr
Currently Tasks have their own tab on the navbar. But we don't have a landing page for Tasks. A landing page could be created or we can do a fly-out submenu with the tasks listed there. Open to other ideas.
Does anyone have a rough idea of what range I should expect in the number of tasks? I suspect it's linked to the user's role, but what's a reasonable upper limit? Should I be designing for 10 tasks? 20? 100?
I suspect we should design for the power users -- the ones in the trenches day in and day out. I also assume that people might have a lot of tasks on the back-burner, so finding the right one in a larger list might be important.