Hello everyone. Last time, I wrote about CTQ, a tool used in the first step of Lean Six Sigma, “Define”, to identify improvement opportunities within the company from VOC (Voice of Customer).
Let’s look back the flow up to now around this timing.
Until the last time, “Define (the problem)” has been completed (although “general problem solving”, which is not Lean Six Sigma, is still in the process of analyzing the current situation). So, here I would like to write about “5W2H” and “Project Charter” as tools used in summarizing “Define”.
1. What is 5W2H?
I think many of you have heard of “5W2H”. It was originally a framework for organizing things in general rather than a tool specifically for problem solving. Since it’s common, if you google it, you’ll find a lot. So let me put only post one link here.
Specifically, it means What – Why – When – Who – Where – How – How much/many, which is “5W2H” with five interrogative words starting with W and two interrogative words starting with H. I’m sure many of you have heard of “5W1H”, but the difference is whether or not there is “How much/many”.
The meaning of each of these interrogative words also changes depending on what the purpose is, but in the case of problem solving,
What : What is the problem?
Why : Why did the problem happen (has been happening)?
When : When did the problem happen (has been happening)?
Who : Who found the problem? / Who suffers from the problem?
Where : Where did the problem happen (has been happening)?
How : How did the problem happen (has been happening)?
How much／many : The number of problems/money conversion
like these.
This is a simple table that summarizes the above items can help clarify the problem. As background data, I think it would be perfect to add the results of the research and analysis that we have done so far.
2. What is Project charter?
This is also common, so if you google it, you will find a lot. So let me only post one link here.
“Project charter” is originally the first thing to appear in “PMBOK” , which is the bible in the project manager community. I would like to write about this PMBOK later on this blog.
If you are working for consulting firms, I think that there are many cases where you have a “methodology” within the firms, but isn’t the charter included in them? But strangely it’s not used much. In the case of a consulting project, I feel that the proposal is more often used as the “base” of the project (this is from when I was in the consulting industry). I remember going back to the proposal and checking it when we confirm our understanding with the client.
When you’re working on a project and you’re immersed in the work and discussions, you’ll often find yourself wondering, “What was the purpose of this project”? “Project charter” is a “base” for everyone to return to the starting point in such a case. Therefore, it is said that it is better to keep it simple, preferably on a single sheet of paper, and put it on the wall of the project room. Recently, I think that remote work is increasing, so in such cases, it would be nice to share it on the network.
3. By the way, what is the relationship between “5W2H” and “Project charter”?
This time, I am introducing “5W2H” and “Project Charter” as tools used to organize Lean Six Sigma’s “Define”. After this, we will actually proceed to solve the problem, but I think that there are many cases where the project is started to tackle problems around this timing. In such cases, “Project charter” is useful when obtaining project approval within the company. In the charter, of course, the problem should be described, but 5W2H as well can be used there. A hybrid is recommended.
If this is the case, I think that the contents of the project will be clear to anyone in the company, including stakeholders (although it should be written in such a way).
That’s all for this time, and I would like to continue from the next time onwards. Thank you for reading until the end.