Wednesday 8 December 2021

Make sure your plans are solid for Project

How do i make a project more manageable? here the author helps you develop a complete set of methodologies (tools) for a project scenario. 'not the only answer, but every specific point in it is a summary of the individual's nearly 50 successful or failed project planning experiences, hopefully to be useful, ' he said. enjoy~

This article comes from a part of the advanced version of the project management course developed by the company itself, about how to make a project more controllable, the purpose is to solve many project pm or operating products in the planning process always feel that there is no clear place to lead to follow-up implementation of many problems, but there is no appropriate method and tools to help themselves to think clearly this scenario.

In the course of the actual teaching found that this link is very interesting, but also asked more questions.

After class down on everyone's more comments and suggestions have been repeatedly revised and improved, and now formally for everyone to provide a personal thought can help you perfect the development of a project program a complete set of methodology (tools). 


Not the only answer, but each specific point in it is a summary of the individual's nearly 50 successful or failed project planning experiences, hoping to be useful.

For scenarios: common online projects, special events, interactive marketing, innovative business columns, etc.;

Programming standard process: propositional dismantling - programming - feasibility assessment - result simulation - ten questions and ten answers

1. Proposition disassembly

The first step in all project planning is to receive a task, receive a kpi, and then begin the program planning. but often many of the problems in the follow-up project execution are buried in this link, mostly from the understanding of the initial task (proposition) or the failure to reach a consensus. the propositional teardown session contains two-angle concepts to help you find out the direction of your project at the outset and to have a clear checkable tool to help you determine if the project is going in the right direction.

1.1 locking the quantitative indicators and guiding indicators ensures consistency of execution

Most of the project starts, we are all led to a or focused or fuzzy kpi, perhaps the transaction volume to reach sequencex million, perhaps to do an sequencex innovation project. many of the project planning was born from such a meeting "hello everyone this is our kpi, let's think about how to do it." but each project in the different role perspective and position is not the same, the understanding of the project background is not the same, often the understanding of the goal here there are differences, differences bring about implementation bias, implementation deviation brings rework adjustment delay or even everyone to run in the wrong direction together.

Believe that most of this phenomenon of project pm, product operation has a deep understanding and suffer from it. looking deep into the sources, an observation of all the project planning processes reveals that differences are often caused by differences in the ability of quantitative indicators and guidance to interpret under different roles. operations and business like to look at indicators, gmv to do how much, disassembled for traffic and conversion rate, respectively, how much to do, lack of traffic then i go to inventory resources. products (of course, most products are kpi) or research and development more oriented indicators, through the sequence strategy to achieve sequence purposes. this in itself is two kinds of dismantling and doing things, there is bound to be conflict.

Therefore, the effective solution is, when you get a project goal, please invite all project members to sit together, on the understanding of the project objectives or disassemble consensus, and this consensus is specifically presented is to come up with a set of closely related quantitative indicators and guidance indicators, one is indispensable, one by one corresponding, one indicator must have a strategy corresponding. quantitative indicators constrain the direction of everyone's contribution to the project is consistent, and the guiding indicators ensure that everyone is making efforts under a unified strategy. but often most project goals have only one.

1.2 clear propositions are a prerequisite for effective creativity

Many projects involve creative brainstorms, but often fall into disorder and confusion, putting aside all kinds of brainstorm rule methodology, in fact, most of the brain storms will be clear here has failed. to talk about this topic, we can first talk about all the creative course theories are avoided to explore: how do people produce ideas? (the following theory is purely personal creation, and if there is a conflict or conflict with a theory of a great god, i suggest you listen to me)

To answer this question, it is time to understand and endorse the concept that creating creative nature is the process of solving problems.

Therefore, generating creativity is nothing more than the process of clarifying the problem-information retrieval-combined answers. this process we have been through a lot of previous exams, information retrieval and combination of answers later said, first talk about the most problems occurred: clear questions.

A lot of brain explosion meetings start with 'let's think of a creative solution': 'let's do some innovative play at this year's sequence festival'. then a bunch of people sit together, put forward one idea after another, deny one proposal after another, play with mobile phones, dazed, run questions. recall a person experienced the scene, primary school teacher let you write, the most terrible topic is not specific and clear topic, but the teacher said today we go back to write a composition bar their own choice of topics. tangle began, write this good or bad, as if that is better, the draft changed over and over again, and finally can only sloppy things. but if the teacher is saying that today everyone will go back and write an 'my father'. vince like a spring began, eyes covered with blood, you stand here do not move the old man to buy you some orange or anything inspiration can not stop.

