> ## Content Index
> Fetch the complete content index at: https://www.cesarrg.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Backlogs
- URL: https://www.cesarrg.com/backlogs/
- Published: 2021-08-14T03:13:06.000Z
- Updated: 2023-07-17T06:34:22.000Z
- Author: César Rodríguez
- Tags: Design

#19 - Aug.2021

Huge product backlogs should be a symptom that you are probably trying to *predict* things that you don't know yet about your users. Is likely that you will end up having solutions searching for problems. And this is a waste.

Building a solution should be an iterative process - a constant discovery of confirmed/failed hypotheses to improve a *real* customer need. There is no rush in trying to map any single opportunity that comes to mind but, instead, you should focus on increasing your chances that you are building the [right thing](https://www.cesarrg.com/test-it/). 

![](https://storage.ghost.io/c/10/f4/10f4a52f-1b7d-4284-b66d-0fccfd9dc5da/content/images/2021/08/backlogs.png)

Anything that your map as a feature or [opportunity](https://www.cesarrg.com/product-discovery/) should be tightly linked to your product's goal; in other words, addressing a real pain-point of the user you're helping. An extensive backlog does not mean that your product is in better shape. Aim for a few *high-value* features to launch. Then listen, learn and improve. 

![](https://storage.ghost.io/c/10/f4/10f4a52f-1b7d-4284-b66d-0fccfd9dc5da/content/images/2022/12/sign_CRG2.png)

💡

 Interested in more ideas like this one? [Subscribe here](https://www.cesarrg.com/#/portal/signup) and get future posts delivered straight to your inbox. No spam, don’t worry. If you’re already a subscriber, thanks for being part of this journey.