Best Practices

No more silos for your product feedback

Silos. Tunnel vision. Operational misalignment. They go by many names, but silos in the workplace have negative effects on productivity, morale, and even product quality. 

Product quality can suffer when one team, like support, knows about a product issue, then reports it to engineering. Then engineering, not having enough data about a given bug report, fails to take action quickly and goes about their other business. 

And when product quality suffers, so does the customer experience. Silos can result in bugs that never get fixed, disappearing into a black hole because engineering lacks sufficient data to prioritize the issue, or they have a hard time reproducing the problem.

The Great Disconnect

There often is a disconnect between the support and marketing teams and the engineering and product teams as they struggle to align on which quality issues or bugs need to be addressed. The scenario usually plays out like this: the support team gets a few reports about a problem with the product, so a support engineer files a bug with engineering, mentioning the examples. Engineering gets the report, but since it only contains a few anecdotes, it’s unclear how prevalent the issue really is. They may not have good information as to whether the issue is new, how long it’s been around, whether it’s spreading quickly, and so forth. 

And in an environment where everyone is moving fast, communicating that information may not be easy. 

unitQ Monitor Tears Down the Silo 

The seamless communication and single source of truth for product feedback that unitQ Monitor, unitQ’s AI-enabled monitoring platform, provides helps to break down the silos between support and engineering. unitQ Monitor turns qualitative feedback into quantitative data, so engineers now have the hard numbers to help prioritize their fixes.

Providing this indisputable data to engineering is one of the main benefits that support and marketing leaders frequently tell us, as it has helped them get their issues fixed quickly instead of just lingering in production.

Fixing issues fast improves the customer experience, which has the added benefits of decreasing customer churn and reducing the amount of tickets customers file.

If you need help tearing down the silos in your company, request a unitQ demo today.

Best Practices

Quantifiable human data: The missing link for observability and monitoring

You’ve invested many resources — human, technological, financial — building out your product’s monitoring and observation systems up and down your entire tech stack, thinking you’re finally able to catch any issue that may arise. And while you’ve automated capturing all the machine data, you’re still missing out on one crucial set of data: human data, which comes in the forms of product reviews on app stores, social media posts, and even the bug reports your customers submit. 

Monitoring all these different systems is a very manually intensive process, often done by disparate teams that may not always be aware of what the other teams know when it comes to feedback on your product.

One Ring to Rule Them All

That’s why unitQ Monitor, our AI-enabled platform, is the one ring to rule all monitoring. It consistently finds issues that should be caught lower in the stack, where your machine monitoring occurs, as sometimes these systems do not have full coverage. Your observability platform may be full of machine data, but it won’t know about the poor reviews your product is getting in the app stores because of a long-standing login issue.

Quality issues tend to arise due to external factors, like network connectivity or third-party integrations. And your existing monitoring systems are unable to see into these opaque areas.

It’s very difficult to instrument certain critical engagement flows, such as “is the password reset link working?”, “did we double bill many of our users?”, or “did a user pay for an upgrade but didn’t receive the feature set which was promised?” Also, content changes and bugs related to them are hard to monitor with the most popular monitoring tools.

unitQ Monitor takes qualitative feedback and turns it into quantitative data. Your engineering, support, marketing, and product teams can all see the same data all in one place, keeping them aligned on which product quality issues are most pressing and most prevalent. 

But don’t just take our word for it. “We love unitQ Monitor! It used to take us so much time to identify and quantify issues,” said Anja Richter, the head of QA at LOVOO. “unitQ Monitor has really improved the workflow between our QA and Product teams, because we now have all the data we need to make decisions in real-time. Plus, it’s great that we can now search everything from one place!”

Do you want to find out what quality issues you’re overlooking in your product? Request a demo today.

Best Practices

Reduce support ticket volume by fixing ongoing quality issues

The best support ticket is the one that never gets filed. At unitQ, we’ve found out that the best way to keep your customers from filing support tickets is by fixing long-standing quality issues.

We’ve noticed that many companies have persistent quality issues that never seem to get fixed. This usually happens because the issues get lost in the noise from the overwhelming amount of user feedback from multiple channels a company gets day in and day out. 

Turning User Feedback Into Actionable Insights

But there’s a way out: unitQ Monitor, our AI-enabled monitoring platform, can dig through all the noise from support tools like Zendesk, Helpshift or Intercom, to public app review sites like the App Store or Google Play Store, taking all this qualitative user feedback and turning it into a quantitative goldmine.

