K
Kerry
I am perplexed as to why Outlook does not allow the user to create subtasks
and impose simple task dependency. I would expect any calendaring
application to support the management of common, day-to-day, multitask
"mini" projects.
Consider an example such as preparing a dinner party. This main task may be
composed of several subtasks in the following manner:
TASK Prepare dinner party
SUBTASK - Invite guests
SUBTASK - Purchase ingredients for dinner items
SUBTASK - Prepare dinner items
Additionally, tasks in most projects must follow sequence contraints that
determine the order in which tasks must be performed. In the above example,
naturally one cannot prepare the dinner items until after the ingredients
have been purchased.
You might suggest that one turns to project management software for these
types of assignments, but should it really be necessary to create an MS
Project file just to manage simple multi-part tasks such as planning a
dinner party, researching a book purchase, or contacting your co-workers?
Furthermore, these multiple part tasks often rely on the type of integrated
scheduling, email connectivity, and contact management for which Outlook was
designed.
Outlook's inability to outline and create dependencies for subtasks strikes
this user as a glaring development oversight in an otherwise very robust
group information manager. Does anyone know of a simple workaround? Does
anyone know if future versions of Outlook will allow users to create
subtasks?
Thanks,
Kerry
and impose simple task dependency. I would expect any calendaring
application to support the management of common, day-to-day, multitask
"mini" projects.
Consider an example such as preparing a dinner party. This main task may be
composed of several subtasks in the following manner:
TASK Prepare dinner party
SUBTASK - Invite guests
SUBTASK - Purchase ingredients for dinner items
SUBTASK - Prepare dinner items
Additionally, tasks in most projects must follow sequence contraints that
determine the order in which tasks must be performed. In the above example,
naturally one cannot prepare the dinner items until after the ingredients
have been purchased.
You might suggest that one turns to project management software for these
types of assignments, but should it really be necessary to create an MS
Project file just to manage simple multi-part tasks such as planning a
dinner party, researching a book purchase, or contacting your co-workers?
Furthermore, these multiple part tasks often rely on the type of integrated
scheduling, email connectivity, and contact management for which Outlook was
designed.
Outlook's inability to outline and create dependencies for subtasks strikes
this user as a glaring development oversight in an otherwise very robust
group information manager. Does anyone know of a simple workaround? Does
anyone know if future versions of Outlook will allow users to create
subtasks?
Thanks,
Kerry