August - December '24
Lead UX Designer
UX Researcher
Hanna Fu
Umme Ammara
Elaine Xu
Leon Ma
Maggie Garratt – Industry Shepherd
Katie McIntyre – TA
Carrie Bruce – Instructor
In one of our core classes at Georgia Tech, we partnered with Accenture, a global professional services company that provides a wide range of consulting services and solutions to various businesses, governments, and organizations.

There is a lack of a centralized tool for accessing client information within the 5 internal divisions. This fragmented approach makes it difficult to share information across consultants and often leads to double work.
Accenture offers internal tools that helps consultants with client research, including an internal information database called Knowledge Exchange (KX); however, these tools are either unpopular or unknown.
Our solution revolves around Accenture consultants, who are both are user base and stakeholders. Due to the diverse roles of both clients and consultants, there is no common workflow for client research.
Currently, there is a lack of a centralized tool for accessing client information within Accenture Song or other divisions. Teams rely on a mix of platforms to gather client information like Teams and Google News, or they have to manually reach out to relevant consultants themselves. This current fragmented approach makes it difficult to share information across consultants and often leads to double work as most of the client research has already been done if it is a repeat client.
Accenture does have an internal database called Knowledge Exchange (KX) where consultants can upload their past client research, however it is very unpopular due to its confusing interface and non-relevant search results.



To explore our problem space, we asked questions based on our understanding of our primary target audience, the key stages of consultants' workflows, and their pain points and preferences around client information. Over the course of a month, we utilized a mixed-method approach of qualitiative and quantitative research to investigate our questions. Ultimately, we aimed to form a comprehensive understanding of Accenture consultants and their relationship with client information.

Once we conducted our research, we utilized affinity mapping to synthesize our findings across all of our methods and prioritization to synthesize our findings.


To go into more detail with our findings, consultants’ roles and divisions significantly influence their workflows and the deliverables they produce for clients, meaning that there's no single protocol consultants follow. However, they often face challenges with accessing and using internal tools and are frequently unaware of all the resources available to them. Finding and sharing client information takes significant amount of time, with many consultants relying heavily on other Accenture employees to seek information. Client data privacy and security are critical concerns when sharing deliverables, further complicating the process. Due to the absence of a centralized system for sharing client information, consultants often have to redo research, leading to inefficiencies.
By synthesizing and prioritizing all of our research, we came up with 8 main user needs that our solution needed to take into account. Then, we created 8 correlating design implications that our solution needed to include, allowing us to address user pain points in the final design. Critically, these findings analysis served as the basis for the rest of our project.

Based on research and user needs, we decided to create two consultant architypes that would utilize our solution. We wanted to represent the diverse experience pool at Accenture with two extremes: an entry-level consultant and a managerial-level consultant. These personas capture the diverse challenges and requirements consultants face at different stages in their careers. By developing these personas, we had a better understanding of our users’ goals, frustrations, and needs, allowing us to design solutions tailored to both persona's specific challenges.

Because our solution was based on redesign an experience, we utilized a JTBD to formate the ideal steps a consultant could to fulfill their goal. Critically, this method was key to understanding how consultants felt and behaved during this process, giving us a better idea to identify their ultimate goals and design solutions to meet them. Through our JTBD, we found that there was a need for a more streamlined process for connecting with colleagues, better internal tools for gathering information, and centralized platforms to improve efficiency and reduce frustrations.

To really hone in what experiences we should highlight in our experience, I led an activity to ideate user stories to focus on the specific goals a consultant would make when finding and sharing client information. Once we finalized our user stories into 6 major tasks–each correlating to a design implication–we sketched out concepts and tested it with users. We used these concept sketches to inform decisions of our lo-fidelity wireframes.

To really hone in what experiences we should highlight in our experience, I led an activity to ideate user stories to focus on the specific goals a consultant would make when finding and sharing client information. Once we finalized our user stories into 6 major tasks–each correlating to a design implication–we sketched out concepts and tested it with users.