Last Update: March 2025

Last Update: March 2025

Last Update: March 2025

Company

Ridgeline

Roles

UX/UI Design

User Research

Prototyping

Team

1 Product Designer

1 Product Manager

5 Developers

Timeline

5 months

(Apr—Sep 2024)

Integrations Hub

Integrations Hub

I identified a high-impact opportunity through usability sessions, secured it on the roadmap, and led it from concept to launch.

Overview

Integrations Hub unifies third-party connections, streamlining workflows in Ridgeline.

Integrations Hub unifies third-party connections, streamlining workflows in Ridgeline.

Before IHUB, users relied on external tools, leading to inefficiencies. Now, they can schedule automations and monitor real-time data flows—all within Ridgeline—reducing errors and improving operational efficiency.

Background

Context

Ridgeline’s 2024 strategy focused on streamlining the user experience.

Ridgeline’s 2024 strategy focused on streamlining the user experience.

Leadership prioritized automation, cross-platform integration, and AI-powered insights. IHUB aligns with this goal by centralizing integrations and simplifying workflows.

Problem

Users struggled with integrations scattered across bespoke pages.

Users struggled with integrations scattered across bespoke pages.

Without a centralized system, integrations lived in different parts of the platform, making it difficult for users to locate, manage, and troubleshoot them efficiently.


This increased onboarding time and costs.

100%

of firms are migrating from outdated systems

64%

of users have never switched platforms before

Research

Interviews

Users faced inconsistent workflows, frequent errors, and limited visibility into integrations.

Users faced inconsistent workflows, frequent errors, and limited visibility into integrations.

Interviews with operations teams revealed pain points: unclear workflows, frequent errors, and lack of integration visibility, reinforcing the need for a more intuitive solution.

“It’s difficult to understand where everything is.”

Scott P. (Business Operations)

“It’s painful to run the integrations often.”

Daniel R. (Operations Specialist)

“There’s nothing worse than when a PM comes to you and says the data doesn’t match.”

Keith L. (Director of Operations)

“There’s nothing worse than when a PM comes to you and says the data doesn’t match.” Keith L. (Director of Operations)

“If there are errors in the data, everything crashes and there’s no way to predict whether the integration will be successful.”

Victor V. (Operations Associate)

Old UX

Before, users had to navigate multiple bespoke pages to manage integrations.

Before, users had to navigate multiple bespoke pages to manage integrations.

This fragmented approach made finding critical data difficult, increased troubleshooting time, and created inefficiencies in onboarding and daily workflows.

Ideation

Early concepts focused on centralization, visibility, and efficiency.

Early concepts focused on centralization, visibility, and efficiency.

I explored multiple design directions with PMs and engineers, prioritizing API efficiency, integration health monitoring, and reducing manual effort.

Integration Page

Connections Dashboard

Integration Store

Runs Dashboard

New UX

IHUB consolidates all integrations into a single, structured interface.

IHUB consolidates all integrations into a single, structured interface.

Users can now manage connections, monitor integration health, and access real-time status updates—all within Ridgeline—eliminating inefficiencies.

Summary

IHUB streamlined onboarding, reduced errors, and improved efficiency.

IHUB streamlined onboarding, reduced errors, and improved efficiency.

By replacing a fragmented integration process with a centralized hub, we simplified workflows, reduced manual work, and enhanced the overall user experience.

Let's connect—I'd love to share more!

Let's connect—I'd love to share more!

This is an early glimpse into my process. Please reach out to learn more.