CLIENT:
Digi-International
CLIENT:
Digi-International
CLIENT:
Digi-International
CLIENT:
Digi-International
CLIENT: Digi-International
METHODS:
Cognitive Walkthrough, User Research, Wireframing, Prototyping, Visual Strategy
METHODS:
User Research, Wireframing, Prototyping, Usability Testing, Visual Strategy
METHODS:
Cognitive Walkthrough, User Research, Wireframing, Prototyping, Visual Stragegy
METHODS:
Cognitive Walkthrough, User Research, Wireframing, Prototyping, Visual Strategy
METHODS: Cognitive Walkthrough, User Research, Wireframing, Protoyping, Visual Strategy
TOOLS:
Otter.ai, Paper & Pencil, Sketch, Invision
TOOLS:
Otter.ai, Paper & Pencil, Sketch, Axure, InVision
TOOLS:
Otter.ai, Paper & Pencil, Sketch, InVision
TOOLS:
Otter.ai, Paper & Pencil, Sketch, InVision
TOOLS: Otter.ai, Paper & Pencil, Sketch, Invision
SUMMARY:
Project Mercury is is a young, web-based application, used by product managers at Digi-International. Its intent is to improve their ecosystem for creating and approving product change notifications, or PCNs, by making the tedious process of creating PCNs more efficient and less error-prone.
After interviewing the Product Owner, as well as several others who work in the industry, I identified and prototyped a number of new features to improve the application. These, along with a style guide, were then passed off to developers for implementation.
SUMMARY:
Project Mercury is is a young, web-based application, used by product managers at Digi-International. Its intent is to improve their ecosystem for creating and approving product change notifications, or PCNs, by making the tedious process of creating PCNs more efficient and less error-prone.
After interviewing the Product Owner, as well as several others who work in the industry, I identified and prototyped a number of new features to improve the application. These, along with a style guide, were then passed off to developers for implementation.
SUMMARY:
Project Mercury is is a young, web-based application, used by product managers at Digi-International. Its intent is to improve their ecosystem for creating and approving product change notifications, or PCNs, by making the tedious process of creating PCNs more efficient and less error-prone.
After interviewing the Product Owner, as well as several others who work in the industry, I identified and prototyped a number of new features to improve the application. These, along with a style guide, were then passed off to developers for implementation.
SUMMARY:
Project Mercury is is a young, web-based application, used by product managers at Digi-International. Its intent is to improve their ecosystem for creating and approving product change notifications, or PCNs, by making the tedious process of creating PCNs more efficient and less error-prone.
After interviewing the Product Owner, as well as several others who work in the industry, I identified and prototyped a number of new features to improve the application. These, along with a style guide, were then passed off to developers for implementation.
RESEARCH
RESEARCH
RESEARCH
UNDERSTANDING PRODUCT INTENT:
My first step to understanding the application and related problem-space was to perform a cognitive walkthrough on Project Mercury gain a better understanding of its mechanics. The focus was on the essential operations that comprise the core of the program.
UNDERSTANDING PRODUCT INTENT:
My first step to understanding the application and related problem-space was to perform a cognitive walkthrough on Project Mercury to gain a better understanding of its mechanics. The focus was on the essential operations that comprise the core of the program.
UNDERSTANDING PRODUCT INTENT:
My first step to understanding the application and related problem-space was to perform a cognitive walkthrough on Project Mercury gain a better understanding of its mechanics. The focus was on the essential operations that comprise the core of the program.
UNDERSTANDING PRODUCT INTENT:
My first step to understanding the application and related problem-space was to perform a cognitive walkthrough on Project Mercury gain a better understanding of its mechanics. The focus was on the essential operations that comprise the core of the program.
PRIMARY TASKS:
PRIMARY TASKS:
PRIMARY TASKS:
PRIMARY TASKS:
PRIMARY TASKS:
Register a new user account
Register a new user account
Register a new user account
Register a new user account
Create, search for and view 3 types of product notifications (PCN, EOL, NPI)
Create, search for and view 3 types of product notifications (PCN, EOL, NPI)
Create, search for and view 3 types of product notifications (PCN, EOL, NPI)
Create, search for and view 3 types of product notifications (PCN, EOL, NPI)
Approve/Deny a product change notification
Approve/Deny a product change notification
Approve/Deny a product change notification
Approve/Deny a product change notification
While going through the tasks I took note of any steps that were difficult or caused confusion. These observations were then compiled to create a cognitive walkthrough that documented in detail exactly which operations were challenging and what the cause of the difficulties were.
While going through the tasks I took note of any steps that were difficult or caused confusion. These observations were then compiled to create a cognitive walkthrough that documented in detail exactly which operations were challenging and what the cause of the difficulty was.
While going through the tasks I took note of any steps that were difficult or caused confusion. These observations were then compiled to create a cognitive walkthrough that documented in detail exactly which operations were challenging and what the cause of the difficulties were.
Cognitive Walkthrough
Following this, my team and I interviewed Andy Reiter, a product manager at Digi International and the originator of the concept for Project Mercury.
Data points were organized using affinity mapping and synthesized into personas to represent different archetypes within the target audience.
Following this, my team and I interviewed Andy Reiter, a product manager at Digi International and the originator of the concept for Project Mercury.
Following this, my team and I interviewed Andy Reiter, a product manager at Digi International and the originator of the concept for Project Mercury.
Stakeholder interview
AREAS OF INQUIRY:
How do you currently create product change notifications?
What tools do you use in order to assist with the process?
What problems with your workflow is Project Mercury intended to solve?
AREAS OF INQUIRY:
How do you currently create product change notifications?
What tools do you use in order to assist with the process?
What problems with your workflow is Project Mercury intended to solve?
AREAS OF INQUIRY:
How do you currently create product change notifications?
What tools do you use in order to assist with the process?
What problems with your workflow is Project Mercury intended to solve?
AREAS OF INQUIRY:
How do you currently create product change notifications?
What tools do you use in order to assist with the process?
What problems with your workflow is Project Mercury intended to solve?
AREAS OF INQUIRY:
How do you currently create product change notifications?
What tools do you use in order to assist with the process?
What problems with your workflow is Project Mercury intended to solve?
We learned from Andy that many of the product managers at Digi International create their own personal templates for creating product change notifications, new product introductions, and end of life notifications. He explained that filling out and submitting these long forms was a painstaking data-entry process filled with many areas for user error and other mistakes.
We learned from Andy that many of the product managers at Digi International create their own personal templates for creating product change notifications, new product introductions, and end of life notifications. He explained that filling out and submitting these long forms was a painstaking data-entry process filled with many areas for user error and other mistakes.
We learned from Andy that many of the product managers at Digi International create their own personal templates for creating product change notifications, new product introductions, and end of life notifications. He explained that filling out and submitting these long forms was a painstaking data-entry process filled with many areas for user error and other mistakes.
After getting a feel for how PCNs were created at Digi International, and which parts of the process were pain points for them, our team then conducted contextual analyses with other product managers at Banner Engineering, a financial software company called Branch and a freelance hardware and software developer of how they go about creating and using PCNs. We also had them perform user evaluations of Project Mercury. Doing so gave us insights on how different organizations create and use PCNs, as well as a number of interesting perspectives on what they thought of the application.
After getting a feel for how PCNs were created at Digi International, and which parts of the process were pain points for them, our team then conducted contextual analyses with other product managers at Banner Engineering, a financial software company called Branch and a freelance hardware and software developer of how they go about creating and using PCNs. We also had them perform user evaluations of Project Mercury. Doing so gave us insights on how different organizations create and use PCNs, as well as a number of interesting perspectives on what they thought of the application.
After getting a feel for how PCNs were created at Digi International, and which parts of the process were pain points for them, our team then conducted contextual analyses with other product managers at Banner Engineering, a financial software company called Branch and a freelance hardware and software developer of how they go about creating and using PCNs. We also had them perform user evaluations of Project Mercury. Doing so gave us insights on how different organizations create and use PCNs, as well as a number of interesting perspectives on what they thought of the application.
After getting a feel for how PCNs were created at Digi International, and which parts of the process were pain points for them, our team then conducted contextual analyses with other product managers at Banner Engineering, a financial software company called Branch and a freelance hardware and software developer of how they go about creating and using PCNs. We also had them perform user evaluations of Project Mercury. Doing so gave us insights on how different organizations create and use PCNs, as well as a number of interesting perspectives on what they thought of the application.
After getting a feel for how PCNs were created at Digi International, and which parts of the process were pain points for them, our team then conducted contextual analyses with other product managers at Banner Engineering, a financial software company called Branch and a freelance hardware and software developer of how they go about creating and using PCNs. We also had them perform user evaluations of Project Mercury. Doing so gave us insights on how different organizations create and use PCNs, as well as a number of interesting perspectives on what they thought of the application.
Product manager interviews
CRITICAL FINDINGS:
CRITICAL FINDINGS:
CRITICAL FINDINGS:
There are many different types of PCNs and different product managers have different ideas of what type of information should be included with each
There are many different types of PCNs and different product managers have different ideas of what type of information should be included with each
There are many different types of PCNs and different product managers have different ideas of what type of information should be included with each
There are many different types of PCNs and different product managers have different ideas of what type of information should be included with each
Some product change notifications have very long lists of parts affected, which are frequently detailed in spreadsheets provided by engineers
Some product change notifications have very long lists of parts affected, which are frequently detailed in spreadsheets provided by engineers
Some product change notifications have very long lists of parts affected, which are frequently detailed in spreadsheets provided by engineers
Some product change notifications have very long lists of parts affected, which are frequently detailed in spreadsheets provided by engineers
Often a new product change notification will closely resemble an existing product change notification with the need to only updated a few new details
Often a new product change notification will closely resemble an existing product change notification with the need to only updated a few new details
Often a new product change notification will closely resemble an existing product change notification with the need to only updated a few new details
Often a new product change notification will closely resemble an existing product change notification with the need to only updated a few new details
"I wouldn't want to start from scratch every time." - Product Manager
"I wouldn't want to start from scratch every time." - Product Manager
"I wouldn't want to start from scratch every time." - Product Manager
research findings and prototype plan
After these inquiries were complete, I used the results to create a research finding and prototyping plan aimed are making Project Mercury are a more useful tool for creating and managing product change notifications.
It detailed refinements and new features that would accelerate the process of creating PCNs while reducing mistakes. Also included in the report were annotated sketches of how these changes would integrate into Project Mercury's current interface. The context for how and when these modifications would be most beneficial was detailed in specific scenarios.
After these inquiries were complete, I used the results to create a research finding and prototyping plan aimed are making Project Mercury are a more useful tool for creating and managing product change notifications.
It detailed refinements and new features that would accelerate the process of creating PCNs while reducing mistakes. Also included in the report were annotated sketches of how these changes would integrate into Project Mercury's current interface. The context for how and when these modifications would be most beneficial was detailed in specific scenarios.
After these inquiries were complete, I used the results to create a research finding and prototyping plan aimed are making Project Mercury are a more useful tool for creating and managing product change notifications.
It detailed refinements and new features that would accelerate the process of creating PCNs while reducing mistakes. Also included in the report were annotated sketches of how these changes would integrate into Project Mercury's current interface. The context for how and when these modifications would be most beneficial was detailed in specific scenarios.
KEY IMPROVEMENTS:
KEY IMPROVEMENTS:
KEY IMPROVEMENTS:
Allow project managers to create their own templates for the different types of PCNs
Allow project managers to create their own templates for the different types of PCNs
Allow project managers to create their own templates for the different types of PCNs
Allow project managers to create their own templates for the different types of PCNs
Create a feature for importing parts affected from an XLS, or CSV, file
Create a feature for importing parts affected from an XLS, or CSV, file
Create a feature for importing parts affected from an XLS, or CSV, file
Create a feature for importing parts affected from an XLS, or CSV, file
Expedite the process of creating new PCNs by allowing product managers to start working from similar existing ones
Expedite the process of creating new PCNs by allowing product managers to start working from similar existing ones
Expedite the process of creating new PCNs by allowing product managers to start working from similar existing ones
Expedite the process of creating new PCNs by allowing product managers to start working from similar existing ones
Create a more useful dashboard for the admins who approve or deny PCNs through improved labeling and filtering
Create a more useful dashboard for the admins who approve or deny PCNs through improved labeling and filtering
Create a more useful dashboard for the admins who approve or deny PCNs through improved labeling and filtering
Create a more useful dashboard for the admins who approve or deny PCNs through improved labeling and filtering
DESIGN
DESIGN
DESIGN
VISUALIZING THE SYSTEM:
Project Mercury, as it currently exists, is a fairly straightforward application consisting of one interface for project managers and another for admins. However, I still chose to create a screen flow of the current ecosystem that would help me visualize exactly what changes I would make and how they would integrate with the system.
VISUALIZING THE SYSTEM:
Project Mercury, as it currently exists, is a fairly straightforward application consisting of one interface for project managers and another for admins. However, I still chose to create a screen flow of the current ecosystem that would help me visualize exactly what changes I would make and how they would integrate with the system.
VISUALIZING THE SYSTEM:
Project Mercury, as it currently exists, is a fairly straightforward application consisting of one interface for project managers and another for admins. However, I still chose to create a screen flow of the current ecosystem that would help me visualize exactly what changes I would make and how they would integrate with the system.
screen flow
Once this was completed I created new versions of the needed screens in Sketch and linked them together with InVision to create a working prototype to illustrate the changes made and new features created.
Once this was completed I created new versions of the needed screens in Sketch and linked them together with InVision to create a working prototype to illustrate the changes made and new features created.
Once this was completed I created new versions of the needed screens in Sketch and linked them together with InVision to create a working prototype to illustrate the changes made and new features created.
Once this was completed I created new versions of the needed screens in Sketch and linked them together with InVision to create a working prototype to illustrate the changes made and new features created.
FORM CUSTOMIZATION:
Selecting different types of forms from the PCN dropdown changes the fields on the current form. In the settings screen, Project Managers can select specifically which inputs they would like included on each type of existing form.
They also have the ability to create new categories of PCNs and designate which data fields will be associated with them.
FORM CUSTOMIZATION:
Selecting different types of forms from the PCN dropdown changes the fields on the current form. In the settings screen, Project Managers can select specifically which inputs they would like included on each type of existing form.
They also have the ability to create new categories of PCNs and designate which data fields will be associated with them.
FORM CUSTOMIZATION:
Selecting different types of forms from the PCN dropdown changes the fields on the current form. In the settings screen, Project Managers can select specifically which inputs they would like included on each type of existing form.
They also have the ability to create new categories of PCNs and designate which data fields will be associated with them.
FORM CUSTOMIZATION:
Selecting different types of forms from the PCN dropdown changes the fields on the current form. In the settings screen, Project Managers can select specifically which inputs they would like included on each type of existing form.
They also have the ability to create new categories of PCNs and designate which data fields will be associated with them.
LOAD PARTS FROM SPREADSHEET:
Lists of affected parts can be imported from spreadsheets in the xls or csv format. Appropriately named columns will be matched with corresponding columns in Project Mercury.
LOAD PARTS FROM SPREADSHEET:
Lists of affected parts can be imported from spreadsheets in the xls or csv format. Appropriately named columns will be matched with corresponding columns in Project Mercury.
LOAD PARTS FROM SPREADSHEET:
Lists of affected parts can be imported from spreadsheets in the xls or csv format. Appropriately named columns will be matched with corresponding columns in Project Mercury.
LOAD PARTS FROM SPREADSHEET:
Lists of affected parts can be imported from spreadsheets in the xls or csv format. Appropriately named columns will be matched with corresponding columns in Project Mercury.
WORK FROM PAST PCN:
When a product manager is creating a new product change notification that contains much of the same information as an existing one, they can import the previous one into the new form, then making only the necessary changes before they submit it.
WORK FROM PAST PCN:
When a product manager is creating a new product change notification that contains much of the same information as an existing one, they can import the previous one into the new form, then making only the necessary changes before they submit it.
WORK FROM PAST PCN:
When a product manager is creating a new product change notification that contains much of the same information as an existing one, they can import the previous one into the new form, then making only the necessary changes before they submit it.
WORK FROM PAST PCN:
When a product manager is creating a new product change notification that contains much of the same information as an existing one, they can import the previous one into the new form, then making only the necessary changes before they submit it.
ADMINISTRATOR DASHBOARD ENHANCEMENTS:
Administrators who are in charge of approving or denying product change notifications can see how many approved, pending, incomplete or denied PCNs there are right from the dashboard.
They also have the ability to filter by user in order to see how many PCNs in each category belong to a specific product manager.
ADMINISTRATOR DASHBOARD ENHANCEMENTS:
Administrators who are in charge of approving or denying product change notifications can see how many approved, pending, incomplete or denied PCNs there are right from the dashboard.
They also have the ability to filter by user in order to see how many PCNs in each category belong to a specific product manager.
ADMINISTRATOR DASHBOARD ENHANCEMENTS:
Administrators who are in charge of approving or denying product change notifications can see how many approved, pending, incomplete or denied PCNs there are right from the dashboard.
They also have the ability to filter by user in order to see how many PCNs in each category belong to a specific product manager.
ADMINISTRATOR DASHBOARD ENHANCEMENTS:
Administrators who are in charge of approving or denying product change notifications can see how many approved, pending, incomplete or denied PCNs there are right from the dashboard.
They also have the ability to filter by user in order to see how many PCNs in each category belong to a specific product manager.
Project Mercury style guide
To accompany the prototype, I created a style guide that could be used as a reference for developers, marketers or anyone else working on Project Mercury in the future. It contained specific recommendations on using logo, icon, colors and typography of the application as well as examples of common page elements.
To accompany the prototype, I created a style guide that could be used as a reference for developers, marketers or anyone else working on Project Mercury in the future. It contained specific recommendations on using logo, icon, colors and typography of the application as well as examples of common page elements.
To accompany the prototype, I created a style guide that could be used as a reference for developers, marketers or anyone else working on Project Mercury in the future. It contained specific recommendations on using logo, icon, colors, and typography of the application as well as examples of common page elements.
To accompany the prototype, I created a style guide that could be used as a reference for developers, marketers or anyone else working on Project Mercury in the future. It contained specific recommendations on using logo, icon, colors, and typography of the application as well as examples of common page elements.
OTHER WORK:
