Created with SOUL by Alexandra M. Nguyen; Stay curious.



Identifying and ameliorating tasking challenges for in-store associates to improve the overall customer experience and work experience


The Home Depot Enterprise UX Team


4 months


Ask Homer, an app to connect the right store associates, at the right time, for rapid assistance, for any query



UX Researcher

  1. Planned, selected, and conducted appropriate research methods

  2. Survey & Interview design

  3. Interpreted results into design parameters and recommendations

Project Manager

  1. Created meeting agendas &  timeline

  2. Team management & organization

  3. Identified the team's strong-suits and delegated tasks

The Historian

  1. Documentation: Defined file naming conventions, folder management

  2. Progress updates

  3. Note-taker for meetings and assessments



With about 80 - 300 associates, over 35K products, and about 20 departments in each Home Depot store, store associates are tasked with too many tasks which vary:

  • day-to-day

  • department-to-department

  • store-to-store

In addition to tasking, associates are required to always put the customers first.

 Therefore, there is a trade-off for associates to juggle: 


Simplifying ways to delegate, explain, and track tasks may generate more efficient Home Depot store associates and therefore save, increase, and optimize $$$ for Home Depot in the long run.














The impact of this project should address the motivations behind tackling the issues of tasking for store associates:

  1. Simplify, improve, and innovate processes of associate tasking

  2. Create better efficiency in task management 

  3. Ensure higher quality task completion

  4. Create better practices & standardization to improve performance

  5. Create more accountability and task tracking

  6. Improve associate satisfaction



With the defined problem space, the impact, potential contributions, and project motivations identified, I defined what success entails for our project scope to keep in mind for our end design: 

Provide an outside perspective and explore potential opportunities in project motivations with user research

Addresses user wants & needs by targeting pain-points and challenges that store associates face in day-to-day: task delegation, management, and execution

A system that is designed for use at a large scale: used across several different departments of The Home Depot

User Evaluations

Brainstorming &

Design Thinking

Wireframing &


Identifying User

Pain Points 

Stakeholder Interviews &

Competitive Analysis




As the primary UX Researcher in the project, I devised the research action plan by selecting appropriate methods to address our research questions to investigate pain points, who should be included in our sample, and an interview script. In addition, I liaised with our corporate point of contact for scheduling, created a timeline of who, what, when, and where, and recorded/took notes during interviews for documentation.

I believed that the first step was to clearly identify the problem space, identify our goals, and understand the motivations behind the project. Therefore, from Stakeholder Interviews, we identified the general foundation about the problem space, the impact it would make, success metrics, and project motivations that can be found in the challenge section. With this information, we defined a research question, which became the foundation on how I planned our research process to investigate user pain points. Once this information was obtained and there was a better understanding of the environment, process, and context, I created design implications and parameters for the design. 


How can we delegate, track, and ensure tasks are efficiently and effectively completed on a daily basis to create ideal customer experiences?


To provide any solution or start ideating on opportunities for design, our next step was to conduct user research to understand the problem space of tasking, defined by our research question.


Our sample included associates with variable ages, experiences, skill levels, and different departments to more accurately represent all types of associates working in The Home Depot Stores.


These are the main users of our end design who are in charge of day-to-day activities.


2  Home Depot Stores (Kennesaw & Midtown)

6  Store Visits 

3  Stakeholder Interviews

3  Interviews 

8  Contextual Inquiries

2  Competitive Analysis at Lowes & Target

First look into the world of Home Depot

Inside scoop with the Chain of Command

Be the apprentice to the frontline

Naturalistic Observations

While waiting for approval to get on the field with store associates, the research team wanted to get familiar with
The Home Depot environment before interviewing store associates to:

  • develop a more intuitive understanding of the work culture

  • construct more insightful questions to ask store associates during interviews

  • compare what store associates actually do vs. what corporate thinks they do

Semi-Structured Interviews

