Problem Statement

Problem solving is the act of defining a problem; determining the cause of the problem; identifying, prioritizing, and selecting alternatives for a solution; and implementing a solution.  This approach is helpful in discreet challenges but may not be best suited to systems thinking particularly given the complexity of the equity challenges this guide puts forth.  However, in some cases, it is easier to define a problem when it is a specific initiative.
  
A problem statement is a concise description of an issue to be addressed or a problem to be solved.  It includes further detail of context, scope, risks, and stakeholders.  Aligning a team on a problem statement is a critical first step in any project. The importance in creating a problem statement really is in the process; it forces everyone to think through specifics, align on language, and think broadly before focusing. 

The problem statement guides the work of the project team and is backed up with detailed work plans, business cases, and other supporting materials. While it is a critical “first” step, the problem statement should be revisited often and refined as needed.  
‍
The problem statement template included in this resource guide has been used by dozens of teams over many years and includes the most basic elements; teams maybe want to tweak or add additional elements such as: 

• Major milestones - major dates that may drive progress, i.e. industry conferences, legislative deadlines,
• Out of scope - what is NOT included in this project, i.e. specific region. This is often helpful in syndicating progress with external parties to show how the team has prioritized its work. 
• Sponsor and/or working team 
• Definitions - alignment on terminology particularly for non-standard words or terms open to interpretation, i.e. equity, rights of nature
• Sponsor and/or working team 

Keep in mind:

• It is best to start any project with a problem statement, but don’t hesitate to apply it at any stage of implementation; going through the process will validate what you are solving is still a critical item.
• Ensure the scope is not too broad or too narrow
• Defining terminology and semantics upfront is really important to the planning stage, e.g., what is equity? what are RoN?, Who is asking the question in the problem statement?

SMART Goals

SMART is a well-known acronym for describing goals an individual, a team, or an organization sets out to achieve.  
‍
Questions to ask when establishing SMART goals:

• Specific - What and where is the primary focus of the issue, e.g. which business unit, which geography, what product or function?
• Measurable - What metrics or key performance indicators (KPIs) will be evidence of success, i.e. 10% increase in participation from BIPOC groups
• Actionable - Can we achieve this all things considered? Are we able to take action to get there?
• Relevant - How is this related to the overall strategic diversity and equity priorities, is it the right time to solve this?
• Time-bound - ​​When will the work be completed?

How to Write SMART Goals for more examples

Tool Collaboration

This is a growing, evolving, and community-created resource. Please share any additional resources, personal experiences using this tool, or ways this page could be improved!