[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-240567-105":53,"doc-detail-240567-en":126},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":119,"head_meta":121,"extra_data":123,"updated_unix":125},105,"en","understanding-your-problem-toolkit-guide-problem-statement","Understanding your Problem - Toolkit Guide - Problem Statement","","Improvement Cymru Academy Toolkit Guide explains how to define a problem clearly at the start of an improvement project. It focuses on creating a concise problem statement—typically around 18 words—that communicates current pain, relevant issue information, and the consequences for organisations or individuals. The guide clarifies that problem statements should not describe solutions or root causes, and provides rationale, timing, step-by-step creation guidance, and a practical example plus tips and template references.",{"@graph":63,"@context":118},[64,80,101],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":51,"@type":70,"position":76},"https://docshare.wps.com/template/general/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/understanding-your-problem-toolkit-guide-problem-statement/240567/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/understanding-your-problem-toolkit-guide-problem-statement/240567.png","ImageObject",442,249,{"name":88,"@type":89},"Paura","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-09-20","2026-09-11",true,{"@type":98,"interactionType":99,"userInteractionCount":76},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"What is the purpose of a problem statement in an improvement project?","Question",{"text":108,"@type":109},"A problem statement is used at the start of a project so everyone involved understands what the project is about. It provides clarity for stakeholders about the issue and its consequences.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"What should a problem statement include and what should it avoid?",{"text":113,"@type":109},"It should be clear, concise (often around 18 words), and include the context, the issue, and the impact. It should not describe solutions or root causes.",{"name":115,"@type":106,"acceptedAnswer":116},"When should you share a problem statement and how can it be used during the project?",{"text":117,"@type":109},"It is written at the start of the project and shared once the team has decided on the problem. It can be referenced throughout the project as a point of reference to maintain momentum and engagement.","https://schema.org",{"og:url":78,"og:type":120,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":122,"canonical":78},"index,follow",{"doc_id":124,"site_id":56},240567,1789162807,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":50,"category_name":51,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":76,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":47,"language":135,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":136,"faqs":137,"seo_title":138,"seo_description":61,"update_tm":125,"read_time":73},13056712833777,"https://ap-avatar.wpscdn.com/davatar_29158cc5080c5b710cf443261637dec0","Improvement Cymru Academy  \nToolkit Guide  \nUnderstanding your  \nProblem  \nIntroduction  \nThis toolkit guide is focussed on supporting you to understand your problem, which is the starting point of any improvement project. To support you , this guide helps you create a problem statement, a vital tool that will support you , your project team and your stakeholders as you initiate your improvement project.  \nWhat is a Problem Statement?  \nA problem statement is used at the start of any project so that those involved are all aware of what the project is about. It is a short description of your project and is a clear and concise way of letting your stakeholders know what project you are about to embark on. It is typically about 18 words long and will often convey what the current ‘pain’ is and the consequences of the problem. It can contain information about the issue and the impact on the organisation or individual. It needs to be clear enough so that anyone reading it is aware that this is something that requires attention. It is important to note that problem statements do not describe the solution or root causes.  \nOnce the problem has been defined, the aim of the improvement project can be developed. An aim compliments the problem statement by summarising what you intend to achieve once you’ve identified your problem. Please see our ‘SMART aim’toolkit guide for more information.  \nRationale  \nProblem statements are vital for any project or organisation as they requirestakeholder attention and engagement. Without a problem statement stakeholders can be left feeling confused and not sure what to prioritise or what is happening. They are powerful tools that create influence and team engagement to ensure everyone is aware of the issues or ‘problem’ that needs to be addressed. As the project is being carried out in real time , it creates relevance and purpose to what’s happening within the organisation.  \nHow to create a problem statement  \nIt is important to involve your project team in helping you to identify your problem and write your problem statement.  \nData plays a vital role in understanding your problem; without evidence of your problem, you are left with opinion. Whilst this is often based on observation and subject knowledge , it is important to gather data to gain an accurate representation of the problem. You can use data that already exists or collect data on the process that you want to focus on.  \nEvery problem should identify the impact of the situation at hand. This will form the basis of your aim – what you want to achieve.  \nWhen to use a Problem Statement  \nA problem statement is written at the start of any project and seeks to answer the question ‘What issue needs to be addressed and why?’ Once you and your team have decided on your problem, you can then share the problem statement with your stakeholders. This gives the stakeholders clarity of the problem. You can then refer to your problem statement as a point of reference to keep momentum and engagement throughout your project.  \nNext Steps  \nOnce you have completed your problem statement and developed your SMART aim, you need to understand your system to make improvements. There are a number of tools that can help:  \nPareto chart; Process Mapping; Spaghetti diagrams, Measles chart, Fishbone and 5 Whys. We have Toolkit Guides for each of these tools in our Resource Library on our webpage. [https://phw.nhs.wales/services-and-teams/improvement](https://phw.nhs.wales/services-and-teams/improvement)  \ncymru/improvement-cymru-academy/  \nProblem statement example  \nVariability in the standard of history taking on admission to a mental health unit are resulting in risk assessments that do not inform which safety measures are required for children and young people presenting with deliberate self-harm and overdose.  \nHelpful tips  \n• A successful problem statement will contain context of what the problem is.  \n• A problem statement is a clear description of the issu","cbCaitJX5fafUZwE","https://ap.wps.com/l/cbCaitJX5fafUZwE","pdf",279133,"English","# Introduction\n## What is a Problem Statement?\n## Rationale\n# How to create a problem statement\n## Data and impact\n# When to use a Problem Statement\n# Next Steps\n## Supporting tools\n# Problem statement example\n## Helpful tips\n# Additional resources\n## Further reading","[{\"question\":\"What is the purpose of a problem statement in an improvement project?\",\"answer\":\"A problem statement is used at the start of a project so everyone involved understands what the project is about. It provides clarity for stakeholders about the issue and its consequences.\"},{\"question\":\"What should a problem statement include and what should it avoid?\",\"answer\":\"It should be clear, concise (often around 18 words), and include the context, the issue, and the impact. It should not describe solutions or root causes.\"},{\"question\":\"When should you share a problem statement and how can it be used during the project?\",\"answer\":\"It is written at the start of the project and shared once the team has decided on the problem. It can be referenced throughout the project as a point of reference to maintain momentum and engagement.\"}]","Understanding your Problem - Toolkit Guide - Problem Statement | PDF"]