"Quest for demand – quality before design" read Note two

7. find the right person

Identify the right people, customers and users. The customer determines the external attributes of the product and the user determines the success or failure of the product. Railway contradiction is that because the product does not meet the needs of current users, so they can not lead the potential customers to a better product, so they are not considered, so the product continues to be inferior. It suggests that products we never had before could actually create a user base. Consider the user should not only consider the beneficiaries of the product, but also include losers. List of possible user groups and repair user groups, divided into friendly, unfriendly and negligible three categories to simplify. When sampling, identify your goals, behavior and take effective methods.

8. Preparing the meeting for Everyone

The meeting decided on the improvement of the demand work. A suitable meeting should establish an interrupt mechanism, set time limits, oppose personal attacks and belittle, relieve stress, acknowledge end times and end on time, deal with related issues, and improve rules. Publish an agenda, do not intervene in the burst mode, deal with the relevant personnel, including the correct personnel and so on. The meeting should be as small as possible.

9. Minimize ambiguity throughout

In order to reveal the ambiguous sources due to negligence, different inspirations are used in the case of observation, recollection, interpretation and problem understanding. These inspirations are mainly vague votes, memory inspiration, "Mary once had a little lamb" inspiration and "Mary cheat businessman" inspiration and other different findings vague inspiration.

Chapter Three: Exploring Opportunities

10. Meetings that generate ideas

Brainstorm one: Increase the number of ideas. Don't criticize and blame, let the imagination fly, the more ideas, the better, change and synthesize ideas;

Mind Explosion II: Reduce the idea to an actionable scale. Threshold voting, campaign speech voting, synthetic ideas, application criteria, scoring or ranking systems.

11. Right Brain method

The need to visualize the map that inspires our right brain. Specific types have sketches and graphs.

12. Name of the project

The naming of the project is very important, often resulting in a certain degree of ambiguity. An ambiguous, non-distinctive designation can cause misunderstanding and hinder the project.

13. Advancing the process in the face of conflict

Conflict is the driving force of a project, preventing insignificant conflicts, preserving valuable artistic or technical conflicts, and being a skill that leaders need.

Fourth article, clear expectations

14. function

There are functions, test functions, record all and only functions, record all potential functions, understand obvious, hidden and decorative features, identify unnoticed features, avoid hidden solutions, "If you can implement it" list. The function is determined by the process of finding the function.

15. Properties

The properties are identified like functions and are also recorded for continuous screening. The properties are then matched to the functionality.

16. Constraint conditions

A constraint is a mandatory condition that is placed above a type property. A constraint is a criterion of approval or objection to a system being built, dependent on attributes. Constraints also require brevity, correctness, and completeness, especially constrained boundaries, and need to be aware of excessive.

17. Preferences

Preference is a wish on an attached property, which is a selectable condition. From the user, quantifiable, binding and different from the constraints. Develop value maps and time-of-demand graphs after the preference is established. Constraints define acceptable areas in the solution space, and preference guidance searches in an acceptable region.

18. Expectations

Expectations and constraints are inseparable and expectations are more applicable with limitations. Designers need to be open to the user's expectations of the restrictions, often in fact, not reach the user's broad expectations.

Summary: This part of the reading summarizes the requirements of the engineering approach is basically the first to list and record all possible, and then discuss by article to determine its applicability, the deletion. Finally, the function, attributes, constraints, or preferences that are suitable for implementation are left behind.

Users often have a lot of expectations, and some even unrealistic, in demand engineering, with the user appropriate reasonable communication about the desired effect is also a very important skill.

"Quest for demand – quality before design" read Note two