Refactor Process

Process Flow for Refactors

What is a Refactor?

A refactor is an effort to apply enterprise design and strategic guidance to a small section of pages or a specific zone of the website. A refactor enforces:

  • Goal setting
  • Audience focus
  • Application of UI standards from Arches
  • Content retooling based on the Content Strategy Playbook

How Long Does a Refactor Take?

The optimal timeline, as outlined by the EDSC Teams, is 10 weeks.

Considerations:

  • Timelines may shift due to business priorities, team response times, and scope changes.
  • Delays can occur when external parties miss deadlines for returning deliverables or scheduling meetings.
  • IT components, such as adding dynamic feeds and personalization, can extend the timeline by 3-6 weeks or more.

Who is Involved in a Refactor?

The Refactor Team includes members from:

  • Enterprise Content Team
  • UX Team
  • Client SME (Subject Matter Expert) responsible for providing necessary inputs to ensure project success.

High-Level Process Outline

Step 0: Intake and Preparation

  1. Step 1: Review (Weeks 1-3)

  2. Step 2: Content Design (Week 4)

  3. Step 3: Content Creation (Week 5)

  4. Step 4: Iterating and Reacting to Real Content (Week 6)

  5. Step 5: Editing (Weeks 7-8)

  6. Step 6: Publishing (Weeks 9-10)

Detailed Process with Team Responsibilities

Step 0: Intake and Preparation

  • The Client submits a project intake form on the Monday Platform.
  • Project intake review:
    • Intake form is assessed.
    • Team is assembled (Marketing, SME, Client, UX, EDS, Analytics).
    • Kick-off meeting is conducted.
    • Deadlines are reviewed.
    • Project enters the UX and EDS backlog.
  • Timeline begins once the project is picked up from the backlog.

Step 1: Review (EDS & UX)

  • SME Responsibilities:
    • Provide all relevant content (Web, Communications, Print Materials, Marketing).
    • Meet with Analytics to define reporting needs.
  • Evaluation & Retooling:
    • Content is reviewed and adjusted based on goals and audience.
    • Follow-up Discovery Meeting conducted.

Step 2: Content Design (EDS & UX)

  • Tailored content delivery may include:
    • Wireframes
    • Process Flows
    • Publication Schedules (Marketing involvement)
    • Content Collection Documents
    • Outline of required artwork (Marketing contribution)

Step 3: Content Creation (EDS, SME & Marketing)

  • Content is completed based on refactor team guidelines.
  • Marketing request:
    • If required, artwork is created by Marketing.

Step 4: Iterating and Reacting to Real Content (UX)

  • The content collection document may require a refactor of UI structures outlined in wireframes.

Step 5: Editing (Full Team Review)

  • Team reviews and finalizes:
    • Artifacts
    • Wireframes
    • Content
    • Design elements
    • Artwork
  • Once approved, materials are prepared for Production.

Step 6: Publishing

Production Requests

  • The Refactor Team submits all final content and designs to the editorial team via Jira Ticket.

Production Support

  • The Refactor Team liaises with stakeholders to ensure smooth project progression through Author Site.

Production Review & Release

  • SME, Marketing, and Client conduct final reviews and corrections on the Author Site.
  • After final approval, the Web Production Team releases the Refactor Pages to the live site.

Summary of Key Responsibilities

Client SME

  • Provides all necessary content.
  • Engages in review meetings and approvals.

Marketing Team

  • Supplies required artwork and publication schedules.
  • Supports promotional aspects of the refactor.

UX & EDS Teams

  • Drive content design, review, and iteration.
  • Ensure adherence to UI and content standards.

Analytics Team

  • Defines reporting needs.
  • Evaluates data impact.

Web Production Team

  • Implements approved pages on the live site.
  • Conducts final quality checks before release.

This document provides a structured workflow to ensure an efficient and goal-driven Refactor Process.