Redesigning 4m annual users marketplace

Redesign entirely the experience of the Seller/Supply users of a marketplace

Task

Cause of a complete Company Reorganisation & Strategic Realignment, we’ve had the opportunity to question and redefine the complete experience of the Supply users of a spiritual advice Marketplace.

  • Strategy

    Enhance Supply Users

  • Design

    Product Lead

  • Client

    in-House

Overview

Introduction

adviqo Group connects people seeking spiritual guidance with experienced advisors, offering a life-coaching GPS. With 20+ years in the business, they ensure users across the US, Europe, and beyond receive a top-tier experience.

After a company reorganization and a shift in focus, they set out to improve the advisor experience on the supply side. The reason? Realising that our products are the Sellers of our Marketplace. Enabling them to be successful, we are improving our Customer experience. 

 

Adviqo GmbH has been acquired by Ingenio, US-based category leader on May 2022.

In this case study, we’ll dive into the redesign process aimed specifically, at enhancing the advisor experience.

The Role

Lead Product Designer

I joined the project as Lead Product Designer, having been specifically transferred to the business unit to take ownership of that project and in general of the design work of this business unit.  My recent experience leading a successful migration for a US/Latam marketplace proved valuable for this initiative, since the same backend would be used as the starting point.

-Led a Product Design team of 4

-I worked closely with three Product Managers for the operational tasks

-Work in a Product Trio with the Chapter Leads for both Backend and Frontend development for the big migration project.

Process

Approach

Tight deadline with the advantage of an existing US/Latam marketplace as a tech starting point for the DACH marketplace
•Launch MVP first, accompanied by training for Seller users
•Collect feedback quickly through surveys
•Address major UX issues based on survey results
•Conduct interviews and usability tests for deeper insights
•Implement final design in React with rollout of advanced features
Overview

Problem

The platform’s tech, unchanged since 2003, faced major challenges: an inflexible backend and outdated HTML/CSS frontend blocking progress. With a full tech overhaul underway, it was the perfect chance to redesign the site and tackle key issues, which are detailed below.

Problem #1

No Relevancy

Without a clear structure, the platform’s interface was a maze. Poor visual hierarchy mixed critical advisor workflows with customer-facing content, creating a chaotic experience. High-value features were buried under clutter, slowing workflows and testing patience.

Example

No separation between advisor and customer content meant irrelevant information everywhere.

• Too much text and scattered design made focusing nearly impossible.

• High-priority tools were hidden, requiring advisors to hunt for them.

Impact

Advisors, unable to streamline their workflows, spent more time researching competitors instead of focusing on improving their processes and serving their customers effectively.

Problem #2

No Defined User Journey

The platform lacked defined user flows, turning every interaction into guesswork. Navigation was messy, with multiple disconnected entry points. The interface presented a steep learning curve, overwhelming users with all options at once, without progressive disclosure to ease them in.

Example

A cluttered interface with no clear task paths made even simple actions feel daunting.

• Users stumbled into flows unintentionally, creating confusion and inefficiency.

• Without onboarding guidance, new users faced a mountain of effort just to get started.

Impact

The steep learning curve and undefined journeys led to frustration and wasted time, leaving users struggling to complete tasks and diminishing overall productivity.

Problem #3

Outdated Tech

The website’s design and performance were stuck in the ’90s, leading to major trust issues and a dated experience. Manual processes overwhelmed customer support, and there was zero mobile compatibility. The backend and frontend lacked flexibility, causing constant friction and internal inefficiencies. Inconsistent design components created a patchwork interface—when one broke, the entire site could crash.

Example

Advisors had to manage billing and queues manually.

• Common tasks like profile edits or registrations required CS intervention.

• Maintaining two websites (Viv and QDE) meant duplicating effort for everything.

Impact

Without a unified, scalable design system and consistent UI, the platform remained fragile and inefficient, wasting time patching outdated solutions instead of delivering value.

HMW

Defining the problem

Goals

Business Goals

Increase Trust with Advisors (Supply-side users)

By shifting focus from customers to advisors, we aim to improve product quality, a key area we’ve overlooked for the past 20 years.

