How do you measure a new feature's success beyond bugs and uptime?

This question tests if you think like a product-minded owner, not just a coder. A strong answer connects success back to the original business goals (e.g., increase engagement). It then outlines specific user behavior metrics (adoption rate, key action completion) and business impact metrics (retention, conversion), and names the technical tools to get this data (e.g., Amplitude, Datadog, backend DBs). A major red flag is answering with only system health metrics (latency, errors) or deferring entirely to the product manager.