As a product manager, your pace in the entrepreneurial team is always ahead of the team. Clear and complete requirements, clear and rigorous business processes, a good user experience, elegant and beautiful visual effects are the issues you need to consider. Because time waits for no person, the market waits for a person, we are running forward of time, the most do not want to see is constantly change demand, modify business logic. Because, this will seriously drag the progress of research and development and product online rhythm.
Any detail, we have to strict demands on themselves, overtime is common, the key is often a person to work overtime, you will give up once a variety of leisure and entertainment, love like, alone to keep lonely, in PPT, prototype map, flow chart to find their own fun. I believe that any product manager (whether he is a start-up or not) has experienced such a process. The so-called one into the product deep like the sea, from the struggle to the dawn. 30 do not regret, 40 no regrets, since the choice is not regret, I believe that each of the selected Internet Product Manager students have not regretted it now.
As a product manager for a start-up team (also known as a small team), how do we build a solid foundation for the first phase of the product? As mentioned above, clear and complete requirements, clear and rigorous business processes. So how do we do that?
First, as a product manager, you have the sole decision-making power over the design of the product (small team or entrepreneurial team does not have the Product director), you need to be familiar with each function of the product, how to expand each function later, how each function planning must be meticulous, There is also a need to use convincing persuasion to reject unreasonable airborne requirements from the boss (so we need to be able to reject them) and identify and determine the product requirements as soon as possible.
Of course, product demand is not a single existence, any product requirements need to combine the product's business logic and processes. So another important thing is to define the business logic and process of the product while clarifying the functional requirements. At this point, maybe we need a process to say dry on the brain storming, product, research and development, operations together constantly comb, clear, optimize the process, because at this time more involved in the following user experience. This is also the time when the most time-consuming, as product managers, you may draw the prototype every day, painting process to late at night or even overnight, and then a review of all call back. This time, we need a strong heart, not discouraged, and then start again.
Is the so-called "lonely lights with the night, Chaoyang Shine on Passers-by" (this is probably said that, anyway, there is no moral integrity), this time is our products are the most lonely time (sometimes even a bit cold, haha), because you need to walk in the forefront. Moreover, we are always repeating the same work, perhaps you will be slightly boring, boring, and sometimes constantly changing the prototype, has let us lose a trace of inspiration, but there is no lack of fun. Products on the line, we also need to continue to focus on how to better optimize product details, the dead of night, at the desk buckle words, pay attention to opponents dynamic ...
Through this lonely road, to reach the bustling. The process is lonely, lonely, but the end user feedback results are gratifying, you will find that all the process is actually a kind of enjoyment.
Focus, professional to make a good product, the ultimate, Word-of-mouth to win the trust of users.