Endpoint Monitoring

A centralized monitoring feature that allows IT administrators to track endpoint properties, software versions, and compliance across targeted device groups.

Role: Product Designer
Year: 2026
Team: HCL BigFix
Tools: Figma, Figma Make, Claude

Overview

Analyses

Analyses is a reporting and endpoint monitoring feature within HCL BigFix that enables IT administrators to collect, monitor, and summarize device information across managed endpoints. By grouping multiple property checks into a single analysis, administrators can track software inventory, device health, security compliance, and system configurations across devices. The centralized view helps identify compliance gaps, monitor application states, and make informed decisions without manually inspecting individual devices.

BigFix background

HCL BigFix is an enterprise endpoint management platform that helps IT teams manage, secure, and automate operations across thousands of devices through a centralized console.

My objective

To collaboratively design the Analyses experience with two designers, defining the feature's UX and UI to help administrators efficiently monitor endpoint data, and translating business requirements into an intuitive experience.

The Analyses screen on a phone: the Analyses list with Manage reports, a view selector, search and an Add analysis action.

The problem

No centralized view of endpoint properties across managed devices.
Manual collection of device, software, and compliance information.
Difficulty monitoring application versions and deployment status at scale.
Limited visibility into endpoint health and configuration across target groups.
Time-consuming identification of devices with outdated or missing software.
Inability to quickly summarize endpoint data for reporting and decision-making.
Increased administrative effort to monitor and audit large endpoint environments.
Lack of customizable reporting for organization-specific monitoring requirements.

The challenge

Understanding the existing BigFix platform and adapting the Analyses experience for a modern SaaS environment.
Designing a scalable experience that could support large volumes of analyses and retrieved properties.
Defining consistent UX patterns while aligning with the evolving design system.

Goals

Business goal

Improve endpoint visibility by centralizing device insights and simplifying monitoring and reporting.

User goal

Help IT administrators quickly find, monitor, and analyze endpoint data from one centralized place.

Impact

The Analyses experience brought endpoint insights into a single, centralized interface, simplifying monitoring, reporting, and decision-making for IT administrators.

Design timeline

The design system carried most of the UI, so the effort sat elsewhere. Research took ten percent, mostly requirement understanding and defining the IA. Design took seventy, going straight to hi-fidelity because there was very little UI to invent; the weight was in UX, structuring the information and how it gets used. The remaining twenty went to an accessible handoff.

Research

Defining IA

I mapped the information architecture first, covering the pages, the key tables and content they hold, the create and edit actions, and the states and errors, so the whole feature had a structure before any screen was drawn.

An information-architecture diagram for Analyses, organised into rows: pages (Analyses Landing, Analysis Details, Properties), key tables and content, create and edit actions, states and errors, and a global Manage Reports CTA, connected by navigation and CTA links.

Persona

The work centered on one user: an IT administrator who monitors thousands of endpoints, prefers visual low-code tools over scripting, and relies on assistive technology, which set the bar for accessibility from the start.

Final design solution

Analyses landing page

The landing page for Analyses, which also appears as its own dedicated app within Explorer.

The landing page for Analyses. It also appears as its own dedicated app within Explorer.

The Analyses landing page: a left navigation and a table of analyses with results, tags, properties, device scope, activation, site and modified columns, plus Activate and Add analysis actions.

The Analyses table with rows selected and the Activate-in-bulk action, with the checkbox disabled for an analysis that is already active.

The Analyses table showing that deactivation is not offered as a bulk action; it is only available from the analysis details page.

The Properties tab open from the Analyses landing page, listing properties in a table.

A property drawer open over the Properties page, allowing the user to view and edit the property's details.

01 / 05

Analysis details page

Clicking any analysis opens its detail view, with the property group, device scope, relevance clauses, tags and the full properties table in one place.

Clicking any analysis opens the detail view.

The analysis details page for BES Component Versions: property group, site, description, tags and activation toggle on the left, device scope with relevance clauses on the right, and a properties table below.

The analysis details page with the View more drawer open, showing all of the relevance clauses for the analysis.

01 / 02

Add analysis main flow

Adding an analysis end to end: from the landing page, into the Add Analysis drawer, and back to the list with a success confirmation.

Add analysis, step by step

The Add Analysis drawer, step by step: naming the analysis, choosing a site, adding tags, and defining new properties with their relevance and evaluation cadence.

The empty Add Analysis drawer: name, site, description, tags and properties.

The Add Analysis drawer, empty: an info banner, Analysis name, Site, Description, Add tags and Add properties fields, with a no-properties-added empty state.

The Add Analysis drawer with the analysis name and site being filled in.

The Add Analysis drawer with a new property being defined: property name, an Evaluate dropdown open showing Every report, Daily, Weekly, Biweekly and Monthly, and a relevance field.

The Add Analysis drawer with a relevance expression entered for the new property and a Create property action.

The Add Analysis drawer with the newly created property listed in the properties table.

The completed Add Analysis drawer with name, site, tags and properties filled in, ready to add.

01 / 06

Edit analysis main flow

Editing an existing analysis follows the same structure: reopening the analysis, changing its properties, relevance and tags, and saving back to the details view.

Edit analysis, step by step

The edit flow step by step, reworking an analysis's details, properties and relevance from the same drawer pattern used to create one.

Reopen the analysis with its existing details loaded.

The Edit Analysis drawer with the analysis's existing name, site, description, tags and properties loaded for editing.

The Edit Analysis drawer with a property being edited: its name, relevance and evaluation cadence.

The Edit Analysis drawer with the updated properties listed, ready to save the changes.

01 / 03

Accessible handoff

Page layouts

The handoff specified responsive layouts across the full range, from 320px to 2560px. Scroll to move across the breakpoints.

Grid & spacing layouts

The grid and spacing specification across the same breakpoints, so the layout stays consistent at every width.

Grid and spacing layouts for Analyses across breakpoints, showing columns, gutters and margins at each width. — Grid and spacing across breakpoints.

Dark mode

The full dark-mode treatment across the same responsive range.

Design and accessibility indications

The rest of the handoff is the accessibility spec engineering builds against: components, page regions and landmarks, alt text, screen-reader labels, keyboard navigation order, and skip links.

The Analyses landing page annotated with its component inventory: BigFix header, left nav, solid, outlined and ghost buttons, icon buttons, tabs, checkbox, search, tags and links. — Components

The Analyses landing page annotated with landmark regions: header, global navigation, nav, and main. — Page regions

The Analyses landing page annotated with alt-text specifications for its images and icons. — Alt text

The Analyses landing page annotated with accessible labels for screen readers on its controls. — Labels for screen readers

The Analyses landing page annotated with the keyboard navigation order across its interactive elements. — Keyboard navigation order

The Analyses landing page annotated with skip links that jump focus to the main regions. — Skip links

Result

Designed a scalable Analyses experience that established a foundation for endpoint monitoring in the BigFix SaaS platform.

Product thinking

Since there were no existing references for the feature, I learned to think beyond the individual flow and how it would connect with the rest of the product.

Designing within constraints

Working closely with two designers, the UX Lead, UI Lead, and Product Manager taught me how collaborative design leads to stronger solutions. We explored multiple approaches, iterated through feedback, and aligned the experience with the evolving SaaS design system while ensuring it remained scalable.