EY Atlas - Browse View

UX Process


The Audit Insights project originated in the EY Global Digital group and was a new piece being added to their already existing Canvas Dashboard application. The purpose of the addition was to help EY to check the work of their local audit teams to see if they’re doing consistent, quality work. The simplest explanation of the application is that when an audit is created the primary team creates an audit plan that needs to be followed by the local audit team that is executing the audit.

There are times when the local team doesn’t follow the audit plan or follows it and does extra work that wasn’t requested. In those instances the audit can cost more money as the local teams submit the work done expecting to be paid for it (even though the different or extra work wasn’t part of the original audit plan).


The project consisted of the following phases:

  1. Discovery
  2. Ideation
  3. Visual Design

The Global Digital Group’s main focus was on quickly getting work done so research with users, concept maps, empathy maps, user journeys, personas and other tools the user experience group would like to use were not a part of the project. Most of the information gathered to work on the project was done during the discovery phase.


The project was composed of the following people and roles:

  1. 2 Stakeholders/Domain Experts
  2. 1 UX Visual Designer
  3. 1 Business Analyst
  4. 1 Project Manager
  5. 1 Solutions Architect
  6. and myself in the UX Strategy/Architect role

For this project we proceeded with a short kickoff meeting and a series of discovery meetings. The kickoff and discovery meetings laid out the vision of the project and surfaced what ended up being the main information that the application needed to focus on and display to the user. The main areas of an audit that needed to be focused on in order of importance were:

  1. Risks
  2. Controls
  3. Findings
  4. Procedures

The user of the application would be able to compare how the primary team performs all of the above categories to how the local team performed all of the above categories. The high-level review of those comparisons would show if the local team’s execution was close or similar to the primary team’s performance or if the local team’s execution wasn’t close or similar to the primary team’s performance. If there was a cause for concern the user of the application would be able to further investigate in more detail exactly what the local team was doing.

From the discovery meetings the initial idea for the application came into focus, that of a main dashboard to display the information that allowed users to drill into information for each category at a more focused level. To dig deeper into uncovering more information about Risk, Controls, Findings and Procedures a questionnaire was created for the subject matter experts to help uncover how the users would best consume the information and in what case would the data cause the users to take action.

The initial questions proposed were

  1. What is the user trying to asses or take away from the Risks/Controls/Findings/Procedures data visualizations?
  2. What are the decisions/tasks the users will make/complete based on the Risks/Controls/Findings/Procedures information (i.e. the critical must see and must do items?)
  3. Which of the Risks/Controls/Findings/Procedures data values are the most important to the user and why?
  4. What user interactions with the Risks/Controls/Findings/Procedures data do we want to support?
  5. What Risks/Controls/Findings/Procedures data conditions would cause the user to be alerted that there’s a problem?

The answers to the above questions along with the other information gathered from the discovery meetings set us up to move on to the Ideation phase.


From the review, feedback and discussions with the Director and Developer, some brainstorming at the white board was done that gave some basic direction for the what the site structure and pages would look like…a main dashboard landing page with charts that could be interacted with as well used to drill down into further levels of the Risk, Controls, Findings and Procedures categories.

The first round of wireframes went through a review process with the project team and feedback was given during the meetings pointing out where there were issues or the structure didn’t work. With that feedback another round of wireframes were created.

Visual Design & Clickable Prototypes

The visual design phase built on the wireframes and added in the typography, style and color selections for the different charts displayed as well as refining how the content was presented visually and how it was laid out. I did not create the initial visual designs for this project but did edit the designs from the feedback sessions we had when working towards the final visual design.

From the visual designs I created clickable prototypes using Sketch and InVision. The clickable prototypes were first used to execute some basic first impressions and feedback with internal subject matter experts who represented the users (we were unable to gain access to potential users of the application). The SMEs gave us feedback regarding the fact that thresholds weren’t the best way to measure the local team’s work as a threshold could differ from region to region, country to country etc.

Below are the base images for the design and all of the prototype images are in the following zip file:

Audit Insight Prototype Images...


The project was being worked on near the end of the year and was put on hold due to a change of priorities in the Global Digital Group. It does appear that the project may be getting restarted at some point in the near future. So essentially this work wast mothballed for use when the project was made to be a priority again.