Pete Ratkevich Product Manager

Case Study: WPS and WRAPS

WRAPS

Background

Pearson’s Web Publishing System (WPS) had been a core platform for over a decade, enabling the authoring and management of digital content. However, the platform had become outdated, struggling to meet the demands of modern web standards, such as responsive design, accessibility, and enhanced performance. Additionally, maintaining the legacy system presented increasing challenges in terms of security and scalability.

To address these issues, Pearson initiated a project to replace WPS with a new, modern platform: WRAPS (WebDev Responsive Accessible Publishing System).

As the Product Manager, I was responsible for guiding the transition from WPS to WRAPS, continuously engaging with stakeholders, and ensuring that the migration was smooth and met the primary objectives of modernization, accessibility, improved workflows, and enhanced security.

Project Overview

Objective:

The key objectives of transitioning from WPS to WRAPS were:

Challenges

1. Data Migration:

Migrating large volumes of content—including complex media assets—was a significant challenge. Ensuring this data transition occurred without disrupting ongoing content creation projects was critical.

2. User Training:

Authors and administrators accustomed to the WPS system faced a steep learning curve in transitioning to WRAPS. Effective training and support were required to ensure a smooth adoption of the new platform.

3. Content Adaptation:

Existing content needed to be reviewed and adapted to meet the new platform’s standards, particularly around responsive design and accessibility.

4. System Integration:

WRAPS had to integrate seamlessly with Pearson's existing tools and workflows to avoid any operational disruptions during the transition period.

Solution

1. Development of WRAPS:

WRAPS was designed with a mobile-first approach, ensuring that all content was accessible across devices, from desktops to smartphones. The platform was built to meet WCAG 2.0/2.1 accessibility standards, including essential features like:

WRAPS introduced streamlined tools and processes, simplifying content creation, management, and publishing. Features such as automated JSON generation, template-based authoring, and media integration reduced the complexity of content management.

2. Phased Rollout and Migration:

The migration to WRAPS was executed in phases, starting with less critical content and gradually moving to more complex and critical assets. This phased approach allowed for adjustments based on feedback from early users. The WPS system was maintained alongside WRAPS in a dual environment during the transition period, allowing content creators to continue using WPS while WRAPS was tested, refined, and gradually adopted.

3. Training and Support:

To address the learning curve associated with moving from WPS to WRAPS, a comprehensive training program was rolled out. This included:

4. Content Review and Adaptation:

To ensure all content was optimized for WRAPS, we undertook a comprehensive review of migrated content. Custom scripts and tools were developed to automate parts of the content adaptation process, particularly focusing on responsiveness and accessibility. This minimized manual effort and ensured consistency across the platform.

Outcomes

1. Enhanced Accessibility:

The migration to WRAPS resulted in content that was fully compliant with WCAG 2.0/2.1 accessibility standards, making it accessible to users with disabilities. Features like screen reader compatibility and high-contrast modes improved the overall user experience for individuals with diverse needs.

2. Improved User Experience:

The streamlined and intuitive design of WRAPS provided content creators and administrators with an improved user experience. Feedback from users indicated that the new platform significantly reduced the time and effort required to create, manage, and publish digital content. The mobile-first approach also ensured that content looked good and functioned well across all devices.

3. Successful Decommissioning of WPS:

The WPS platform was successfully retired after all content was migrated to WRAPS without causing disruptions to ongoing projects. The phased migration allowed the team to maintain system stability and ensure a smooth transition.

Lessons Learned

1. Importance of Phased Migration:

Breaking the migration into phases proved to be essential for ensuring a smooth transition. This approach allowed for incremental improvements and risk mitigation, avoiding potential data loss or major disruptions to users.

2. User-Centered Training and Support:

Providing comprehensive training and ongoing support was crucial in helping users adopt the new platform. Early workshops, detailed documentation, and dedicated support channels helped to ease the learning curve and reduce frustration among content creators.

3. Automation for Content Adaptation:

The development of custom scripts and tools to automate content adaptation saved significant time and effort during the migration. By automating the adaptation process, we were able to ensure that content was consistently formatted for responsiveness and accessibility.

4. Ensuring Seamless Integration:

Integrating WRAPS with existing systems was key to maintaining business continuity. The platform's ability to seamlessly interface with Pearson’s tools and workflows ensured that the migration did not disrupt ongoing operations.

Conclusion

The transition from Pearson’s legacy WPS system to the modern WRAPS platform was a major success, enabling Pearson to stay ahead of evolving web standards and user expectations. By prioritizing accessibility, user experience, security, and performance, WRAPS has established itself as a future-proof platform for managing digital content at Pearson.

By modernizing Pearson's content management infrastructure, WRAPS not only improved workflow efficiency but also delivered a secure, responsive, and accessible platform that is aligned with industry standards and future growth.