Asset Dashboard

Role: Product UX/UI Designer

Company: Seerist
Team: Chief Product Officer, Chief Technology Officer, VP of Engineering, Head of Product, Head of User Experience, Product Manager, Data Science Team, Development Team
Duration: 3 months
Tools: Figma, Miro, Confluence, Jira

High-Fidelity Mobile Prototype (Final Design)

Context

Seerist aimed to retain enterprise clients by migrating a critical feature Assets from the soon-to-be-retired Seerist Core. This version of the platform, built in collaboration with Control Risks, allowed clients to monitor threats and intelligence data related to their specific assets.

I was tasked with designing the integration of this feature into the main Seerist platform under a tight deadline. The challenge was to simplify a complex, data-heavy experience and support informed decision-making. I partnered closely with the Product Manager to rapidly prototype and refine an Asset Dashboard that improved usability, aligned with business goals, and met technical requirements.

Results

The Asset Dashboard delivered for MVP improved retention for enterprise clients by 9%.

Initial Project Requirements from Project Manager

Provide wireframes based on the following requirements and on Miro sketches.

Remove Custom Field columns to remove horizontal scroll. Custom fields on horizontal scroll was originally a feature for the Beta version that the Head of Product required. The Product Manager wanted to move this feature to an Asset Profile pop up.
Provide filters within table column headers.
Provide function that allows user to view a specific Asset on a Map with nearby Hotspots and Verified Events.
Provide a Back button from Asset on Map back to Asset Dashboard.

Research

UX Heuristic Evaluation

I conducted a UX Heuristic evaluation of the existing platform Seerist Core, and of the existing Beta version in Seerist (Test Mode).

The current version in Beta has UX issues, such as multiple options for the user to access their Asset on Map: a View on Map toggle at the top and a Globe icon within the Asset row. In either case, when the user clicks to view their Asset on Map, the user must figure out to close this Asset Dashboard by clicking the close icon in top right before they can access the Map view. Once they have done this, there is no clear way to the user on how to reopen the Asset Dashboard: the user is stuck in Map View.

Throughout the product, there is inconsistent iconography for the Map View. There is also inconsistency issues with layout patterns and branding, for example, the Asset Type icons here are not using the Seerist brand colors.

**Screenshot of Asset Dashboard in Beta from Existing Seerist Test Mode**

These issues violated UX Heuristics, so in addition to delivering a solution that met business requirements, technical constraints, and user needs, I wanted to make sure I solved for the existing usability issues in order to restore user trust with the product and user confidence in their experience with the product.

Nielsen Norman Usability Heuristic Violations

Consistency and Standards
Visibility of System Status
User Control and Freedom
Recognition Rather Than Recall
Aesthetic and Minimalist Design

User Interviews

I conducted user interviews with Seerist Core customers to better understand how they interact with Assets and identify pain points in their workflows.

The most common issues for users were:

Difficulty locating asset-specific data: Users often struggled to find information directly relevant to their selected Asset. This slowed down their workflow and created frustration when performing time-sensitive tasks.
Information overload: While users needed access to all available data, the volume and lack of clear hierarchy in the UI made the experience overwhelming. This highlighted the need for improved data prioritization and organization to support efficient decision-making.

User Personas

To address low usability issues in the Seerist platform, I developed detailed User Personas for its two primary user types - Analyst and Security Manager (Federal) - based on insights from user testing, support tickets, user feedback, and stakeholder input. These personas were used to inform design solutions, ensuring the user experience was tailored to meet the distinct needs of each group.

Define: Jobs To Be Done (JTBD)

As a security lead, I want to quickly see which assets are experiencing the highest number of nearby events, so I can prioritize investigation and mitigation.
As an analyst, I want to click into an asset and view a timeline of nearby threats, so I can understand the pace and trend of activity.
As a regional security manager, I want to visualize hotspots near my sites on a map, so I can understand geographic clustering and proximity.
As an operations leader, I want to export a report that shows threats near a specific asset or region, so I can brief stakeholders or inform policy.

Additional JTBD focused on alert configuration and asset-specific threat discovery were addressed through the Notifications and Assets in Search projects.

Design Process

Early Iteration

Desktop

**Wireframe of Map View**
To align with the use case that user’s want to view events affecting their Assets, I added a feature proposal to add “Distance to Asset” within Event cards.

Native Mobile: iOS

I created wireframes to define how Assets would be integrated into the native mobile app for MVP. The goal was to enable users to quickly identify nearby Hotspots and Events affecting their Assets, in both List and Map Views, and read more about potential threats. A swipe-up modal was used on the map to match product’s pattern requirements.

To support mobile use cases, I streamlined the Asset Dashboard to focus on the core JTBD: “What nearby events are affecting my Assets?” Assets were grouped by Country (alphabetically), and custom fields (desktop feature) were removed to keep the interface lightweight. Users can now easily access key information like Pulse and Risk Rating per Asset.

