Pete Ratkevich Product Manager

Case Study: Unified Dashboard

Unified Dashboard

Background

The Unified Dashboard (UDB) project at Pearson was conceived to address significant operational inefficiencies caused by a fragmented toolchain across departments handling content authoring, asset management, and product distribution. Teams were using a variety of tools that lacked integration, resulting in workflow silos and delays.

As the Product Manager, I was responsible for aligning the project with business objectives, defining the product roadmap, gathering and prioritizing requirements, and ensuring successful integration of these tools into a single, cohesive platform. This was a large-scale initiative that demanded technical precision, robust planning, and strong collaboration across teams.

The goal was to create a unified system that streamlined workflows, enhanced collaboration, and simplified access to resources for all users, whether they were technical or non-technical.

Project Overview

Objective:

The goal of the Unified Dashboard was to consolidate several content authoring, asset management, and distribution tools into one platform, reducing operational overhead and improving efficiency. By unifying these systems, we aimed to provide a streamlined user experience, eliminating redundant workflows and improving team collaboration across departments.

Scope:

Challenges Faced

1. Complex Integrations:

The project required integrating several legacy systems, each with its own API and data formats. These systems were not designed for easy interoperability, making the integration process highly complex. We had to design custom middleware and implement extensive testing protocols to ensure seamless communication between these systems.

2. Scalability and Performance:

Given the platform’s central role, UDB needed to handle large datasets and high user concurrency, especially during peak times. The architecture had to be scalable to accommodate future growth without performance degradation.

3. User Experience (UX):

The platform needed to cater to a diverse user base, including technical and non-technical staff. Balancing ease of use with functionality was crucial, as different users required varying levels of system complexity and flexibility.

4. Agile Development and Continuous Improvement:

We adopted an agile approach, but managing evolving requirements while maintaining focus on core functionalities was an ongoing challenge. New needs often emerged as users interacted with early versions of the platform, requiring us to balance flexibility with timely delivery.

Solutions and Execution

1. Technology Stack:

We selected a modern, scalable tech stack to ensure the platform could meet current and future needs:

2. Agile Methodology:

The project was divided into multiple sprints, each focusing on delivering specific features and functionalities. We held regular retrospectives to review progress and identify areas for improvement, which allowed for continuous refinement of both the product and our development processes.

3. User-Centric Design:

We adopted a user-centered design approach, engaging end users throughout the development process. Workshops and usability testing were key to refining the UI/UX, ensuring the platform was accessible to both technical and non-technical users. Wireframes and prototypes were tested and iterated on based on user feedback, helping us balance simplicity with functionality.

4. Microservices Architecture and API Integration:

To manage the complex backend integrations, we designed the platform using a microservices architecture. This approach enabled us to break down the system into smaller, independently scalable components, making it easier to integrate the various tools and services.

5. Continuous Integration/Continuous Delivery (CI/CD):

To support rapid, frequent updates, we implemented a CI/CD pipeline using Jenkins, Docker, and Kubernetes. This allowed for automated testing and deployment, ensuring that new features could be rolled out quickly without disrupting existing workflows.

6. Scalability and Performance Optimization:

We designed the UDB with scalability in mind from the beginning. By using ElasticSearch for high-speed search functionality and monitoring tools like New Relic for real-time performance tracking, we ensured that the platform could handle increasing user demand without performance bottlenecks.

Outcomes

1. Improved Efficiency:

The UDB reduced time spent switching between different tools, resulting in significant improvements in productivity. Teams could now collaborate more efficiently, with all necessary tools accessible from a single interface.

2. Enhanced User Experience:

The platform received positive feedback from users across the organization. Technical users appreciated the advanced features and flexibility, while non-technical users found the interface intuitive and easy to navigate.

3. Scalable Architecture:

The platform’s microservices architecture allowed it to scale as Pearson’s user base grew, without any degradation in performance. This scalable infrastructure ensured the UDB could meet increasing demands without the need for major architectural changes.

4. Continuous Delivery:

The CI/CD pipeline enabled us to deliver frequent updates and improvements, keeping the platform aligned with evolving user needs. This allowed the UDB to remain flexible and responsive to feedback, ensuring it could adapt to changes in user requirements and technology advancements.

Lessons Learned

1. Importance of User Feedback:

Incorporating regular user feedback into the development process was critical to ensuring the final product met user needs. Involving users early in the design phase helped us refine the platform and avoid costly redesigns later on.

2. Managing Scope Creep:

In an agile environment, scope creep can be a challenge. By maintaining clear communication with stakeholders and prioritizing requirements, we were able to manage scope effectively, keeping the project on track.

3. Integration Complexity:

Integrating multiple legacy systems required thorough planning and testing. Early identification of potential integration challenges helped us mitigate risks and ensure smooth system interoperability.

4. Scalability Considerations:

Designing for scalability from the outset ensured the platform could grow alongside user needs, avoiding the need for costly refactoring down the line.

Conclusion

The Unified Dashboard project successfully delivered a user-friendly, scalable platform that consolidated multiple tools into one cohesive system. Through a combination of agile development, user-centric design, and technical innovation, the project overcame significant challenges and delivered a solution that improved efficiency, collaboration, and user experience across the organization.

As the Product Manager, I was able to lead the project to successful completion by ensuring alignment with business goals, managing the product roadmap, and fostering strong collaboration across teams. The UDB continues to provide value by enhancing productivity and streamlining operations, and it stands as a testament to the power of agile methodologies and a user-focused approach in delivering complex solutions.