You cannot measure success if you never defined it

Strategiesglossary×StrategyStrategy is a high-level plan that defines long-term goals and the approach to achieving them.Open glossary term→ are often built around goals that feel directionally right (improving experience, increasing engagementglossary×EngagementEngagement refers to how users interact with a product, content, or experience, including actions like clicks, time spent, and interactions.Open glossary term→, driving growth), but when you look closer, those goals are rarely translated into something concrete enough to measure. At the beginning, this doesn't feel like a problem. There's alignmentglossary×AlignmentAlignment is a shared understanding of goals and priorities across teams and stakeholders, strong enough that people act consistently without checking first. It is not the same thing as everyone agreeing.Open glossary term→ around intent, teams understand broadly what they're trying to achieve, and work begins to move forward. Progress is visible in the form of new features, redesigned journeys, and improved interfaces. From the outside, everything appears to be working. The problem only becomes visible later, because without a clear definition of success, there's no way to know if any of it is actually effective.

Ambiguity is often what allowed the goal to be agreed in the first place. Improving the experience means something slightly different to every person who nodded at it, and that shared approval is worth more in the room than a specific target would have been. The cost arrives later, when nobody can say whether it happened.

What tends to happen instead is that proxies are used. Deliveryglossary×DeliveryDelivery is the process of building, testing, and releasing a product or feature.Open glossary term→ milestones become a substitute for progress. Outputs are mistaken for outcomes. A new featureglossary×FeatureA feature is a specific piece of functionality within a product that delivers value to users. It represents something users can do or experience as part of the overall product.Open glossary term→ is launched, a journey is redesigned, a platformglossary×PlatformA platform is a system or environment that enables users, services, or applications to interact, build, or operate.Open glossary term→ is updated, and each of these moments is treated as evidence that the strategy is working. In reality, they're only evidence that work has been completed.

When success isn't clearly defined, it becomes easy to reinterpret results in a positive light. If conversionglossary×ConversionA conversion is any action a user takes that aligns with a defined goal, such as making a purchase, signing up, or completing a task.Open glossary term→ hasn't improved, engagementglossary×EngagementEngagement refers to how users interact with a product, content, or experience, including actions like clicks, time spent, and interactions.Open glossary term→ gets highlighted instead. If engagement is flat, attention shifts to trafficglossary×TrafficTraffic refers to the number of users visiting a website, app, or digital product over a given period.Open glossary term→. There's always another metric that can be used to justify progress, but none of it provides a clear answer to the original question: is this actually working?

Metric substitution is easy to spot once you know the shape. If the number being reported this quarter is not the number that was promised last quarter, and nobody has mentioned the change, the measure is being chosen to fit the result rather than the other way round.

A strong strategyglossary×StrategyStrategy is a high-level plan that defines long-term goals and the approach to achieving them.Open glossary term→ doesn't just describe what's going to be done. It defines what will be different as a result. That difference needs to be specific enough to measure, but also meaningful enough to reflect real impact, not just superficial change.

That often means moving beyond generic metrics. Increasing conversionglossary×ConversionA conversion is any action a user takes that aligns with a defined goal, such as making a purchase, signing up, or completing a task.Open glossary term→ isn't just about driving more clicks on a button. It might be about reducing hesitation in a booking journey, increasing trustglossary×TrustUser confidence that a product, service, or organisation will do what it promises.Open glossary term→ at key decision pointsglossary×Decision PointA decision point is a moment in a user journey where a user must choose between actions that affect what happens next.Open glossary term→, or removing friction that causes users to abandon. Measuring success in that context requires understanding where users struggle, what causes them to drop off, and how changes in the experience affect their behaviour. This is where measurement and strategy need to be tightly connected.

A useful discipline is to write the target down with a date and a direction before the work begins, and to keep it visible afterwards. It does not need to be sophisticated. It needs to be specific enough that somebody could later say it did not happen.

It is also worth agreeing what would count as evidence that the approach is wrong. Teams define success routinely and almost never define failure, which is why work rarely stops even when it is clearly not delivering.

In practice, that connection is often missing. Metrics are defined after the work has started, or worse, after it's been completed. At that point, measurement becomes retrospectiveglossary×RetrospectiveA retrospective is a session to reflect on a sprint and identify improvements.Open glossary term→ rather than intentional. Teams look for signalsglossary×SignalsSignals are data points or triggers that indicate changes in user behaviour, context, or external factors.Open glossary term→ in the dataglossary×DataData is raw, uninterpreted information collected and stored so it can be analysed, processed, or used to inform decisions. On its own it carries no meaning; context and interpretation are what make it useful.Open glossary term→ that might indicate success, rather than having clear indicators established from the outset.

When success is defined early and clearly, it creates focus. Teams understand what they're aiming for, decisions can be evaluated against a consistent set of criteria, and progress can be measured in a way that reflects real impact. It also makes it easier to stop. If something isn't delivering against the defined measures of success, it becomes clear that a change is needed. Without clear measures, those decisions become far more difficult, and work often continues simply because there's no objective reason to stop. Measuring success isn't about reporting. It's about clarityglossary×ClarityClarity is how easily users can understand what is happening and what they need to do.Open glossary term→.

Defining it late has a second cost beyond the reporting. You often discover you were not collecting what you needed. The event was never tracked, the baseline was never taken, and the question cannot be answered retrospectively at any price.