Catchpoint

2025 - 2026

Empowering IT Teams with Full Visibility of Their Internet Stack

Transforming dense, multi-vendor network telemetry into an interactive map that cuts through noise and accelerates root-cause analysis.

Role

Product Designer

Timeline

May 2025

Team

1 Product Designer, 3 Product Managers, Engineering Lead

Platform

Web Application

Role

Product Designer

Timeline

May 2025

Team

1 Product Designer, 3 Product Managers, Engineering Lead

Platform

Web Application

Overview

Shaping the way Engineers Diagnose Service Outages

I led customer research, user testing, and end-to-end UX design for the Internet Stack Map, an advanced observability tool that visualizes complex service dependencies across hybrid infrastructure. The new experience eliminates visibility blind spots—empowering engineering teams to instantly isolate outage root causes, drastically reduce Mean Time to Remediation (MTTR), and drive broader platform adoption.

The Impact

Problem

Diagnosing internet dependencies felt unnecessarily complex

IT and Operations teams struggle to diagnose complex internet outage paths across hybrid infrastructure, third-party CDNs, and SaaS vendors. Legacy telemetry views present data in dense, fragmented tables that require manual correlation, leading to high cognitive load, and prolonged mean time to diagnosis (MTTD) & Mean time to resolution (MTTR).

Initial Observations

A missed potential for one the top Digital Experience Platforms

Navigating live service disruptions, triaging multi-vendor internet paths, and protecting mission-critical uptime, IT Operations teams are under immense pressure to isolate failures fast. Primary Solutions these problems lacked a cohesive way to instantly separate internal infrastructure failures from third-party provider outages.

Even Catchpoint provided a comprehensive set of observability tools but the user experience remained siloed. Engineers had to stitch together complex alerting rules and jump between disparate dashboards to trace a single incident. This disjointed workflow increased cognitive load during critical outages and highlighted a key opportunity: unifying multi-vendor telemetry into a single, cohesive view.

Research

We wanted to understand what IT Professionals really face when triaging an outage

In order to understand our users’ needs better, I reached out to 15+ Site Reliability Engineers, IT Operators,
and Network Operators

01

Tool sprawl and fragmented troubleshooting

IT professionals used an average of 8 tools when investigating a service outage.

02

False and noisy alerts that lack confidence and erode trust

72% of operators mentioned that alert fatigue and false alerts add a substantial amount of noise and stress while on-call.

03

Third party blind spot “Is it us or is it them?”

Third party providers account for Two-Thirds of public outages making it crucial to know when a provider is affecting their services.

Key Insight: Workflow while navigating a performance problem

Below maps the process and possibly workflows an Operator uses when investigating a service outage.


Design Decisions

How Observability Platforms guided our UI

To establish baseline user expectations, we benchmarked adjacent observability tools to analyze where current market solutions introduce friction, visual clutter, or unnecessary cognitive load during incident triage.


UI Development: Lo-Fi to Mid-Fi Interfaces


Before
After


User Testing

Does the design work?

Following the initial release of our MVP design, we met again with the 15 Site Reliability Engineers, It Operators, and Network Operators to test the content and functionality of our solution.

Test Objectives

  • Test the ease of use and navigation of the Internet Stack Map

  • Test the overall workflow and how our tool integrates with their monitoring workflow

  • Observe any friction, frustration, or hesitation within user interactions 

  • Gather any additional information around the data SREs use to monitor their sites 

Test Conclusions

Through user testing our MVP design we learned the stack map’s usability could be improved specifically when trying to build the map itself and while trying to navigate the map

  • The design does not scale well when working with large maps with a high volume of layers and services

  • The size/format of both layers and services is cumbersome and does not provide additional benefit to users’ overall workflow

  • Operators will needed quick correlations into larger public outages that could effect their services.

Final Delivery

Our research and user testing with Operators helped us improve the functionality of the Stack map and define key features of the new Stack Map.

Alan Hensel

Strategic Product Designer who transforms complex enterprise workflows into scalable, high-impact digital products that drive efficiency, retention, and business growth.

Contact

alanjhensel@gmail.com

Alan Hensel

Strategic Product Designer who transforms complex enterprise workflows into scalable, high-impact digital products that drive efficiency, retention, and business growth.

Contact

alanjhensel@gmail.com

Alan Hensel

Strategic Product Designer who transforms complex enterprise workflows into scalable, high-impact digital products that drive efficiency, retention, and business growth.

Contact

alanjhensel@gmail.com