Device Inventory (tablet) and Intro Page (mobile)
Device selection
Service Fulfillment Options

Best Buy

AI-Assisted Self-Diagnosis


Best Buy's AI-Assisted Self-Diagnosis is a fully responsive, concept-to-release microsite embedded in BestBuy.com to help customers self-assess hardware and software issues with the power of Geek Squad's twenty-five years of call transcripts and troubleshooting models.

The application leverages three facets of artificial intelligence:

  • Conversational Design
  • Machine Learning
  • Automated Handling

The conversational system, puts customers in control, results in greater issue resolution and satisfaction—but the primary goal was to reduce Best Buy Customer Service's Average Handle Time.

The MVP was only targeted laptops, but the initial decision tree, UI and conversational elements paved the way for all hardware and software products to be triaged through the application.


Objective

Reduce call volume to tech support

Outcome

All participants in the unmoderated study quickly identified the rationale behind the application; reduce call volume (top answer—surprisingly), to save  customers' time, and encourage self-service. Most participants were not aware that Best Buy did computer repair (which surprised us all on the Services team, both marketing and tech).

The reactions among test users were largely positive. The length of the interaction was considered appropriate, had logically sequenced stages and was easy to complete. However, some participants found the outcomes predictable or "surface level”, and expected more in the way of pricing and timing options. Overall, the majority found it useful, and gave them a base understanding of their issue without setting foot in a store.

About 80% of users who tested it said they would use the feature in real-life—a win win for Best Buy and the customer experience.


Live Links

Self-Diagnosis (has been updated)
Microinteractions Study.pdf
Conversational Design Study.pdf

Goals

Awareness, Productivity, Engagement, Sales

Research Methodologies

Participants were screened for having a computer or device issue in the past six months, so we could leverage a "true to life" scenario within our test.

  • Competitive Analysis (Services Team)
  • Competitive Analysis (Company-wide)
  • Field Studies with Geek Squad Agents
  • Customer Interviews
  • Unmoderated Remote Usability (Desktop and Mobile)
  • "Walk the Wall" / Heuristic Analysis
  • Dot Voting

Comparable Products

HelloTech, Ifixit.com, Microsoft Fix It, Virtuwell

Deliverables

Decision Tree, Technical/API Map, Copy Deck, Wireflows, High-Fidelity Design for Mobile and Desktop

Team

Tech Support/Engineering Lead, UX/UI/Visual Design Lead (myself), UX Research Lead, Business Analyst, Copywriter, Information Architect

Challenges

Many overlapping Product Managers resulted in communication challenges about what content would be available at launch. Once a technically-savvy BA was engaged the linking APIs (like DIY and troubleshooting databases, etc) content paths were clearer to myself and the development team. The technically-focused copywriter was challenged with brand voice and conversational design (I supplemented with coaching, conversational design study, and conversational structures). Overall the product team and company had limited experience with custom interactions.

Next Steps

  • Taxonomy Study
  • Auto-Authentication
  • Analytics Analysis
  • Device Auto-recognition
  • Improve DIY and troubleshooting databases
  • Link appropriate paths to Geek Squad Chat
  • Add pricing and timing estimates
  • Estimate current product's value
  • Revisit UI module for standalone use
  • Reduce login friction
  • Improve fluency of conversational design

Final Analysis

At the time, the product managers on this product had limited vision about what this self-diagnosis could do and understand. They were very MVP-focused and if it reduced any call volume it'd have been considered a win for them. Anything outside of that was seen as scope creep. It was early in my UX experience, but found the lack of "big picture" as well as the disinterest in details from the product managers very frustrating.

Unfortunately, it's a very nuanced process to understanding the variety and complexity of users' personal taxonomy and goals. Even more complex, but highly valuable to the customer experience— we missed the opportunity to help the customer with their decision to repair or replace (for example, give the customer their current device's value, Best Buy's trade-in value and show them pricing on new devices.) Attempting to discuss ideas like these with the product managers were immediately stifled and met with hostility.

However, this was precursor to the Best Buy intelligent chat, and this triage application didn't not have the flexibility nor logistics to use natural language processing. It did eventually, with a newly-formed CX team's guidance, roll into a triage model currently used for all Best Buy-supported products.

Supporting Artifacts

