Project Report

Six Sigma – iSixSigma Forums General Forums General Project Report

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
  • #55052

    Philip Lee

    Hi all, I’m a new member so forgive me in advance if I’m repeating already covered ground.
    I’ve recently completed Black Belt training and ready to submit my 1st project. I put together a PowerPoint presentation but was advised by the lecturer I was not following the Roadmap correctly and would need to put a Project Report together.
    Having been out of education for over 20 yrs and never written a report I am really struggling with this so any advice would be much appreciated.


    Shelby Jarvis


    The purpose of reporting your project verse a road map is it aids in telling the story succinctly. You will find varying opinions and formats. I will share a few resource ideas to help you find the one which works best for you. My advice is to speak with your instructor and more importantly your stakeholders to identify what method they prefer.

    Within your BB course should have been a reporting process. It may not be in every curriculum, but it is common to many. If yours does not address the reporting process, you can likely google this as well as search for it here on this site.

    Another method is story boarding. Each phase of DMAIC is broken into steps to guide the solution process. If you are using this, it may help you to review your storyboards to identify the key points.

    If you don’t have luck with either of these, I typically flow my presentations as follows:

    1) Problem statement with gap identified (timing, financial, performance, etc.) Work this in a manner which meets your stakeholders needs. Acknowledge your team and any resources which were critical to the project.
    2) Review the project at a 50K ft level. If you intend on sharing data, pick the vital few and make it graphical.
    3) Specifically identify any risks and how they were abated.
    4) Share the solution. At a 50K ft level, explain the process, highlight any relevant controls (including metric dashboards), and share results. If R and Rs changed, identify them here as well. (Make certain the leader with the new responsibilities is present and comfortable.) Same format as the data shared previously, but now you have the after data. Remember, if you utilize photos, take the before and after from the exact same perspective.
    5) Close with a summary. Remind them of the initial problem, the timing, the solution. Thank them and your team.

    I find that the more efficient I present, the better the adoption. Two common phrases for reporting are 1) Tell them your going to tell them, tell them, tell them you told them 2) Start with an end in mind. The key is find your style which best matches your audience and practice. It is important that you feel confident as their perception of your confidence will transfer to their confidence in the solution.

    Good Luck


    Chris Seider

    It sounds like you weren’t communicated about the specifics for graduation from BB training.

    I’m torn about written written project reports because it’s a time drainer of days for many students.


    Amit Kumar Ojha

    Hi Philip,

    Shelby has almost covered all the aspects. In addition I would just like to share my experience with Six Sigma projects. I have found that many people are not very much interested in the documentation part of any Six Sigma project and it is done half halfheartedly which clearly reflects in the output. It is very important to understand the purpose of proper documentation. While in your case, you may think that the main purpose is your BB evaluation, however please note that one of the most important aspects of documentation is to convert your tacit knowledge (gained while doing the project) into explicit knowledge which may help many people in applying the similar solutions and help in overall addition to the Six Sigma knowledge-base.
    Hence, apart from focusing on you curriculum specific details (if there are any) please document the project in such a manner that it helps others from your experience.

    All the best.




    Really good points have been brought up by the other posters. It’s hard to say from the outside looking in. But, the wording “not following the road map correctly” would make me think your class adviser was expecting your project presentation to follow the DMAIC road map. It’s a best practice to report out the deliverables for each phase as succinctly as possible. Don’t dwell so much on all the work that was done but, the key lessons learned, highlights, root causes identified, solutions and results.

    But, if your not clear what your instructor is asking for, I’d ask them more questions. :-)



    Philip Lee

    Thanks guys,
    All of your points are a big help. I’m starting writing it today, I’ve searched the Internet for example reports but not sure of the correct format and content as they vary so much. Does anyone have a sample I can take a look at?


    Mike Carnell

    @Phil72 The purpose of the final report is pretty simple. We put it in place when we began teaching at Allied Signal simply because the knowledge you have gained belongs to the company that paid you to do the project not you. A company like GE was world class at taking that knowledge and rolling it out across the company and getting exponential benefits from a project. It may have become a “best practice” but I am not sure who has the authority to determine that or the data to support it. It is just business.

    This is an assumption on my part. As you went through the training process you should have done a presentation at each step DMAIC. If you take all those presentations and put them together they should tell the story of your project i.e. the final report. Take those PP slides and turn it into a word document – tell the story and you should be done. I don’t see this as a very complicated issue. Most of the work should be done.

    Just my opinion.

Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic.