Visual Task Management for Individuals and Teams
droptask.com
droptask.com
The information density is very low. Doesn't seem to allow you to easily order tasks beyond dates. Lousy on phones. I could go on.
List aren't boring... there useful. I don't go to my project management software to be entertained - I go there to get shit done ;-)
What I want to know when I go to project management software is what everybody is doing now and what needs to be done next and by whom. This interface seems to hinder not help with that.
When you have 1000 items (conservative for our business, in Asana we must have at least that many), the problem is that no matter how many categories or hierarchies you make, there's no way to make sense of the information overload. I call it importance overload because that's what it is: when everything looks the same and feels the same, everything becomes the same importance. And when you have 1000 items of the same importance, nothing is important. This is a design paradigm used on information. I think it works well to describe the problem.
There's no list structure that yet exists that solves this problem. Nothing that brings your list of 1000+ things into a manageable analogue of what is actually important for you to see and do at any given time, in any given context.
I don't think this is it, but it's getting closer. And "lists" are still not sufficient. We can do better.
The product video emphasised "say goodbye to boring lists of tasks" which was why I mentioned it ;-)
The point I was trying to make was that boredom wasn't really a pain point for PM software.
When you have 1000 items (conservative for our business, in Asana we must have at least that many), the problem is that no matter how many categories or hierarchies you make, there's no way to make sense of the information overload. I call it importance overload because that's what it is: when everything looks the same and feels the same, everything becomes the same importance. And when you have 1000 items of the same importance, nothing is important. This is a design paradigm used on information. I think it works well to describe the problem.
You stated the problem very well - if everything looks equally important then nothing is.... so don't do that ;-)
I've easily about 500 items organised on various kanban style boards ATM (not all in trello). That's actually pretty low for us. I've worked with places that successfully do this with many, many more than that.
The thing that the OP missed in comparing droptask to trello and similar tools is that you're not just making lists - you're modelling the process you're using to do work too. For me droptask makes it harder to deal with that information overload - not easier - since it seems to be focused on task categorisation - not workflow modelling.
When I'm looking at our company's current-work board I can see - at a glance - what folk are doing right now (the WIP column), what's blocked (the blocked column), what's been done in the last seven days or so (done), and what's coming up in the next week or so (on deck column) and so on.
Once a week we make sure the backlog on that board is topped up with another week's worth of work from a separate general-work board. Takes an hour tops as part of our weekly retrospective. Usually more like ten minutes.
With have a few class-of-service rules that decide whether incoming work goes onto the current-work board or the general work board.
Once a month we spend an afternoon sanity checking the general work board against our company goals and cull / re-prioritise as appropriate.
(It's a little bit more complicated than this - since we have some external public-facing boards we use for client work and some volunteer efforts we're involved with, plus create separate boards for one-off tasks like recruitment and for tracking our consulting sales funnel, etc).
In short I find that prioritised lists are a stupidly effective for visualising our workflow. Droptask seems to only have date-based ordering which is a very blunt - and often counter productive - tool to help prioritise work.
It seems a step backwards to me.
Can I show you a mockup I have that addresses the prioritizing problem?
Let me know.
A great example of how great UI doesn't necessarily equate to great UX, in my opinion.
One thing that the circle metaphor does add is nested groups, which I can see being important for a different set of use cases.
That said, I tend to agree. Trello works at least in part because it's immediately intuitive to anyone who's ever made a "to-do" list or used cards-on-a-whiteboard to manage a project.
The Droplist approach is a cool idea though, and for some things it might be better.
This is true - the group (used to categorize task circles) grows to fit the content. We did play with allowing task circles to be resized to show priority/effort, etc, but couldn't get it to work well. We may revisit it, though.
Note: Trello has this color representation also with editable labels, of course. For some reason I dig the circles though.
The circles kind of kill the whole point of a taskboard, IMO.
I think this could be a great tool for planning or just looking at a snapshot of your day, developer, project, etc.But in order to be a full fledged issue tracker, you need to be able to filter, report,pivot,etc.
Just my two cents.I think it looks great and is promising.
Using it quickly makes me want a couple of features:
- not needing drag n drop for something (like creating a new task or group - be default putting them in the previous group or top level)
- being able to add tasks that are at the intersection of two groups. I imagine this would look something like a venn-diagram.
Finally, I am reluctant to support a startup unless I know how you are planning to survive. Is it going to be advertisement? not yet release feature? large teams? Once you do this, I will be more comfortable telling others.
Is DropTask really free?
Yes! In the future we plan to offer paid-for business
accounts and premium individual accounts
(each with additional features), however the basic
version of DropTask will remain free.In terms of how we will survive, as Ygg2 has posted from our FAQ, we plan on charging for premium features and business accounts which will offer team administration/reporting, etc. In the meantime, we are well funded :-)
Here's my feedback: from an interface perspective a visual process for organizing tasks is very appealing. But things weren't as intuitive as Trello. For example: clicking a task didn't let me edit its name; it brought up a window. Clicking "new task" was my first step, when really, I have a list of groups I want to create (like in Trello)
Speed is really crucial for me in using a system like this.
This is by design - we simply could not get the visuals to look at all decent with mixed colours for nested groups. The idea is that the one colour applies for the entire category.
Thanks for the clearification.
make your modals close on the click action for the actual close button on the modal. Right now, you can dismiss the "edit task" modal by clicking outside of it. This causes you to lose any work done inside said modal via misclick.
While more such project management tools are undoubtedly a good thing, I'd much prefer to have one I can host myself for corporate use (for security/confidentiality/hacking on it).
Edit: Also, a visual indicator of task progress, or more intermediate states (blocked, started, in progress, etc) would be helpful too.
Edit 2: And I've hit an arbitrary three project limit. So much for dumping my task list into this thing. Evaluation concluded.
Not as yet, but this is an early release of the product and we are aggressively adding new features and improvements. This is definitely something we are considering.
How did you find backbone and D3. Do they play well together in terms of overall code maintainability? What worked and what didn't?
http://upload.wikimedia.org/wikipedia/commons/thumb/3/39/Dir...
I especially like how things are visual and how you can zoom in and out and see this as potentially very useful feature. I will continue to review it and use it.
Also, describing it as Trello killer, I think made us expect way too much of it. So this might not worked the way it was intended.
My guess is they don't. My guess is people might find them fancy and pretty initially but eventually recognize that they don't actually improve efficiency or effectiveness.
The point is if you masquerade a solution to a non-problem with pretty things, it just wastes everyone's time and energy.
Like I said, it would be interesting if there is a study to find out if any of these pretty task management tools actually increases productivity.
Let's be realistic here ...
Cool idea just not very useful for me personally.
I have no idea if I'll continue use it on a daily basis (Trello for now), but it's fun, and pretty.
Well done, and thank you!
The entire app is written in CoffeScript - we're using Node.js on the backend and the front is mainly SVG/D3.js/Backbone.js.
We are currently considering all feature requests and this is one I've heard a few times. As such, it is definitely something we will consider!