How to push the team's executive power

Some time ago, I took part in a podcast recording session, which talked about how the team's executive power should be how to push , think about it and share it with everyone, and hopefully it will help you . :

1, Product Manager affirmation of the work principles: strategic decision-making products, product-driven development;

2, according to the actual situation, design executable workflow, clear the function of the work of the output (prototype/interface design, requirements document/mind map or flowchart);
P-Line: Product management, product design, interface design, interactive design, and other
T-line: project management, technical framework, technical leader, Developer (front-end, page, backend, server, data, operation, etc.)

3, the most likely clear measurable results of the work of the Standard, by the P line manager to provide the outline of needs, indicating what to do, do not do what, T line Manager in accordance with the needs of the relevant personnel to set work goals and standards;
Virtual Example: A functional module, V2 version optimization, 2 weeks for an iterative cycle, a total of 2 cycles
The requirements are: functional process and V1 version compared to the point of no increase, the focus is to practice the development model of the front and back end of the function module to reconstruct the implementation code, pay to the user more stunning effect of the operation process, strengthen each operation of the guide or hint experience
The key to the first cycle is clear demand, full communication between functional roles
The 1th week target is: the P line member completes the product detail demand plan, the T line member related Technical framework's preliminary research
The 2nd week goal is: The demand plan completes delivers, two key display page's technical functional development completes
The key to the second cycle is to ensure quality and achieve the desired goals within the schedule.
Week 1th Goal: All technical functional development complete, key business processes can be done correctly
The 2nd week goal is: All requirements planning details of the development and completion, the focus is the use of design, interface design lossless implementation
This product development team a total of 4 people: the responsibility Product Manager 1 people, technical backbone and project Manager 1 people, related technical development personnel 2 people; Peripheral support resources: interface design, interactive design, page production, about 6 people/day

4, seize every opportunity point, in the team to inform and explain the work principles and process standards of importance, pay special attention to the boss of the notice;

5, for the implementation of the various functions in the process of coordination issues, maintain a high degree of sensitivity, the most timely manner to deal with such problems;

6, the communication skills of different functional roles, the product manager itself needs to have considerable flexibility in thinking to adapt to different role thinking mode, boss, technical leader, members, interface design, user experience, front-end development, customer, etc.
in the communication with the P line role, To properly explain the technology to achieve the relevant principles, can do why, can't do more why, and on the premise of satisfying the essence of demand, put forward compromise or more reasonable solution;
when communicating with T-line roles, as much as possible to illustrate the source of the functional requirements, user feedback times and attitudes, analysis of its rationality, Use concrete cases and simulation cases to make the performance reasonable;
Virtual instance: Project Management = Project member management and authorization function = "Product requirements can increase Department for project members
     Existing functional processes: access to project member management, select Department dropdown box = Staff Drop-down box, point to join the members of the
    product thinking: After the selected department, you can directly add the department to the project members, so that the project manager to reduce the operation, when the Department of employees do not need to cancel the membership of the project member
     Technology Ideas: The demand technology is feasible, need to involve the function point, the project member management interface can increase the department, the Department binding authority role is authorized, 3 other functional modules similar to the selection of personnel to do the same processing, about 2-4 people/day workload.
    My analysis: To understand the needs of the idea, the department's starting point is to reduce the number of project manager operations, this can be identified, but a project manager in this project selected departments as members, if the department has increased staff and is not exactly involved in the project, Is it not necessary to return to the members of this project to remove this department, plus the original staff; second, although the vulnerability is very small, the user's actual operation of the probability is very low, but since we provide this function, there will be users to the problem, Wouldn't that be a violation of what we did? The purpose of this modification is to improve user operation and obtain user recognition. Notice that for the user, we should do better, most users may not perceive that the perceived user may not be able to spread; but if we do a product that will cause a problem, most of the problem does not appear in the silent state, the problem will certainly be transmitted feedback (complain about complaints ... ), affecting the group of users who did not have this problem.
    Conclusion: The principle of demand decision: the product link to the problem-free solution to determine or prioritize the choice, you can pay attention to the number of user risk, but if there is a problem, it can not be judged by the user's concern probability, Even if only 1 of the users are likely to have problems, it is fatal. TheRequirements should seek other solutions.
    My scenario: After the project manager selects the department, the first item in the Drop-down box is "Join all employees in the department", the product is considered to meet the needs of the starting point, the technology is considered to be involved in the workload of about 0.5 people/day, to reach a consensus;

7, in a reasonable way to show the team's work in each phase of the results, a collection of demand feedback, two harvest companies and customer recognition to improve team morale;

In summary, the main idea is: Determine the principle, clear strategy, set standards, unity, continuous communication, cultivate skills, show results. This is mainly about setting standards and communication skills to share two examples, other links have the opportunity to talk about.