Triage (Before) Screenshots.pdf
IA's (Before) Wireframes (password: Triage)
Services Baseline Study.pdf
Usability Results.pdf
Facets of AI.pdf
Date Picker for Responsive Web.pdf
API Tech Flow.pdf
User Journey / Decision Tree.pdf
MVP Question Framework.xls
Dot Voting.jpg

Vendor Portal Landing Page
Vendor Apps, Training Schedules

Best Buy

Partner Portal


The Best Buy Partner Portal is a web-based application that allows vendor partners (like distributors, resellers service providers and other strategic partners) access to product registration, marketing resources, pricing and sales tools.


Objective

Streamline an organically-grown system into a modernized, partner-focused architecture.

Stakeholder Feedback

"When Dan joined my project, I didn't realize how lucky I was. His insight, direction, sense of urgency, quick turnaround, long term vision and overall calm demeanor was invaluable. I would be honored to have him work on my site again and was so impressed with him."
Sarah Ailabouni, PHR
Senior Manager of Strategic Communication and Engagement - Digital and Technology at Best Buy

Live Links

Partner Portal (limited access)

Goals

Productivity, Communication, Engagement, Loyalty

Research Methodologies

Given the size of the company, breadth of the project as well as the tremendous amount of vendors, our first layer of users were internal—content creators and the vendor support team, who would be creating content, applications and dealing with vendors daily using the platform. They were also the best resource to build a portal that would work "80%" of the time. Outlier actions would be improvised outside the system.

  • Content Analysis
  • Stakeholder Interviews
  • Content Team Interview
  • Vendor Internal Support Team Interviews

Comparable Products

Alibaba Seller Channel, Ford Supplier Network,
Microsoft Commercial Partner Network

Team

Business Analyst Lead/Subject Matter Expert, Liferay Engineer, UX/UI/Visual Designer (myself)

Technology

Liferay DEX Platform and Lexicon Design System

Deliverables

Wireframes, High-Fidelity Responsive Design, Design System and Custom Assets, Style Standards

Challenges

Not many. We moved fast, met daily and delivered daily. Having exposure to the BA/SME and developer daily resulted in fast and correct work. One stakeholder did continually push for more features, but the BA Lead kept scope in check, had a precise understanding of user roles, and the agreed requirements. Design iteration and testing were limited to none due to an aggressive timeline. In retrospect, we should have found internal representative users to test with, since direct access to vendors proved to be too much of a logistical and relationship-taxing challenge. My understanding of Liferay's capabilities was initially limited, but I'd discovered Lexicon, a design system and assets for Liferay. That sped my work and closed up the dev/UX communication gap quickly.

Next Steps

  • Vendor Interviews within a Vendor Event/Summit
  • Usability testing for Home Page + Primary Navigation
  • Analytics Analysis
  • Leverage IoT to allow data sharing of merchants' products' data with Best Buy's customer inventory

Supporting Artifacts

Journey Maps
Lexicon Design Library
Previous design screenshots.pdf

Best Buy

Services Baseline Study


While on the Digital Services team at Best Buy, our team conducted a Services Baseline Study. We looked to understand how our current experience fared against similar-scaled companies like Amazon and Sears, and compared to nimble specialists like the start-up HelloTech.

Objective

Understand what we were doing right and wrong in the field of electronic repair services

Outcome

While we found Sears and Best Buy very closely rated in ease of use, and Best Buy had a slight edge in user confidence within the scheduling component. Both Sears and Best Buy services were very difficult to find, whereas no test subjects were able to find Amazon's services component.

As expected, the HelloTech experience was superior, given their only task for users was to estimate and schedule. We also found hesitation across all platforms when it came to taxonomy, as well frustration when there was a need to create an account to get an estimate or schedule a repair.


Live Links

Service Scheduling
Services Baseline Study.pdf

Goals

Awareness, Productivity, Communication, Engagement, Loyalty, E and M-Commerce

Research Methodologies

  • Moderated Usability Testing
  • Usability Analysis

Comparable Services

Amazon Computer Repair, HelloTech, Sears Appliance Repair

Deliverables

High-Fidelity Prototypes (Desktop and Mobile), Executive Summary, Supercut of Usability Findings

Team

Senior UX Manager, Research Lead, Junior Researcher, Two UX Designers (including myself), Information Architect, Copywriter

Next Steps

After baseline testing, we were able to cite this study explaining our UX rationale on iterations and new service-related products.

Supporting Artifacts

Initial Key Observations.pdf