Why did the product fail?

I have been a software Planning Assistant for seven months. In the past two years, I have learned how to make mistakes, learn how to grow, and make mistakes again. Cycle.

 

1. I want to innovate and be different from others?

In the initial stage, the concept of innovation was not fully understood, and the design of functions was too tangled and must be "different ". Innovation can be divided into two types. The first type is disruptive innovation. Its mission is to subvert mature and recognized solutions in the market, however, such innovation may not be favored by the mainstream market, but may be ridiculed or even blocked. The second is "micro-innovation". Its mission is to make existing solutions in the market better and better understand users. These two innovations are built on the same basis, that is, the market demand. The purpose of innovation is not to be different, but to make the product easier to use.

Conclusion: innovation has never been in place and independent. When designing features, you should consider how to better solve the needs. When you find a better solution, innovation naturally emerges. Any innovation is a low probability of success, and a high probability of failure. If you cannot afford the failure, select the most popular and mature solution on the market and optimize it with your own products.

 

2 avenue to simplicity?

This seems to be the mantra of every product designer. Yes. "I must make the simplest product that looks like me. I tried my best to reduce functions and interfaces, and threw fewer functions into fewer interfaces. Finally, the user said to me, "How can this thing be used ". I was shocked at that time!

Summary: unless your function requires only one operation step. Otherwise, you can draw a complete operation flow to let the user know where to click first and then where to click. Here is an example of a Windows design. This process is required for a function: New> add data> Save to make it take effect. At the beginning, I put all the four operation steps on the same main interface. This function only has this interface. By default, I have created an empty data table for the user, after the user adds the data (if the user knows how to add the data), I will help the user automatically save the data. But the user does not understand my intention. After seeing the interface, he does not know where to click for the next step. Finally, we optimized the interface and process: after the first startup, we added a function column with a new button. When you click "new", another sub-interface will pop up. The interface provides good process guidance, similar to the mail interface. Finally, the user clicks the Save button to end the operation flow.

To make the product simple, you can delete the function as appropriate. However, you must ensure that the remaining features can meet your needs. Instead of deleting functions for a simple interface. We must make it clear that the product is simple not because it has few features, but because it is very convenient for users to use and does not need to be considered too much.

 

3 can this design be implemented technically?

At the beginning of designing the features, I will be confident in my programming skills. The technical feasibility of a function point will be considered, which will make the design more "easy" to implement.

There is nothing to say. There is only one sentence: technically impossible. This is not a question you need to consider!

When designing a function, if I realized that a function would make technology a bottleneck for release on time, I had two solutions at work: 1) during the design of the function, the programmer is pulled over, and the implementation cost is consulted on the spot; 2) the function is fully designed and discussed with the programmer, so that the programmer can list the possible progress issues during the implementation process, then, optimize the design based on the questions raised by programmers. There is usually not only one way to make products better.

 

4. They don't have time to implement my functions.

Generally, programmers do not have only one project at hand. How to Win resources for your project is a problem that must be faced in project management. I started from the following aspects at work:

I. coordinate time with managers of other projects to at least let the other party know that you also have functions that need to be implemented by these awesome programmers.

2. deadline must be set for each function point to detail the Function Points of the module.

3. Set the time node, check the completion status at each time node, and adjust the function priority based on the completion status.

 

You can make mistakes, but you must be able to learn and grow in the Process of mistakes. It is only true to apply the theory to practice.