We interviewed Store Managers and Product Managers to build rapport with users and capture attitudes and opinions that questionnaires or observations cannot capture. Our goal is to understand at a higher level:


  • the process of how tasks are managed, delegated, tracked, and selected

  • feedback loops of tasking

  • communication

  • general attitudes about systems and tools that are used

Contextual Inquiries

This method gave us the ability to also build rapport but to ask questions while associates complete tasks in their complete social context to obtain rich data, that interviews lack, to help us understand more granularly:

  • accuracy and complexity of tasks and behaviors

  • variability and differences from associate to associate in different departments

  • the behaviors and motivations surrounding these tasking process

  • observe associate interactions and potential ‘distractions’ in real-time


Here are photos of a few artifacts and photos that I snagged while conducting contextual inquiries with store associates.


Unfortunately, due to liability/confidentiality and lack of document logging to track how tasks are completed, we were unsuccessful in gathering further information.


Based on our problem space and overall research question, the team created more granular research questions. I identified the best research methods to use and devised an interview script. 

High Level Questions:

  • How are tasks decided, delegated, and selected?

  • What methods/tools are used to track associate activities?

  • What tool(s) do associates use when completing tasking?

  • What are major tasks that associates do on a daily basis?

  • How do associates complete tasks?

  • What circumstances require associates, supervisors, and managers to communicate?

  • How does communicate take place?

  • What are the general attitudes/opinions for pain & pleasure points​?

During interviews, I used these questions as a guide but had the freedom to ask more in depth questions. Though this method is less structured and yields less consistent data, it provided rich information from associates about the problem space. After each interview and contextual inquiry, I revised the script to add more questions for associates to clarify information that I was unable to understand proficiently because of time constraints. After each session, I debriefed with the team to see how we can move forward for the next sessions. 



Our team conducted a competitive analysis to compare The Home Depot with similar, competitor stores and help understand what other companies do in terms of tasking. With this information, we analyzed strengths, weaknesses, similarities, and between companies







Handwritten notes and audio recordings from interviews, contextual inquiries, and competitive were transcribed. The team created a digital affinity map to categorize, organize, and group information from each of the user research methods to aid in brainstorming phase for ideation as well as to get the team on the same page.

From this information, I wrote a report on Details on Context of Store Associates that included an overview of tasks and responsibilities with flow diagrams, requirements to perform tasks, work environment, training, communication, equipment and tools that the team used as a reference to as we created design implications, empathy maps, and personas.






A total of 19 pain points were uncovered from our user research. Each pain point describes an aspect of system or user behavior that fails to support a balanced need of associates, managers, corporate, or customer stakeholders.



Based on what we learned and synthesized our research with affinity mapping, I created a design implication table to ensure that our design solution accounts for the perceptual, cognitive, motivation, physical environment, and social attributes for the variety of associates that considered skills, training/domain knowledge, and environment. 


As a team, we created personas and empathy maps  to represent different groups of users by advocating for each of the users that we individually talked to. This method is a fairly quick and cost efficient way to synthesize data to better understand motivations, behaviors, and needs of our user types to aid in design decisions.


Using these three methods, we put ourselves in our users' shoes to begin the next phase of brainstorming, design thinking, and ideating.






Our goal is to translate user needs and design criteria into sketched concepts, wireframes, and prototype description for evaluation. 


However, to create and improve our system, we obtained feedback from:

  1. CORPORATE STAKEHOLDERS to compare, critique and narrow down system-level concepts​​

  2. USERS to understand clarity, benefits, feasibility, and preference in order to implement improvements to the prototype

Our team used this feedback to uncover weaknesses, blind spots, understand critiques, and identify recommendations for improvements before the final prototype.



From the 19 pain points, we decided on 5 pain points to tackle by systematically sorting into groups: 

  1. feasibility vs. opportunities for innovation

  2. client preference, project motivation, and success metrics

  3. strong evidence from user research

My goal was to be the liaison (bread & butter) between company goals and what the people (users) want by designing solutions that target multiple pain-points to reduce current efforts, increase pleasure, and optimize cost. It's a win-win for everyone!


