SOP - DXT Project Overview (Merch)

Purpose

This document outlines the key processesย a typical Merchandise/Digital Experience Team project.ย 

Policies and Procedures

Submitting a Project Request

In order to submit a project request to the DXT Visual Designers, you must fill out the Marketing Request Form found in the drop down on this page in Workfront: https://ferguson.my.workfront.com/requests

Make sure you select the following fields on the form in order to route your request to the DXT Project Manager:

What teams would be needed for the success of this request?
eBusiness

Job Type
Website Content

Please make sure you fill out the section in the screenshot below. The boxes filled in are just examplesโ€ฆ

DXT Deliverables Sheet

Purpose

In order to get the Merchandisers, Visual Designers, Copywriter and SEO literally on the same page for each project, we have created the DXT Deliverables Sheet. The folder containing these spreadsheets can be found here: https://mydigitalspace.sharepoint.com/:f:/s/fei.eb.designcenter/ElOVjGht_mFCsyHFCW6egMoBhqUsZtOkj4cIEG_NXnCI8Q?e=NoIKok

Submission, Sharing and Editing

The Merchandiser can submit the DXT Deliverables Sheet at the time of the request, at the Kickoff/DPR, or at a later specified date. It must be provided as a link. The document must be editable by โ€œPeople in MyDigitalSpace with a link.โ€ This allows us to work from one true document at the same time. DXT cannot begin work until this spreadsheet is provided. The copy must be provided or approved by the Copywriter on the spreadsheet.

Description

Each Merchandiser has their own sheet. They are to use a new one each calendar year. The spreadsheets all contain the following:

  1. A โ€œTEMPLATE TO COPYโ€ tab that can be duplicated for each new promotion. Each promotion should have its own named tab.

    1. WF Project # (you only need to put this number in one cell as it pertains to the entire promo tab)

    2. Deliverable

      • Hero

      • Secondary

      • Skinny

      • Catalog

      • Catalog Skinny

      • Side

      • Landing Page

      • JSON

      • Other

    3. Primary Message

    4. Secondary Message

    5. CTA

    6. Disclaimer (if any)

    7. Imagery Specifics/Details/Etc.

    8. Tracking Code

  2. A hidden โ€œDROPDOWNโ€ tab which houses the data for the drop downs in column B of the โ€œTEMPLATE TO COPYโ€ tab. You can ignore this tab. It is locked so it cannot be edited.

Kickoff Meeting/Daily Project Review (DPR)

The goal of the project kickoff meeting is to discuss the project details with all parties involved,ย establish tasks needed and a timeline, andย get commitment from everyone.ย  There is a daily project review meeting called the DPR which is scheduled every morning at 8:30. This allows for a consistent blocked period of time when everyone can come together to discuss new project requests.

If you wish to discuss your new project request in the following dayโ€™s DPR, you must submit the request by 2:00 and it must be reviewed by the DXT Project Manager before 2:30. If you are near the cutoff time, please contact the DXT PM directly to ensure your request makes it into the following dayโ€™s DPR. If there are no projects to discuss for the following day, a cancellation for that DPR is sent out around 3:00pm. The reason for this is so everyone can plan to be in attendance for the early morning meeting the next day.

Brief Outline of a Typical Merchandise/DXT Project from Start toย Finish

  1. Merchandise has an idea for a promotion and gathers information needed so it can be submitted.

  2. Merchandise fills out the project details on the Marketing Request form and submits the request in Workfront.

  3. DXT Project Manager receives the request and forwards the details to stakeholders, designer, copywriter and SEO for their review.

  4. DXT PM schedules a kickoff meeting/DPR

  5. All parties involved attend the kickoff/DPR and the project is reviewed.

  6. All parties involved commit to their tasks and dates.

  7. DXT PM converts the Workfront request into a project in Planning mode.

  8. DXT PM adds tasks to the project and sets the project status to Current.

  9. All work is completed and the deliverables are published to Production.

  10. Once all tasks are marked complete, the project's status automatically changes to Complete.

DXTย Project Phasesย 

Theย Digital Experience Teamย separates out their projects inย 6ย main phases:

  1. Define

  2. Design

  3. Design Review

  4. Develop

  5. Testing

  6. Deliver

Define

Includes kickoff meeting/DPR,ย research, and any tasks that need to be completed before Design can begin.ย ย ย 

  • Discovery -ย The Designer uses the โ€œDiscoveryโ€ time to make sure they have what they need to get started.ย  They can also use this time to complete any research that is needed for the project.ย 

  • Copy & SEO โ€“ Tasksย to be completed by a Copywriterย and an SEO Strategist.ย 

  • Additional tasks might be added here and assigned to the appropriate person if there are outstanding items needed before someoneโ€™s work can begin.

Design

Can include the following tasks:

  • Initial wireframes - low fidelity designs

  • Designย - time allowed to create designs for deliverables

Design Review

Can include the following tasks:

  • Peer review - designs are shared internally with either the DXT Manager or Design Lead

  • Design review - designs are shared with the requestor and anyone else who is marked as approver on the project

  • Design copy review - designs are shared with the Copywriter to ensure copy is correct

  • Design final edits - time allowed to make corrections before development based on feedback from reviews

Develop

Can include the following tasks:

  • Development - work needed to get the designs coded and into WCS

  • XM Setup - work Merchandise has to do in order to get the assets to show up on production

Testing

Can include the following tasks:

  • Test on Staging - Assigned to the requestor, this is time allotted to test assets on Staging

  • Develop Final Edits - time allowed to make corrections to the copy before Go Live

Deliverables are tested on Staging by the Merchandiser and any additional approvers. Marking the โ€œTest on Stagingโ€ task as complete indicates approval of the assets on Staging.

Deliver

Can include the following tasks:

  • Publish - task which contains information for publishing to productionย (WF number, Go Live date)

  • Search Engine Submission - work needed for submitting a new page to search engines