Any.do allows tasks to be created, scheduled, shared then beautifully re-scheduled. Once a list of related tasks are complete it the product of the completed tasks forms the backbone of a project - but the growing set of structures that characterises a growing project is not recorded in Any.do.
For example: Any.do can wonderfully manage complex interrelated tasks that relate to the development a new customer relationship: emails, meetings, pricing, proposals, contracts, service delivery - and so forth.
The result of successfully completed tasks are the building blocks of project management and, unlike completed tasks, do not need deletion.
Any.do could have functionality that takes 'task outcomes' and enshrines them as project components.
These will lead to next-step tasks, which, when completed, will in turn suggest components of the project.
Navigation and structure needn't be different - but there would need to be variance in what gets deleted and how lists of project components nest and are linked. That would need some thought - but the Any.do structure would be a good starting place.
Good luck
Anonymous
Any.do allows tasks to be created, scheduled, shared then beautifully re-scheduled. Once a list of related tasks are complete it the product of the completed tasks forms the backbone of a project - but the growing set of structures that characterises a growing project is not recorded in Any.do.
For example: Any.do can wonderfully manage complex interrelated tasks that relate to the development a new customer relationship: emails, meetings, pricing, proposals, contracts, service delivery - and so forth.
The result of successfully completed tasks are the building blocks of project management and, unlike completed tasks, do not need deletion.
Any.do could have functionality that takes 'task outcomes' and enshrines them as project components.
These will lead to next-step tasks, which, when completed, will in turn suggest components of the project.
Navigation and structure needn't be different - but there would need to be variance in what gets deleted and how lists of project components nest and are linked. That would need some thought - but the Any.do structure would be a good starting place.
Good luck