We rapidly generated ~50 high-level design ideas within parameters created by the pain-points.

Three concept amalgamations were then selected by the team for a storyboarding and stakeholder feedback.





















Task Capture is a high-level interface concept meant to provide associates and managers a platform to capture, describe, and post tasks in an efficient and systematic fashion. Tasks are contained by information cards that holds the task’s urgency level, verbal description, tagged departments, tagged experts needed, and other supporting references such as photos. Cards are organized and displayed in scrollable feeds that can be filtered by recency, location, and assignments.

Task Follow-up is rare:


Managers want to issue tasks to their associates and know the status of the task completion. Current systems and personnel habits do not allow for this.


Expert Directory is a concept created to bridge the experience gap between junior associates and senior associates/department experts. Junior associates send inquiries to an expert directory through voice or text, and the system responds by connecting them to nearby associates with the expertise needed to answer their question. The Expert Directory is built upon an associate profile syste, where associates are tagged with expertise in a in a department, equipment, or certification. The Directory monitors current expertise available through an associate attendance system and cross references inquiries for expertise and connect the right people where help is needed.



Department Waypoint is a concept that attempts to eliminate the need for customers and associates to search for each other within the “maze” of Home Depot’s warehouse like stores with endless aisles and bays. A Waypoint is an informational kiosk that customers and associates can utilize. Waypoints are intended to be installed within major departments of Home Depot.


A report with more detail of the feedback sessions can be found here.


Compare, critique, and narrow down proposed solutions​​ with the most potential impact in terms of utility and feasibility for store associates by utilizing experts 



Corporate Stakeholders: 

  • UX Designers

  • Product Manager

  • Store Operations Manager with in-store experience

Selected concept was then fleshed out in more detail through narrative walkthroughs and wireframing from feedback




To gather and gauge (in a confidential manner to reduce response bias) evaluation criteria to quantify qualitative opinions and evaluation criteria such as effectiveness, utility, feasibility, strengths, weaknesses, and opportunities for analysis

Question Types

  • Likert Scale

  • Open-ended questions

Note: Two forms were provided ~ electronic or paper

Interview to Focus Group

To easily explain system concepts by answering participants' questions in real-time, ask participants in depth questions and to elaborate their answers in detail, ​help the researchers gauge non-verbal responses. This method compensates for qualitative information that the questionnaire method lacked.

CHANGE OF PLANS: When we arrived at the Corporate Office, we were double-booked with another team and half the participants left. Therefore, we compromised and adjusted our plan to conduct two small focus groups


1. Session Facilitator explained concept one by one

2. As the Session Moderator, I asked participants to complete the questionnaire on their own after each concept​

3.  Then, I verbally asked participants open-ended questions so participants can provide more contextual feedback and information about their opinion on the system

  • ​Note: Participants were allowed to record on their forms for more confidentiality if they felt uncomfortable to discuss with the team, but were also able to discuss with the group about their opinion

4. Notetakers took notes and recorded the session (with permission) for later interpretation





With the quantitative data from the questionnaire, I coded the Likert Scale from 1-5 and took averages of answers for each question, for each concept from the seven participants.


The results demonstrated Concept Two: Expert Directory had the highest average for the majority of the evaluation criteria which also corroborates with the qualitative data where 7/7 participants preferred Concept Two. 

Concept Two was the clear winner!

Amazing! Expert Directory can really solve major problems and avoid loss of sales. 


Saves unnecessary waste of time for 
associates in finding other associates.


From analyzing the qualitative data from the focus groups, we created an improvement and recommendations table that addresses concerns and limitations of the design for Concept Two. With this information, we created recommendations that can turn into actionable solutions for our wireframe before prototyping.



Narrowing our scope: It is a hurdle for associates to help customers, as well as manage various kinds of tasks. No single associate can know everything and anything about all the products and processes in the complex environment of The Home Depot.


How can we get associates and customers expert help when and where they need it in store?