A Client Success Metric We Disagreed On Until We Rebuilt It Together

I closed out a tracking overhaul project confident it had gone well. Data quality was dramatically better, dashboards finally matched between teams, and every deliverable in the original scope was shipped on time. The client's reaction on the final call was muted, almost disappointed. I genuinely didn't understand why until I asked directly.

They'd hoped the project would move a specific business number — qualified leads per month — and it hadn't, because the project was never scoped to do that. It was scoped to fix data quality, which it did, completely. We had both been right about our own definition of success and had never actually compared definitions before the project started.

A project can hit every deliverable and still feel like a failure if the deliverables were never tied to the outcome the client actually cared about.

What we did to fix the disagreement

We didn't argue about who was right. We sat down and rebuilt the success metric together, retroactively, which sounds odd but worked: we agreed explicitly that this project's job was data quality, stated what that specifically meant (matching numbers across GA4, the CRM, and finance reports), confirmed it had in fact been achieved, and then scoped a separate, clearly distinct next phase aimed directly at the lead-generation number they actually wanted moved.

• I now ask explicitly in every discovery call: 'what number do you expect to look different because of this project, specifically?'
• If the answer is a number the scoped work can't plausibly move, I say so before the contract is signed, not after.
• Success criteria go into the proposal in writing, stated as a metric and a direction, not just a list of deliverables.
• At project close, we review that stated criterion explicitly, even if it feels redundant, because the deliverables-complete checklist isn't the same conversation.

The project itself didn't need to change. The conversation about what it was supposed to do needed to happen three months earlier than it did. That gap — between what gets delivered and what gets felt as success — is almost always a scoping failure, not a quality failure, and it's entirely preventable with one direct question asked early.