Blog

From Demand to Product: The Journey from Concept to Implementation

The core value of product development lies in transforming requirements into features or products that users can use, find easy to use, and enjoy using. This article will explore this process in detail and summarize experiences for reference.
1. Overview

The main role of a company is to convert requirements into products (a system composed of many functions, which in the physical domain is a carrier that meets specific needs). Years of cooperation experience have shown us that transforming requirements into products is actually a very complex and challenging task.

Generally, the process from requirements to products can be divided into the following stages: user research, market analysis, product planning, requirement collection, requirement analysis, code development and testing, trial operation, launch, and iterative upgrades.

In a typical product development process, companies often cannot handle all stages. Usually, the product team is only responsible for the key stages from product planning to code development and testing, solving the problem of what to do. Before this stage is planning and design, which focuses more on feasibility verification, and after this is the determination of system implementation, focusing more on resources, time, and schedule issues.

This stage determines the user experience of the product and how product features provide value to users. However, many companies overlook the essential value of this stage, lacking analysis of real needs and often focusing only on problem-solving while neglecting overall demand analysis from a system design perspective.

2. From Requirements to Features

Transforming requirements into features or products that users can use, find easy to use, and enjoy using is the core value of a company. To achieve this value, the company must not only act as a user’s mouthpiece but also deeply understand the real and underlying needs of the user, consider the rationality of the overall system architecture, and design from multiple dimensions such as business, application, data, and experience.

Requirement Transformation Process
User Research and Market Analysis
Product Planning and Requirement Collection
Requirement Analysis and System Design
Development and Testing
Launch and Iteration
Case Studies

Case 1
When reviewing product requirements for promotional activities, only the front-end mall page was considered without the corresponding activity configuration page. This led to the inability to control activity time, price, and inventory. Therefore, we need to clearly understand the logic and meaning behind each field and interaction.
Case 2
When designing the e-commerce product module, the SPU+SKU system was adopted, but the business logic of the supply chain was ignored, leading to confusion in product data usage. We need to consider all aspects of product management from a more comprehensive perspective.
Case 3
When designing the mobile end order placement function, the cumbersome operation process affected the user experience. Through research, we found that the search results arrangement on the product selection page and the operation method for individual products needed improvement.
Demand Analysis & System Design Methods:
  • Entity Models: defining primary objects for functional operations, their attributes, and lifecycle.
  • State Machines: analyzing state transitions.
  • Business Logic: detailing business logic to form structured descriptions.
Frontend Design & User Experience
  • Structure Layer: focusing on information architecture and interaction design.
  • Framework Layer: focusing on page layout and navigation structure.
  • Presentation Layer: focusing on visual communication, including color schemes, fonts, images, etc.
3. Conclusion

Transforming demand into a product is a multi-layered process from user research to market analysis, through product planning and requirement analysis to development testing, launch, and iterative upgrades. This requires comprehensive consideration of user needs, business logic, and system architecture ensuring the product not only solves real problems but also delivers quality user experiences.