Why I Won't Start Implementation Before Stakeholder Alignment Anymore

I built an entire conversion tracking migration to the spec my primary contact gave me. It was correct, tested, and deployed on schedule. Then finance saw the numbers and said it measured the wrong thing — not wrong as in buggy, wrong as in it answered a question marketing cared about and not the one finance needed for revenue reporting.

Nobody lied to me. My contact genuinely believed they were speaking for the org. They weren't, because nobody had checked that marketing's definition of a qualified conversion matched finance's, and I'd built against one definition without knowing a second one existed.

A spec from one stakeholder is a hypothesis about what the organization wants, not a confirmed requirement.

What changed in how I scope projects now

• Any project touching a metric used across departments gets an explicit alignment phase before implementation starts, billed and scheduled as its own step.
• That phase means a short written definition of every key metric, circulated to every stakeholder who touches it, with sign-off requested in writing.
• Disagreements surfaced in that phase get resolved before a line of implementation happens, even if it delays the start date.
• I now ask directly in discovery: 'who else needs to agree with this definition before we build it,' rather than assuming my contact already knows.

The cost of skipping this versus doing it

The alignment phase adds a few days to a project timeline and, in my experience, catches a conflicting definition on roughly one in three multi-stakeholder projects. The rework from building against the wrong definition costs far more than a few days — in that migration case, it cost nearly two weeks of redone implementation plus a client relationship that took real effort to rebuild trust in.

Clients occasionally push back on paying for a phase that produces no visible deliverable beyond a document. I now frame it plainly: this document is what prevents the thing we're about to build from being wrong in a way nobody notices until it's already shipped.