Szymon's Zettelkasten

Powered by 🌱Roam Garden

PN: Problem space vs. solution space

Reference: PN: O The Lean Product Playbook p. 14, 16


The problem space addresses what the product has to accomplish or enable the user to accomplish. It's the benefits, jobs to be done, and end result that the product should deliver.

The solution space tells you how your product will solve the problem. It consists of functionalities, design, and technology used to implement the product.

“What” is problem space and “how” is solution space.

What's more, problems don't change that rapidly because people will always have similar desires that will need to be met (think of Maslov's hierarchy). Solutions change way more quickly – each new invention can drastically change the landscape of 'how' we solve particular problems (think of electricity, the first computers, the internet).

The problem and solution space need to be kept separate. Because customers don't care about your solution. They only care about their problems. And they will always choose the product that solves their problem in the most effective way.

Therefore, if you want to create a product, you should always start with the problem space and only then get to the solution space. If you do the opposite, you will drastically limit the possibilities of solutions to the problem because you will be constrained to the functionalities, design, and technology you have defined in the solution space. Starting with the problem space invites novel possibilities because it removes the constraints. Starting in the solution space is like trying to decide what to wear without knowing whether it snows or the sun is shining.

For instance, if in 1900 you said, "I need a carriage that will let me make 100 kilometers in 5 hours" you would exclude the possibility of creating a car because it must have been a carriage. A better way to phase it would be, "I need a vehicle that will let me make 100 kilometers in 5 hours."

As a rule of thumb, you should always start with the question "What amazing benefits can we give to our users" and then figure out the rest.


Relevant notes:

The product OKRs: OKRs are similar to the relationship between the problem and the solution. It's about stating 'what' needs to be accomplished and leaving the 'how' to the team.