Say, for example, you see a report that your password reset link isn’t working. You might think that it was user error and the user just logged in with the wrong account. However, after a few days of unitQ Monitor analyzing your user feedback, you may discover that the login issue has been persistent and ongoing for days or weeks!

Fixing Long-Standing Quality Issues

We consistently see outcomes like this — whenever a new partner goes live with unitQ, it’s like they turned on the lights in a dark room. Armed with actionable data directly from their users, they act quickly to identify the root cause of the problem and fix it. As a result, they dramatically reduce the volume of support touches — whether email, chat, tickets or phone calls — since these issues stop being reported over and over again. 

The end result is a higher unitQ Score, less user churn, fewer 1-star reviews and fewer support tickets. unitQ Monitor does all this by leveraging your existing data assets, without asking your users to do anything differently, like reporting more bugs! What’s more, your support team becomes more efficient and can now spend more time on the right tasks.

But don’t just take our word for it. Our partners are seeing these dramatic declines in support touches soon after they start using unitQ Monitor. LOVOO saw their support ticket volume drop by 40% in the first months after going live with unitQ Monitor. Pandora’s support ticket volume dropped by 10% in the first 45 days. And Strava estimates that it will see as much as a 20% reduction in support ticket volume.

Next Steps

So while it’s a great idea to invest in tools that deflect support touches, like chatbots and knowledge bases, it’s an even better idea to invest in fixing quality issues that generate the support touches in the first place!

If you want to see how unitQ Monitor can help reduce the burden on your support team, schedule a live demo today.


Is Your Customer Feedback Getting Lost Without Translation?

Chances are good that your company operates online, which means your customers can live anywhere and can speak many languages. And chances are also good that your team doesn’t speak every language your customers do. So how would you know if someone who speaks a language you don’t understand has a problem with your product?

Translations require a lot of time, money, and effort to do correctly. And even then, you may not cover all the languages your customers speak. You would need to pay either a company that specializes in translations, or else use a third party tool to do the job.

The good news is that with unitQ Monitor, we do all the translating for you! unitQ Monitor translates every piece of your product’s feedback into English. To understand why this is important, let’s revisit an incident that planted the seed for unitQ itself.

Fix Bugs Faster, Save Money, Improve Customer Goodwill, Reduce Churn

The founders of unitQ previously started another company called Skout. Skout is a mobile social media service with users around the world. One time they had a login bug that was visible only to its Polish users. No one on their team understood Polish, and no one was aware that there even was an issue. The company estimates that it lost hundreds of thousands of dollars in revenue because they didn’t act on that bug for months. Had they been using a service like unitQ, they would have known right away that their Polish users couldn’t log in, and they could’ve fixed the bug quickly, saving the company a lot of money, not to mention improving customer goodwill while reducing user churn. 

When you look at your unitQ Monitor, all your customer feedback is already translated into English, which can help you fix issues that affect customers in non-English speaking locales. However, you can also see the original report in its native language. 

Once translated, it’s much easier to structure and categorize your feedback. Then unitQ analyzes the content of each piece of feedback, detecting trends and patterns based on the words used, possibly surfacing issues before you even are aware of them. From here, the feedback can be shared with engineering, enabling you to make data-driven decisions on which problems need fixing, and in what order.

If you haven’t tried unitQ yet, request a demo today!

Best Practices

What Time Is It? It’s Time to Fix!

First in a series of posts on breaking the vicious cycle of poor product quality.

The software industry has done an excellent job developing a set of growth metrics: DAU, MAU, DAU/MAU, retention/return rates, and so forth. For product quality or user experience, no one has really developed any metrics, until now. It is very hard to improve what you cannot measure. As a result, we developed two quality metrics: the unitQ Score and unitQ TTF.

unitQ TTF (for Time to Fix) essentially describes how much time it takes for a company to fix an issue in production. A shorter time to fix results in a higher unitQ score, and less time an issue has to impact users, which means fewer tickets to your support team and lower negative sentiment.

unitQ Helps Decrease Your Time to Fix in Three Areas

  • Issue detection
  • Alignment among the teams within your organization
  • Fixing issues

Early detection of quality issues reported by your user base means there is no need to wait until an issue snowballs into a crisis. With unitQ Monitor — our AI-enabled platform that empowers you to take a data-driven approach to identifying, prioritizing, and fixing product quality issues in the most efficient way — you configure alerts to trigger when a specific threshold amount of feedback is crossed, or when the percent change of feedback over a given time period is exceeded. When an alert triggers, it sends a notification to PagerDuty or Slack, so your team knows almost immediately about the issues.