“The supply knows our customers better, let’s enable them to make the most of it.”

Operational Efficiency

By shifting focus from customers to advisors, we aim to improve product quality, a key area we’ve overlooked for the past 20 years.

“The supply knows our customers better, let’s enable them to make the most of it.”

Eliminate Manual Processes

By shifting focus from customers to advisors, we aim to improve product quality, a key area we’ve overlooked for the past 20 years.

“The supply knows our customers better, let’s enable them to make the most of it.”

Goals

Users Goals

Increase Transparency & Awareness

  • Lack of transparency has impacted trust with advisors. We aim to demonstrate the value we bring to foster better partnerships.
  • Increased awareness and metrics’ transparency can shift their focus where it will affect their performance, therefore their income

Increase Productivity & CRM capabilities

• Improve advisors’ daily workflows, decrease pain points so they can spend less time on repetitive tasks and more time delivering valuable services to clients.

• We’ll provide performance tracking to help them monitor and enhance their productivity and CRM features to enable Sellers doing the CRM for us 🤓

A delightful, consistent user experience

To ensure a proper design system is in place to reduce technical debt and give our users a better, consistent, responsive, and intuitive experience.

Results

Impact 🎯

As this was a large-scale project, we rolled out the new designs in phases to quickly validate some of our hypotheses with the MVP.

For confidentiality reasons, I have omitted the specific values for these metrics.

Research

Our Users

To make sure our MVP truly met our users’ needs, we started with some quick but meaningful research.

•We had semi-structured conversations with Seller users, inviting them to share their experiences, challenges, and wishes for the platform. These early interviews helped us see things from their perspective instead of guessing from afar. •We also dove into marketing surveys already in hand, searching for patterns and recurring themes from a product standpoint. This gave us a head start in spotting what mattered most. By combining real conversations with data, we were able to validate our ideas, better understand user expectations, and shape our priorities for the MVP launch.
Steps

Process

My Role

With prior experience on the platform we were migrating to, I was able to lead the gap analysis efficiently across both backend and frontend. By combining this technical understanding with insights gathered from our users, I was entrusted to own the process, working independently, with the Product Manager mainly supporting approvals and key decision points. My approach enabled both the FE and BE teams to anticipate challenges early, and they appreciated the actionable insights that helped us tackle issues smoothly.
Decision 1

Prioritized Back-End Migration:

The focus was on transitioning to the new platform as seamlessly as possible.
Decision 2

Reused Front-End Components:

Leveraged existing elements from the new platform to accelerate development.
Decision 3

Limited Front-End Team Involvement:

Kept developers free for post-MVP enhancements.
Decision 4

Deferred Research to Phase 2:

extensive research and testing were planned for after the MVP launch to refine the experience.
Decision 5

Scoped Through Gap Analysis:

Identified critical functionality and prioritized essential features for launch after validating hypothesis with other departments insights and user interviews
Decision 6

Release MVP & Training

Since we knew that a radical release like this one we prepared Tutorial and training to ease the lurning curve and shared snippets for the upcoming features to ease the friction from the big change
Steps

USA to DACH market platform migration

Pain point 1

Zero research is too risky

Skipping research entirely was flagged as a no-go after a gap analysis revealed major risks in omitting key features. To move quickly, the Design Team collaborated with customer support to gather fast, actionable insights.
Pain point 2

Seamless integration vs. downscoping 🙃

Migrating to the USA/LATAM platform posed challenges. It lacked essential Seller tools like customer groups, callback queues, and notes, making it clear that these non-negotiable features had to be integrated for a smooth transition.
Develop

Early Designs

Research Objectives

1

Collect User Feedback

Evaluate user satisfaction with the new software post-migration and identify usability challenges.
2

Uncover Pain Points

Explore difficulties faced during the migration and post-launch to guide improvements.
3

Validate New Features

Compare the performance and usability of new functionalities against the previous platform.
4

Set Priorities

Identify and prioritize unresolved bugs and deferred features for future updates.

Research Methods

Our research approach combined qualitative and quantitative methods to capture a holistic view of advisor experiences:

Surveys

We gathered insights from 184 supply-side users to identify key trends and pain points.

Interviews

