Migration Support

Method: Page Tracking
Why?  To support development in migrating 2,200 pages.

After designs and requirements were delivered to development, my team and I began to work on migrating pages.

The website was built using Wordpress.


Rewriting content for core pages

Method: Shared Google Doc Templates
Why?  Many pages had outdated business jargon on it - it was not user friendly. As development was building the site, we used Google Docs as a temporary means to collaborate with Stakeholders in rewriting their copy.

Feedback from the DX Ad Hoc (core personas), was that the language on the website needed improvement.

After evaluating the quality of the existing copy, we focused on medium to high effort pages, the Digital Editorial team rewrote the copy, and my team followed up with stakeholders to get sign off.


Define Voice and Tone

Method: Google Doc
Why?  For future governance. To establish consistency and standards in how the organization speak to our users.

The Content Improvement project (above) allowed us to begin to define web Voice and Tone.

Learnings were captured in a document and shared with staff during Content Migration trainings.


Define Images Guidelines

Method: Google Doc
Why?  For future governance. To establish consistency and standards in how the organization chooses images.

For future website governance, I worked on an Images Guideline document that I shared with staff.

This was a helpful guide for future website governance and decision making once the website went live and was updated by stakeholders.


Ensure the New Website was ADA Compliant

Method: Excel Tracking Sheet
Why?  To ensure the website experience works for disabled people. To be compliant with 'Level A' ADA standards.

IEEE requires all websites to be 'Level A' ADA Compliance (the old website was not).

Using the SiteImprove Accessibility Checker, I began evaluating each template to see if it was ADA 'Level A' compliant or not.

Violations were documented and given to IT to resolve.


Define Usability Benchmarks and Capture Usability Issues

Method: Qualitative Observational Testing
Why?  To measure usability, set benchmarks, and get user feedback.

As development was busy building the website, we used the additional time to do usability testing on the website.  This would help future benchmarks in usability and also check for any usability issues.

Non-critical usability issues would be slated to be fixed in Phase 2 of the project since IT bandwidth was maxed out.

For testing...

  • JZ created the script with my review
  • I created Task Scenarios (~13 tasks total)
  • JZ prepared the Invision Prototype for all tasks

After each task, we captured:

  • Task completion rate
  • Time to complete task
  • Errors
  • Ease of Use
  • Satisfaction