Cognitive walkthrough / contextual inquiries / prototyping

Screen Shot 2019-12-18 at 8.47.35 AM.png

Design, prototype, and test features to lift Project Mercury out of its MVP platform

“Documenting and communicating changes that have occurred to a mass-produced product is a key job requirement for many product managers. When a change in the fit, form, function or price of a product is introduced, a product manager issues a Product Change Notification (PCN) to their customers in order to share what changes have occurred. Today, this process happens through a variety of mechanisms (e.g., Microsoft Word template > PDF > Dropbox file shared with customers; posting change notices on a company blog), with little standardization and many opportunities for missed communication between businesses and customers. Project Mercury is an MVP platform to address these key challenges with documenting and communicating changes to products, including new product introductions (NPIs), end-of-life announcement (EOLs) and all other product change notifications (PCNs)” -Andy R, Stakeholder. What happens when a product change isn’t communicated well? Production lines go down, end consumers become upset, hours or days are waisted on the phone between manufacturers and distributors. Manufacturers are missing vital opportunities to create genuine cohesion between production lines and end consumers. PCNs are issued by manufacturers to inform customers about a change to a mass-produced product or its manufacturing process. A New Product Introduction (NPI) encompasses all the activities within an organization to define, develop and launch a new or improved product. "End-of-life" (EOL) is a term used with respect to a product supplied to customers, indicating a product is in the end of its useful life (from the manufacturers point of view). It is meant to standardize the creation process and streamline the distribution of that information to those who need to know it. Project Mercury is a web application that facilitates the creation and tracking of PCNs. The overall goal of Project Mercury is to streamline and standardize the PCN creation process, while providing a user-friendly experience for locating and viewing the PCNs.

 

Users

  • Product Managers needing to communicate product changes to customers efficiently

  • Individuals looking for updates on the products they are using or selling

Goals

  • Receive email updates when products are included in a PCN. If a product is changed, each product owner using that product will be notified via email

  • Product details page with timeline showing history of changes. Once a user has decided to navigate to the product details page, they would be able to view every PCN, EOL, and NPI that include said product

Methods:

  • Cognitive walkthrough

  • Contextual inquiry

  • Prototype

 

Research/Evaluate


Cognitive Walkthrough

Project Manager Dashboard sketched wireframe

Project Manager Dashboard sketched wireframe

Andy provided me the key tasks a Product Manager can perform:

  • Create a PCN/NPI/ or EOL

  • Edit a PCN

  • View a PCN

  • Search for a PCN

Remote and on site cognitive walkthroughs revealed natural patterns of communicating change among companies and organizations both internal and external. The focus of the cognitive walkthrough is to understand our user’s and system's learnability for new or infrequent users. You can download the deck featuring lightly annotated visuals matching the data sheet below.

 
 

Testing


I created a system for users to be notified about their PCNs and an easy way for Project Managers to communicate that change. Project managers will have a list of “customers” as represented below to select customers who use the product that PCN is for. Once the PCN is approved by the admin, an email notification will be sent out to the PCN group with a PDF file of the PCN form. Clients can respond to that notification via a contact form. A customer service representative will receive the response and respond accordingly. Feel free to take the Invision tour!


 
Updated dashboard with search bar, updated iconography, and simpler PCN form

Updated dashboard with search bar, updated iconography, and simpler PCN form

Customer list and PCN group

Customer list and PCN group

Project Mercury keeps the end user off the platform as much as possible while communicating vital and important information for them about changes in products
— Andy R, Founder
Clients email notification and response opportunity

Clients email notification and response opportunity

Customer service representative notification and response to client

Customer service representative notification and response to client

 

Research Recommendations


Contextual Inquiry

Remote contextual inquiry with founder Andy Reiter

Remote contextual inquiry with founder Andy Reiter

Product Change Notices (PCN’s) are used among a magnitude of industries to communicate changes in product from manufacturer to end user with a distributor as the middle man. Project Mercury wants to become a key influencer in the space of PCN’s. They’re goal is to formalize the process of PCN’s so the end manufacturers are fully informed of all product changes that distributors may not convey. Currently, there is no one standardized way to communicate changes in products efficiently and consistently from manufacturer to manufacturer. This is what Project Mercury is set out to do. With average five per week roughly 260 PCN’s/ year, there is a lot of communication to be had that currently isn’t being held

End of Life (EOL’s) notices help the end users save money allowing them time to find new manufacturers for the parts they need. If an end user doesn’t find a new manufacturer or doesn’t want to, their end product will be discontinued. Manufacturers communicate product changes (PCN), new product introduction (NPI PCN), and end of life (EOL PCN) to distributers who are responsible for communicating these PCN’s to the end user. These notices are essential to the end user. When these EOLs are inaccurate, miscommunicated or worst of all not communicated it puts strain on all parties involved all the way down to the final consumer.

One of the largest issues perceived in this space is delivering PCN’s to the end user. There is no accountability system for distributors to hand off PCN’s from manufacturers to the end user. Emails and informal documents have been proved by research to be sufficient for small operations, however Project Mercury is hoping to achieve a larger goal.

Its tedious work to create a PCN/NPI/EOL and due to the informal process, is very easy to make mistakes, miss important information, and make sure it gets to everyone who needs it. They are often handed from person to person in hopes that’s they make their way down the chain to the end user. What happens when the end user doesn’t get any PCN’s? The end users spend hours wasted on the phone talking to distributers who need to talk to manufacturers to get simple answers such as “why is this part going out of production? Where will I get these parts now? How long do I have to purchase these parts still?”. Some tools currently used to communicate PCN’s are email, Dropbox and Microsoft Word.

 

Site style guidelines


Colors and icons

Colors and icons

Symbols

Symbols