Spoke with 5 advisors of varying demographics and popularity to gain diverse insights.

User observations

Visited two advisors to observe daily routines and real-world use of the new design.

Our research approach combined qualitative and quantitative methods to capture a holistic view of advisor experiences:

Research Insights

1

Reduced Cognitive Load

Simpler workflows led to a significant reduction in cognitive load, though the steep learning curve remains for long-time users transitioning from decade-old software.
2

Accessibility Barriers

Bugs and limited error recovery disrupted users’ flow, highlighting critical accessibility gaps.
3

Task & Challenges

Users struggled with completing tasks smoothly, such as managing customers, promotions, and communication, revealing persistent pain points.
4

Affordance & Navigation

Suboptimal affordance and navigation often caused confusion and reduced intuitiveness.
5

Design Successes

Users struggled with completing tasks smoothly, such as managing customers, promotions, and communication, revealing persistent pain points.
6

Process Flexibility

Manual processes requiring Customer Support caused delays and hindered transparency, emphasizing the need for automation.

Quantitative Research Insights

We dug into surveys and user stats, connecting the dots between what users say and what they actually do. This helped us spot trends, validate behaviors, and figure out where the real pain points are hiding.

Quick Actions

We tackled the high-priority, low-hanging fruit right away, rolling fixes into the next sprint. This included squashing bugs, addressing UX issues like error prevention and recovery, and automating advisor profile creation and editing – boosting their flexibility and cutting out unnecessary roadblocks. As a result amount of customer support tickets decreased by 30%.
CS Tickets were decreased by 30% 🚀
0%

Dive Deeper

Exploring advisors’ daily routines and marketing needs helped us uncover insights essential for refining workflows and boosting engagement strategies. As a result amount of customer support tickets decreased by 30%. After spotting the areas we wanted to focus, we continued with Qualitative research.
1

Daily Routines

To refine key user flows, we needed to understand their rituals better—what a typical session with a customer looks like and how they spend downtime between session.
2

Marketing Activities

Like any freelancer, advisors focus on retention and engagement. We explored their CRM needs and upselling strategies to uncover ways to boost their sales effectively.

Cross Team Workshop

We teamed up with Customer Support and Marketing to compare findings, gathering insights like advisor reach, session stats, and coupon usage. They also shared qualitative nuggets on how a spiritual session works. This collaboration helped refine our focus for user interviews and observation analysis.

Qualitative Research

We focused on understanding the real-world routines of spiritual advisors through user observation sessions. These sessions offered a behind-the-scenes look into their workflows and everyday challenges. Below, you’ll find snapshots and key insights gathered from these observations, providing a closer look at how advisors interact with the new designs.

Key Qualitative Research Insights

Exploring advisors’ daily routines and marketing needs helped us uncover insights essential for refining workflows and boosting engagement strategies. As a result amount of customer support tickets decreased by 30%. After spotting the areas we wanted to focus, we continued with Qualitative research.
1

Mapping the User Journey

We identified several friction points along the user journey that disrupted workflow and efficiency.
2

Flexibility Matters

Advisors need adaptable tools. Rigid systems caused frustration and inefficiencies.
3

Feature Gaps and Prioritization

Post-migration, missing or postponed features required immediate focus to meet user needs.
4

Bug Tracking and Resolution

Identifying and resolving critical bugs became a top priority to ensure a seamless and reliable user experience.
#Workshops #Product rituals #Decision-making

Updated The Way We Work

Introduced New Product Rituals

During the MVP phase, many bottlenecks surfaced. I took the initiative to adress them and actively try to solve them by introducing new routines that shaped the way we work. These rituals evolved into practical habits, fostering smoother collaboration and consistent progress. The workshops and guides were aiming to improve how we:
  • Identify and report problems
  • Gather and organize insights
  • Brainstorm, prioritize and validate insights

New Product<>Tech Delivery Process

Smarter Design-to-Development: Unified Systems & Chromatic
I introduced a new workflow inspired by leading design handoff practices, connecting Figma, Storybook, and Chromatic. This streamlined collaboration, enabled side-by-side review of coded and design UI, and reduced friction between teams.
  • Faster, clearer feedback between designers and developers.
  • Shared component library for consistent UI across products.
  • Automated visual tests to instantly spot unintended changes.
