A feedback routine for running five products

Give each product a fixed slot every week

A routine for five products has one hard limit, which is your hours. Every product wants them, and the loudest one will take them all unless you assign slots. Start by giving each product a weekday for its deep review. With five products, Monday to Friday covers everything once a week.

Put each slot in your calendar as a recurring event with the product name in the title. The slot is not a promise to fix anything. It is a promise to read that product's new items and decide what happens to each one. Keep the same weekday every week. If a product's customers write mostly over the weekend, review it on Monday so you see the full batch.

Check the counts every day and nothing else

Each morning, open the dashboard and look at the New count for each product. That takes a few minutes. If one count is higher than usual, or a bug count has moved, make a note and move on. Do not read ideas or praise during the daily check. Those belong in the deep slot, and reading them in pieces makes repeats hard to notice.

The 30-day chart is the other view you might be tempted to watch daily. Glance at it the morning after a release, and otherwise leave it for the weekly review.

What order should the triage follow?

Every deep slot follows the same order, so the most urgent work always comes first:

1. Bugs first. Open every New bug. Use the page URL and browser saved on each item to reproduce it. Then fix it, move it to Planned, or write a short internal note explaining why it is not a bug.
2. Ideas with repeats. Search the product's inbox for the two or three words customers use most. Count distinct people, not messages. A single request with a clear reason can go to Planned later. A request with no context can close with a note.
3. Praise. Read it, copy any line that describes what the product does well, and move on. Praise tells you what to protect when you change things.
4. Close the rest. Every item that stays New after its slot is a decision you postponed. Close it, plan it, or write a note saying what you are waiting for.

Nothing should stay New when its slot ends. If it does, your daily count will keep the product on your mind without ever moving it forward.

Time-box each product and stop on time

Give each product a fixed box of about 45 minutes. Set a timer. When it rings, stop, even in the middle of an idea. Before you close the tab, write one line in your notes app about where you stopped, such as "Product B: read bugs up to Tuesday, ideas not started". Next week, start from the New filter, not from memory.

Time boxes make the routine sustainable. Without them, one loud product takes the whole afternoon and the quiet ones slip for a month. The box also forces a choice. If an item needs a longer look, it becomes a task for the next slot instead of an open-ended hour.

What do you do when one product needs extra time?

Launches, outages and migrations change the picture. If a product shipped a large change on Friday, move its slot to Monday and give it a short second pass on Thursday. Take the time from the product that had the least in its slot last week. Do not skip a product for a whole week, even if all you do is read its bugs.

What to skip when the week gets busy

When time runs short, skip in this order: praise first, then ideas with a single request and no context, then the 30-day chart. Never skip bugs. A bug left in New for two weeks is often the one a customer writes about again, and that second message is harder to answer than the first.

Keeping the routine honest over several months

Every month, read your closed items from the previous four weeks. If you closed a request that later came back from three people, your close note was too quick. If a product's slot ran out every week, its box is too small or it needs a different day. The routine is a tool you adjust, not a rule you obey.

Watch for one drift in particular. Teams often start the routine with real discipline and then let the daily check quietly replace the weekly slot. The counts feel like progress, but nothing moves from New to a decision. If you notice the weekly slot has been skipped twice in a row, cut the daily check down to bugs only until the slot is back.

How to run this routine with Escuta Produto

Escuta Produto gives each product its own inbox, so the weekday routine maps directly onto the dashboard. Add the five products, point each product's notification webhook at the channel you watch, and use the status and type filters as your starting point for each slot. The daily check reads the counts. The deep slot uses the filters and text search. Alerts tell you a bug arrived, but the decisions happen in your slot, not in the chat channel.

If you want the reasons behind one inbox for all products, read one feedback inbox for many products. To order your slots by impact, read how to choose which product to work on.