UX/UI Design

Defining the framework & design for the CRM Navigation

Defining the framework & design for the CRM Navigation
Year
2020
Role
Product Design Intern
Length
12 Weeks

Defining the experience & guidelines of the Client Relationship Management tool's navigation

A platform that Facebook sales employees use to interact with, analyze and optimize advertiser’s ad spend.

Overall problem

Framework & Structure - The CRM tool lacked the guiding structure to scale as more teams deliver and expand its many uses.

This lack of framework, both physical and mental in terms of design, ended up creating a rather complex navigation with limited intention for its elements and their placement.

Beginning with the end in mind

With a problem defined, all I needed now was a goal to aim for. What does our user need? The answer was simple... literally. Simple

The CRM was an ever-changing complex tool, and what sales needed was simplicity in their workflow. This led me to my first area of opportunity, the Global Navigation.

Global Navigation

People problem

Currently within CRM, there are six global actions all users can take. These actions have previously been added to give value to different user sales roles, however different user roles don’t use almost half of the actions.

Platform Problem

As more teams ship into CRM and more actions are added each half it’s apparent that the Global Navigation needs a framework to determine what actions should or shouldn’t displayed to our users.

Goal

Enhance Sales user experience by creating a design framework that provides the Global Actions each role needs to complete their workflow, while also surfacing other actions contextually throughout CRM.

Actions identified to take

  • Create a mapping of Global actions by sales roles
  • Design a framework that simplifies the user’s experience
  • Come up with a way to surface actions not displayed globally in CRM

Who is this for?
There were five different types of sales with different use cases and flows on the CRM platform. I had to understand both them and how I could create a global toolbar that satisfied all of their needs simultaneously.

Data-driven design
After teaching myself how to use the company's internal data searching software, I took a look at the use statistics on the current global toolbar.

Visualizing data
I created this easy to digest visual to better understand the usage of actions between our users

With this information now it was easy to understand how to approach a data-driven solution. However, there were two ways I could move forward with this data.

Limited Global Navigation with Contextual Actions
This direction shows users the possible limited global navigation with the top three most widely used actions + the new notetaking action. This would allow users of all sales roles to access the most used actions at all times while also allowing for more contextual actions in a three-dot button on specific entities.

Dynamic Nav with Contextual Actions
This solution displays the user based on their sales role, the most used global actions by that role. If the needed to take contextual actions they could through hovering over an entity's name which will reveal a hover card with the actions and additional information.

The next area of opportunity; the personal navigation

Problem

The secondary or “personal” menu within our navigation currently exists with limited logic or consideration to why something belongs within it or without. It currently has no framework for future guidance on what features we could add or remove.

Goal

A well-crafted design recommendation for the CRM secondary or “personal” menu in the navigation that makes user flows clear, addresses all relevant use cases, and helps establish a framework by which we ship future items into this space.

Plan of action
  • Start by taking a look at the usage data of each section to see what is actually needed and what can be removed
  • Create a framework or intention for what tools/sections should belong in this area
  • Prototype & test

Usage Data
The data showed that while there were three main tools being used, two lagged behind. The report a bug feature being a special case because of its use leaves the last tool, bookmark as an outlier.

Creating a framework

The first step was to iterate of defining what this section of the navigation really was and what it is meant to be used for. Collaborating with our team content strategist, we then came up with this statement.

The personal navigation hosts foundational functionality that supports the current user's platform-wide experience.

With this guideline in mind, I began to evaluate each object within the section and proposed an ideal solution.

Current experience

Ideal experience

Expanding my scope

Navigation Side Tray

After working on the Personal Navigation framework and interaction design, my manager and I increased the scope of my project to include creating a design recommendation for side tray consistency. Within our Personal Navigation actions currently, the three actions Notifications, Tasks and Bookmarks all surface their information in side trays.

Problem

The Side Tray surface that is displayed when acting on some of the Personal Navigation actions doesn't have consistent design or headings across the different features.

Goal

To create a simple design layout for the Side Tray surface that is consistent across the different actions and use cases.

Solution

Telephony Integration into CRM Navigation

Problem

The Telephony system that Marketing Experts currently use on the CRM platform works, but obstructs the user's view and ability to use some of CRMs necessary functionality.

Goal

To integrate the Telephony System into the CRM Navigation so that Marketing Experts and possibly in the future other sales roles, can access its functionality at any moment without obstructing part of their CRM experience.

Current Experience

Ideating solutions
Refining into three possible flows

Final Prototype

Let’s make something together, say hi.