Project Knowledge

Business Putting in place a project of any size and not learning from the experience is one of the most .mon errors that is made in businesses of all sizes. If you think back to the projects that you have been involved with have you truly run through the project to plan – or did you find numerous diversions that you were forced to go down? For most of us the diversions were in the form of problems that needed to be over.e, sometimes the diversions brought us benefits that were not originally planned. The ability to hold this information in the business to learn for the future can shorten design lead times, reduce the cost of future projects and reduce the fear of the unknown when similar projects are met in the years to .e. An example of how a project may run into problems could be involved with the installation of a new piece of kit. When you have installed the machinery you find that the specification was ropey and you need to spend some time and money on upgrading the equipment. After some delays you get the production process running and then you find that the design production rate cannot be achieved. The root cause factors for this issue get defined and the necessary training and Engineering work takes place. Eventually after some long hours and pain from the peers within the business you end up with a reasonable production process. The key question that we must pose is this – "what will be different next time around?" Our ability to take the information gained from this process and use it to our advantage will allow future projects to be managed more easily – meaning that the project management gets easier and less burdensome for those that undertake it. The most .mon case however is to not consider the recording and learning from our own experiences – especially on projects – and suffer the same mistakes when we get around to a similar project in years to .e. So, going back the question above, what can we do to make this knowledge stick in the business? There are two good options that spring to mind that can be incorporated into any business easily. Both options start with making a list of all of the good points and the bad points of the project. By defining a list we can work out the root cause to the items we list – be they good or bad, after all if we can work out why we had the good points we can recreate them. Using a tool such as 5-Why is a great place to start (see the article on ‘Getting to the root of it’ for more information). Once we have the full list we can work out what to do with the root causes. The first option is to change the systems that are used in the business to control the effect. In the case of the example above, the poorly specified equipment may be due to a flawed system for specifying the equipment (i.e. the scope on the invitation to tender), we can change the system and then monitor the results in the future to evaluate the change. The second option is to store the information into logical files that other people within the organisation can refer to when they work on projects. It may be that the project management guidelines for the organisation will include a mandatory research stage of the businesses knowledge library. The key to this process is that the information that we gain from our efforts should be stored somewhere outside of people’s heads so that the organisation stronger from that knowledge. Too many times .anisations let skilled people leave with all of the information still tucked away in their brains. The process of recording information to improve project development and implementation covers only one aspect of running a business effectively. The day-to-day operations that take place all have valuable information that can be stored back into the business that can improve future performance. This article assumes that most of this information has been stored already within the .anisation in the form of Standard Operating Procedures (SOPs) or something similar. Take the time today to sit back at work and reflect upon the message of this article. Would your .anisation’s future projects avoid all the previous pitfalls that you have encountered if you (or other key members) were not present? About the Author: 相关的主题文章: