How to Boost Backend System Experience: Practical Design Strategies

Since joining e‑commerce backend interaction design in June 2018, the author has focused on overall system experience improvement and design standards beyond daily UI tasks.

Why Backend Experience Matters

Initially backend systems only needed to support front‑end functions, but as products grow, every front‑end improvement relies on a complete backend support chain, affecting team efficiency and product image. Improving backend experience boosts efficiency and enforces logical product standards.

Differences in Backend Experience Optimization

Unlike isolated UI tasks, backend experience optimization requires designers to proactively measure, manage, and plan experience globally rather than reacting to single requests.

Process Overview

Measure → Collect → Plan → Design

Communication is crucial because backend systems involve complex business logic, many stakeholders, and require collaborative effort.

Measuring Experience and Gathering Feedback

Traditional metrics like NPS or bounce rate are less applicable due to small sample sizes and the fact that users must complete tasks regardless of satisfaction. Instead, direct user interviews, usability testing, and experience maps are effective.

Three Measurement Methods

Satisfaction questionnaire converting abstract experience into concrete scores.

User‑experience map to locate system pain points and opportunities.

Process timeliness as a tangible indicator of experience improvement.

1. Satisfaction Questionnaire

The questionnaire includes overall product satisfaction, generic metrics, and functional satisfaction, plus user attributes and open‑ended feedback. Questions avoid technical jargon and use concrete descriptions, e.g., “page load speed and error frequency” instead of “system stability”.

Analysis of questionnaire results highlighted low satisfaction in modules D and E and lower scores from overseas users.

2. User‑Experience Map

While questionnaires provide quantitative data, a comprehensive experience map visualizes user journeys, pain points, and opportunities across the entire system.

Co‑creating the map involves product, technical, design, and business stakeholders, guided by a predefined main workflow to keep discussions focused.

3. Planning and Design Output

After mapping, common experience issues such as inconsistent form standards, chaotic notifications, opaque process progress, and poor small‑screen layouts can be addressed with reusable solutions.

These are categorized into:

Simple optimizations without design (bug fixes, one‑line requests).

Framework or common‑issue designs (navigation, homepage, global notifications, form standards).

Complex, non‑reusable designs requiring deep business logic changes.

Homepage Redesign

Define design positioning for new and existing users, populate content modules (announcements, help, tasks, business incentives), and determine presentation formats.

Notification Tiering

Classify notifications into “important & urgent”, “important but not urgent”, “not important & not urgent”, and consider removing low‑value messages.

Complex Form Optimization

Provide clear examples, highlight audit points, and supply templates, reducing a 41‑day process to 21 days.

Process Node Transparency

Introduce a progress module showing each node, responsible person, deadline, and actions, saving extensive communication time.

Conclusion

The outlined workflow—identify experience, collect feedback, extract common issues, and design solutions—helps teams systematically improve backend system experience, fostering deeper user understanding and cross‑functional collaboration.