Pipeline: How I replace a tool advisors have used for years, without costing them a single productive day

Pipeline is the screen every financial advisor at Interhyp, internal or external, opens first each day. It shows all of their open tasks and lays out their plan for the day. It's the basically advisor's main workspace.

Role

UX Designer (founding team, then sole designer for the last 2.5 of 4 years)

Duration

Since 2022, launched ~1 year ago, ongoing

Team

Product Owner, backend engineers, frontend engineers

Industry

Mortgage & financial services

Users

Internal & external financial advisors

Tools

Adobe XD, Figma, Miro

New Pipeline, responsive screens
For confidentiality reasons, I can't publish the detailed designs here.

New Pipeline, responsive screens
For confidentiality reasons, I can't publish the detailed designs here.

Impact

2x faster onboarding

a new advisor learns and uses Pipeline about twice as fast as the old tool, thanks to the clearer, more structured design

+5 Design iterations

since launch, each shaped by qualitative and quantitative feedback from multiple channels

-20% Time on Task

estimated drop in Time on Task for scanning the Pipeline with Compact mode: more tasks fit on screen at once, so fewer scrolls are needed

Pipeline launched about a year ago, so formal business metrics are still limited. Advisor feedback has consistently been positive, though satisfaction hasn't been measured in a structured way yet, which is part of why I'm now leading the UX-KPI framework work at Interhyp to define a baseline for tools like this one.

Pipeline launched about a year ago, so formal business metrics are still limited. Advisor feedback has consistently been positive, though satisfaction hasn't been measured in a structured way yet, which is part of why I'm now leading the UX-KPI framework work at Interhyp to define a baseline for tools like this one.

Challenge

Interhyp decided to move away from its old, complex legacy system and rebuild each product area as an independent microservice. The old Pipeline lived entirely inside that legacy service, so it had to be rebuilt from scratch.

  • The old Pipeline was outdated, but advisors had used it for years and were completely comfortable with it

  • A purely "better" redesign risked being rejected simply for being unfamiliar

  • Any drop in productivity during the switch would hit advisors' daily client work directly

Designing something objectively better wasn't enough: the new Pipeline needed to convince advisors it was better, and let them start using it from day one without a drop in productivity while they learned it.

Approach

01

01

Discover

Internal advisors were easy to reach, so we worked with them constantly from the start: regular sessions for open questions, shadowing, and one full day I spent just watching an advisor work through their actual day. We also ran workshops and interviews to understand what stakeholders wanted and what advisors' days actually looked like.

02

02

Design & test

Design moved through six rounds of wireframes and moderated usability tests, each with a moderator and two or three observers, adjusting after every round based on what we saw. Testing directly changed the design:

  • Reworked the color coding system used across tasks

  • Added the ability to set a priority level on each individual task

  • Made overdue items (überfällig) always surface at the top, regardless of other sorting

03

03

Launch & irritate

The new Pipeline rolled out gradually to different advisor groups instead of all at once. About 2.5 years ago I took over as Pipeline's sole designer, and the same cycle of feedback and iteration continued, but now the roadmap and design decisions were mine to drive.

some of previous designs from each iteration

Key Features

Since becoming sole designer, I've designed and shipped these on my own:

Vacation mode. Task handoffs, from one by one to a single flow.
Before this, an advisor going on leave had to reassign each open task to a substitute colleague one by one, a slow and error-prone process on top of everything else they had to wrap up before time off. I designed a 3-step flow instead: pick a substitute, review the full task list in one place, and hand off everything at once

Vacation mode. Task handoffs, from one by one to a single flow.
Before this, an advisor going on leave had to reassign each open task to a substitute colleague one by one, a slow and error-prone process on top of everything else they had to wrap up before time off. I designed a 3-step flow instead: pick a substitute, review the full task list in one place, and hand off everything at once

Advanced filtering. Combine filters instead of applying them one at a time.
Filters could previously only be applied one at a time, so advisors had to filter, reset, and filter again to narrow down a long task list. I introduced combinable filter parameters that work together as a single quick filter, which shortened the daily workflow noticeably, especially for advisors managing a high volume of cases.

Advanced filtering. Combine filters instead of applying them one at a time.
Filters could previously only be applied one at a time, so advisors had to filter, reset, and filter again to narrow down a long task list. I introduced combinable filter parameters that work together as a single quick filter, which shortened the daily workflow noticeably, especially for advisors managing a high volume of cases.

Compact mode. More tasks on screen, less detail per task.
Built for advanced users who spend most of their day inside Pipeline. It reduces how much detail each task shows by default, so more tasks fit on screen at once, trading some visual detail for a broader overview when advisors need to scan their day rather than dig into individual tasks.

Compact mode. More tasks on screen, less detail per task.
Built for advanced users who spend most of their day inside Pipeline. It reduces how much detail each task shows by default, so more tasks fit on screen at once, trading some visual detail for a broader overview when advisors need to scan their day rather than dig into individual tasks.

Mobile-friendly design. A separate mobile experience, not a shrunk desktop one.
Pipeline is a dense, information-heavy tool, so simply shrinking the desktop layout down wasn't an option. I designed a separate, mobile-specific experience built around what advisors actually need on the go, rather than compressing the full desktop feature set onto a small screen.

Mobile-friendly design. A separate mobile experience, not a shrunk desktop one.
Pipeline is a dense, information-heavy tool, so simply shrinking the desktop layout down wasn't an option. I designed a separate, mobile-specific experience built around what advisors actually need on the go, rather than compressing the full desktop feature set onto a small screen.

Scalability. Design of the Pipeline is generic, not mortgage-specific.
I designed Pipeline's task structure so it isn't tied to mortgage specifically. It can be configured for any product an advisor sells, business or consumer, which gives Interhyp a reusable pattern for future product lines instead of a one-off tool built for mortgage alone.

Scalability. Design of the Pipeline is generic, not mortgage-specific.
I designed Pipeline's task structure so it isn't tied to mortgage specifically. It can be configured for any product an advisor sells, business or consumer, which gives Interhyp a reusable pattern for future product lines instead of a one-off tool built for mortgage alone.

Key Features in the pipeline.