Take the 2-minute tour ×
User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It's 100% free, no registration required.

Would you suggest for a To-Do List section of a progject management app I am working on have multiple checkboxes inspired by Speckle

Or keep things simple and "common" using single checkbox like Ta-Da Lists

I think that multiple checkboxes will show milestones/stages in a task clearly. But if I were to want to assign due dates to them it becomes alot more complicated both from a UI and development stand point

share|improve this question

4 Answers 4

I don't know what your users want, but I'd personally prefer to have single-state tasks that can be grouped together.

So the application treats/sees the to-do list like:

  • Write new article [ ]
    • start writing [ ]
    • complete rough draft [ ]
    • proof read #1 [ ]
    • revise draft [ ]
    • proof read #2 [ ]
    • complete final draft [ ]
    • get editor approval [ ]
  • New album [ ]
    • write songs [ ]
    • write lyrics [ ]
    • record in studio [ ]
    • mastering [ ]
    • get work releases [ ]
    • get label approval [ ]
  • Get milk [ ]

But the user might just see this:

  • Write article [3/7]
    • Next: revise draft [ ]
  • New album [4/6]
    • Next: get work releases [ ]
  • Get milk [ ]
share|improve this answer
    
Ah. I never thought of the 2nd point where users will just see "next ...". I did think of the 1st point, and I though if I have tasks in a project that will have similar stages, with single-state task, I'd have to create sub-tasks repetitively. Any ideas on that? –  Jiew Meng Dec 31 '10 at 7:25
2  
@jiewmeng: Hrmm... you could allow the user to save task "templates" so that they just need to name the "group" (i.e. "Jan 2011 Article") and the subtasks will be generated automatically. Or, you could have a list of generic subtasks that are grouped into categories like "Development", "Writing", "Business", etc. that the user can just drag-and-drop into their new task. –  Lèse majesté Dec 31 '10 at 9:47

The thing about project management is are very different directions you can go with them.

Some focus on showing as little information as possible, such as the "next..." lists, while others aim at giving you as complete an overview of a project as possible.

A good example of the latter is pivotal, where a project is broken down into features which move through the states unstarted, to accepted, while each feature contains it's own task list. Tasks on this are just a checkbox to mark as complete. http://www.pivotaltracker.com/

If you are aiming to be as simple as possible, focusing on productivity for a single user, then you might want to do something like Lèse majesté's suggestion with nested subtasks.

You can assign due dates to a task and have a checklist of subtasks.

The ability to clone and edit an existing task when creating a new one could solve your problem of repetition. Rather than using templates and adding more interface clutter, you just add an inkdropper style tool to copy an existing task and edit from there.

If you're aiming for bigger collaborative projects with multiple users, then I'd look to tools like pivotal for inspiration.

share|improve this answer

I would go for the single check-box option. It's more clear for the user, it will achieve instant gratification for a user (opposed to flow type grouped check-boxes) and it will inadvertently force the user to create simple, to-the-point, manageable tasks, which can be checked off with one click.

In my opinion todo-lists work because you can feel your moving forward, so with that in mind keep it as simple and goal driven (ticking off tasks) as possible.

Maybe you can also check out: http://www.realmacsoftware.com/clear/ (no stocks), easy to the point todo app for Iphone.

share|improve this answer

The multi-checkbox approach shown in the first example is overwhelming. A system like the one used in MindManager that shows a circle with quarters colored in to represent the percentage complete for a task (25, 50, 75 & 100) is less obtrusive, and requires a single control rather than a series of check-boxes. It could translate well to 'started, done, checked and live'.

Assigning due dates could be simple or complex. A color system could shade overdue elements in red, those due within a week (user set time range) yellow, and those further off in green.

For a single 'parent' task that can be broken up into stages, nested 'child' tasks are helpful. These can be shown with indentions in the interface and borders to group them with a parent task.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.