imported>742a: typo

2024-09-15T11:51:14Z

typo

New page

{{Short description|Description of an issue}}
A '''problem statement''' is a description of an issue to be addressed, or a condition to be improved upon. It identifies the gap between the current problem and goal. The first condition of solving a problem is understanding the problem, which can be done by way of a problem statement.<ref name=":0">{{Cite journal|last=Kush|first=Max|date=June 2015|title=The Statement Problem|journal=Quality Progress|volume=48|issue=6}}</ref>

Problem statements are used by most businesses and organizations to execute process improvement projects.<ref name=":1">{{Cite journal|last1=Annamalai|first1=Nagappan|last2=Kamaruddin|first2=Shahrul|last3=Azid|first3=Ishak Abdul|last4=Yeoh|first4=TS|date=September 2013|title=Importance of Problem Statement in Solving Industry Problems|journal=Applied Mechanics and Materials|location=Zurich|volume=421|pages=857–863|doi=10.4028/www.scientific.net/AMM.421.857|s2cid=60791623}}</ref>

== Purpose ==
The main purpose of a problem statement is to identify and explain the problem.<ref name=":2">{{Cite book|title=Six sigma for dummies|last1=Gygi|first1=Craig|last2=DeCarlo|first2=Neil|last3=Williams|first3=Bruce|publisher=John Wiley & Sons|year=2015|location=Hoboken, NJ|pages=76–78}}</ref><ref name=":3">{{Cite web|url=http://www.ceptara.com/blog/how-to-write-problem-statement|title=How To Write A Problem Statement|last=Lindstrom|first=Chris|date=2011-04-24|website=www.ceptara.com|language=en|access-date=2018-04-10}}</ref>

Another function of the problem statement is as a communication device.<ref name=":2" /> Before the project begins, [[Stakeholder (corporate)|stakeholders]] verify the problem and goals are accurately described in the problem statement. Once approved, the project reviews it. This also helps define [[Scope (project management)|project scope]].<ref name=":4">{{Cite book|title=Commercializing Great Products with Design for [[Six Sigma]]|last1=Perry|first1=Randy|last2=Bacon|first2=David|publisher=Prentice Hall|year=2010|pages=18}}</ref>

The problem statement is referenced throughout the project to establish focus within the project team and verify they stay on track. At the end of the project, it is revisited to confirm the solution indeed solves the problem.

The problem statement does not define the solution or methods of reaching the solution, and only recognizes the gap between the problem and goal.<ref name=":3" /><ref name=":5">{{Cite news|url=https://www.proprojectmanager.com/problem-statement/|title=How to Write a Problem Statement|last=Shaffer|first=Deb|date=2017-07-12|work=ProProject Manager|access-date=2018-04-10|language=en-US}}</ref>

== Writing ==
There are several basic elements that can be built into every problem statement. The problem statement should focus on the [[end user]], and the statement should not be too broad or narrow.<ref name=":7">{{Cite news |last=Widen |first=Steven |date=2018-04-02 |title=Take These Steps To Define Your UI/UX Problem And Avoid Haphazard Changes |url=https://www.forbes.com/sites/forbesagencycouncil/2018/04/02/take-these-steps-to-define-your-uiux-problem-and-avoid-haphazard-changes/#22f21cda7c6c |access-date=2018-04-10 |work=Forbes |language=en}}</ref>

Problem statements usually follow a format. While there are several options, the following is a template often used in [[business analysis]].

# Ideal: The desired state of the process or product.
# Reality: The current state of the process or product.
# Consequences: The impacts on the business if the problem is not fixed or improved upon.
# Proposal: Potential solutions.<ref name=":6">{{Cite web |last=Shaffer |first=David |date=2015-12-21 |title=Cooking Up Business Analysis Success |url=https://www.batimes.com/articles/cooking-up-business-analysis-success.html |access-date=2018-04-10 |website=BA Times |language=en-gb}}</ref>

==References==
<references />

[[Category:Problem solving]]

Problem statement - Revision history

imported>742a: typo