Grasping small amplification-product function requirement Priority management

As a product manager, you have a voluminous list of features, long sigh of relief, look, Ye's products are more powerful, planning so many cattle snapping function; As an interactive designer of you, dizzy finish the product prototype and process, secretly pleased road, see, my flow more meticulous, Combing out so many special situations and possibilities; As a visual designer, you design a lot of gorgeous interface, you for each page meticulously carved, expect users to see every page thumbs up said that the interface is really beautiful; as a developer, after you've built the frame, found that each module has a review of the missing details, a module of the progress of a module, resulting in your exhaustion.

In fact, in a product, not all functions are so important, if the product manager is simply delivering a list of features, rather than prioritizing the requirements, the product may become a product without a backbone, when the interaction designer is not sure what the main task is; visual designer design, Unsure which interfaces and modules to provide more sophisticated design; When developers develop, do not know which features to set higher development priorities, so it will form everyone in the state of stirring paste, may be due to some weak and weak branching process complexity, leading to the developers spent a lot of time to overcome the problem; Perhaps because of a less important setup interface, the UI adds a complex transition effect, causing the developer to get badly beaten up, perhaps because developers pick up simple features to do first, leading to complex important features to the last to be scratched, a bunch of bugs. Don't complain about the roles, think of their own needs analysis is in place, whether to your needs row rank, which to solve the business value of the product + user value has the greatest help, priority to achieve it, not important, not anxious, can be achieved by the second priority.

The product function is like the flower in the lens, if your lens, all is the flower, will because all is the bright spot to become no bright spot, if your lens, focuses on the most delicate and charming words, the bright spot is easy to emerge. But sometimes it is harder to say nothing than to do something. Must each revision, has some new function, can let the user know that we continue to improve, can let the boss know our team is full of fighting power. For these features (or from the customer, or from the boss, or from their own whim), if you have been repeated research, the conclusion is not very meaningful, you do not even dare to report, or to bite the bullet on the new features. It was not until the underlying architecture of the program was a big problem that we had to stop and refactor the code.

"Arranges the means saying yes to the thing for you ' ve got. But that's not what it means in all. It means saying no to the hundred, other do ideas that there are. You are have to pick carefully. I ' m actually as boys of the things we haven ' t do as the things I have done. Innovation is saying ' no ' to 1,000 things.--steve Jobs

Yes, I have to say, jobs is a wise product manager, he has a unique vision, dare to choose, will be for a product secret research and development for several years, and finally thick thin hair. Domestic environment is not the same, the success or failure, fast changing, not a boss willing to let the team research and development so long, the next big bet on a product. They want to see the results immediately, forcing the team did not even have too much time to in-depth research, can only find some of the models have been proved available, Copy to, although some metamorphosis, but more is helpless.

Even so, product managers can still articulate what the core modules and core functions of the product are. Like such a pyramid, the spire is the most important demand, without these, there is no product value.

and an interaction designer, you need to understand the main requirements, the corresponding decomposition to the main task flow, you need to spend 80% of the effort to design the 20% of the important task flow, and this 20% of the important task process is enough to solve 80% of the user's core needs.

There are two tricks you can do to keep your hands off the--1. Catch big put small, want to elaborate the main task quickly completes minor task; 2. From coarse to fine, don't come up and fall into the details

Actually spent so much ink, just speak a simple truth, learn to do subtraction, learn to prioritize, learn to grasp the main contradiction. But this is a easier thing in itself, and it needs to be honed in practice.