As a solution designer or marketer, tuning into the context and experience of a person in a predicament is fundamental. There is no side-stepping these questions:
A cogent, well-crafted problem statement answers these questions and provides clarity of context to solution designers and product marketers.
Why a Problem Statement Is Important
A problem involves a person in the context of a specific predicament. The problem is the raison d'être for any solution under consideration and, by extension, the solution designer and marketer engaged in addressing it.
A person experiencing a problem expresses it through emotion. Describing the circumstances that are causing that emotion, in words a user would use however strong or subtle, provides a foundation of empathy through which to envision an ideal solution. It is important to not overlook the emotion because it creates personal resonance with the problem and with the solution being marketed. A problem statement depicts the moment of opportunity when a transformational solution would make all the difference in a person's quality of life.
From a marketing perspective, borrowing a concept from Pragmatic Marketing, a “market” is a group of people who share the same problem. Therefore, understanding and clearly defining the problem is the cornerstone of any solution to be created and/or marketed. This makes a highly refined problem statement or set of statements all the more valuable.
Who needs or uses a problem statement? Solution designers and architects need to understand the context under which a problem occurs. The more empathy the designer or architect has for the person experiencing the problem the better. A product manager needs to know out of all the problem statements that exist, which ones are urgent and pervasive. That set represents the high potential candidate problems to research, assess, verify and build a business case for solving.
How To Create a Problem Statement
Here is an effective way to create a statement that expresses an understanding of the context and the problem so that it informs and influences solution designers and architects.
A problem statement is a sentence or two that contains these descriptive elements:
Actual Statements and Mad-Lib Styled Templates
You may be fortunate and have the ability to describe the problem statement by simply transcribing what you have actually observed people say in the context of experiencing a problem. That's a preferable way in which to produce a problem statement.
But, if you don't have that form of recall handy, or if you need some help constructing a statement that can be easily understood, then some fill-in-the-blank templates might prove helpful to help demonstrate what this looks like.
To that end, here are some Mad-Lib styled templates:
Here are two examples of problems statements based on conversations I've or observations I've had in just the past day:
Best Practices and Pitfalls to Avoid
Problems Lead to Solutions
How To Create an Ideal Solution Statement
An ideal solution statement is a sentence or two that:
Here are ideal solution statements based on the aforementioned problem statements:
Best Practices and Pitfalls to Avoid
An ideal solution statement can easily feed into agile development practices in the form of a user story. User stories are used in agile application development solutions as a means of creating a backlog for product development.
The canonical form of a user story is: As a _____ I want ____ so that ____.
Here is how our example statements can be transformed into a user story that can be used by an agile development team:
In addition to user stories, the problem statement described herein offers a richer contextual insight for solution designers to understand how the problem is experienced by an envisioned solution user.
The combination of a problem statement and an ideal solution statement increases the potential for designers and architects to empathize with the problem. This insight improves their ability to design a solution that resonates with the intended user. It also improves the ability for a product manager to strategically position the solution in the market, communicating with resonance through marketing channels and sales efforts.
Subscribe to my free blog updates to receive content that vividly describes the techniques and leadership skills that embody the practice of agile design methods. The blog contains not only my ideas on the topic but the insight of others who actively work and thrive wholeheartedly in the realms of collaborative creativity and solution design.
Learn the Art of
Successful Agile Design
(boo'-dro) - I help people design solutions collaboratively using agile design methods. I have 30+ years of experience in designing software solutions and business processes, leading cross-functional process improvement teams as a business analyst, and helping product managers define and position products using Pragmatic Marketing. I am passionate about user experience design, dog training, beating drums in musical ensembles and collaboratively creating solutions with people.