We love Workflowy - a to-do list creator that offers unlimited amount of nesting. It basically allows you to create to-dos or tasks to track, then split them into sub-tasks, then split each of those into sub-tasks, creating sub-sub-tasks and so on. You can create as many subs as you want. And it’s great! At least for some individuals, it really is.
It’s always good when technology isn’t limiting. When an app doesn’t enforce too many constraints and allows you to use it the way you want, or the way you expect it to work, it really sticks. It is liked, used, re-used. It makes your life better in its own small way.
That’s what Firmzen wants to be. An app that adapts to your requirements (without the makers having to rewrite it for each one of you o’course), doesn’t force you to follow a limiting framework and works the way you do in real life.
We’d love to have taken some “inspiration” from Workflowy for offering a simple way to divide work into smaller parts – to as many levels as needed (and who knows, maybe we will some day). When it comes to managing task lists for teams though, things aren’t that simple, are they? There are procedures, deadlines, responsibilities, accountability. Tracking all of this becomes important – and keeping it simple is crucial for lasting adoption.
Up until now, Firmzen has had one level of work splitting – Sub-Tasks. This has generally worked well. You could structure your data easily by dividing it into smaller parts and allocating those parts with individual deadlines to specific people. We received a lot of suggestions around wanting to enlist a procedure or list of steps within these Sub-Tasks. Sometimes we were asked if you could store a list of prerequisites or checklist of documents within Sub-Tasks. In other words, there was demand for one more level of nesting, and here’s Firmzen supplying an update to that effect.
You could always create Services (or templates of Tasks) for creating repeatable Tasks. These Tasks could be split into Sub-Tasks, which could each individually have a due date and assigned users. These Sub-Tasks, can now further contain a checklist – which is essentially a simple list of items that are tick-able. This list of items can stand for a Sub-Task’s procedure or a list of prerequisites or anything else that requires further division of work. We hope this helps.