Metrics question

The users of a mobile app complain that the app is slow. As a product manager, what will you do about it?

Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.

What this question tests

Whether you can turn a vague complaint into a measurable diagnosis and action plan.

Clarify: define slow, is it app launch time, screen load, or search results lag, and on which devices.
Instrument: pull performance metrics, like time to first render and API response times, segmented by device and OS.
Prioritize by impact: find the specific screen or flow driving most complaints and affecting the most users.
Diagnose root cause: check for bloated payloads, unoptimized images, or slow backend queries.
Fix and validate: ship a targeted fix, then measure the metric improvement before declaring it resolved.
Set an ongoing guardrail: a performance budget alert so regressions are caught before users complain again.

Moves past the vague complaint to a specific metric, like time to interactive over 4 seconds on the listing page (assumption).
Segments by device, since older Android devices are often the real source of slowness complaints.
Sets a performance budget as an ongoing guardrail, not a one-time fix.

Jumping to a fix before instrumenting to find the actual bottleneck.
Treating all users as having the same experience, ignoring device or network segmentation.
No mention of a guardrail to prevent regression.

Chapters of the AI PM course that teach what this question tests.