write a memo to the project team A mentioning them the deadlines for different tasks and the final date for project submission.
Answers
Answer:
The deadline for a project may be perfectly distinct in your mind, but that doesn't mean you're communicating it clearly to other members of your team. The first question to ask yourself is about the method you use to delegate tasks and projects. Are you assigning work verbally, via email, during planning meetings, using a project brief or template, or perhaps through an online work management system? Perhaps a little bit of each? The more different methods you use for assigning work, the more likely it is that tasks and projects will slip through the cracks and deadlines will be misconstrued.
The second question to ask is how you are phrasing the time limit. Is the deadline expressed in vague "It would be great to see this back by Thursday" language—or in more concrete terms? Unless you really do mean that it would be "great" to see it by Thursday but also good enough to see it by Friday or Monday, then be more clear.
The Solution:
Include an actual date-based deadline with every single work request, and "ASAP" doesn't count, unless you want team members to end up with a work queue full of ASAP requests, with no idea how to prioritize them. For best results, assign every task and project in the same way, every time, preferably using a repeatable template or an online system, where the deadline is in a predictable, easy-to-spot location.