Deal Management Experience
π§© Context
As part of revamping our Partner Relationship Management (PRM) software at Coachbar, we identified the need to streamline how users track and manage deals. Users struggled with visibility across stages, lacked bulk editing capabilities, and had no centralized view for deal details.
π― Problem Statement
Users currently lack an efficient and flexible interface to manage deals throughout their lifecycle. The absence of both a structured list view and an intuitive visual overview limits their ability to track progress, update stages, and view key details at a glance. Additionally, without a dedicated detail page for each deal, users struggle to access comprehensive information, leading to inefficiencies in decision-making, collaboration, and follow-ups.
π‘ Goal
To design a multi-view deal management system that allows users to:
View and manage deals in both list and kanban views,Track deal progress visually by stages, and
Access a comprehensive deal detail page for full context and collaboration
βοΈ My Role
I led the UX research, user flow creation, and high-fidelity prototyping. I worked closely with product managers and engineering to define interaction patterns and information hierarchy.
π Research Insights
Users preferred different modes of working: some preferred structured tables, others preferred visual flows.
The lack of a deal detail view meant users had to switch between tabs to gather context.
Stage movement was frequent and needed to feel instant and intuitive.
π§ͺ Solution Overview
β List View
A tabular layout for:
Quick scanning and sorting of deals
Bulk updates (stage, owner, delete)
Search and filters
π¦ Kanban View
A visual pipeline with drag-and-drop functionality:
Categorized by deal stages (e.g. New/Open β Qualified to Buy β Closed & Won/Closed & Lost or Unqualified)
Card summaries with partner name, amount, closed date, and source
π Deal Detail Page
A centralized detail view showing:
Deal overview, partner info, stages with infographic model
Timeline of activity, notes, and attachments
Inline editing and commenting for collaboration
π Impact
80% of users used both list and kanban views within the first month
2x faster stage updates through drag-and-drop
High engagement with detail page (average 3+ visits per deal)
π Tools Used
Figma Β· FigJam Β· Notion Β· Loom (for developer handoff)
π What I Learned
Designing for different mental models (list vs. visual pipeline) improves adoption. And, prioritizing a clear information hierarchy in the detail view directly boosts user trust and actionability.
To check this use-case on a live application, please visitΒ https://channelboost.com/