Talk:Kaizen Event - a managerial tool for problem-solving

Revision as of 22:16, 25 November 2014

Review by Nemo

Layout and Wiki-issues

• Layout looks good in general.
• You are using the Wiki functions for keywords and references very nice.
• When doing numbered bullet points I can recommend that you use "#" instead of "*"
• You have some errors with missing references, that are highlighted with red in the text. It looks like you are already working on this.
• You link to some sides that does not exist fx. "Kaizen" and "Kaizen Events".
• You are doing some quotes, which are very nice in general. I can recommend the function <blockquote> xxx </blockquote>

Abstract

• The abstract assumes that the reader knows what Kaizen Event is about. At this stage I did had never heard about it. For me it would have been nice that the concept was shortly introduced in the abstract.
• Why is it limited to project management - what about programme and portfolio?
• The keywords make sence:)

Introduction

• What are the 5 basic lean principles that you mention? It would be nice to mention them. Or maybe you do so in Table 1? But then please refer to Table 1.
• It should be considered to have the section "Kaizen Event definition" before "Kaizen vs. Kaizen Events in Lean thinking".
• "Arrow diagram" - is that a gantt chart?
• To some degree I see the subsection as separate. Flow in the article and transition between subsections can be optimised. This can typically be done with 1-2 lines text in the end of each subsection focusing on the transition to the next subsection.

Overview of Kaizen Event

• "Three- to five-day concentrated work session" - you mentioned a week in the introduction.
• It is unclear for me who is attending a Kaizen Event - employees or management?

Guide for a Kaizen Event process

• Nice with an example. To be hornest - at this point in the article I start to understand what it all about.

Sum up of factors to consider during the Kaizen Event process

• I like this section. But maybe the title should just be "Conclusion". It is not necessarily something that should be considered during the KE process.

Benefits & Challenges

• Fine section :)

References

• Looks like proper references in general.
• You are not 100% consequent about how you are writing your references.

GENERAL

• It looks good but be carefull that there are a clear and harmonious line through the article.
• You could consider having a section in the end of the article about similar/other tools.

reviewed by $Young-Money$

• Good article, making it clear what your topic i.e. Kaizen Events is about to the reader.

• Like the methodology elaboration through out the article.

• Good idea with the keywords, makes it easier to know if the article is of relevance when doing research.

• I suggest you proof read the article before submission since there are some minor formulation an spelling mistakes through out. e.g. in the abstract

• Mention the 5 basic lean principles, since future readers might not know about them thus they can make their own research on them.

• You have two table named Table 2, remember to edit that

• Your integrated links, leads no where, so i suggest you remove them or try to find anther apppm article that relates

• I suggest you increase the spacing between the different headings. They are too tight to each other making it difficult to read.

All in all you have done a good job elaborating your subject and seems like you have done a great deal of research. Just remember to proof read it before submission, it will be a spoiler if you don't reformulate some aspects e.g. like the abstract.