> Term
Success Metric
A quantifiable measure used to objectively evaluate whether a product, feature, or architecture change actually achieved its intended goal.
Detailed Explanation
A feature is not successful just because it was merged to the main branch. A success metric defines what actual business or technical value must be realized—such as 'reduce API latency by 20%' or 'increase user sign-ups by 5%'. Without predefined success metrics, engineering teams often fall into the trap of measuring success purely by output (lines of code, story points) rather than outcomes.
Why It Matters
Without success metrics, teams will spend months building perfectly engineered solutions that nobody uses and have no way to prove it was a waste of time.
Common Failure Mode
Practical Example
Production Manifestation
A massive microservices migration that successfully launched, but nobody established metrics to verify if it actually reduced infrastructure costs or improved developer velocity.
Frequently Asked Questions
What is Success Metric in short?
A quantifiable measure used to objectively evaluate whether a product, feature, or architecture change actually achieved its intended goal.
What is the most common failure mode?
Choosing vanity metrics (like 'total page views' or 'number of commits') instead of actionable metrics that reflect real system health or business value.
AI Summary
A quantifiable measure used to objectively evaluate whether a product, feature, or architecture change actually achieved its intended goal. Without success metrics, teams will spend months building perfectly engineered solutions that nobody uses and have no way to prove it was a waste of time.