Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Clear and frequent communication. Comments in chatter should clearly describe any issue or question you may have. Check-ins from other teams regarding the status of the task should not go unanswered, even if you are not certain on a timeline to resolve.

  • Be mindful of the listed due date. Launch typically keeps the due dates on these tasks updated to account for where the project should be at to meet our goals of getting the site launched. If you are unable to complete a task by the due date listed, you must leave a comment for Launch to let them know there will be a delay as soon as possible.

  • Summarize any interactions off Salesforce that led to resolution. If a phone call or a Teams chat needs to happen to resolve a task, a Chatter comment should be placed by either you or the person you spoke to with a summary of the conversation and where the task currently stands (are we waiting on dealer response, do we need help from another team, etc.).

  • Keep the task status updated. Statuses should be utilized as follows:

    • New - the task has not yet been started, or the items you were waiting on have recently been provided to you and you have not yet started the necessary work after receiving what you need to do the task.

    • In Progress - You have started work on the task, but not completed it yet. This should be updated right when you start to work on it.

    • On Hold - The task is waiting on AM/Support/etc. to contact the dealer for necessary clarification, assets, etc.

    • Completed - The task is done.

  • Do not close Fulfillment tasks while you are waiting on more information. Put the task in the On Hold status and let it sit until you have what you need to complete. We should not complete a Fulfillment task unless 1) the work is actually complete, or 2) the dealer decides to cancel the work and we no longer have to do it.

  • Keep the “Actions Taken” section updated. When we have a task that has multiple to-dos listed (for example, a QA Updates task where there is a list of items to do), and we do not complete the entire task in one go, we should be adding items to the Actions Taken area when we stop work for the day on that task so it is clear what has been completed. This also helps other teams figure out where the task is at, and potentially what items Launch may need to address (as they will be kept in the Details/Instructions field above Actions Taken) to get the task finished.