First development sharing lessons learned _ sharing

In the company to do a development of sharing, share in the development process of some of the experience gained. Despite his confidence, he was hit hard after the speech, and despite the lack of recognition of the effect, many lessons were learned.

Inaccurate positioning. I will share the theme of "development", hoping to "impart" some thoughts and methods that I think are very important, but obviously too optimistic. Although two heavyweight executives came to attend lectures and work partners to join, the focus was on the system I was responsible for and the issues discussed were focused on the system rather than on development. Therefore, we should pay more attention to the feelings and needs of the audience.

Explain what you are unfamiliar with. Some of the content, such as "Unit Test", is not rich in experience, just to enrich the PPT, which can be put in ppt, and a word is used, offline communication.

Don't speak well enough of what you know. Originally only "Development is what", "implementation of the Model", "" Refactoring "and" table "four parts, the understanding is also more in-depth, but later because of the temptation to withstand the ego, but also added a lot of thought very important content, the result is limited to time and content pressure, not the familiar things to speak thoroughly.

Try is not fine, the content and time ratio imbalance. Time is only one hours, but want to speak more things, doomed to be easy to fail.

Too confident. Be confident that you can remember what you need to tell, able to control the mood and rhythm, little preparation, training less beforehand, the results are still tense, missing some really important things, and too fast, pause too much, lack of communication with the audience, and even wrong, thinking confusion. speech, or more training, a lot of preparation.

Less sentiment, more dry goods. Even if you want to talk about sentiment, but also as much as possible to sacrifice as many dry goods, so that others can reap, worthy of others to hold their own field.

Ask the supervisor for advice beforehand. Their advice is usually very important, allowing you to focus on the right direction rather than acting on your own assumptions. If I had asked for advice from my supervisor beforehand, he would have pointed out where my focus was, and my boss's supervisor would have been able to look at it and say that PowerPoint was back to redo.



Summarize:

Positioning to be accurate, determine the scope of content to be shared;

Speak only of things that are familiar to you, and speak thoroughly of familiar things;

Content to refine, talk about others interested in things;

A lot of training, a lot of preparation;

Study and explore, focusing on a thorough explanation.


What a truly successful speech should be. The content is very small, but very thorough, can arouse the enthusiastic discussion, everybody from each other's opinion sharing more than expected more things, but not limited to the presenter to book the content.


Failure can yield more things than success. Although the failure of the speech will cause some setbacks, but not to speak, it is difficult to find their own problems. Therefore, it is worthwhile to weigh the pros and cons.

It's best to say one thing at a time, stress in two things, and three things will be a test. No more than three things. If you can connect things together and form a story, you can talk about countless things.

Therefore, the order of the narration is not limited to the linear sequence shown in the PPT, it can be interspersed freely--because things are inherently interrelated--the most important thing is to give the audience a sense of coherence and devotion.

Even for those who are extremely good designers, to do a great work is usually through a lot of thinking and tempering, it can not be done in a one-time. Don't be too confident about your ability, don't slack off. In fact, all people understand this, but only a great designer can put it into practice.