Discussed demand collection, collation described, feedback implementation, use and acceptance embodiment, steps of the method and insights

Discussed demand collection, collation described, feedback implementation, the embodiments use and acceptance, the method steps

One. Discuss first product demand collection.

two. Outcome of the discussions with the sort described distributed technology.

three. And technical discussions, feedback and ultimately communicate.

four. Release new features, instructions for use and on-site training, gather customer feedback.

 

One. Discuss first product demand collection.

1. Author needs: the use of customers, the implementation of on-site personnel, experienced qualified older employees, industry experts, and so on.
2. Relevant personnel to discuss, analyze, summarize, and draw final demand plan.
3. The product was collected , "user" or "industry": the "pain points", "need to function," "Scene demand."
4. According to the user's scene, the scene of the actual business scenarios, the application needs to raise and collect.
5. Principle: do not use their brains product is a good product, go with the flow of the product is good.
6. Objective: To obtain a good product and function. Only discuss business functional needs, try not to take into account other factors and more problems.
7. Achieve the desired effect: the customer is willing to pay, willing to use, like to use, ready to use, loyal to products.
8. Feel good visual effects, the use of cool features.
9. Good products and people may be human and psychological factors.
10. Give full consideration to the feelings of aesthetic experience a sense of tactile and visual.
11. Taking into account the reality of industrial policy (official documents, laws and regulations) trends and future (industry, demand) is.

two. Outcome of the discussions with the sort described distributed technology.

1. Discussions absorption and understand the results, and then sort and description.
2. Context; in what context raised this feature, for text, images, photographs, scene description, or industry pain point, clear to understand why.
3. Functional purpose; to solve what pain points, needs to address what, to what effect.
4. Functional Description; text, images, HTML , clearly describe the effect and experience the feeling function.
5. Summarize; summarize time and realize version of this function, or notes describe other ideas, opinions.
6. Sort demand function, function names, priority setting, to achieve time or node version, a priority instructions, notes, in tabular form.
7. Method Description: picture, renderings, the HTML , flow charts, text, CAD .

three. And technical discussions, feedback and ultimately communicate.

1. Forwarding requirements document.
2. On a clear demand for the product, file format, spoken explanation.
3. Listen to their understanding.
4. The difficulty of collecting technology, time, cost, and ultimately points.

four. Release new features, using the operation manual, operation video, on-site training, gather customer feedback.

1. Implementers (proposed staffing requirements) for testing and acceptance.
2. Production Manual; simple, clear images and text, not complicated, to Jane, fine. Configuration flowchart.
3. Operation video; overall business processes demo recording, to explain the main points of the function of recording time 3-5 minutes one can see he wants to put a address, and then record a different role operations, tied together with the operating manual use set.
4. Collect feedback; product of experience, usage, frequency of use, functional assessment, new requirements and ideas.
5. Leave feedback channels; phone, micro-channel, micro-channel group, QQ , QQ rapid processing group, the public number, to facilitate the issue of feedback, problem solved.
6. Enhance communication; conducive to gather business information, product information, using the experience, strengthen communication and in-depth cooperation with the secondary.