Additionally, the problem statement is used to explain what the expected environment looks like.
(Method) Conclusion , Wally Davis taught me that one.
And he's right, the better the clarity around what the team is attempting to fix, the more efficient they'll be in solving the problem, the solution will better 'fix' the issues, and the team can get back to executing the business versus fixing it.
Only after the problem statement is written and agreed upon should the solution(s) be discussed and the resulting course of action determined.
Before the problem statement can be crafted, the problem must be defined.
The main purpose of the problem statement is to identify and explain the problem.
This includes describing the existing environment, where the problem occurs, and what impacts it has on users, finances, and ancillary activities.
A problem statement is a concise description of an issue to be addressed or a condition to be improved upon.
It identifies the gap between the current (problem) state and desired (goal) state of a process or product.
If we ignore this problem; resources will need to increase to handle the cascading problems, and we may miss critical customer deadlines which could result in lost revenue, SLA penalties, lost business, and further damage to our quality reputation.
(Issue Statement) We will use our Kaizen Blitz methodology in evaluating the last release to help us improve our processes.