What we measure after a launch

Every project we ship gets a post-launch review at two weeks and again at eight. Not a retrospective about how the work went — a look at whether it did what it was supposed to do.

We track four things. Core Web Vitals from real users rather than lab tests, because a site that scores well on a developer’s laptop can still be slow on a three-year-old Android. Task completion for the two or three journeys that actually matter commercially. Support ticket volume on the pages we touched. And, where it applies, conversion against whatever the baseline was before we started.

The useful part is not the numbers themselves but the arguments they settle. Opinions about a layout stop mattering quite so much once you can see what people did with it.