SLX Internal Design Asana Process

SUBTASKS

1. Design

3. Designer Review

4. Client Test

2. Build & Test

4. QA Review

5. Schedule Send

 Looking for our Internal Salesforce Asana Process?

CLICK HERE

About

This internal design process outlines how client tasks are assigned and how our various teams collaborate towards completing design tasks. Please review the following process below. If you need additional help or clarification, please reach out to your team leads.

COMING SOON: Video tutorials!

Versions

Last Updated: November 12, 2024

As we continue to improve and optimize this process to be as efficient and streamlined as possible, there will be on-going process updates. Process updates will always be announced in huddles and updated on this document. We welcome feedback and suggestions on the current version of the process. Thank y’all for your patience! 

Back to Top ↑

The Process: General Overview

DESIGN Subtask

  1. The AC creates a parent task on the relevant client PRIVATE board (internal)
  2. The AC assigns this subtask to the Creative Team Lead, who will assign it to a Designer
  3. Designer reviews task request and creates designs in Figma, WordPress, or Adobe Creative Suite
  4. For emails only, the designer checks the design for dark mode compatibility in Email on Acid
  5. Designer submits design proof (including dark mode proof for emails) to Creative Team Lead by tagging them in the Asana
  6. Creative Team Lead tags QA once design is approved
  7. QA tags Designer once review is complete
  8. Designer sends a fresh Figjam link including GD project folder and Figma/Emailify link for the client and developer, then tags AC
  9. The AC will provide the Figjam link to the client for review
  10. If there are any edit requests by the client, the AC will return to the internal task and tag the designer with requested edits
  11. Once edits are made, the Designer tags QA again for approval
  12. Once QA approves, follow steps 7-8 above
  13. The AC verifies that the design is approved by the client. Once the design is approved, the AC takes the copies the approved Figma, Emailify, and Google Drive links and pastes them into the BUILD & TEST subtask.

Back to Top ↑

BUILD & TEST Subtask

For emails (all teams):

  1. AC will assign this to Developer Team Lead, who will assign to a Developer. 
  2. The assigned Developer will put the email into Pardot using the Emailify link provided by the designer in the DESIGN task.
  3. The developer upload all images in Pardot and link in the code using the GD folder images provided by the designer from the DESIGN task (folder will in Asana task description)
  4. The assigned Developer will send a test email to themselves and to email on acid.  They should click every single link in the email to ensure they are all working correctly. 
  5. If approved, the assigned Developer will send a test email to:
    1. The designer assigned to the DESIGNER REVIEW subtask
    2. QA (SLX_QA) Pardot list
    3. internalqa@saleslabx.com (add as individual email) 
  6. The developer upload all HTML in GD folder provided by the designer from the DESIGN task  (folder will in Asana task description)
  7. The assigned Developer will close this task out once the tests are sent in step 4.
  8.  

For landing page (all teams):

  1. AC will assign this to Developer Team Lead, who will assign to a Developer
  2. The developer upload all images in SLXCloud and link in the code using the GD folder images provided by the designer from the DESIGN task (folder will in Asana task description)
  3. The assigned Developer will build the landing page in Webflow, test it and optimize for ipad and mobile, and put into Pardot.
  4. If approved, the assigned Developer will close this task.
  5. Then, the assigned Developer will submit the live Pardot link into the following subtask and reach out to QA in the comments for them to review:
  6. DESIGNER REVIEW subtask: Developer will drop the link here then tag the original Designer

Back to Top ↑

EXPORT FOR DEV Subtask

  1. AC assigns this to the last Designer who worked on the DESIGN task
  2. The Designer will fill this subtask out when they are exporting their design files for dev
  3. Developer will mark the task complete once they’re sure what was exported was satisfactory

DESIGNER REVIEW Subtask

  1. AC assigns this to the original Designer on the same day as the “Build & Test” subtask
  2. This task should block the QA Review subtask
  3. The original Designer will close this out once they have reviewed and approved the asset
  4. If any edits are needed, the Designer will tag the original Developer who built the asset to make the necessary changes
  5. Once changes are made, the Developer will tag the Designer for review again, then follow step 3

CLIENT TEST Subtask

  1.  ACs assign this to Eliav on the same day as the “QA Review” subtask, who will then reassign to another Developer
 

For emails: The assigned Developer will:

  1. First send a test to SLX_POC+AC
  2. Then send to any other test lists as requested by the client
 

For landing pages: The assigned Developer will:

  1. Submit the live landing page link and Pardot link and tag the AC to share with the client

 

If there are any minor client edits requested during this stage (such as text or spacing adjustments):

  1. The AC will first tag the Developer to make the edits.
  2. The Developer will make the edits.
  3. For emails: The Developer will send an updated test out and tag the AC.
  4. For landing pages: The Developer will provide an updated link for the client and tag the AC to share with the client
Note: QA review is not necessary in this stage for minor edits, as long as the AC reviews the updates and confirms them before sharing with the client.
 

If there are any major design client edits requested during this stage (such as layout updates or new sections):

  1. The AC will reopen the Design subtask and tag the original Designer, providing the edits needed
  2. The original designer will make the edits and tag QA to review the edits
  3. After QA approves, QA will tag the Designer 
  4. The Designer will provide a fresh Figjam link to the update draft, tagging the AC
  5. The AC will send the link to the client to review
  6. After the client approves, the AC closes the Design subtask and moves back to the “Client Test subtask” to restart the test process
    1. For emails: The Developer will send an updated test out and tag the AC.
    2. For landing pages: The Developer will provide an updated link for the client and tag the AC to share with the client

Back to Top ↑

SCHEDULE SEND Subtask

For list emails only:
 
  1. AC will assign this to the original Designer after the tested email has been approved
  2. The Designer assigned to this task will go to the CLIENT TEST subtask to get the Pardot email link. They will schedule the email out and provide the SEND details in the card (see below), tagging QA to review the SEND details first
  3. The SEND details must include:
    1. Send date and send time with timezone
    2. Preheader text
    3. Mailing lists with total mailable prospects per list (if multiple)
    4. Screenshot of email send “content” details (not the report screenshot) 
    5. Screenshot of Account’s “My Profile” page displaying time zone  [UPDATE]
  4. The SEND details for A/B sends must include: [UPDATE]
    1. Send date and send time with timezone
    2. Preheader text
    3. Mailing lists with total mailable prospects per list (if multiple)
    4. Screenshot of both email send “content” details 
    5. Screenshot of both email send “report” details
    6. Screenshot of Account’s “My Profile” page displaying time zone 
  5. Once QA has reviewed and approved, QA will tag the AC
  6. The AC will only share SEND details with the client once QA tags them. The AC should still do a quick review of the SEND details as well
  7. Once the client has approved the SEND details and after the email goes out, the AC will close this task and the parent task if there are no other remaining subtasks


Back to Top ↑


The Process: Detailed Overview

CLICK HERE for the Account Coordinator Detailed Process Overview

CLICK HERE for the  Detailed Process Overview for Designers