82 Principles in the Software (iii)

82 Principles in the Software (iii)

4. Statements on housekeeper and translation

4.1. housekeeper

Our line in the Invoicing field is a good company, its housekeeper series in small businesses are very popular, I and its founder in an upstairs office. So, I know the ins and outs of housekeeper, and they have been successful so far. Then, when flipping through its flyer, it will find that it clearly puts forward 80/20 of the idea. Probably means to tell the customer: there is such a law, our products are able to meet the 80% customer "longitude function" needs. The external voice is: Your 20% of alternative features require first put, I do not give you this expectation and commitment, when the expectations are not, in the hope that the ultimate customer satisfaction will be higher. Or, also "justified" not to provide customers with customized development.

That's what the housekeeper said, but what's the reality? Does the housekeeper rely on this for success? I don't think so, look at it:

The first is the price. A set of small and medium-sized invoicing software, is sold in the form of boxes, and at hundreds of thousands of prices in the sale. In this pattern, the customer will naturally not ask you to give me a custom development of a feature requirements. This is different from ERP, LIMS, his and so on tens of thousands of hundreds of thousands of or even tens of millions of software. At this point, the customer can abandon his 20% alternative needs are met because the price is low. Not because he realized and understood the 82 principles.

Next is the competition situation. At the beginning of the distribution of the software, the nature of each home is less than 20%, but also hope to meet the requirements of 80%. Then began the warlords melee, at this time one of the 20%, he was out. Because, it's 20% more than the other 20% shrink. When the customer finds that there are more better choices, they will abandon you. This 20% is no more than 20%. Its scope is more and more wide, the standard is a certain period of time the industry is generally able to provide functional boundaries. I call it the "threshold." You said 20% only at least to reach this threshold is meaningful, otherwise, the theory of unilateral emphasis on the 82 principle is like a nerd on the battlefield, will die. The same situation in the OA is the same, look at the OA 10 years ago is what kind of, and then look at what OA is like, look at those standard features. Has the customer's basic functional requirements changed substantially during this period? No, it's still those.  Just at the beginning, people are not deep in these needs, or have not had time to achieve good. Back to the housekeeper example, the housekeeper has been through nearly 8 years, in the field of invoicing, in a large number of customer applications and feedback on the basis of continuous improvement and improve their products. At this point they emphasize 20%, is already not simple "20%".

Therefore, to correctly interpret their propaganda slogan, not "I only provide 20%, and then can sell 80%", but:

1) Through this statement, on the one hand stressed that they have grasped the focus (to promote their own ideas), on the other hand to dispel the customer's bizarre ideas (satisfaction = received/expected).

2) Its 20% has actually exceeded the 80% functions that many people have encountered in many fields. It's a word game, a language trap.

3) Its function is from less to more, in the latitude and longitude of two aspects are constantly developing and perfecting. But in this development process, its guiding ideology is to grasp the principal contradiction, first meet the most able to embody the 82 principles, and then further further forward. The gradual product is plump. They are not, I just stay there when the aspect of the static emphasis on the 82 principle.

4.2. The statement of translation

In the "Just Good is really good", there are telephone, video, books and other examples, especially including Google's SketchUp software and an example of AutoCAD. They can sell 80% because they are only 20%. I think not, but because of the "convenience, flexibility, low price." This is often different from the customer base of the same products that emphasize functional chatty, or the type of demand that satisfies the same customer group. So they have a market.

Among them, Google's SketchUp software and AutoCAD examples. Does Google's SketchUp really take the place of AutoCAD's position as a king in real work? The price difference is $50 and $4000, even if that's not true. An engineer you said I would Google SketchUp but not AutoCAD, you go to find a job to try. So far, or after a constant period of time, in the field of AutoCAD King status is irreplaceable, Google SketchUp still shake it. But Google's SketchUp will also have its market, because its focus is different and the emphasis is on lightweight. What will happen in the future. Or, Google's SketchUp maintains its own customer base in its lightweight space, both at the high end and the low end. Or, if Google's SketchUp wants to shake AutoCAD, it has to implement AutoCAD's fancy features and make it better and more powerful. At this point, Google emphasizes that 20% features make sense. There is no point. Make another assumption, if the other one has introduced such lightweight applications. The features are comparable to Google's, and the customer experience is better and the price is similar or lower. Then, will force Google on this product forward and improve. At the end of the day, people will gradually approach the "truth value" of this field (which is also changing over time). We will not only spell the function of longitude, but also to spell the function of the dimension, the customer experience. These all determine their own quality, this is their hands of cards, and then cooperate with the price, market operation and other cards of the strategy and game. In the end, the winner is the loser. Win, how to say how reasonable, can casually propaganda casually said. But at that time it was often not the truth, but propaganda and show.

The same applies to the Internet of Things (IoT), which is now starting.

These are some ideas.

So how does the 82 principle in the software work? How should we use it rationally?

adjourned