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
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
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
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.
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
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:
Key Features in the pipeline.





