1. 当前研发问题产生的根源在哪里？
在体系建设初期，问题的根源在研发流程的各阶段/节点的控制，在于每个环节谨遵实施与控制的能力。比如：
1) 控制什么：不同阶段、不同产品的控制要素。
2）如何控制：控制方法（如设计、评审、仿真、测试），手段（如项目管理等）
3) 谁来控制：团队与角色分工
4) 如何才有能力控制：专业团队建设，人员专业发展规划，知识维度/逻辑维/时间维能力的提升。
5) 借助什么工具控制：IT管理系统、设计软件等
6) 如何运用积累：总结、复盘、CBB构建与应用。
7) 员工成长与绩效管理：工作数量、质量、难度、态度、职级通道等。
上面陈老师的这段经验总结：其实已经非常系统的告诉了我们，研发管理体系建设的行动策略，至于每一个模块的详细实现路径，对于真正有一定研发管理实践经验的人来说，应该不太难吧？当然，研发管理是个复杂系统工程，有些企业推行IPD觉得很难落地，就是因为流程中规定的每个动作没有能力做好，而要求做的动作却越来越多，就形成了两层皮。其实，对大多数制造型企业，初期都是要做好研发项目管理，否则基础不牢，地动山摇！
2. 产品管理主流程框架
1) IPD是一套完整的研发业务管理体系，主要包含：研发战略、研发流程、研发组织、研发绩效、研发IT等。研发战略关注做正确的事，研发流程关注正确地做事，研发IT支撑高效地做事。
2) IPD源自实践，是一套完整的理论体系，能指导与规范我们的研发管理，有利于我们更加系统地去开展研发工作。
3) 但是IPD给出的产品主流程框架过于复杂，大多数企业的一般员工都难以理解和掌握。怎么办呢？如陈老师书中所说：“我们需要基于自身的能力，遵循“二八原则”，构建轻量级的产品管理主流程框架，先解决当下核心业务痛点。然后在此体系推进的基础上，根据实际需要不断迭代完善”。其实也是在提醒大家，不要为了学某为而去学某为，赶潮流容易花了眼睛，一定要想清楚搞明白：你要知道学什么？解决你当前阶段什么问题？不要急于求成，要脚踏实地，也要仰望星空！（活学活用，理解精髓、基于逻辑，不僵化执行）
翻译：
What are the root causes of R&D problems and product management main process framework design?
1. What are the root causes of current R&D problems?
In the early stage of system construction, the root of the problem lies in the control of each stage/node of the research and development process, which lies in the ability of each link to comply with the implementation and control. For example:
1) What to control: control elements of different stages and different products.
2) How to control: control methods (such as design, review, simulation, testing), means (such as project management)
3) Who controls: Teams and roles
4) How to have the ability to control: professional team building, personnel professional development planning, knowledge dimension/logic dimension/time dimension ability improvement.
5) What tools to control: IT management system, design software, etc.
6) How to use accumulation: summary, duplicate, CBB construction and application.
7) Employee growth and performance management: work quantity, quality, difficulty, attitude, rank channel, etc.
In fact, it has told us very systematically the action strategy for the construction of R & D management system. As for the detailed realization path of each module, it should not be too difficult for those who really have some practical experience in R & D management. Of course, research and development management is a complex system engineering, and some companies find it difficult to implement IPD, because each action specified in the process does not have the ability to do well, and more and more actions are required, forming two layers of skin. In fact, for most manufacturing enterprises, the initial stage is to do a good job of R & D project management, otherwise the foundation is not solid, the earth is shaking!
2. Product management main process framework
1) IPD is a complete R & D business management system, mainly including: R & D strategy, R & D process, R & D organization, R & D performance, R & D IT, etc. R&d strategy focuses on doing the right thing, R&D process focuses on doing the right thing, and R&D IT supports doing the right thing efficiently.
2) IPD originates from practice and is a complete theoretical system, which can guide and standardize our R&D management and help us to carry out R&D work more systematically.
3) However, the product main process framework given by IPD is too complicated, and it is difficult for ordinary employees of most enterprises to understand and master. What to do? As Mr. Chen said in his book: “We need to build a lightweight product management main process framework based on our own capabilities and follow the” 28 principle “to first solve the current core business pain points.” Then on the basis of the promotion of this system, it is constantly iterated and improved according to actual needs.”
In fact, it is also to remind everyone, do not learn to learn to do something, catch the trend is easy to spend your eyes, must think clearly to understand: you want to know what to learn? What problems are you solving at your current stage? Don’t rush, keep your feet on the ground, and look up at the stars! (active learning and application, understanding the essence, based on logic, not rigid implementation)
