SOLVE Toolkit: Problem Definition

This Tool & Why It's Valuable

A well-defined problem is the focal point of your project and should be written with clear, concise language. This critical step helps ensure you mobilize the right resources and that you are working on a meaningful issue, not just an irritant. Writing a well-defined problem statement is the first step towards a successful project because a problem well-defined is a problem half solved!

How to Apply It

1. Identify the consequences associated with not solving this issue

2. Confirm this issue has been around – it is not just a one-time occurrence 

3. Write a clear, concise problem statement – not a solution statement. 

   • A good problem statement:

     • Identifies the issue

     • Includes supporting facts/data

     • Identifies the impact the issue has on the organization

4. Know where the problem begins and ends – remember not to “boil the ocean”

5. For additional help, complete the checklist below to confirm you have a well-defined problem circuited the SOLVE model. 

Perils & Pitfalls

Example of a solution statement: We need to hire more full-time employees to staff the call center because the number of calls

• If your problem statement tries to address several issues or problems, this will cause confusion later and may be an indicator you are “boiling the ocean.”

• If your problem statement contains the solution, you have short has increased.

• Jumping into a project without confirming the problem could waste time and resources especially if it was a one irritant.

• If you cannot clearly describe the problem, then you and others will struggle to solve it.

If you are able to answer these questions, then you have a solid foundation for proceeding to Scope the Opportunity.

Examples

• Poorly defined problem: It takes forever for a contract to be executed 

• Well-defined problem: It takes an average of 150 days for a standard contract to go through our internal review and clearance process resulting in complaints from nearly 25% of our vendors.

• Poorly defined problem: I had to rewrite the enrollment report 5 times this month. 

• Well-defined problem: For the past year, on average we rewrite the enrollment report 4 times each month, requiring 15 extra hours (which makes me want to look for another job).