Process of product design

Generally come to water, we will always pay attention to product development process and project management process, a reasonable process is the basis of team cooperation. As the saying goes, "flow is dead, man is alive." "The goal of all processes is to make the process smoother and to be flexible in the process.

Product Prophase analysis, design links, on-line summary feedback, basically includes, from the demand to the line through the process, compared to the large ued team will be "light" some, suitable for small and medium teams. If the company does not have a design process inside, you can refer to this process, you can also on the basis of their own improvements.

Click to read "Product design process"

Prophase analysis

Know the Product

Requirements & What to do: Understand the needs, know what to do, the new product to understand the background, positioning, concepts

Now how the product & market how: The current level of product business, user what the situation, market how

What I'm going to do: what I need to accomplish, what I'm responsible for, and how much I do.

Purpose & Benefits: The purpose & benefits of new products

* Future plans: Scalability considerations, you can reserve location at design time

Analysis Products

Data analysis: Comprehensive data (overall environment, user population base, male and female ratio, etc.), the existing product data indicators (methods: Google Analytics, find internal staff to fetch data)

Competition analysis: and domestic and foreign similar products to carry out comparative analysis, the enemy

* Other methods: can analyze and help design a lot of ways, you can choose according to the project

Find & Set Data indicators: according to their own project to set measurable data indicators, on the line after the validation (for example: estimated new features expected to reduce the loss of more than 20%)

Logical process: The production of logical & internal processes throughout the product

* User Path Map: Describes the user's path within the product

Design Links

Making prototypes

Low-fidelity prototype: Draw the product main flow, the smallest possible prototype (MVP), ignore the details of the prototype (tools: paper Prototypes, sketches, Axure)

Communication: The use of low Fidelity prototype and project related personnel to confirm Product direction Framework (invitation: Demand side, development team)

Improvement: According to the communication after the communication to improve, then confirm

High-fidelity prototype: On the basis of the lowest-fidelity refinement of the prototype (Tools: Axure)

Review: Product & Function and related personnel validation (invitation: Demand side, development team, UED) with a full demo of high-fidelity prototypes

Prototype Documentation: Explain interactive prototypes & details to facilitate development & interface design

Interface design

Mood board: Use the Emotion Board (Mood Board) method to develop the style color (emotional version Introduction)

Custom style: According to the designer's own judgment on the product style set

Visual Design Draft: Complete the design draft according to the High-fidelity prototype

Review: Final confirmation of visual design Draft (invitation: Demand side, development team, UED)

Page callout: The color of the key place of the page, the dimension of the element, the distance (tool: Markman)

* Interface Specification: Writing interface element usage Specification document

Summary Feedback

After online

Data Observation & Verification objective: To observe the product & Comparison data index after the line to see if it meets the design target.

On-Line Summary report: Brief introduction of early design ideas, products and sharing of data on the online comparison

Sharing: Product experience sharing within UED team (invitation: UED, interested person)

Identify problems, continuous improvement: continue to iterate according to the Data observation & new function after on-line

Notes

Plus * Indicates the steps that can be made according to the product function size

• Communication or review will not need to be more formal, agile fast, effective communication, solve the problem is the key

• Process is dead, if there is a special case, please specific questions specific analysis