Nielsen Admin Manager
"Your question is music to my ears"
That was the response of A. M., a Director Solutions Engineer, to my request to take part in user research sessions.
​
A. M is a key user in the current Admin Manager system and he was thrilled with the idea of an improved system that will make his life much easier.
And he was not the only one.
So, what was it all about?
Nielsen Admin Manager is a system for managing tens of thousands of organizations’ users.
The system provides and manages users’ permissions, providing them access to applications and products and enabling them to perform various types of actions and tasks.
Additionally, one can define entities of users that share the same features and objectives.
Current System Challenges
Separate Applications
The current system is divided into five separate applications, even though the content is connected and intertwined between applications. Numerous relations and dependencies are not reflected or displayed on the system screens. Moreover, navigation between the applications, which is generated from the user drop menu, is not user-friendly.
Partial overview
Each display allows the user to view only part of the information.
There is no ability to view all relevant information and grasp the whole picture.
Lack of information
For each element, no description or additional information is available. For example:
-
A specific role's view does not contain the list of relevant tasks and authorizations.
Thus, the user has no idea what abilities this specific role grants him. -
Screens do not list the permission properties required to view them, thus; the admins don't know what type of permissions they need in order to have access to a specific screen.
-
The user group’s view does not list the group's permissions and roles. As a result, when adding a new user to an existing group, one cannot know which permissions and roles the user was just granted.
Exposure to a load of irrelevant information
As a user, one is exposed to a lot of information, a big part of not relevant to their task.
This causes both information overload and confusion.
Analysis Process
-
Usage experience: I had dived into the system and tried every task available
-
System architects' interviews: I had sessions with product owners to learn how the system was developed and what were its limitations
-
System mapping: I mapped the connections, relations and dependencies between the applications
-
Users' interviews: I conducted interviews with key users, such as product admins, to list the main usage flow, system issues and pain points
-
Report and recommendations: I summarized research conclusions and specified my recommendations for new UX and UI
Our research led us to the conclusion that the system's current UX and UI are confusing and inefficient. For a new concept, we have decided on a completely different perception:
One Place to Rule Them All!
All actions and tasks are available from one application, so the user can easily navigate within all the different entities. Every user is exposed only to relevant information, according to their permissions and roles. No more overload by endless data!
​
I designed the new UI according to the new Global Design System (GDS) so it was composed of the new fully accessible components. Accessibility is the key!
The Solution
