Reconstructing Business Value and Productizing Design for an E‑commerce Backend Dashboard

The e‑commerce platform’s backend is divided into a front‑end guide and a back‑office management system, serving both buyers and sellers; most work occurs in the backend, which is complex, business‑heavy, and challenging for designers.

What is the buyer‑seller workbench? It is a data‑driven operation console that provides SMEs with business decisions and daily management tools.

Design before the project: Designers shift from passive reception to proactive proposal, aligning product direction with business by iterating through focus, discussion, design, reporting, and confirmation stages.

Three‑step business value reconstruction:

1. Understand positioning and switch perspective – grasp the product’s strategic role (people, goods, venue) and translate internal operations into user‑centric language.

2. Unite the front line – align product, operations, and business goals to create a user‑service‑centered platform.

3. Clarify relationships – involve platform, buyer, and seller to build a value ecosystem that links upstream and downstream markets.

Productized design process:

1. Identify user pain points through agile co‑creation research, involving cross‑functional team members, flexible client interviews, and rapid result synthesis.

Qualitative findings reveal buyers need integrated procurement, sales, and logistics tools, while sellers lack clear guidance and lifecycle support.

Quantitative analysis shows concentrated usage with low adoption in certain modules, indicating long‑tail effects.

2. Define design goals and strategies for buyer and seller versions:

Buyer: streamline information architecture, personalize services via behavior data, and enhance interaction between buyer and seller.

Seller: simplify navigation, enable data‑driven self‑operation, and implement a growth‑stage incentive system.

3. Interaction design – refine information architecture into three core handles: scenario‑based navigation, data‑driven content, and modular design guidelines (task service and messaging modules).

Example: Customer Management module defines purpose, goals, actions, and outcomes.

Feature maps were optimized to reduce navigation depth, allowing users to pin frequent entries.

Visual design – after establishing a perception loop, designers extracted core visual tags (simple, clear, efficient) and applied style definitions (minimal decoration, limited color, flat design, whitespace separation). Navigation colors differentiate buyer (orange) and seller (blue) while icons are categorized as explanatory or rights‑based.

Special modules such as the growth panel use 2.5D elements and animated characters to convey progress and motivate users.

Motion design – subtle backend animations were added to make interactions smoother.

The case concludes that product designers must act as co‑creators, continuously iterating and collaborating across teams to enhance backend tools for both buyers and sellers.