Spotting feedback patterns across products

Why the same complaint shows up in several products

Products built by one person or team often share parts. The login screen, the billing flow, the email that confirms an account and the code that loads a profile frequently come from one codebase or one library. When one of those parts breaks, customers report it in every product that uses it, each in their own words. One person writes "I can't get back in", another writes "my reset link is dead", and a third writes "I keep getting logged out". Each message looks like a separate issue in its own inbox.

That is why a routine that reads each product in isolation misses the big fix. You see five small bugs and fix five small things, when one shared component needed one repair.

Label cross-product themes in internal notes

Escuta Produto has no tags, so give each cross-product theme a consistent label in the internal notes of the items it touches. A simple convention works: start the note with the word theme, followed by a short name such as login or billing. Spell the label the same way every time, because a spreadsheet filter or a notes search only finds the exact words you used.

Keep the list of themes short. Five labels you use every week are more useful than twenty you used once. A label is private to your dashboard, so it never reaches customers, which makes it a safe place for your own reasoning.

Search each product for the same words

Once a month, search each product's inbox for the words that matter across your products: login, password, sign in, billing, invoice, email and export. The text search runs inside the product you have open, so repeat the search for each product. Write down the number of distinct people per product for each word.

If the same word shows up in three products within the same two weeks, you have a pattern worth investigating, even when each product has only a handful of messages. A pattern is a question, not a verdict, so check it before you act.

Find the shared component behind the complaint

When a pattern appears, trace it to the part that the affected products share. Ask what they have in common. Is it the same authentication library, the same payment provider, the same transactional email service or the same onboarding screen? Open the code for one product, look at its imports or configuration, then compare it with the others.

Write the answer in the theme note, for example "theme: login, shared auth package, affects three products". That one line tells you where the fix belongs and saves you from repeating the search next month.

Count across products in a spreadsheet

Export each product's feedback as CSV. Each file covers one product, so combine them yourself. Add a product column to each file, paste them into one sheet and filter by the theme words. The UTF-8 files open cleanly in Excel and Google Sheets, so you can sort and count without a cleanup step.

Count distinct people, not rows. A customer who wrote twice about login in two products is one person with two issues, and a single fix probably helps them both times. Use the email column where it exists, and mark rows without an email as estimates.

Decide whether the pattern is worth a shared fix

Not every repeated complaint justifies a shared fix. A pattern across three products is strong when the shared part is the cause, and weak when the words only look similar. For example, "export is slow" in two products may have two different causes. Check the reproduction steps and the page URLs before you decide the code is shared. Also ask whether the problem is a setting rather than shared code. A wrong configuration in one app can look like a shared bug until you compare the two configs side by side.

Announce the fix in every product

Fixing a shared component once is the efficient part. Telling customers is not. Reply to each person who asked about the problem, in each product's inbox, with the same short message: what was broken, what changed and what they should do now. Set the status to Done on each item once you have replied, so the inbox shows the work is finished.

A shared fix that ships quietly leaves customers wondering whether you noticed. A reply in each product closes that loop and tells the person they were heard, which is the goal of this whole routine.

Keep a short record of which items you answered and when, in the theme note. The next time a similar issue appears, you can see whether the last fix reached everyone who asked.

How to find cross-product patterns with Escuta Produto

Keep one inbox per product, use the same type and status rules across them, and run a monthly search for your shared words. Store the theme labels in your notes, export each product's CSV when you need a count, and merge the files in a spreadsheet. The notifications guide explains how each product's alerts reach its channel, so a login complaint in one product does not get lost in another. For the reasoning behind one inbox, read one feedback inbox for many products, and for the weekly habit that makes this search possible, read a feedback routine for five products.