Early warning signs and corrective actions on projects
Be aware of the early warning signs on a project and take the appropriate corrective actions as soon as possible. Monitor the outputs for each stage of a project.
Stage 1 – Start-up activities
Main outputs: Project objective, scope and schedule, and possible feasibility examination
Problem: Objective is not clear.
Stop and write down a clear, concise objective in a few sentences, and review it with the project’s customer.
Customer is not “on board” yet.
Set up a discussion meeting with the project customer before continuing.
Schedule is too tight.
Reduce scope, look for more resources, or do the project work in phases (if ok with customer).
Started work without a plan or schedule and now causing some confusion.
Limit the initial work until an overall project plan is developed. Make a project schedule as soon as possible, and continue to update it throughout the entire project.
Project is very large and may be beyond the capability of the current team.
Develop a project plan and discuss initial concerns with customer; may need to limit project scope, form a larger team, or break the project into phases in order to accomplish the bigger project.
Stage 2 – Process documentation & measurement
Main outputs: Historical and any new data, observations, flow diagrams, cause/effect, and benchmarking
Having difficulty getting access to the people that own the area under investigation.
Discuss access with project customer, may need them to assign a focal to the project or introduce the team to some of their people (explaining the assignment given to the team).
Hard to view the entire process at once, due to multi-shift operation, etc.
Break the process up into viewable sections, but make sure all portions are covered.
Current available data is not conclusive or not specific enough.
Determine what new data is required and set up a data collection plan. New data being collected is not helping the project. Review the original objective & planned deliverables, and see what data needs to be collected to support the project; may have started data collection before identifying project’s data needs.
Stage 3 - Develop & evaluate solutions
Main outputs: Preliminary solutions, evaluation of findings
Having difficulty coming up with any viable solutions.
May need to review the results from earlier stages and look for partial solutions; may also need to do some benchmarking of other similar operations to see some possible solutions already being used elsewhere.
All solutions look good, not sure how to compare them or choose one.
Discuss the solutions with your project customer (or their assigned focal) to see which of the solutions might work best for them; may also need to have a ranked criteria for evaluating, or even some limited testing to pick the best solution for this application.
Want to do some limited testing, but not sure how to proceed.
Discuss the solutions you want to test, with the project customer, and get their help with setting up a simple, but fair, test of the solutions.
Stage 4 - Conclusions & recommendations
Main outputs: Final report & final presentation
Have lots of hand-written notes and data, but difficult to come up with any conclusions or recommendations.
Need to go back as a team and type up all findings and see what the data says; may need to have a team “white board” discussion session to draw out the team’s knowledge and, if necessary, to continue benchmarking or other solution generating activities.
Have a lot of findings & conclusions, but not many recommendations.
May need to organize the findings & conclusions into a preliminary presentation and discuss with the project customer; this may generate some recommendations, or the need to continue developing more viable solutions.
Final presentation or final report is too long, and not easy to follow.
Develop a good working outline, before starting to write the final report, or build the final presentation. Practice and get some feedback on the presentation to make sure the objective and all deliverables are met.
Stage 5 - Implementation or follow-up
Main outputs: Implementation plan (if required)
Not sure if any implementation would happen, so no implementation plan was prepared.
Discuss need for developing an implementation plan later, with project customer (based on whether initial recommendations are accepted).
Trying to use the final presentation or final report as an implementation plan, and running into trouble.
May need to stop and develop a detailed implementation plan and review this with the original project customer – based on the findings, conclusions & recommendations of the earlier project. May also have to discuss the earlier presentation/report with the original authors (for clarification).
Not sure if any follow-up is required, after the final presentation has been given.
Discuss this with the original project customer – or if possible, check the area for any problems they may be experiencing with the original recommendations.
- Be aware of the early warning signs at each stage of an industrial engineering project.
- Take the appropriate corrective action for each early warning sign.
- Monitor the outputs for each stage of a project.
- Utilize good project management techniques throughout the project.