Ux Design
Product Enablement Hub

Overview

The Product Enablement Hub is an internal tool in order to limit the risk of bringing new products to the US and Global markets. The web app devised of Angular and QuickSuite frameworks serves as a cross functional workbench designed to provide real-time product statuses, a repeatable review framework powered by a workflow engine, and a task management system.  I lead the projects User Experience initiatives as a part of the core product management team.

Process

The project was agile, and so this design process was an approach taken to be able to discovery and ideate the entire product. Next I’d wireframe and style the prototypes for hand off to our QA team to test. We’d formulate user stories to test against for experience. We’d iterate on some and create bugs for others. Lastly, wed launch our new features throughout the project, giving our stakeholders time to test certain sections of the product throughout. We’d collect their feedback and create a backlog of system updates to take into account.

Discovery

Ideation

Wireframe

Styling

Testing

Launch

Competitive Analysis

As this was an internal facing application, It was important to note comparisons amongst other applications rather than competitive ones. The application functionality was to act much like a project management system like ADO Azure with backlog items, active items, and on hold items. Items that would be assigned to individuals and groups, items that were then to be prioritized and sized, and items that were then turned into tasks. Tagging systems and commenting functionality also embodied some of the requirements of the application. It was important to see the connections, and to use the analysis to understand some of the positive traits that others were implementing into their systems in order to better assess how to tackle ours.

Survey Analysis

We surveyed a handful of users to understand what types of devices they were using to handle their efforts and tasks.

70%

70% of users handle their work on laptops or desktops

30%

30% of users handle their work on tablet devices

0%

0% Full Time Mobile – Those using mobile would do so only when they absolutely needed to. 

We were designing for a fully accessible application, 300% zoom and mobile have very similar features, and so designing for a mobile friendly application killed two birds with one stone, with few adjustments needed – font sizing and button sizes. 

User Personas

Katy Lewis, Product Enablement Approver

Product Enablement Approver- Katy Lewis 40. Goals, To find a more cohesive way to assign, prioritize, and approve product use cases for launch. Biography– Katy is a product approver, working on the Innovation Coordination Team. Katy manages the risk management process bringing products through an analysis to bring them to market for the betterment of PwC as a whole. Frustrations Currently, Katy does all of this work through google sheets.  Documents are all over the place. There is no automation between the intake requests for products and the information she is working on managing on google sheets.

Current uses: Google Sheets Google Slides Google Docs Behaviors: Assign, Prioritize, Size, Approve

Jeremey Langry, ICC Facilitator

ICC Facilitator- Jeremy Langry 32. Goals, To facilitate the product enablement process and easily collaborate with product owners to understand the background of each product that was coming into the system. Biography– Jeremy is a Facilitator that works with the Innovation Coordination Team. Jeremy facilitates the process by collaborating with product owners to understand where their products fit into PwC as a whole. Frustrations– Currently, the process Is through word documents that don’t allow the facilitators to track decisions very easily, nor understand the risks quickly. The process is very lengthy and Jeremy feels this can be shortened.

Current uses: Google Sheets Google Slides Google Docs

Behaviors: Assist Intake Responses and Guide

User Journey

It was important for the journey of the system to flow holistically as the product was not to be thought of as a linear process. The user journey helped steer the information architecture of the product and helped to determine dependencies which ultimately lead to a better understanding of the UX road map by helping to align the hand off prioritization so that development would have enough to develop every sprint. It was important for Design to stay ahead of Dev sprints.

System Intake

Because we were creating a system that would automatically create project types based on specific product specifications and use cases, there was a lengthy intake process that required a series of questions that would make up the data that would be imported into product profiles.

Planning

Planning was an important part to design into the system for our power users. Since this was an area that one of the user personas would use frequently, we planned out a process for them to be able to prioritize, capacity plan, and backlog products that were needing working on.

Task Execution and Summary

Each product that would go through this process would have supporting documentation that would need to be easily referenced, so the creation of summary screens was important to be able to view everything in one place. From here, users were able to manage their task executions as well.

Next Case Study
Interaction + Experience Design
Microsoft.com Motion