Documentation of change is required after it is approved as people leave the project in the middle and it is necessary that the person replacing the one ho worked previously knows why exactly was the change made and will be easier for him/her to understand the project and no detail has been missed.
I think every change has to be important in a project as we cannot actually have a say which one is of higher to the other.
The PM has to look pass logging everything as this might be of some use in future for reference and it would be a waste of time and money if the same change is repeated again in some other project in future.

As mentioned in this week's lecture that it is important to log all the information in the closing phase . However, it is important to log information through all the phases of the project.This is because at any given time all the members of the team should be on the same page as mentioned above in cases where any of the members are no longer associated with the project. Logging makes it easier to understand the changes and the mistakes made at a particular stage of the project and to review them before starting to work on a new project as this will be helpful in getting past those mistakes/changes.
A project manager has to look pass the logging as it will help him/her to know the changes made and keep a track of them in the future projects for personal growth as well as the for the success of the project and also save time by not doing a loop of the same mistakes/changes.

I think it's important to keep track of all lessons learned throughout the project by each individual team member who has a role in this project. If one of the team members leaves the company, their log can be a useful transition document for the person taking over the role. For other projects, this document can help avoid similar mistakes already made or keep track of problems that came up during the project that need to be documented in the final report, and therefor save time and money. Logging everything also just helps yourself when you start writing up final reports. In my experience, I was working on a final report that had time points that lasted up to two years. I came into the company when this project was closing and was asked to help write the final report however it was difficult to start the report since the project had various deviations that came up throughout. I was not aware that a lessons learned document existed but that would have been very helpful in drafting up all the issues that came up throughout the years and saved time.

Requiring a project team to report on the lessons learned is very important for many different reasons. Firstly, it's essential for project teams to learn from their experiences so that members can perform better in future projects. Future projects will only run more efficiently if individuals on a project team learn from their mistakes and find out how they could've worked better on the project. In my opinion, everything that you do in life is a learning experience. Even if you succeed at something, you can always find a way to do it better the next time up until you reached perfection. Furthermore, it's important for project members to learn how to work better as a team so requiring them to report on lessons will allow them to reflect on their experiences with each other to see where the problems were, if any, and how they could be avoided next time. Not only is it important to learn about how to do the work efficiently, but understanding each other's strengths and weaknesses is vital to a successful performance. Some of the lessons that could be reported would be: to start your project earlier if it's possible because starting early is always better than starting later; what type of people did the project need and who wasn't needed. It's in your best interest to get a head start on your work so that you are better prepared t deal with problems later on. Time is a crucial factor because everything has a deadline. Time pressure can make work very stressful. Starting things early will save you a lot of stress down the road. A project manager may look pass logging lessons if he/she feels that the lesson is very basic and something that is easily understood. Also, the project could've been very successful and there may have been flaws in the process but were unavoidable for some reason.

It is important to document the lessons learned during the course of a project. Documentations of decisions made or decisions/actions that would have been better if done are crucial to transferring the knowledge of the team members of others in the organization that might run into similar circumstances. While the physical documentation of these lessons are needed, what may be equally as important is the why behind why this change/decision/action was done or is preferred. This will give much more perspective to the person reading the document. If there isn't much context behind why something was a lesson learned, then readers may not take much stock on the point and end up running into the problem themselves. For example, in a previous role, during a project a change was made in a process which was a result of a 'lessons learned' from a previous project. However, because there was no context behind why the change was desired, when a review of the process came, no one knew why the change was done (since the people on the project were either new or not on the old project). The process change was reverted, however a problem occurred that put into perspective why the previous team member had put that change in the lessons learned. If there had been more context behind that point, time would likely not have been wasted undoing and redoing the change and the problem probably could have been avoided altogether.

In addition to understanding the decisions made in the past, looking over the lessons learned provides invaluable insight that can be used to streamline a projects progression. The obvious reason as some mentioned is learning and avoiding past mistakes made. In addition, taking certain courses of action based on previous decisions in the past to ensure a timely completion is another benefit of a lessons learned. The lessons I believe are particularly worth recording include: the time frames for deliverables from 3rd party vendors, unexpected decisions/justifications from upper management in any magnitude, and of course all estimates for tests, parts, and materials. These few items are some of the most critical variables I've noticed that redirect the path a project takes so having as much insight as possible on them would certainly prevent delays and other situations down the line.

I think the reason lessons learned is always documented is so the mistakes are not repeated. Additionally, this can attribute to any preventative actions that can be implemented in proceeding projects. The objective is always to learn from your mistakes, which will better yourself as well as the project at hand. Lessons that pertain to change control can range from soft skill lessons, such as contacting certain personnel that is directly affected, as well as more technical skills, such as figuring out the impact of said change and how it will fit within procedures. A project manager may look passed logging all the lessons to close the project and get final approvals as soon as possible; maybe because of the urgency of the project. However, this is very poor practice as the lessons learned can help build a better process or improve on something that was not efficient; ultimately, saving time and resources for the company or for the employees.

Getting feedback from your team is an important part of improving as a project manager. With change orders, a PM can understand the impact of changes on the project scope, schedule, and budget. Additionally, the PM may be able to gain knowledge on best practices for evaluating and managing changes to the project. By logging everything that was learned from a project, a PM can reflect on the successes and failures of the project and use that information to improve future projects. Moreover, having a record of what worked and what didn't can help the project manager make data-driven decisions in the future.

Requiring a project team to report their lessons can also help in becoming familiar with the documentation. It can also help the team understand where everyone's mindset was during the project process. It can also let overseers see where the project derailed or thrived so that in future projects, that can be picked up upon earlier. More importantly, members of the project can bring in the acknowledgment of other team members' thought processes and bring that into their next project.

I believe that documenting what you have learned and the steps you have taken is crucial for the whole team. There may be some parts of the team that understands something while the other parts do not. This is why it is so important to document what has been done or learned throughout the process. If someone does not know what is going on they can look back at what was learned throughout the project and figure out what they are doing. Not only that, but if a problem arises, the project manager or project team can look back at the steps documented and decipher where the project may have gone wrong. with that being said, documentation could also be used for future projects as well. If there are new projects that consist of similar ideas to past ones, the lessons learned in the old projects can be referred back to help in the newer projects. Overall, I believe documenting lessons learned can not only help one project team succeed, but multiple over long stretch of time. 

I think that it is very important to document everything. For example, if you had a learning and document it. In the event, someone else gets into a similar situation. They can avoid the learning process by taking the learnings you had and apply it to their situation. This way they will not have to learn the hard way.