Analysis- an Internet product born of Past and Present（分析-一个互联网产品的过去和现在）

Analysis- an Internet product born of Past and Present（分析-一个互联网产品的过去和现在） Analysis: an Internet product born of Past and Present (To free download News) a product from the very beginning the project to the final on the line to go through many stages, different companies are not the same product development process. I recently ‘broken cocoon into a butterfly,’ this book from the perspective of all aspects of the designer of the product development cycle to do a very detailed introduction, I read the book also learned a lot, and share with you my experience. From the user point of view The first is a product to solve a practical problem of users, followed make this problem easier to solve, and finally allows users to use the product in the process of deep impression, leave a good experience. So when we designed the product should be considered from the three aspects, namely, to solve the needs of users, for users to understand and reduce operating costs, allowing users to stay beautiful and deep impression. From a product perspective 1 Demand for the product can go from three aspects to consider user needs, business value and development costs. Where the user needs is essential, a product can only satisfy the needs of users, would have been willing to use, the product has to get business value. Companies received some commercial value, it will spend more energy and resources to improve the product, and continuously improve the product experience to better serve customers. At the same time no matter how wonderful a product of creativity, from technology developers need to go to achieve, in the development of resource constraints, the evaluation of the development costs can not be ignored. Before determining product requirements, first to give the product to make a clear position, which is the follow-up to the general direction of all the work. Product positioning can be divided into two parts, one is the product definition, the other is the user needs. Product definition includes use of the crowd, the main features, product features, user needs include the target user, usage scenarios, user goals. By direction from these 2 segments analysis, we will be able to come to a complete product positioning. The best way to define the product is summed up this product, let everyone know that this product is doing, what are the characteristics, and for whom use. For example, public comment is a through review of information to help users quickly find a good place to eat, drink applications. Product initial function can not be many and complex, single-point focus on a core function of breakthrough products that can help to quickly find a clear position, to avoid the product development process is too complicated, difficult to choose. In addition to well-defined products, the needs of users should have a deep grasp of user needs is simply what people in what circumstances solve any problems. Here must first identify their core users, do not expect anyone to make a satisfactory product, such a result can often be anyone dissatisfied. Core users are usually large number of people, and people of high commercial value. Requirements gathering many ways, including user research, user feedback, Competitive Analysis, product data. Faced with a large number of needs, how to 3 efficiently filter needs to become worthy of concern. A more efficient process: first filtered out patently unreasonable demands, then tap the true nature of the needs of the user by user demand phenomenon, combined with the positioning of the product according to the prioritization of certain product demand. - Priority needs to consider user value, business value and achieve cost. Writing documentation When it is determined after the demand for the product, in order to standardize project processes and to facilitate product development, usually you need to write product requirements documents. Requirements document is no uniform requirement, different companies, different requirements for documentation of the project may be different. Normally a requirements document has the following contents. Document modification and audit records. A request for documents may be amended several times, needs to be done in the revised summary record. Background description. Why do the product, product positioning, market conditions and the like. User types and features. A brief description of their target audience as well as features. Project schedule. 4 When to start and when to complete. Information structure. Page-level product structure, mind mapping class available software. Overall business process description. Business logic flow operations, help designers understand the specific business logic. Demand in detail. The main content of the requirements document, listing detailed description of each function. Product Requirements Document not as obvious, the above document, some content may also be placed MRD document, the specific implementation of the project should be determined according to the actual situation. In the requirements document information structure, the overall business process description, detailed description of demand is the core content must be clearly expressed, or when designers do the design will encounter many problems to be repeated to confirm. Draw prototype When demand is determined, the document written can begin to do prototyping. Finely divided according to the degree of prototype low-fidelity prototypes and high-fidelity prototypes. Different companies different from that required for the prototype, but generally recommended to start from the paper prototype, because 5 it is easy, you only need a pen and paper can quickly record and expression, regardless of the format and details. With a paper prototype products can quickly draw a sketch and then, and team members to discuss, easy to modify. Paper prototype can be seen as the final design of the prototype, focused framework, processes, basic features and content, and ignore the details of the design. After completing the paper prototype, you can draw finer wireframe under the existing framework to refine the product’s interface. At this stage requires a lot of detailed work, such as planning and reasonable layout, grid specification compliance, chiaroscuro expression, marking the first screen height, articulate UI logic, consider the effect of post-implementation, understand visual trends. This version of the wireframe is to be delivered to the visual designer for visual design, so in addition to improving product interface wireframe outside also need to make certain interactive instructions. Wireframe represents the static part and the dynamic interaction described represents part of what prompted such 6 operation instantly appear, how much text is displayed, click on a part of what is feedback. All in all, the interactive instructions make it clear that in addition to static pages, but also need to consider a variety of dynamic situations; in addition to normal circumstances, but also need to consider a variety of special and error conditions. Tracking iteration When the visual designers make visual draft, you can deliver technical personnel to develop, but that does not mean the work is finished, in the development process, but also the need for frequent and technical personnel to maintain communication, to avoid the final product and design Contributed larger deviation. After completion of product development, product manager for the same there are a lot of work to do, the front of the line to the product usability testing and A / B testing, the product line to keep after the data was collected user feedback and product testing. By collecting feedback information, the product of iterative improvement and constantly improve the user experience. Birth of a product to go through repeated grinding and optimization, product manager in the process also 7 need to follow the standard process from the abstract to the concrete, from the frame to detail to ensure a smooth development of the product. So, want to be a good product manager is not an easy task. (Source: everyone is a product manager for text / Fei compile: ) 8