Designing User Experience: A Practical Methodology for Product Teams

Two Types of Experience: Basic vs. Customized

Basic Experience

Basic experience forms the underlying rules that run through the entire product, ensuring usability and consistency. It covers visual standards, typography spacing, interaction logic, and error prompts. Its core goal is to lower the user's most fundamental operational cost. The entire rule set must stay unified to avoid cognitive burden when users switch between pages. Basic experience is the product's experience baseline.

Customized Experience

Customized experience targets specific pages or business flows with tailored designs that serve the unique business goals of each scenario. No universal good/bad standard exists. For example, Taobao's homepage focuses on content distribution and guiding exploration, while the product detail page aims to drive purchases — their design logic differs completely. In B-end scenarios, an approval flow prioritizes efficiency and data accuracy; visual polish is secondary. Different scenarios shift the center of gravity for experience design.

C-End vs. B-End: Divergent Design Priorities

C-End User Experience

C-end experience centers on lowering entry barriers, boosting delight, and evoking emotional resonance. Before the business model is proven, strong experience acts as a powerful catalyst. Small copy tweaks, button adjustments, and other low-cost optimizations can improve retention and conversion, helping the product survive its seed stage.

B-End User Experience

B-end experience focuses on raising business efficiency and reducing operational errors; design must fit real business logic. B-end work cannot stop at beautifying single pages — it requires upgrading from page thinking to flow thinking, designing around the complete business chain. Approval pages often carry massive business data and must guarantee rigor; visual appeal comes later.

Quantifying User Experience: Let Data Speak

Experience evaluation cannot rely on feeling alone; an objective measurement framework is needed to verify optimization effects.

General metrics: conversion rate, click-through rate, page dwell time, bounce rate — directly reflect changes from experience tweaks.

Depth metrics: steps and time to complete a core task. Compressing a flow from 10 steps to 5 is an intuitive experience gain.

B-end specific metrics: full-cycle business duration, operation error rate, manual intervention frequency. Shortening the approval cycle from submission to closure is the most direct proof of B-end experience optimization.

Dual Value of User Experience

For Users

User experience = lower usage cost + corresponding gain (C-end: delight; B-end: operational efficiency). Experience essentially manages user expectations: the lower the operational cost, the easier to exceed expectations; the higher the cost, the easier to disappoint.

For Enterprises

In C-end products, quality experience is a low-cost lever to acquire users, accumulate early seed users, and build competitive moats. A simple tooltip optimization can lift points-redemption rates. In B-end products, experience ensures smooth business chains, cutting training costs and error costs. If the flow logic works but operations are cumbersome, that is an experience problem causing direct business loss.

Distinguish one issue: a flow that cannot complete is a product logic defect; a flow that runs but feels painful is an experience problem.

Using the Kano Model to Prioritize Experience Needs

Resources are always limited; the Kano model helps classify needs and allocate R&D/design resources rationally:

Basic needs — must-haves; absence causes dissatisfaction. B-end data accuracy, C-end core functionality availability are baseline needs, secured first.

Performance needs — the better they are done, the higher the satisfaction. Examples: page smoothness, information clarity.

Excitement needs — exceed expectations, deliver surprise. Smart shortcuts, thoughtful emotional prompts belong here.

Indifferent needs — users barely perceive them; minimize investment.

Reverse needs — implementing them degrades experience, e.g., redundant complex configs, frequent popup interruptions; identify and avoid.

Implementation Method: From Visual Perception to Guiding Behavior

The core logic of experience design: visuals influence perception, perception influences behavior. Visual element design can intervene in user behavior and reduce churn. A user completing an action passes through three stages, each carrying churn risk:

Perception stage — user doesn't see or know the feature exists (passive churn). Solution: images, motion, prominent identifiers to grab attention first. Example: ads with real-scene photos attract eyes far better than pure text.

Interest stage — user sees it but feels it's irrelevant or unappealing (active abandonment). Solution: highlight benefits — price, perks, scarcity — to trigger intrinsic motivation. Example: a hotpot ad adding a half-price coupon next to the image lifts interest.

Behavior stage — user is interested but the operation is tedious or guidance vague (passive churn). Solution: clear action paths — button copy, arrows, countdowns, slot indicators — to cut cognitive load. Example: adding a "View Now" button with remaining slots creates urgency.

Passive churn volume often exceeds active churn. Much of experience optimization is about plugging passive-churn leaks.

Core Principles for C-End and B-End Experience Execution

C-End Practice Points

Details move metrics — low-cost changes like copy, button color, placement, and hint text often yield measurable conversion lifts. Run A/B tests at key conversion nodes.

Actively manage user expectations — clear information architecture and onboarding let users grasp product value quickly. First impressions form in seconds; clear value expression lowers bounce.

Add emotional design — inject emotional touches at task-completion, error, and other key moments to boost goodwill and error tolerance.

B-End Practice Points

Flow first — don't polish isolated pages; design around the complete business loop to ensure closure. A beautiful page with a broken chain still yields poor overall experience. Map the full business flow chart to locate bottlenecks.

Clarify role boundaries — separate product manager duties from requirement analysts. PMs focus on how experience drives business goals, not on granular feature descriptions.

Value over experience — when experience optimization conflicts with system stability or risk control, experience yields. Experience is a bonus, not the product's core value.

Correctly Identifying Real Experience Problems

Judging experience problems combines objective data and business context in two steps:

Watch objective data signals: rising payment failure rate, lengthening approval duration, etc., signal problem occurrence.

Make qualitative judgment: analyze whether the data anomaly stems from poor experience causing user churn or business blockage.

Beware of imagined needs : don't substitute the product team's own cognition for real user scenarios. Many experience optimization projects fail because teams subjectively guess user needs, detached from actual work/use contexts. Validate through user interviews and behavioral data analysis whether the experience problem truly exists.

Relationship Between User Experience and Business Value

User experience ≠ business value. Product success ultimately hinges on the business model; experience is an accelerator, not the destination. Early on, when the business model is immature, good experience retains users and helps cross the seed stage. Long-term, a sustainable business model is the foundation.

Excellent experience design deeply understands user scenarios and business goals, leverages data, finds the balance between user cost and gained value, guides target behaviors, and ultimately supports business success. Whether C-end or B-end, experience always serves business goals — it is an efficiency tool, not the end goal. When experience design clashes with core business value, business value takes priority.

Closing Summary

User experience is not just feeling; it is a learnable, actionable methodology. Core aim: through design, change user perception, guide user behavior.

C-end pursues low barrier + high delight; B-end pursues low error + high efficiency.

Basic experience guards the product floor; customized experience matches scenario-specific business goals.

Experience analysis depends on scenario and data; use objective metrics to measure optimization, reject pure subjective judgment.

Apply the Kano model for need prioritization; use the perception-interest-behavior model for experience design.

Always remember: experience serves business goals — it is an enhancer, not the goal itself.

Every experience optimization creates value for users and is also a process for product people to deepen their own capabilities. Maintaining reverence for users, sensitivity to data, and understanding of business logic enables sustained great product experiences.