Guardrail metrics are crucial but are not Job Function Email Database always embraced by organizations that are experimenting. And this while they do have a direct impact on goal and driver metrics. The use of guardrail metrics is also part of a certain degree of maturity within a CRO team or CRO Job Function Email Database program. The large tech companies, which have elevated experimentation to an art form, sometimes use tens to hundreds of guardrail metrics per online experiment. It suddenly turns out that changes in specific cases can have an unexpected impact on the Job Function Email Database business.
Overall Evaluation Criteria (OEC) It would be fantastic if we could summarize Job Function Email Database everything we do in one metric. Unfortunately, that is not possible. After all, a cockpit of an airplane or a dashboard of a car also needs several measuring instruments. It is irresponsible to fly, sail or drive on just one metric. Still, there is a Job Function Email Database method you can use to better validate the success of an online experiment than by just looking at a goal or key metric. You can do this by combining different metrics into one metric. In our field, this is called an OEC or the Overall Evaluation Job Function Email Database Criteria of an experiment.
Multiple metrics are involved and taken into account in the Job Function Email Database result of an A/B test. The final judgment on this result is, therefore, better substantiated and provides extra certainty for the implementation. In an OEC, one or more key metrics are usually brought together as one KPI and these are Job Function Email Database supplemented with a few guardrail metrics. The big difference between an OEC and a guardrail is that an OEC does Job Function Email Database contribute to the business value of an organization.