Thi Chung

Thi Chung

Data Analyst | Data Scientist

About

Hi there! I’m in Data Science field. I’m excited about the opportunities this field offers to make a difference. I love exploring trends in AI and machine learning. My journey has taken me through various roles, from analyzing rare plant species as a Data Research Assistant at the Botanic Gardens of Sydney to exploring the European market as a Sales and Marketing Analyst Intern at Cinch. I enjoy using data to tell stories and make impactful decisions. But there’s more to me than just data! I have a passion for acting, singing, and cooking.

Badges

Tastemaker
Tastemaker
Gone streaking
Gone streaking

Forums

•

13h ago

How to turn customer support tags into a clear product roadmap

We gathered more than three hundred support tags during the last quarter. We still had trouble deciding what to build. I thought that tags that appeared times were the most important, but then we realized that half of those tags were coming from a single confusing button.

We organized support tickets by the workflow instead of by tag name. Then we counted how many paying accounts were affected by each issue. That revealed where small interface changes could eliminate groups of support requests.

Support ticket volume dropped by twenty two percent in six weeks after we fixed the three workflow bottlenecks. I now group feedback by the impact on workflow and by the number of paying accounts, not by raw support tag counts. How can I separate the loud edge case requests from the fixes that lower support load?

Google's new agent works on your product until a metric moves. Which one would you hand over?

An agent that chases a number will usually get you that number. I'd like to hear which of your numbers you'd be comfortable handing over, and which you wouldn't.

On 18 November Google Labs announced Stitch Loop, which it describes as a long-running product agent. I'm going by Google's own blog post, written by Justin Toupin, a director of product management at Google Labs. It's an experiment with a waitlist and I haven't used it. The post gives no pricing, no customer results and no stated limitations, so everything below is what Google says it does, not what anyone has seen it do.

The idea is that you connect your GitHub repo and your product context, meaning logs, user behaviour and feedback, through what Google says are over 180 integrations. Then you set up loops. Three come by default: security, latency and accessibility. You can add your own, and Google's example is improving checkout conversion.

Each loop has four steps. It suggests opportunities based on evidence from your product. It proposes one or more solutions with the tradeoffs. It builds the one you pick in a sandbox and opens a pull request. Then it watches the live data to see whether the number moved, and after the goal is met it keeps watching in case the metric slips.

View more