## Explain Ownership of a Project Business Metric Choose one technical project and explain how its primary business success metric was selected. Identify who proposed, challenged, approved, instrumented, and monitored the metric, and clarify your own contribution. Show how the metric connected engineering work to a user or business outcome and how you guarded against optimizing a misleading proxy. ### Constraints & Assumptions - Distinguish the business outcome from delivery milestones and system-health metrics. - Do not claim sole ownership if product, analytics, finance, operations, or another group made part of the decision. - Include the metric's definition, denominator, observation window, and important guardrails. ### Clarifying Questions to Ask - Is the interviewer asking about metric definition, target-setting, instrumentation, or all three? - Was the project evaluated through an experiment, an operational rollout, or observational results? ```hint Reconstruct the decision trail Map each metric decision to the person or function that supplied evidence, authority, implementation, and review. ``` ### What a Strong Answer Covers - A precise outcome metric and why it represented value better than obvious alternatives. - Clear ownership across proposal, approval, instrumentation, data quality, and ongoing review. - Personal contribution stated without erasing cross-functional decisions. - Guardrails, segmentation, and evidence used to detect proxy gaming or harmful side effects. ### Follow-up Questions - What would make the metric improve while the product actually became worse? - Who had authority to change the target after launch? - How did you verify that the instrumentation matched the metric definition?