Table of Contents

Comments and Communication

Messaging through comments, and @mentions, are an essential aspect in making sure every team member involved in the development of a course is kept up to date on all important updates and changes that pertain to them. Without following up a update or change to a project, or a task within a project, with an @mention communication with all relevant team members in Wrike, there is a large chance those people will end up "out of the loop".

Making an @mention in a comment in Wrike is very straightforward an intuitive. Please see an example here:

Keep in mind the following when creating comments and @mentions within the project and task details views in Wrike.

Who to Message

The following are the types of project roles that should be consistently @mentioned within tasks:

  • Task Assignees: As the personnel who expected to be able to complete the given task, this is perhaps the most crucial group to make sure is kept in the loop regarding any important task communication.
  • Downstream Task Assignees: Team members who are assigned tasks downstream in the project plan, that will be impacted by the progress of the given task, should be considered when critical task updates are being communicated. Especially when said update revolves around a change in when a task is expected to be completed.
  • Project Managers/Overseers: The team member tasked with managing a course, or program, level project (usually the course ID and sometimes the IDA or IDD) should be @mentioned to be kept apprised of all critical task updates and changes, as they need to keep aware of all factors affecting overall project completion and progress.
  • High Level Team Leads/Directors: When discussions around a task's progress reaches the level of impacting higher level functions, directors or team leads should be brought into the conversation. Some examples could be delays in a program's completion (IDDs) or potential changes/questions regarding the assumed steps to complete a task (leads for teams such as QA, CSG, ITG, etc).

When to Message

The following are potential events that should lead to the use of @mentions within tasks:

  • Questions Regarding Task Completion: When a task assignee has questions regarding the steps or needs for completing a task, they should @mention the team member who assigned them the task, who will usually be the project manager/overseer.
  • Task Progress Updates: When a task assignee has any updates to give regarding the progress made on a task, the team member who assigned them the task should be @mentioned. Some potential examples of this would be status changes, expected completion date changes, new file attachments added, change in assignees, etc.
  • Changes in Task Parameters: When the original assigner of task has any updates on the expectations/parameters of a task, an @mention to the task assignee should be used. Some potential examples of this would be changes in task start/expected completion dates, change in the relative priority of the task, additional info/guidance to aid task completion, change in assignees, etc.
  • Task Deletions: When a task has already been assigned, and is no longer needed for the development of a course, the team member deleting the task should always @mention the current assignee to inform them of the task removal, and a brief description of the reasoning for doing so.

Comment Attachments

When commenting, or @mentioning, in Wrike, it is possible to attach relevant files to the message. The file(s) will be attached both directly to the individual comment and the task as whole.

How did we do?

Adding Tasks

Statuses

Contact