Solutions, not functionality

Ask yourself, do you really know what you're selling to users? What you think is revolutionary, will certainly shock the world function, characteristic, the user really pays?

I mean, we always get used to forgetting the fact that we're not selling a product or service to a user; we're selling a solution that can fix the problem, he can create value for the user, and let him worry less about the problem.

A simple example: when you think you're selling a drill, the user actually wants to buy a hole.
It's about solution, not features

As a product designer, you should focus on what the product can solve for the user, rather than focusing on the specific features.

On a regular basis, when a feature is presented by your users or your colleagues, and the function sounds so exciting and your competitors haven't done it, you have to think calmly: what kind of solution are they?

Often you think a good feature, put in your product, may be a very bad solution.

Qqmail,gmail, NetEase mailbox, have a mail-top function, and the design methods are different, can be used as it's about Solution,not features this subject standard case demonstration.

The so-called mail is the top, is in the mailing list page, can let some users think important messages always appear at the end. Reduce user lookup time.

Qqmail automatically displays top three of user-flagged to-do messages

(currently this feature has been canceled, screenshots from the source)

Gmail by adding an intelligent judge of the important tag and priority inbox combination way, so that the user's message automatically set

NetEase mailbox directly added "marked as top" function

Think about it a little bit, why do users say they need mail? The reason I personally think this is that they want important emails to naturally appear in a conspicuous position, eliminating their search time. They don't really want email to be the top of this feature.

From this perspective, qqmail and Gmail through the original function of the combination, with the smallest price, complete the solution, and avoid the product complexity of the increase. and NetEase mailbox processing is too crude direct.

If I listen to the customer, I should give them a faster horse.

Henry Ford

Don't trust your users right away, users will habitually describe their expectations as a specific feature (Features), making you think that this function is desperately needed. And users are prone to whimsical, lack of logic, a little attention, you can be a few users of the requirements of the destruction of your products.

Users are also easily limited to reality, they tend to find simple linear contrast in reality, and refuse to think creatively. If the cell phone battery does not give force, users will want to mobile phone battery capacity is growing, but will not want to walk, cycling and other ways to keep mobile phone power.

But at any time, you should keep an instant listening to your users ' opinions, analyze them, ask them, and find out the real expectations behind them. And to meet him with discretion.

Apps Store has one of the most expensive apps I ' M Rich that can't do anything other than display a jewel on your iphone screen for $999. After eight boring people bought it, it was officially off the shelves of Apple.

To cite this example, I want to say is that your product can really create substantial for users, can directly see the value, not the whole what virtual, user psychology to face this can be shrewd. Otherwise, no matter how good a great product, it is possible to follow the footsteps of Google Wave.

The most effective way to create value is to save time. This is all the Internet, mobile phone products solutions, but also users use their root cause.

Because in general, in real life, they can find alternatives, but more slowly.

The ideal solution for users is to pay the cost and then walk out of the way and wait for you to create value. This and everyone expects that just by depositing the money in the bank he will be able to automatically add value quickly and infinitely.

The basic thing we have to do is to minimize useless interruptions, because it's the most lethal way to damage the value of your users.

This hint of mobile phone application is the biggest damage to user value

Finally, refer to the iOS hig sentence describing the product definition description, and describe how to filter out the list of features for your product by confirming the solution. While this is a guide for mobile products, I believe these ideas are interlinked for PC-side products.

Unreported you begin designing your creator, it's essential to define precisely, what, and your creator. A, way to does this are to craft a product definition statement-a concise persons of your creator ' s main purpose and its Tended audience. Creating a Product definition statement isn ' t merely an exercise. On the contrary, it's one of the best ways to turn a list of features into a coherent product.

Before you start designing your own applications, it is essential to define exactly what your application does. A good way to do this is to write a product definition statement--A concise description of your application's primary purpose and the target user's document. Creating a Product definition statement is not just an exercise, but instead it's the best way to turn a bunch of functional features into a coherent product.

(Source of reference)

Source: http://uedc.163.com/4141.html