This is the interesting place of the human brain, the explosion of creativity must have a clear stimulus point and starting point, throughout any industry, the most exciting ideas never come from the premise of no proposition. often propositions are limited, resources are limited, and limited tools are more likely to inspire and motivate people (it is recommended to focus on thailand's low-cost cosplay little brother to see how a steady stream of ideas comes about).


The programming link is of course the most important and critical part of the output of a programme, the standard methodological wheels and steps are not repeated, here refining the programming of several effective tools and ideas to help you further improve the project programme's relevance and effectiveness.

The so-called debate out of the truth, pk out of the essence. project programming will have a lot of pk debate link, some people will feel that pk is a project program birth resistance, some people feel that is to tear to the head to break the blood flow of a project can be relied upon. are one-sided understanding, meaningless pk and divergence is indeed resistance and waste of time, a sumptive project discussion without a game will miss many items invisible problems.

Effective PK requires that each role in the discussion process need to clarify their correct position, to ensure that several aspects related to the success or failure of the project have a platform for people, we game to form a consensus to ensure that the project considers a comprehensive and balanced multi-party.

Common scenarios (not absolute): Operation as indicator to reach the platform, project manager for the project progress platform, product manager for the user experience platform, research and development for input output / risk platform.

Then the product manager's expectation consistency of the copy to the user in the project and the operation want to use some deceptive copy to improve the indicator achievement rate will form an effective game process. The project manager's requirements for on-line time and the position of research and development on risk control will form an effective game process.

And if several roles are considering metric achievement, then what comes out must be something that looks good but the user experience is bad (or does it this time without the next time). So each side needs to stand firm and clarify its role. The resulting scenario is likely to balance the user experience, progress toward goals, and so on. If your project planning is your own, learn to evaluate yourself from multiple angles and positions.

2.2 standard methodology for effective brain storms (not the only answer)

Programme brainstorm is always the most uncontrollable and feel the most difficult part of the programming process, in fact, the birth of ideas and ideas is not as much uncontrollable as everyone imagines or can not be sought. there are already a lot of methodologies to help people to have a creative birth and not just rely on the specific person is not a lot of ideas. after participating in and studying the industry's 3,4 professional creative methodologies, it is not the only answer but it is useful to summarize and refine a standard process of relative commonality:

(2) think about the situation

A way for the creative section to retrieve information, to think about some of the people or scenarios you've been through, and if so, what they're going to do about it. (for example, if the employees of jiangnan leather factory do this, they might write another oil poem - perhaps netease cloud music was inspired by this)

(3) sketch description, poor results

All creative methodologies will appear: sticky paper tools, and the point to understand here is why your idea is not written in one case but must be described on sticky paper. in addition to convenience, forcing you to write your ideas on a note sheet in the form of a painting or a simple description (usually you'll write with a marker pen so you can't really write much), in order to make your output ideas simpler, clearer and presentable, a note paper endless ideas must be difficult to interpret and present let alone let the user understand the idea, so that the logic behind the sign-off paper is here, in the process of brainstorm creative exhaustion results also force themselves and members, keep your ideas as simple and clear as possible.

(4) fusion scheme

Is literally meaning, nothing to say, we feel that the reliable program to come up with a mix of a string of things.

At this point, it looks like the solution is already in place, and then a project plan takes shape.

But often many project programs are not reliable source is precisely because out of the project program began to rush the implementation, and no more to demonstrate, because many students suffer from no tools and methods to do the demonstration link, there is no relative standard books or methodology to explore this part, individuals also rearranged and summarized the following four tools to everyone, can help from the business value, project continuity and project hidden risk three angles to completely demonstrate the feasibility and viability of a project:

Feasibility assessment

3.1 assessment of the technical aspects of the project implementation programme

The project technical level implementation program evaluation is a basic process, that is, research and development needs review. here are two simple points to help you improve your efficiency:

As mentioned in the previous ten recommendations, the business must have comprehensive knowledge and skills, first of all, the programming part of the project implementation to have a basic judgment, do not need to understand how to write code, but the basic principles to understand, in fact, very simple. understand what static data is, what is dynamic data, how a business model (such as price-cutting play) is translated into code (in fact, it is a calculation formula, how to ensure that the number of users per price node is controllable).

Research and development demand review business must be the leading party, thrown to the product and research and development evaluation is a very inefficient approach, business background considerations and priority assessment is an essential information in the research and development review, the last one talked about the effective pk also requires that can not find the highest input and output to achieve the program in the process of less artificial business indicators completed, progress and other platform roles. finally, the best balance of business value and technology input costs is achieved.

A strategic level assessment of the project implementation scenario


The project feasibility assessment seems to me to be more important and lead to many projects to advance difficult points are the project strategy assessment verification process, most projects start with a good idea, but to move forward to find resistance or difficult to advance, the reason is that a project feasibility assessment is not only technical to achieve, "human" level of achievability is often more important. 


The strategic level of advance assessment of the correction in place project implementation smoothly many people will help you move forward together. in the real business or the workplace is also good, not a good idea must have value, not a valuable idea should be done by you now, not necessarily a valuable idea that you should do can be done smoothly.

Give a gadget to check and verify that the project is smooth enough to be effective in subsequent execution after the first draft of the project scenario.

A project is valuable and should be done by you to be able to move forward smoothly with four factors that require a complete assessment:

(1) business value

Whether a good idea can be transformed into effective business value, whether something fun and interesting is exciting enough, can it bring a direct pull to the business. look at the entire marketing advertising industry is now more emphasis on effective marketing. projects that can turn interesting ideas into boring business numbers are truly valuable.

(2) the role of the project

Why often innovative projects or new areas of business to do swot analysis, not only to analyze whether this project can be done well, more is to analyze why you should do, behind the actual need to understand you and your team in the department play what role. 


The department in the group play what role. what is the overall strategy of the current larger system, and whether your team and your project play a valuable role in it. a sudden idea that has nothing to do with the original business and can't find a project that is customized is difficult to get support from the strategic potential of the group company department, that is, it is difficult to do it or get resource support.

(3) the sense of participation of partners

The ideal situation of a project all participating in the project team to this project as their own thing to fully invest, not just the needs of docking and processing, i believe you pm experienced too much kneeling design product development process. so evaluate your project to get more people to work together and think about what their value is to all partners (design and development, brand b, etc.) 


(a little sad to say that the value that many partners need is not the actual business value, but some value on the right, and you think about what can make them praised by their superiors, and give them what - thank you for the mail?). seemingly gorgeous new play? and to involve key partners as much as possible during the programming phase. remember the sense of participation and participation!

(4) your project is not a complete and valuable story

Project planning often means that there is a need for innovative breakthroughs and new growth, so think about whether the following projects fit into three situations: making new performance with the old model (consolidating resources to shock trading peaks), doing the old performance with the new model (bringing trading products through social channels), and making new performance with the new model.

If you find that your project is just doing old work in the old model, there are only two cases where you are being used as a piecework job (and try to plan your own small projects and small innovation breakthroughs in piecework) / your project really doesn't have to be done because it has no value.

Check that your project is now largely on track, but there are two gadgets that you want people to take a moment to do each time, helping you further improve project control (regardless of project success) and uncover more hidden threats.

Result simulation

First everyone changes the idea that i'm working on a project to make it→ i'm doing a project to make it work but i'm going to make it worthwhile, whether it's a success or not.

A lot of theories about project management and the workplace have mentioned the relevant concepts, common interpretation is to realize that things are continuous, most people's plans for the project only to the online step, at most to sum up even if it is finished. realizing the continuity of things requires that we think fully and adequately about the multiple directions of things to improve our true control over a matter.

Try writing the project summary outline in advance during the project scenario phase, and excel is fine.

Project try points, try strategies, policy success can draw conclusions and subsequent actions, strategy failure can draw conclusions and subsequent actions.

Forcing yourself to comb through the key points of your project from big to small in the format above can help you:

Determine whether this point is in the core orientation of the project, whether it is biased, whether there is value preset the project of various trends of the follow-up interpretation of value and strategy, from the easy to follow the line of the project to get the combination and value, rather than the project after the effect is not good before a hasty way to remedy.

Don't figure out your project, let others help you think it out

In addition to recommending the "don't make me think" book mentioned in the beggar version of the most simple research method as an auxiliary excavation problem, find a melon crowd, let him from the beginning in place with your products or look at your front-end program, encounter any questions do not answer do not answer do not answer, write down to optimize, and then find a mass use, in turn cycle. 


This approach is the most efficient way to verify user response and effectiveness in advance. of course, there are resources to do advance research better, pay attention to the research process to be deeply involved in their own not just simple demand to the research team otherwise the effect is not as good as beggars with research methods.

Ten questions and ten answers

Finally, after each project program is perfected, it is also grammed here to continue to improve the project, recommended an effective tool: ten questions and ten answers.

One of the most classic uses of amazon's innovation incubation system, requiring everyone who proposes an innovative solution to ask themselves more than fifteen questions after the proposal until no one can ask more questions.

Imagine yourself going to the leader / customer to preach the program, you are most afraid of what they asked the question, the project the most indefensible challenge point where (why users want to use, why sequence business does not come to copy), first ask themselves and try to answer, if not answer to explain that the project program still has room for optimization or presentation did not say the key points. return furnace re-engineering adjustment program, continue to ask questions. until you or your leading partner can't ask any other questions, you're really thinking about the project.

Record the questions and answers as an appendix to the project programme, which is the last link in the project programme.

No comments:

Post a Comment