The design process specification of the new product must know

most Product Manager There is a very serious problem, from the beginning of the product concept phase, the start of the product page prototype, ignoring the middle too much about the product architecture, functional module design, product rules Define these very important work. The result is that the page prototype logic does not self-consistent, or ignores too many product key details. So that research and development to get the prototype will not go on, have to repair and rework later, the production of product managers and research and development contradictions.

Of course, our Product Manager team also has this problem, so we are going to train our product managers within the company. The following is a complete product design process specification:

1. Product Concept

． Objective: To collect requirements, organize product ideas, and gradually form and improve the product concept, to achieve through simple dictation let others understand the product Essentials

． output: Handwritten or whiteboard-written drafts and ideas that define the user experience map (Custom Journey Map)

2. Product Architecture Design

． Objective: To design a product's macro framework ( ignore details ) To view products from a global perspective, with a consistent and complete skeleton structure

． output: Product structure diagram ( I'm used to mind mapping, and I can use any flowchart tool )

3. function Module definition

． Goal: Define what core functional modules the product has, the role of each module, and the relationship between the modules

． output: Functional module Diagram ( I'm used to mind mapping, or I can use any flowchart tool )

4. Data structure Design

． Goal: Design the underlying data structure of each function module, similar to the database design, but more abstract, can enumerate only the key fields, ignoring irrelevant details

． output: The Core data dictionary (Excel table )

5. Logical rule Definitions

． Goal: Define the logical rules, branching conditions, and input and output of core functions, similar to the pseudo code of programming languages

． output: A list of logical rules for a bar-by-column (Excel table )

6. page prototype design

． Goal: Design the wireframe of the core page, the key elements of the page, and the layout

． Output: Keynote/axure/sketch prototype Diagram

7. Interactive Design

． Goal: Define the interaction flow between the core pages, jump relationships, and focus on the user experience

． Output: Keynote/flinto

Product managers usually do not do the first step of the "product idea" stage, then skip the second to the fifth step, go straight to the sixth step "page prototyping", and finally may not even "interactive design" is over.

A good product manager may have put a couple of steps together, but that doesn't mean a rookie can do the same. Training a qualified Product manager first of all, follow the prescribed action to give me step-by-step, first learn to walk, and then think how to run up.

Source: Jane Book

The design process specification of the new product must know