Problem Statements

     We will now shift our focus to problem statements and feasibility reports. Firstly, we will talk about problem statements. A problem statement is a short, clear explanation of changes you want to make. We do this by explaining why it is important and whom it might impact. First, we have to find the root cause of the problem. We do this by asking the following questions: Who? Who is affected? What? What component is missing? When? What is the timeline for this issue? Where? Where is the problem located? Why? Why is this issue important? However, it is important to note we want to avoid solutions for now. After asking those questions we need to do some outside research, this can help us identify the root cause problem. After doing outside research we can come to a solution, after finding the solution we want to test it out to see if it could fix the problem. However, we might encounter some more questions. Is there only one solution? Does the problem have to do with money or personnel? Are you sure this is the root cause and not a symptom? After asking yourself these questions you should have a general idea of the basic problem. The first actual step of the problem statement is to explain the problem. Start with a statement of purpose and a brief summary of the problem. This would be your introduction. Next, we will move on to the discussion, here we will discuss anything relevant to the topic. However, we are not stating the solution at this point. You also want to discuss the facts of the problem here. Finally, we would have the conclusion, here we can tie into our research and list the possible solutions or solutions. You want the solution or solutions to be in bullet format. These solutions will be our basis for the feasibility report or the recommendation report. Attached will be a generic outline of the problem statement.