Writing PPT report is an output process, which can be understood as writing a brief article for us. You should present your understanding of the scheme to customers with PPT. So before you do it, it is recommended to frame your thoughts in your mind and build them on paper. Personally, I recommend using mind mapping, which is convenient, quick and easy to concentrate.
Reporting PPT basically consists of the following four parts.
The construction background is mainly composed of policy background, necessity, feasibility and construction objectives. Basically, through the chapter of construction background, it is necessary to present the degree of policy support, construction needs, expected goals and feasibility guidelines to customers.
1. 1, policy background
The policy background depends on the industry where the project is located, but no matter what industry, we must first understand the current hot policies, such as the 19th National Congress of the Communist Party of China, institutional reform, and the latest policies promulgated by the industry to which the project belongs. Secondly, it is necessary to follow the technical guidelines promulgated by the state and the two policy documents of the 13th Five-Year Plan, especially the 13th Five-Year Plan. Basically, each industry has its own 13th Five-Year Plan, and key policies can be extracted according to the 13th Five-Year Plan of the industry where the project is located. Finally, there are some key policy requirements in this regard at the ministerial level (industry ministerial level, such as the education industry belongs to the Ministry of Education) and at the provincial level.
Suggestion on the blackboard: The policy background is suggested to be described in two pages. The home page shows hot policies and the 13 th Five-Year Plan side by side, highlighting key points. The second page lists the policy titles by country, ministry and province in the way of time axis, and extracts a paragraph of policy requirements related to the project within 20 words below the title.
1.2, necessity
Usually, after writing the policy, many people will write the project demand analysis, but simply writing the demand analysis is not prominent enough. I suggest writing it. What's the need? It is necessary to clearly explain the reasons for doing this project, including the current situation of customers, original needs, pain points and ideas for solving needs. Because it is an information project, it is suggested to divide the necessity into data and business.
Data is mainly concentrated in scattered data, so it is difficult to tap the value of data, which leads to slow business progress. Key points such as data-driven business, big data transformation, data sharing and exchange are derived through the problem.
The business mainly focuses on the pain points of customers' business, such as complex business processes, scattered and outdated system construction, and difficult information asset management. Through the above problems, some ideas such as strengthening top-level design, urgent demand points and business optimization are obtained. If the project involves the customer's business process, it is not recommended to tell the customer the business process, especially the government industry process. Customers are certainly more familiar than you, but the focus can be on how to optimize the current business process to improve business efficiency and management methods.
Suggestion on blackboard writing: divide the scene, if it is introduced to non-technical leaders, choose a key blackboard writing page, mainly highlighting directional problems and overall solution ideas; If it is for the technical person in charge, the data and business can be bid separately according to the degree of investigation or understanding, but remember to give a solution to the pain point of the problem and introduce the post-construction content according to the idea, which should be related before and after.
1.3, feasibility
This chapter can be understood as the summary of the last two chapters and the guidance of the next chapter, which plays a connecting role, mainly through three aspects: policy feasibility, technical feasibility and commercial feasibility.
Policy feasibility is mainly a summary of previous policies and a review of policy environment support;
Technical feasibility mainly explains the current technical development trend and the development speed of industry informatization, and at the same time can lead to the key technologies needed by this project;
Business feasibility corresponds to the effect brought by the solution of business requirements in the previous necessity. Here, a small case can be involved to illustrate what gains have been made by completing the same requirements in the same industry in other places;
Suggestion on blackboard writing: the basic page can be summarized, the key point is explanation, and the thinking needs to be coherent, which will pave the way for the next chapter;
1.4, construction target
Mainly divided into overall objectives, data, business, services, management and other aspects. It is suggested that these aspects should be optimized through the construction of the project. After all, we can't deny the owner's previous information construction.
The overall goal is to start with the overall planning, realize the overall planning of informatization through project construction, form an informatization ecological circle and improve the pattern of informatization construction;
The goal of data optimization is to improve the efficiency and value of data usage, including data service, data application, data enjoyment and data life cycle management.
Optimize business objectives, improve business operation efficiency and save business management costs;
Service optimization objectives, government industries write more about promoting people's livelihood, and non-government industries write service systems.
Optimize management objectives, improve information management capabilities, and promote scientific decision-making and efficient management.
Suggestion on blackboard writing: according to the project situation, how many items are planned and build a three-page blackboard writing;
The construction content is flexible and can be adjusted according to the project situation. However, it is necessary to explain three aspects: standard specification, system development and typical application scenarios, because the standard specification of informatization project is the guiding document after the policy document, and the system development is a specific functional module, which corresponds to the problems that must be solved. The typical application scenario is to show the realization effect of key demand points.
2. 1, standard specification
This paper mainly emphasizes the standards and specifications that need to be formulated in this information project, such as safety standards, technical standards, data standards, service standards and so on. Instead of explaining the content of standard compilation, it emphasizes the construction ideas and importance of standards and norms, especially the safety standards of information projects.
Suggestions on the blackboard: you can draw the idea of building standards and norms and the list of standards that need to be built in a graphical way, and one page is enough;
2.2, system development
This chapter depends on the project, but we should pay attention to three points: first, the core functions should be explained in place to match the needs; Second, the functional advantage is relative to customers, and the advantage is that you can solve their problems; Third, the correlation between systems or functions should be clearly explained;
Suggestions on the blackboard: according to the actual situation, pay attention to the combination of pictures and texts, and finally make a summary;
2.3. Typical application cases
It is not an exaggeration to position this chapter as a story-telling chapter, which needs careful logical thinking and good eloquence to assist, and needs to distinguish and explain boring functions and explain the clarity of the case. Mainly according to the three-stage routine of analyzing pain points (demand background), analyzing ideas (solutions) and showing effects (expected effects), the key pain points of the project are brought into the story.
Suggestion on the blackboard: The background must be the real pain point background of the customer, with thorough explanation, accurate analysis of the cause of the problem, clear solution ideas and direct expected effect. The background and problems can be explained in one page, and the solutions and expected effects can be explained in one page. After the solution, it would be better if there were people around to cooperate with the demonstration.
Some people will say that the content of the problem structure has been finished, so why talk about the overall design? First, any project pays attention to integrity, and the construction content focuses on solving customers' problems, without overall planning of the project. For customers, the most concerned is the overall consideration. Secondly, the straightforward explanation of the problem can solve the urgent needs of customers and easily attract customers quickly, while the direct explanation of the overall design and overall planning will make customers feel empty and difficult to listen to. Finally, with so much preparation, the overall planning is clearly explained, the overall thinking is coherent, and the entire project planning presented in the customer's mind is perfect.
3. 1, technical roadmap
It can be understood as summarizing the technologies used in the previous chapters, but the key points need to be connected in series according to the technologies involved in the project and the relevant logic of the system. It can also be illustrated by the technical architecture diagram of the company's products.
Suggestion on the blackboard: PPT is a technology that is not recommended for large-scale explanation. You can draw a picture on a page of PPT, describe the logical relationship clearly, and adjust the way of explanation according to the person who listens to the report. The key is that each technology needs to correspond to the application scenarios and function points described above;
3.2, the overall architecture design
The overall architecture design focuses on the overall planning, business (application) architecture and data architecture. You don't have to explain all three pictures, but you must have them.
Overall architecture diagram: the hierarchical framework of the project. This chart is basically the tonality of an information project, which can be adjusted according to the technical level of the reporting object, with the focus on explaining the core functions and business scenarios clearly;
Service (application) architecture diagram: generally drawn together, mainly highlighting the parts that can be optimized by services or applications, the series relationship between services, the flow direction of data, etc. If it is a big project, it is recommended to draw it separately.
Data architecture diagram: according to the needs of the project, it can be expressed in two aspects. From the technical point of view, we can get the dependence of data architecture on storage, application and enjoyment. From the business point of view, draw a picture according to the way of data flow such as data production, processing, storage, supervision, application and mining. But it is not recommended that two pictures exist at the same time, because there are still many similarities in expression just because of different ideas.
Suggestions on the blackboard: an overall architecture diagram, a business (application) diagram and a data architecture diagram. The idea of explanation must be clearly explained according to the steps of overall introduction. It can be understood that the overall architecture is the portrait and skeleton of the project, the business application is the organ of the project, and the data architecture is the blood vessel and meridian of the project.
3.3, key technologies
It can be understood as the core driving force of this project or product. Among the technologies used in the above-mentioned function points, the most core and novel technologies need not be more than 3-4, such as the architecture at the bottom of the platform, big data used in data processing and some excellent technologies developed by the company itself in business (please take a tall name).
Suggestion on blackboard writing: typesetting should be carried out on demand, only graphics and text can be combined, and keywords can't be used to change words. The effect of the explanation is that customers can remember some key words of the technology you are talking about.
3.4, integrated architecture
From the customer's point of view, the overall project planning must consider the application of the customer's superior department, the integration of the historical system and the third-party system, which can be described simply, but can not be lacking.
Blackboard suggestion: every company's integration scheme is different, but please try to consider this problem from the customer's point of view. A few simple wireframes can actually express clearly.
The last chapter is divided into several scenes. If it is a preliminary contact project, it can be explained by individual cases. Every company has different methods and routines to explain cases, and there are many online, so I won't go into details.
If the project goes further, it is necessary to make a summary report to the leader and explain the implementation plan. The project implementation plan is divided into organizational structure, implementation method and work plan.
4. 1, organizational structure
The organizational structure of the project is also very important in the summary and report, which can highlight the importance that manufacturers attach to the project, mainly to let customers see how many people are working.
Suggestion on the blackboard: use a table or an architecture diagram on one page and focus on the customer-related part of the project. The customer must be a supervisor.
4.2, the implementation method
Not the implementation plan, but the implementation process, ideas, preparations, etc. And it is introduced according to the company's situation. If it is a big project, it is suggested to take a separate page to explain the implementation process of the plan.
Suggestion on the blackboard: it is best to introduce it with a flowchart.
4.3, work plan
According to the requirements of the site, the work plan can be arranged according to the project stage and time, and expressed in tables.
The above is more suitable for the 20-25 page presentation PPT frame structure. If there are any defects or deficiencies, please put forward your opinions in the comment area, and it will be revised reasonably after discussion.
? Text/grassroots pre-sales Wang Xiaomou