Where possible, interactions and UI patterns were kept consistent with desktop to ensure a seamless and intuitive cross-platform experience.

Navigation & Workflow Considerations

How clear is it to users that clicking an asset leads to the Asset Proximity Report?
How can users easily switch to another asset from any point in their workflow?
The modal pattern will be reused for Event selection. How should users return to the Event List from an Event screen? A “Back to Event List” button inside the modal is one option, but placing it near an existing top-nav back button may cause confusion.
What is the best navigation pattern to help users move efficiently between screens in the asset workflow?

“This is looking SO good! ”

— Product Manager

Feedback from Product Manager:
- Need to consider what clicking on the different content sections would do - where do we take the user to view more about Pulse?
- We need to think of how we can configure:
  - Proximity
  - Time
Perhaps we can show it within the table - it is either 'Default' or 'Custom', with the value also shown. Let's explore that in future. I will note down a talking point for our meeting on Thursday with stakeholders to discuss monitoring proximity from time and location perspective. Verified Events would show 3 days of data as default. In further iterations, we can then make time and location proximity customizable.
- How do we align this with alerting, so that user can match the Assets page with how their alerts are set up for each asset? IMO the Assets page should be an extension of the alerts that have been created for those assets, and it should be possible to customize alerts for each asset from the Assets page.
I'll put a talking point in our meeting on Thursday for this. If we link into the existing Alerts set up, then we don't need to start scoping out a new Alerts flow in this body of work.
- Last question on this: not sure if this information is available or helpful for user, but instead of just Risk Rating from Asset table, we could show all Risk Ratings for Country (Nigeria): Political, Economic, etc?
Feedback from Head of Product:
- Customers need to be able to see all Risk Rating types, not just the overall score.
- The filters for Proximity and Time are irrelevant. The Proximity is set for each Asset by the customer when they set up their Notifications. Time for Hotspots is always 24 hours, and Time for Verified Events is set for each Asset by the customer when they set up their Notifications.
- Pulse and Risk Rating information needs to be shown in the Asset Proximity Report for customers when they are in the Map View.

Feedback from Head of Product
- Filters for Time and Distance: VE and Hotspots (not Pulse or RR) shouldn’t be above table if not applied to all header content types.
- Hotspots only live for 24 hours. Only need within VE. Pulse time filter.
- Pulse increase: take to Pulse page (on table, not just from Asset Map). It is on Latest, so not big lift.
- If there is a narrow distance, there might not be Hotspot or Event results.
Response from Product Manager
Is there a way we can link Hotspots to Assets aside from Distance? Location isn’t only factor that conveys relevance.
- Hover label on icons.
- Users forget Asset Types, so take away Asset Type.
Feedback from Head of User Experience
- Info hierarchy: mirror.
- Keep Asset widget to right consistently.
- Build new pattern while using same components that applies across product. Build UI systems to use/reuse to reinforce consistency.
Feedback from Chief Product Officer
- Need feature on Asset Dashboard to sort by Risk Rating level because Risk Rating Dashboard won’t have this feature.
- If Nigeria’s Risk Rating changes from High to Extreme, we need to show when this change happened (date of change or high for 6 years).
- Nature of Hotspot (bomb important more than amount). Human from Analyst team would need to designate significance. What is at the top of the list of Assets: which Asset has the most Hotspot or Event severity?
Response from Head of Analyst Team
Too many icons on Asset Dash. High Severity Hotspot/Events should be colored differently to convey severity: White (nothing), yellow (close), red (massive). Simplify for users on what Assets to start with. Don’t need before and after rating because these change quickly.
Use case for Asset Manager: When do I need to care? Where does the user need to draw attention day to day. Consult Data Science on what models can be used.
- Priority is that we do not design by engineers, and we do not design by committee.
- Too much variety in the table header actions. If we have a huge amount of space wasted at the top of the page, why are we trying to cram filters into the same place as sorting and time/date controls.

Interaction Design for Cognitive Ease: Simplifying Complex Data Interactions

To reduce cognitive load and apply progressive disclosure (Nielsen Norman: "Recognition over recall"), I added a hover tooltip for Pulse and Risk Rating values, allowing users to view all types without cluttering the table.

Clicking on Hotspot or Verified Event numbers now opens a Reading Panel on the right, leveraging an existing platform pattern for consistency and user confidence ("Consistency and standards"). To signal interactivity, I underlined these numbers ("Visibility of system status").

In response to feedback, I proposed offering in-context access to Alert settings via a pop-up, rather than replicating the full Notifications screen. This prevents workflow disruption and minimizes overwhelm ("Flexibility and efficiency of use" and "Minimize user memory load").

