I decide from evidence, and I build the systems that let a team do the same. That means starting from the decision the data has to change, then reconciling the numbers before trusting a single rate.
This is the method before it's any one project, and it leans as much on editorial judgment as on analytics. The discipline is knowing what the numbers are allowed to tell you, and when they've actually earned a decision. What follows is that method applied to one initiative I'm leading.
The deeper problem was never a lack of numbers. It was that almost no decision actually started with them. Reporting lived in disconnected systems that didn't agree — the same conversion read very differently depending on which source you asked — and nothing joined content to pipeline at all.
The temptation in that situation is to jump to a fix. As lead, I set the opposite rule: discovery first, and agree the real gaps before anyone builds anything.
A conversion rate is only as honest as its denominator and its definition. Before drawing a single conclusion, I documented what still had to be nailed down, and built the funnel model that made the gaps legible. The discovery showed where the funnel held and where it leaked. Those specifics stay internal, but the pattern was strong enough to redirect effort.
The website was the one owned surface where content and conversion could connect, and it was being run as a brochure. The analysis pointed to a shift in what the site is for.
Connect the data into one view. Find where measurement and definitions break down. Raise the quality of demand rather than the count of leads. Then use the connected view to steer effort toward what actually converts.
Foundation, then diagnosis, then conversion, then automation. Each objective earns the next, and none of them get to skip the evidence.
Full analysis available on request.