DEV Community

Cover image for What Problem We Solve
Anton Korzunov
Anton Korzunov

Posted on • Edited on

What Problem We Solve

There is a single question you should ask yourself a few times a day. Every time it will sounds a little different, and every time it will require an absolutely different answer.

Ask yourself:
   `What Problem We Solve`
   `Which Problem We Solve`
Enter fullscreen mode Exit fullscreen mode

👉 Where What/Which is a choice between a number of possibilities.

The System

What problem we solve?

Is there any need to solve this problem? This problem, in this area.
Does anyone need your solution?

Which problem we solve?

Where are many different kinds of a single problem. Do we know which one we are going to solve?
Who is solving others?

What Problem we solve?

Is it a problem? Will anyone be happy if we resolve it? Does anyone ready to pay for it?

What problem We solve?

Are we the right people to solve this problem? Are we able to do it? Are we missing something or actually have everything to make it happen?
Might be another team can do better?

What problem we Solve?

Well, do we know what solve the problem? Can we understand that the problem is actually solved? Are we going to solve it completely or just make it a little better?

Do we have a solution already? In this case, go backwards and find the problem it can be applied to efficiently.


Actually sounds very SIMple (Specific, Important, Measurable) framework, as many others which were created to help you to 1) start something, 2) maintain, and 3) finish.
Take a look at Why What How post for details.

Does it work?!

While it can sound too simply - that simplicity is the key to efficiency.
Just ask yourself this question every time you need to make a next step to understand where you are, and clarify how to make that next step.

Firstly, it works like planning and inspiration. You need to find the right problem to solve. Or you can try to find the right problem for a solution you just envisioned.

Secondary, it works like QA-kickoff, ensuring that the next step is worth making. That we should try to solve this problem, not find a better problem to solve.

Then it works like… QA-kickoff, ensuring that the right team was given the right task. Maybe it’s the right time to get more people on board.

And at last, it defines The End Goal. Explains why it will be a solution. Why people will need it, use it, and be happy with it.

Ask yourself

  • 🤷‍♂️ Why you need a new phone. What problem it will solve?
  • 🤷‍♂️ Why you need new work. What is the problem?
  • 🤷‍♂️ Why this PR should be merged. What problem does it solve?
  • 🤷‍♂️ Why should we apply the principles above? We?

Prior art

The origin of this principle is The API Book by Twirl.


Don't have an answer to any part of the Question? Probably you should solve another problem.

Which? 🤔 What? 😲 Oh! 🙀

Top comments (0)