Flexible vs firm task due date

[Jason_Bedford]

Good morning Asana community - looking for some feedback or help.

In our past PM software, I would assign tasks, and not provide a due date, giving my team the ability to assess their workload and propose a date to complete the task. In situations where I had a hard deadline, I would assgn a deadline which would indicate it was a firm/non-negotiable deadline.

We have since moved to Asana, and based on all the guidance I have received through online training sessions and throught he online forms is that all tasks should be dated to provide a reminder to ensure that the tasks gets done.

Does anyone have any tips or tricks to identify a firm date or a negotiable date other than making notes in the description or in the update?

Thanks for your help!

[lpb]

@Jason_Bedford, Here are my recommendations which I believe address all the good questions you raise:

Use Due Dates Differently in Public and Private

What do your Due dates mean? I bet at times yours have very different actual meanings. That’s ok, but only if you are sticking to a workable policy, such as the example below. In private (in My Tasks with private tasks or in my own private projects) I often set Due dates for use with Rules (formerly auto task promotion) so I make sure I get reminders and nothing falls through the cracks. The Due date represents the day I’d like to be reminded, perhaps to follow up on the task or to begin workin…

The commonly-stated guidance from Asana and others that all tasks should have an assignee and due date is not what I recommend except in the most simplistic of cases.

Larry