How to Translate Design Value into Business Impact

1. Understanding Design Value

Design is not art; it exists to solve problems.

In experience design, the business side proposes requirements, while product managers and designers act as problem solvers from different perspectives, and users are both the source of needs and the validators and creators of value.

Design value originates from business goals and is realized through business value monetization.

Design value is the portion of value that designers generate for the business through design thinking, strategy, and methods.

Effective design must precisely meet business demands. When crafting a design solution, ask:

Which business goals are achieved?

Which business problems are solved?

What business value is created?

2. Creating Value by Satisfying User Needs

Business value ultimately comes from monetizing user value, so serving users well is the key to business success. Designers can help business goals by uncovering user needs and improving product features and experience.

P.S. User value = the core value a product delivers to target users, i.e., the problems it solves, the needs it meets, and the services it provides.

3. The Product PRD as a Secondary Reference

For senior designers, a product PRD is not the optimal solution but a second perspective that offers an initial solution, opening design thinking.

Designers handle PRDs at three maturity levels:

Junior: Replicate the PRD directly.

Intermediate: Refine the PRD and suggest experience improvements.

Advanced: Integrate business and product goals, uncover core user needs, and propose the best solution.

2. Three‑Dimensional Derivation of Design Goals

When designers receive a BRD & PRD, they should consider multiple dimensions to set design objectives and strategies.

1. Business Perspective: Clarify Positioning

From the business side, extract from the BRD:

Target user types and scenario scope.

Core value delivered to users.

User value monetization model and strategy.

Quantifiable business metrics.

Key considerations:

Focus on north‑star metrics (e.g., retention vs. conversion).

Understand the business roadmap to align design pacing.

2. User Perspective: Match & Refine Needs

Users are the source of all needs; design must return to the user view when business requirements are vague.

Target user characteristics.

Core demands, tasks, and key behaviors in typical scenarios.

Quantifiable metrics for key behaviors.

Segment users by role, familiarity, value, goal strength, interests, stage, and process.

3. Product Perspective: Strategy & Implementation Constraints

Product managers translate business needs into product strategy and outline implementation constraints (frontend, middle‑/back‑end dependencies).

Product goals and strategy.

Feature scope and core flows.

Support from front‑, middle‑, and back‑end capabilities.

Implementation costs and risk points.

When analyzing a PRD, consider:

Systematically trace point‑level requirements to their module context to ensure end‑to‑end scenario closure.

Account for feasibility, existing capabilities, development cost, and operational effort to avoid unrealistic designs.

Overall, combine business, user, and product dimensions to derive precise design goals. A complete design goal statement follows the pattern: “Through design strategy , help target users achieve X value / satisfy Y need / solve Z problem to support business goal / monetization method .”

3. Solution Derivation & Value Quantification

After setting clear design goals and strategies, move to implementation and validation using two basic models.

1. SKS Model: Strategy → Key Factor → Solution

Identify the strategy, determine key influencing factors, and generate multiple solution concepts based on those factors.

Example: To increase banner click‑through rate (strategy), key factors might include novelty, color, motion cues, benefit highlights, and call‑to‑action design, each leading to distinct design proposals.

2. GAM Model: Goal → Action → Metric

Design value is indirect; quantify it by tracing high‑value user actions that fulfill the design goal and measuring relevant metrics.

Reverse‑engineer high‑value behaviors from the design goal.

Use behavior metrics to assess design impact.

Break down high‑value actions and their metrics across multiple dimensions for more accurate evaluation.

4. Summary

Not every requirement warrants the full analytical process; prioritize high‑impact, high‑potential needs for deeper design research. Future articles will showcase concrete projects applying the business‑product‑user three‑view framework to derive redesign goals and design strategies.

Reference: “Five‑Step Derivation to Become an Experience Design Expert”, Google HEART model, “Understanding Design Value”, “Three Perspectives for Internet Product Managers”.