Versions Compared

Old Version 1

changes.mady.by.user Matthew Evert

Saved on

compared with

New Version Current

changes.mady.by.user Drew Palko

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Placeholder for epic.

Overview

Requested by Billy Colonna, Product Team on June 11, 2020

Description

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Maecenas facilisis orci ut luctus blandit. Vestibulum in urna a odio ornare rhoncus. Nam vestibulum odio eget ante luctus, ac pulvinar orci accumsan. Cras pretium placerat augue, ut lacinia turpis sollicitudin vitae. Sed ac pulvinar tellus. Pellentesque in pharetra quam. Phasellus eget lectus scelerisque, dignissim elit eget, laoreet dolor.

What is the problem?What is the problem?

Punchout users can only see DC inventory. It causes distrust in the inventory displayed in the Punchout experience.

  • We need to capture the zip code from punchout users in order to show availability (Manually provided)

    • How to get screenshots of punchout screens

      • Nathan will provide PO users

  • What's the best way to show that availability

    • Compare to Storefront and Live Prod

How did you become aware of the problem?

Who is affected (customer, associate)?

Larger compnaies (universities, etc…) that use Punchout

What is the value to the business and/or customers?

Ideal outcome

Known constraints

People

UX

  • Drew Palko, Designer

Product Team

  • Billy Colonna, Product Manager, Requestor

Stakeholders

  • S2S

    • Nathan Lienard

    • Stefanie Rauch

Meeting Notes for Discovery Meeting - June 11

Attendees

  • Drew

  • Billy

Objective

  • Define problem statement and ideal solution

  • Capture questions and action Items required to begin discovery

  • Schedule follow up

record meeting

Work

Research

Discovery

???

Analysis

???

Design

Solutioning

Prototyping?

https://fergusonprod.atlassian.net/browse/EDEX-669

Testing

Test prototype

Pros:

  • Compact

  • Easy to edit and sketch out work

Cons:

  • May be redundant if we have to put information (dates for example) in two places, Jira and Confluence

Jira Legacy
serverSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQuerykey = edex-808
serverId6f628555-4e88-3de1-a113-9682348a2f13
Test prototype

Pros:

  • Automated

  • Always up to date

  • Ability to show flagged tickets

  • Ability to pull in info straight from the ticket

Cons:

  • Tickets are sorted by Key only

  • can’t put info in between tickets, all lumped together

Jira Legacy
serverSystem JIRA
columnskey,summary,timeoriginalestimate,assignee,status,flagged
maximumIssues20
jqlQueryproject = "DXT" and ("Epic Link" = EDEX-801) AND labels = ux-research-analysis
serverId6f628555-4e88-3de1-a113-9682348a2f13

Production

  • Week 6

    • UI Design Begins

Evaluation

  • Week 7

    • Rollout Begins

  • Week 8

    • Design Evaluation Begins

Research Timeline

5/4-8/20 Week 2 - Recruit customers

5/11/20 Week 3 - Review prototype; design usability test

5/18/20 Week 4 - Conduct usability tests

5/25/20 Week 5 - Analyze and report resultsQuestions:

  • Do we know what the circumstances that led us to remove local availability were?

    • The site is one account - price driving account

    • No Job board

    • Even if an address was tied to the account, it may not be relevant or accurate.

  • Is the location an important part of availability to these users?

    • Loop in Laurie Drew Palko

    • Users can be gathered by Nathan and Stefanie

  • Can we get general availability of products across Ferguson inventory?

Work

Research

Discovery

Timeline - Accelerated
6/12/19 - Initial project brief
6/17/19 Customer list due
6/17/20 - Develop study plan
6/24/20 - Study Plan review by stakeholders
6/25/20 - Customer list due; interview script written
6/29/20 - Interview script approved by stakeholders; begin customer recruitment; target
6/30 7/2/20 - conduct remote, moderated interview sessions (before July 3-4 holiday weekend) Week of
7/6/20 analyze results and prepare insights report Week of
7/13/20 - report findings to stakeholders Week of
7/20/20 - fulfill incentives to participants; archive study artifacts

Analysis

https://validately.com/insights/96b0b46b-0839-4693-9cbf-d65dc1d63943

  • The team would have liked to have seen more focus on the availability unknowns around Punchout users, but found the general usability issues nonetheless helpful because of the scarcity of UX studies for Punchout

Design

Solutioning

  • The team decided to move forward with attempting to show local availability for Punchout users.

  • A Zip Code is needed to show availability

    • We will probably keep this as a manual capture rather than try to automate it for the MVP

  • We must determine the best way to show availability given the solutions that have already been decided for Prod and Storefront

Prototyping?

Testing

Test prototype

Test prototype

Production

Evaluation

Research Timeline

Resources