How to Map B2B User Journeys with a 3‑D Role Panorama: A Design Framework

Research Background

ToB product development is driving experience‑design demands. Recent B2B tools such as CRM, ERP, and ticket platforms have shown that good design adds value beyond basic functionality, prompting designers to focus on clarity, ease of use, rapid onboarding, labor reduction, and efficiency improvements. Design systems address consistency, aesthetics, usability, and development efficiency, while designers now seek ways to align B2B products with users' work scenarios.

Difference Between Individual and Team Competitions

In consumer‑facing (C‑end) products, designers are close to users and can employ qualitative methods and funnel analysis. In B2B products, designers face many stakeholders, tangled business processes, and varying data completeness, especially in early‑stage internal tools. The analogy of an individual track event versus a relay race illustrates the need to consider multiple participants, handoff timing, and coordination.

Design Method Borrowing and Evolution

We analyzed common experience‑measurement models and user‑analysis frameworks and applied them in a "Rank Evaluation System" case study.

HEART‑GSM Framework

The HEART‑GSM model measures user experience across five dimensions, which can be customized to business goals. By decomposing each dimension into business metrics, we derived specific insights for the rank system.

TECH Model

Originating from Ant Financial, the TECH model evaluates enterprise products, highlighting the role task success rate as a core indicator. Mapping task flows on an experience map allows assessment of efficiency and impact on roles.

CES Customer Effort Score

CES quantifies the effort a user must expend to achieve a task, offering a clearer view of tool‑type product usability than satisfaction scores alone.

Building the “Role Panorama”

After initial research we defined business goals, evaluation needs, process scenarios, and core task roles. We then mapped each role’s tasks and assessed effort.

Role Task Mapping

We divided the workflow into eight business stages—from reviewer recruitment to appeal handling—and used brainstorming and qualitative interviews to collect task flows for five role categories. Two key baselines were defined: (1) Task nodes – critical steps that advance the process, ignoring sub‑tasks; (2) Handoff moments – actions where users transfer information to others or the system. Business goals, carriers, methods, and tools were added to each node.

Role Task Deep Evaluation

With role task lanes defined, we performed a deep dive to evaluate effort and content at each node, filling gaps left by the initial mapping. Representative roles were selected to pinpoint key nodes, then qualitative and quantitative methods measured effort levels and issue distribution. Visualizations of effort grades and experience assessments were compiled into a comprehensive role panorama.

Full Panorama Observation

Once the panorama was drawn, we could overview the entire system and extract systemic design insights. By observing task points—pre‑defined nodes, handoff moments, and carriers—we identified 21 interaction nodes, far exceeding the originally planned three, thus uncovering blind spots in the linear development process and guiding future iterations.

Analyzing the task surface revealed effort‑level distribution across roles, highlighting improvement opportunities such as automating reviewer scheduling to reduce organizer workload.

Conclusion

Returning to the original goal, the role panorama enables designers to gain a global business perspective in complex B2B systems, fostering proactive problem‑solving. The method is still in its early version; its scope and operation require further practice, and we are already applying it to other projects, anticipating future research updates.