A problem summary is a short description of the problem that your product solves. It is the primary way that DiscoveryBuddy uses to generate drafts for the different frameworks and models.
A problem summary should be written in the form of a sentence, and should include the following information:
- What is the project about overall?
- Who is the product for?
- What is the problem that the product solves?
- What is the solution that the product provides (overall)?
Examples of a good problem summary
Here are some examples of good problem summaries:
- UberGuide is a project that helps new Uber drivers getting started on Uber. New drivers have a lot of questions, and UberGuide is a easy way to get answers to the most important questions. It works by connecting new drivers with experienced drivers, and giving access to a database of most common questions and answers
- My project is a new way to find and book a hotel. It is a mobile app that makes it easy to find a hotel that matches your needs. It works by using a combination of machine learning and human curation to find the best hotels for you.
Why is a problem summary important?
A problem summary is important because it helps you to understand the problem that your product solves. By writing a problem summary, you can make sure that you are solving a real problem, and that you are solving it in a way that is unique and valuable to your target audience.
If you can't write a simple problem summary, it is a sign that you don't understand the problem that your product solves. This can be a sign that you need to do more research, or that you need to change your idea.
How to write a problem summary
DiscoveryBuddy will help you write a summary by reading all of the frameworks that you have filled out, and summarizing them using AI.
This can be done from the overview page.