Finale

Final Designs

Dashboard Improvements for Seller User Experience

• Separated actions based on user intention for clarity • Grouped related actions into intuitive components • Designed entry points aligned with key seller routines from discovery
  • Clearer navigation to main workflows
  • Faster access to frequent tasks
  • Enhanced usability through focused grouping
Before After

Chat Enhancements for Advisor Efficiency

• Provided fast, easy access to key customer info (spending, customer type, etc.) for better preparation • Integrated tools for goal setting, note-taking, and reminder creation to keep discussions relevant • Incorporated observed advisor routines seamlessly before, during, and after sessions (chat/call)
  • Quick customer data overview at a glance
  • Improved In-chat note-taking and reminders
  • Streamlined workflow supporting real-time session management
Before After

CRM Advisor Tool: Intent-Based Campaign Management

• Separated campaign flows based on specific advisor intentions • Mapped advisor needs for different campaign types, recognizing not all require coupons or conversion goals • Enabled cohort management and campaign customization • Shared detailed customer spending and behavior history to improve campaign quality • Focused on reducing coupon overusage and oversharing, achieving a 25% decrease
  • Tailored campaign workflows per marketing objective
  • Enhanced insights through customer data integration
  • Improved coupon usage control mechanisms
Before After

Status Feature: Reflecting Advisor Availability

• Introduced a status feature similar to Slack to show advisor availability • Addressed advisors’ need to communicate their current state during breaks or tasks • Enabled status updates to inform customers, reducing missed calls • Made the platform responsive, allowing advisors to stay connected via phone • Helped advisors manage customer expectations and stay reachable even when away briefly • Mapped advisor needs for different campaign types, recognizing not all require coupons or conversion goals • Enabled cohort management and campaign customization • Shared detailed customer spending and behavior history to improve campaign quality • Focused on reducing coupon overusage and oversharing, achieving a 25% decrease
  • Real-time status updates visible to customers
  • Reduced missed interactions by improving transparency
  • Improved coupon usage control mechanisms

Overview

Below you will find interactive prototype, you can navigate through key pages via sidebar menu.
Finale

What We Learned

Research is never wasted time

This project reinforced how vital research is. Whether it was observing users in action, gathering feedback, or diving deep into their workflows, every insight shaped our decisions. It’s not just about making informed choices—it’s about making the right ones.

Collaboration builds the foundation

Creating something from scratch isn’t just about design and development. It’s about communication between product, tech, and support teams. Without their input, the foundation we built could’ve been shaky. Aligning across teams ensured we didn’t just create a visually appealing product but one that was functional and scalable.

Processes are as important as designs

Great designs only come to life when the workflows behind them are just as strong. From introducing new routines to fine-tuning collaboration with tech, we learned that improving processes is just as crucial as improving the product itself.

Take it step by step

A project this massive isn’t solved all at once. By tackling it phase by phase—starting with the MVP—we were able to adapt, iterate, and evolve, making each stage better than the last. This journey wasn’t just about a platform migration; it was about growth—for the product, the team, and how we work together.
Finale

Future

Bug Fixes

Even with thorough testing, a project of this scale is bound to have a few bugs sneak through. Identifying and fixing them post-launch will be a continuous effort.

Post-launch Improvements

Optimization doesn’t stop after release. With user feedback and data-driven insights, we can fine-tune both functionality and design to create an even smoother experience.

Scaling Up

With the foundation in place, the next step is expanding features and improving workflows while sticking to the principles that have guided us so far. This is just the beginning!
This project stands out as my proudest achievement. Not only did we elevate the product based on real customer feedback, but we also introduced and refined internal processes that transformed how our team collaborates. Every milestone was possible because of the incredible dedication and partnership within the team—especially my fellow designer, who embraced co-ownership from day one, the developers and QA experts who were eager to tackle new challenges, and our product director, whose steady support kept us moving forward. Thanks for taking the time to journey through this story with us. This journey wasn’t just about a platform migration; it was about growth—for the product, the team, and how we work together.
Back