Pega Navigation Bar

Desktop• Information Architecture • Design System • UX Research • Wireframes • Prototyping
Project Overview
Pegasystems Inc. (Pega) is an American Saas company that develops software for CRM, robotic process automation, and business process management.

The goal of the project was to redesign the navigation bar for Pega’s public-facing home page. Aside from the visual aspect, the project also requires a re-organization of the current information architecture for a better navigating experience.
My Role & Contributions
The design team I worked in was composed of one product manager, one design lead, one tech lead, and another UX designer.

I owned the end-to-end process of defining the scope, conducting UX research, analyzing and redesigning website structure, creating wireframes, and creating higher fidelity prototypes.

It was reported in the customers’ feedback, that people are having trouble navigating Pega’s website and finding a particular webpage. The current navigation bar consisted of 2 lines of tabs, which were in total 11 tabs to click on.

"How might we create an easy to locate, easy to navigate website experience by creating a navigation bar that has better usability and is consistent with Pega’s design language?

The Challenge

Understanding the Target Audience

Based on the first project kick-off meeting, I categorized the target audience for Pega's public-facing website into two groups:

  • Pega's existing clients
  • The general public

For the existing clients, they use the website mainly to get help with problems they encountered using Pega's digital products. For the general public, they browse the website to look for information about Pega's products, events, and the company itself.

What's the Current Experience?

In order to understand how website users interact with the navigation bar and identify the pain points, I sent out online surveys using SurveyMonkey and interviewed existing clients. Questions were designed mainly to  find out:

  • How do they identify and locate desired information on the website?
  • What's the average time they need and how efficient are they locating the information?
  • What hinders them from locating the desired webpage promptly?

In total, I received 42 questionnaire responses and conducted 9 interviews. Below are some selected responses.

What I Found

From the user research, I grouped the feedback and summarized them into key design insights:

  • For the general public, there are too many tabs on the navigation bar.
  • There are two lines of navigation bars that are confusing for users to identify which is the main navigation bar.
  • For existing clients, the feature being used most is checking reply messages for questions they asked, which requires them to log in to their account first, then click on the notification button to view messages on a separate page.
Pega's old navigation bar

Drawing Inspirations From Others

I then did a comparative analysis to see how other websites accommodate necessary information while providing a clear website structure for navigation usability. Some key inspirations I summarized are:

  • Containing 5 or fewer tabs for the main navigation.
  • Having a user center for all notifications, messages, and log-ins for registered users.

Mapping Out the Current Information Architecture

To better understand the current website's infrastructure, features, and hierarchy, I created a visual representation that clearly showed the structure of its information architecture. And the following issues were revealed:

  • The old website structure lacks "depth" and has a "flat" information architecture.
  • There were many duplications of pages.
  • Some subpages were grouped in the wrong category and put under the wrong tab.
Information Architecture - Before

Removing and Grouping Subpages

Based on the previous analysis, I re-organized the information architecture and kept only 5 tabs that got clicked most. I also removed the duplicated pages and re-allocated each subpage to its correct tab.  

  • Include only 5 primary tabs. Research has shown nav bars with fewer tabs provide a better navigation experience, as having too many choices can be paralyzing and exhausting.
  • Create depth. Creating more layers of subpages can improve the"flat" structure of the original website.
  • Wording. The original nav bar included ambiguous tab names. In the new design, I chose words carefully to describe the page correctly.

Below is the information architecture after the re-structure of website.

Information Architecture - After

Design Explorations

I then made 5 different versions of design explorations with the re-organized structure. I ended up going with the third design because it demonstrates most clearly the status change when a tab is clicked, and fits best with the current design system.

Merging Two lines Into One

The original navigation bar contained two lines of tabs. To merge them into one line, I created a user center for existing clients to quickly log into their profile pages, and a "waffle menu" grouping all other functions from the top line and was visually consistent with the overall navigation bar design.

Navigation bar - Before and after

Same Page Message Checking

As the most frequently used feature for existing clients, checking messages used to require multiple clicks and navigating to a different page. I integrated a notification icon on the navigation bar and used a drop-down menu to show messages, which allows users to view messages with minimum clicks without leaving the current page.

Notification States and Other Features

The notification icon changes according to the user's login state. Other than the notification icon, I also created two other icons, “Profile Page” and “Waffle Menu” to accommodate the rest of the features on the old two-lines navigation bar. The profile icon allows users to check account status and change account settings; the waffle menu integrates other features used less frequently by existing clients.

Account profile page and settings
Integrating tabs into a "Waffle Menu"

Integration with the Design System

Next, I combined the dropdown menu with the new navigation bar design following the design system guidelines.

These mockups helped me to communicate different directions I can take more vividly, and gave other team members, who are not from design backgrounds, better ideas on how the final look of the website will be with the new navigation bar integrated.

Reflections and Next Steps

Although this project mainly focused on one specific feature, the navigation bar, more than the actual output, I’m immensely grateful to have been through an entire UX process. On that note, a few reflections I had:

More Projects

Interested in working together? Get in touch today.

Drop me a message at siachang.work@gmail.com