A/B Testing

The Product Manager wanted flag icons for the Country column and icons for both the Hotspots and Verified Events columns.

I was concerned about adding unnecessary UI elements, as the Hotspots and Verified Events icons lacked workflow relevance and could contribute to visual clutter, which goes against Nielsen Norman’s principle of aesthetic and minimalist design.

Nielsen Norman Usability Heuristic Violation: Aesthetic and Minimalist Design

“Interfaces should not contain information which is irrelevant or rarely needed. Every extra unit of information in an interface competes with the relevant units of information and diminishes their relative visibility.”

Option One

Option Two

I conducted A/B testing with both customers and stakeholders, and the consistent feedback was a strong preference for removing the icons in the Country, Hotspot, and Verified Events columns. Participants found the wireframe for Option One, which included more icons, to be overwhelming and distracting, making it harder to orient themselves upon landing on the dashboard and to focus on their workflows.

Option Two was selected as the design direction due to its preference indicated by the data.

Mid Iteration

While working on FIRI at Seerist, I introduced a top navigation bar for switching between Map, Graph, and Data Table views. User testing confirmed it as an intuitive way to explore complex data. Later, with the new Head of User Experience, we proposed extending this pattern across the Seerist platform, starting with the Assets Dashboard, to create a more consistent and intuitive user experience.

In alignment with the Product Manager’s directive, wireframes were created to demonstrate the integration of the Map Controls project across all ongoing conceptual efforts, for presentation to stakeholders.

To support a more intuitive way for users to explore data by Table or Map, I made several key interaction design decisions, demonstrated in this prototype.

Table View

Enabled horizontal scrolling to support adding custom table fields, as requested by the Head of Product.

Map View

Hovering over an Asset brings its icon to the front and reveals its label.
Clicking an Asset zooms into it on the map.
Map Controls are now accessible directly from this view, in line with the Map Controls project.
Hovering over an Event reveals its type, and clicking takes the user to the corresponding article. This was a new feature requested by the Product Manager.
Selecting an Event icon now triggers feedback. Initial exploration included icon enlargement, with other options like color change to be considered later.

“This is brilliant. Cheyanne has done incredible work bringing our ideation to life and I am excited to move this to the next step.”

— Product Manager

Feedback from Stakeholder Meeting:

Due to the longer development time required to implement this top navigation bar and the risk of delaying the Asset Dashboard MVP, it was ultimately removed, as stakeholders prioritized a quicker solution to deliver value to users faster.

Feedback from Chief Technology Officer
- Clicking on Pulse takes user to Watch Page
- Custom fields in table is imperative.
Response from Product Manager
Please can you make the Asset Actions column fixed and stick to the right hand side of the table so that regardless of whether user is has to horizontal scroll across page they can always access Asset Actions. It's a good compromise if we are going to allow user to have Custom Fields.
Response from Head of User Experience
Lock these Asset Actions to the left of the row for users to access quickly and easily.
- What does 3 miles mean? Is this the radius? I think this makes sense if it is the radius for now, but if we add capability to have multiple Monitoring Proximities per Asset OR to have custom shape Monitoring Proximities, then we will need to think how we express the Monitoring Proximity as a number.
Implementation
In response to the feedback, I suggested the solution to name the header "Monitor Radius” to reduce user confusion.
Response from Product Manager
Yes "Monitoring Radius" is good I think. For now this is fine, may need to change in future.
- Need indicator for if Pulse shown is City level or Country level.
Response from Product Manager
So depending on location of Asset, it will be either one of these. Use an icon to give a visual indication if the Pulse is derived from City Level or Country Level. I am assuming that the colored icon within Pulse score column in the table is displaying the current Pulse score color from the Pulse bar. A key variable is whether the Pulse is within, above or below average. I believe we are not displaying this variable in this first iteration, which is fine but we'll need to solve for this quickly in next iterations.
Response from Chief Technology Officer
Unclear what the new icons do/mean. Do we have an indicator of which city this is? Would seem to be an important attribute.
Response from Head of User Experience
Provide information within a hover component to user on whether the Pulse if from City level or Country level, and if City level, which City. Within this hover, also provide Pulse score information on whether this score is within, above or below average.
- RR can be determined from a Risk Rating Zone OR Country Level. If the Asset is within a Risk Rating Zone then we can use the more localized rating of the Risk Rating Zone. If the Asset is not within a Risk Rating Zone, but only within a Country - then we will use the Country Risk Rating. We need a way to visually indicate which level we are taking the Risk Rating from for each Asset.
Response from Product Manager
Use an icon to give a visual indication if the Risk Rating is derived from Zone Level or Country Level.
Response from Chief Technology Officer
Risk Rating column probably won’t have an up/down as many haven’t changed for 10 years. Unclear what the new icons indicate here.
Response from Head of User Experience

