The redesign they loved, and the problem it hid
An evaluation that confirmed users loved the rebuilt Telemetry Explorer, then looked past the applause to the harder, more valuable problem underneath: people were not confident they were querying the right data to answer their question.
Org
Google Cloud
Surface
Telemetry Explorer (Cloud Monitoring)
Role
Lead Researcher
Team
With product, design, and engineering on Cloud Monitoring
Timeframe
Private preview study
Sample
In-depth interviews paired with a survey, across skill levels
Methods
Senior signals
TL;DR
Telemetry Explorer is the rebuilt tool engineers use to chart how their cloud systems are behaving. Before its public launch, the team wanted to know whether the new design beat the old one. It did: a strong majority of users preferred it, and they loved being able to compare several metrics on one chart. But reading the interviews and the survey side by side, I saw the same struggle in both, no matter the company or skill level. People were happy with the new layout but not confident they were building the right query to answer their actual question, especially once it got complex. I reframed the readout around that gap, turning a simple thumbs-up into the brief for the next phase: lean on the interface itself to guide people toward the right query.
Systems map · Systems thinking
How a thumbs-up turned into a roadmap
The study was framed as a simple go or no-go: did the rebuilt explorer beat the old one? It did, and stopping there would have produced a clean, satisfying, and slightly hollow readout.
The redesign itself was a real improvement. It moved the chart from a cramped side panel to the center of the screen, brought controls that used to be buried in menus into plain sight, and let people stack and compare several metrics on one chart.
The applause was hiding the real problem
Reading the interviews and the survey together, one thing repeated regardless of company or skill level: people liked the new layout but were not confident they were querying their data the right way. The satisfaction scores were really measuring the layout. The thing that would make or break the product sat one layer down, in building the query itself.
- A clear preference. A strong majority preferred the rebuilt explorer to the old version, which felt cleaner, faster, and easier to learn.
- The real struggle. The hardest task was not the layout but choosing the right metrics and shaping them into the right query with confidence; comparing several queries at once ranked close behind.
- People learn by doing. Most people learn the tool through trial and error rather than documentation or videos, so the interface itself has to teach, with worked examples and in-product guidance.
- A loved feature with gaps. Comparing several metrics on one chart was the most valued new ability, yet many found those busier charts hard to read and some never noticed the feature at all.
Built-in quality check
One survey item was written as a deliberately extreme statement, that the tool was already perfect and could not be improved, to confirm people were reading carefully rather than agreeing by default. They disagreed, which both validated the responses and showed they saw room to grow.
That reframe pointed the next phase at the query itself: guide people toward the right one with examples, in-product help, and eventually plain-language querying, so getting it right stops depending on trial and error.
Finding → strategy chain
From a launch check to a roadmap
Brief
Validate the rebuilt explorer before its public launch.
Method
Pair in-depth interviews with a survey, across skill levels.
Headline result
Users clearly prefer the new layout over the old one.
Look underneath
The same struggle everywhere: confidence building the right query.
Reframe
From “is the redesign good” to “guided querying is the next problem.”
Roadmap effect
Aim the interface at examples, in-product help, and plain language.
What I almost missed · Critical thinking
What I almost missed
The study was set up to answer one question: do users like the rebuilt explorer? They did, clearly, and the easy version of this readout was a single slide that said success, ship it. That would have been true and nearly useless. What stopped me was reading the interviews and the survey side by side rather than separately. The same struggle surfaced in both, at every skill level: people were not confident they were building the right query to answer their question, especially once it involved several steps or several metrics. The satisfaction scores were measuring the layout. The real risk to the product sat one layer underneath, in the querying itself.
Verbatim · field quote
“The hardest task is understanding the different metrics and analyzing the data to spot patterns and trends.”
Enterprise customer, interview participant
Impact
What changed because of the work
Outcome 01
Cleared for launch
The redesign tested well and went to public preview.
Outcome 02
Roadmap reframed
Next-phase work shifted from layout polish to guided, example-led query building.
Outcome 03
Assistant concept
Seeded an in-product assistant and plain-language querying so confidence would not depend on trial and error.
Outcome 04
Logs and traces next
A stronger querying experience became the foundation for bringing logs and traces in alongside metrics.