How to make your own transcend landing?

This article starts in Http://oliveryang.net, please include the original text or the author's website link when reproduced.

The engineer's mission is to identify problems, define problems, and solve problems.

Depending on the complexity of the problem, there may be a lot of communication and discussion between the team or the team involved in the process.

Often, it's easy to judge an idea, but it's hard to put it into action, or ask other teams to work together. Many times the idea's advocates need to consider different ways of communication and discussion to step up the landing of idea.

This article attempts to discuss the basics of project proposal from the following areas. 1. The Complete solution

Personally think that a complete problem solution should be done S.I.M, namely the following three aspects,

Story

is to tell a story. What are the user's pain points, what are the problems with the use of the product, and what are the immediate or potential needs? After gathering enough user information to share with users, you can clearly define the problem.

The definition of a problem is the key to storytelling.

Once the problem is defined, the next step is to solve the problem and what specific effects the product has on the use case. This may be an improvement to the original use case, or it may be the introduction of a new use case.

In short, storytelling is from the customer and business point of view, the problem found, definition, solve the wonderful, to be fascinating. The ultimate goal of storytelling is to make your idea more mature, and more importantly to impress and attract the funders of the core contributors and projects that work with you. This is critical in large projects or products.

Idea

is to clarify the key points of the problem solving. The key point is the core value of the solution or the part of innovation. These sections can help us decide whether to file patent.

In addition, a complex project needs to give a summary design (high level) here. Here are the main parts, Project Architecture (architecture diagram)
can help you understand how different subsystems or modules work together to accomplish the main function. Application main flow (application flow)
The system's main thread description, such as data path flow, control path flow, how error handling is handled. Key challenges (key challenges)
This is the key link that will affect the progress of the project and whether it can be landed. To analyze the technical difficulties, we decided to validate the solution by prototyping.

This is part of the important link that proves the core value of idea and ensures that the project can eventually be landed. If you can not do according to the design to start the implementation of the project, it needs refinement.

Metric

To ensure a complex solution to the ground, the common approach is to define multiple phased targets (milestone). The goals of each phase, the output of the project, the timeline, how to measure success or failure should be clear.

More importantly, input-output analysis (ROI). The cost of project implementation (development of test person months, other resources), and the return of the project. The more you invest in huge projects, the more you need to quantify ROI. Relatively simple projects can only quantify inputs, and output can only be qualitative analysis.

From the perspective of different division of labor and roles within the organization, S.I.M actually embodies the focus of different roles on the project. The focus is usually on management, product managers, sales and marketing personnel. The focus of I is usually the architect, engineer, test, it OPS staff. The focus on M is usually project manager, management, and team lead.

Knowing this helps the initiator of the project to organize its core team according to the complexity and difficulty of the project. For example, someone has to focus on the problem that is facing the idea. Some people are thinking about story issues. Moreover, the proposal of the project should be based on the actual situation to communicate with different people in the S.I.M scene, and gradually improve their project proposals. This is the meaning of discussion and review. 2. Clear Discussion and review (review) process

The innovative idea requires a relaxed discussion atmosphere and a clear review process.

Depending on the maturity of idea, different forms of discussion and review can be considered-pitch,presenation, proposal

Pitch

Early idea can be done in a pitch way. The main focus is on story and idea. Make constructive suggestions to ensure breadth and coverage, and don't miss out on missing key points. Participants focused on core contributors. Brainstorming (brain storming) and other forms may be better used in this phase.

Presentation

After a certain investigation, trial and error, discussion, formed a relatively mature idea. The focus of this time is still on story and idea. But more attention is paid to the depth of the discussion, preparing the project for landing. The discussion and review should be focused on bringing together key contributors and stakeholders (stakeholder).

Proposal

Idea is quite mature through staged preparation and research. At this point the focus is on the metric from story to idea. Whether it is the project Phase Division (roadmap) or ROI analysis, it is necessary to discuss the research from the point of view of project implementation and management. The final review of this phase should be taken care of by bringing all stakeholders together to ensure that the feedback is received accordingly.

In addition, the need is not only for stakeholder feedback and verbal advice, but also to obtain their formal promise (commitment). 3. Summary

To propose, analyze and solve a complex problem requires not only hard power, but also soft power: communication ability, leadership ability, project coordination and management ability. There are different concepts and methods that may involve all aspects of the business technology field. More importantly, there is a need for constant practice.

Project proposal Basic This document attempts to help engineers understand what is a relatively complete project proposal from an engineer's point of view, and how to output research results in a phased way. The topic is a bit large, I hope the current version will be a good starting point. As your personal knowledge continues to evolve, this document will continue to be updated.

Writing this document is also a whim: S.I.M's framework is also suitable for learning and summarizing a product or software project. Next you can try to practice.