Provide this information within a hover component.
- Seeing the type name instead of the icon should make searching a bit easier. The icon will likely be changeable through map legend controls, so should not be directly associated with the asset for all users - except perhaps as a default.
- What happens when I just click on the row itself or the asset name?
Thought Process and Proposed Solution
User Feedback or User Testing would be ideal here, but since this isn’t an option with stakeholders, and since we provide all user interactions clearly within the row, I considered what would be most beneficial here. I communicated that a row highlight could be helpful, so they can track across to the end of row, especially with adding Custom Fields back in with horizontal scroll. This would ensure the user to select the correct Asset’s Map icon, reducing user frustration.
Response from Product Manager
Let's place the 'Full Asset View' behind the general row click. Also means we don't have to put it in Asset Actions. What do you think?
Response from Head of User Experience
The Head of User Experience agreed to put all clickable items into an Asset Full Profile View, which would replace a right side reading widget for Hotspots, Verified Events, and Events AI.
- Does filtering table filter map display of icons?
Thought Process and Proposed Solution
I analyzed the feedback and considered an initial solution based on user work flow. When the user selects the Map icon of an Asset, and they are redirected to the Asset on Map, the filters that the user applied in table should be the default in order to allow the user to continue their workflow. If this is the case, then I would implement feedback to user within the design on filters being applied (ie, the Map Controls widget could default to open, etc). I communicated that I would like to understand their feedback on a differing use case.
Response from Product Manager
My input on this is: In our model, the map does not load ALL Assets on to map at once, so actions that affect Table Filters do not affect map. The map interaction is currently that user can place an individual Asset onto the map from the Asset Table. User can add multiple [Assets onto the Map] from Map Controls tool, but not in Asset Dash. Therefore Table actions don’t affect Map display. In the future, we can add this capability so that there can be some alignment between table and what is shown on map, but we feel the map is a deliberate tool to tell the story of an asset, not just a map based mirror of the table. We can progress this iteratively.
- Pulse delta should be based on the average, over the listed period, not the delta from a particular number of days ago. Not really clear how to set the date range for the counts and the pulse delta source point- once it is set, where do I see it?
Feedback from Head of Development
I'd like to see how a user filters the table by city, state.
Feedback from Head of User Experience
There are also a lot of random icons that don't have a clear meaning.
Solution
I had communicated to the new Head of User Experience that the platform has a problem with random icons (meaningless for user) and icon inconsistency. Since the Head of User Experience was in the middle of auditing and reducing icons to a specific icon library, I suggested that the Head of User Experience be brought into my collaboration meetings with the Product Manager, so my designs could align with a mutual decision from both the Product Manager and Head of User Experience.
Response from Product Manager
Agreed. We can exclude icons for now and add these in later once an icon set has been agreed? I'm not super happy to do this since I think that without these icons anchoring data types within the table, they get lost, but if the plan is to reinstate these in future then that's fine.
Feedback from VP of Engineering:
- Since Seerist currently does not offer a card component view in Maps, and this was conceptual, he wanted to remove this feature for MVP.
- Since Seerist doesn’t offer a top navigation bar on how to view Data, either by Table, Map, Graph or Config, do stakeholders want to implement this design for MVP, which means a heavy cross-platform development lift, or will we use the navigation bar in Beta that development has already implemented?
Response from Stakeholders
In order to quickly provide an Asset Dashboard to users, stakeholders decided to hold off on a large cross-platform solution, and to keep the Asset navigation that development had already implemented into Beta.

Final Iteration for MVP

To address user overwhelm while ensuring access to all necessary asset data, I applied the principle of progressive disclosure. Primary information is surfaced upfront, while secondary details (such as Pulse and Risk Rating data) are accessible through expandable sections within the Asset Dashboard. This helps users stay focused on key tasks without being overloaded.

Desktop

User Job To Be Done:

As a security analyst, I want to identify which company asset has the highest number of conflict hotspots, visually review these threats on a map with detailed context, and download a comprehensive report so I can brief executive leadership with actionable intelligence.

**Asset Dashboard**
A filter bar was created above the Asset table. Extensive design went into creating Filter Components that encapsulated all feedback from Stakeholders, Product and Development team.

Native Mobile: iOS

Click Here for Figma High Fidelity Mobile Prototype

To improve navigation, I added an interactive breadcrumb bar that helps users track their location and return to any point in their workflow, especially within the Assets tab on mobile. I replaced modal close icons with a clear “Back to Event List” button in the top left to eliminate redundancy and reduce confusion, using descriptive text for added clarity. I also introduced an Asset selector dropdown, enabling users to switch between assets without leaving the current view.

This ensured that the design solution aligned to these UX Heuristics:

Nielsen’s Usability Heuristics