Align: Decisions to deploy resources to fix certain quality issues are made much faster with a Single Source of Truth — data cross-functional teams can understand and rally around.

Typically, different teams in a company may not be looking at the same information. The support team may learn about issues from bug reports, while the marketing team may notice some trends in their social media feeds. unitQ Monitor collects all your customer feedback, from every source — from public sources like app store reviews and social media to private sources like Zendesk or Intercom — into one searchable data store, a single source of truth. Now everyone in your company — from your engineers and support team to the marketing team — armed with this single source of truth can very quickly decide to deploy resources to fix quality issues.

It goes without saying that the more data you have about a problem, the easier it is to fix it. unitQ Monitor provides additional data from a number of sources to help you triage and fix quality issues: 

  • Translated content: All user feedback is translated into English, which can help you fix issues that affect customers in non-English speaking locales.
  • Custom tags: Add unique labels, categorizations, and other helpful references to any user feedback. If you are using Zendesk, tagging is bidirectional between unitQ and Zendesk.
  • Metadata like platform, language, country, product version.

Since the engineers tasked with fixing the quality issues have direct access to all this information, as well as a timeline of when they started, the time it takes to reproduce and ultimately fix the bugs contracts significantly.


We have the data to prove the impact of going live with unitQ Monitor. When your unitQ TTF goes down and your unitQ Score goes up, you experience:

  • Fewer support touches on the same issue over and over, resulting in a top of funnel impact for your support team.
  • Fewer 1-star reviews and more 5-star reviews.
  • Increased net sentiment in all user feedback data.
  • Decreased churn.
  • Increased engagement and conversion, which ultimately means more revenue!

unitQ Score Improvement

Time to Fix Improvement

Improving your Time to Fix is one way to break the vicious cycle of poor product quality. Keep watching this blog for more tips and tricks on this topic.

And to learn how unitQ is helping category-leading companies like Chime, AppLovin, Pandora, and Strava break out of the vicious cycle, request a demo today.


The Life Cycle of a Quality Issue

The not so lonely journey of a product issue through unitQ Monitor

Did you ever wonder how a quality issue becomes a quality issue? 

Let’s start by defining a quality issue. A quality issue is any user friction with your product, where your product doesn’t work the way the user expects it to work. This includes software bugs obviously, but quality issues are more than that. Quality issues are also anything to do with the overall user experience. Quality issues are not matters of taste, like feedback about the site’s look and feel; nor are they issues like forgotten passwords.

Now let’s talk about the journey a quality issue takes through unitQ Monitor

Every quality issue follows the same pipeline before you see it in your unitQ Monitor. Quality issues can come from many sources: your customer ticketing system like Zendesk, app store reviews, and social media. unitQ Monitor tracks all this data for you. The first thing it does is clean the data. During this phase, we trash around 10 to 20% of data during cleaning to avoid introducing unwanted noise into the Quality Monitors, such as duplicate reports, spam, email headers, long response threads and other irrelevant data. unitQ Monitor tags this feedback as trash but does not delete it.

Next, unitQ Monitor cleans, normalizes and translates the remaining data

Cleaning involves removing all personally identifiable information, like names, addresses, email addresses, and so forth.

Normalizing involves applying structure to the data, like geographic data and user sentiment. User sentiment can be positive, neutral, or negative. Quality issues tend to fall into negative or neutral sentiment. 

Then it translates content into English. Sometimes, product issues can slip through the cracks if you aren’t able to translate customer feedback into a language that you understand.

Now the machine learning kicks in, determining which of the remaining issues are actual quality issues

Most issues are not quality issues, rather they are feature requests, compliments or props, and password resets and other expected use cases. unitQ staff constantly reevaluates and retrains the ML model so it is always growing in accuracy.

The quality issues get assigned to one of hundreds of Quality Monitors, which are collections of quality issues that are all related to the same product defect.

At this point, these quality issues are now visible in your unitQ Monitor. Their presence can trigger alerts you’ve already set up; these alerts can notify your team through PagerDuty and Slack. You can also open tickets in Jira so your engineers can track and fix the issues.


Quality issues serve as canaries in the coalmine to make you aware of problems before they get too big, providing a way for you to make data-driven decisions so you can more accurately prioritize the issues you need to fix first, and fast. By acting quickly, your product quality should quickly improve, as should your unitQ Score.

To learn how unitQ is helping category-leading companies like Chime and Strava detect and fix urgent issues faster and incorporate crucial user feedback into their product decisions, request a demo today.