Projects don’t usually end in dramatic failure. They end in ambiguity. The client thinks the results were underwhelming. You think you delivered exactly what was scoped. Nobody’s lying, they genuinely defined success differently from the start, and nobody checked.
The marketing director wanted brand awareness. The CEO wanted sales leads. You were building brand awareness all along and hit every deliverable. At the quarterly review, the CEO says the project underperformed. The marketing director is caught in the middle. You’re defending work that was excellent by the wrong standard.
The success definition document exists to prevent this. It makes “done” and “good” mean the same thing to everyone before a single line is written or a single design is started.
Why Outcome Clarity Is Harder Than It Looks
Every client believes they know what success looks like. And most of them do, individually. The problem is that different stakeholders often have different definitions that they’ve never had to reconcile because they’ve never sat in the same room and compared notes.
The CMO thinks success is brand lift. The sales director thinks success is pipeline growth. The CEO thinks success is competitive positioning. All three believe their definition is obvious and shared. None of them is wrong, but the project can’t optimize for all three equally, and if you try, you’ll be mediocre at all of them.
Your job in Week 1 is to facilitate the reconciliation they haven’t done themselves. Not by imposing your definition, by creating the exercise that makes theirs explicit, then working with the group to find the hierarchy.
The Exercise: From Individual Outcomes to Shared Document
This exercise takes 30 minutes and can run in-person, on a call, or asynchronously.
Step 1: Individual Outcome Collection (10 minutes)
Send each stakeholder this prompt the day before the meeting:
“Before our success definition session, please write down 2-3 measurable outcomes you’d use to evaluate whether this project succeeded. Be as specific as possible, I’m looking for things you could point to in 3 months and say ‘yes’ or ‘no’ to. For example: ‘email open rate increased by 5+ points’ or ‘a sales deck that sales reps actually use in at least 3 pitches per month.’”
Collect these before the meeting. You’ll see immediately where alignment exists and where it doesn’t.
Step 2: Share and Map (10 minutes)
At the meeting, display all outcomes on a shared document or screen. Group similar ones together. Don’t editorialize yet, just cluster.
You’ll typically see three patterns:
- Consensus outcomes: Multiple stakeholders named similar things. These go in the document immediately.
- Complementary outcomes: Different things that aren’t in conflict, just different perspectives on the same project. Can be combined or both included.
- Conflicting outcomes: Things that actually can’t both be maximized, like “maximize content volume” and “maintain premium quality.” These need a conversation.
Step 3: Reconcile Conflicts Explicitly (5 minutes)
For any conflicting outcomes, don’t paper over them. Name the conflict and ask for the priority:
“I’m noticing we have ‘volume: 20 posts per month’ and ‘quality: each post on par with [reference publication].’ Those two are in tension at the scope and budget of this project. Which takes priority? If we had to pick one to optimize for first, which one?”
Most clients have a clear preference when the trade-off is made explicit. The one who defers is usually not actually the decision-maker on that dimension.
Document the answer: “Agreed: quality takes priority over volume. Target is 8 high-quality posts per month rather than 20 shorter ones.”
Step 4: Write the Shared Outcomes (5 minutes)
Finalize 3-5 outcomes with this template for each:
Outcome: [What we’re measuring] Baseline: [Where we are now, ideally with a number] Target: [What ‘good’ looks like, with a number or observable condition] Verification: [How we’ll measure it and when] Owner: [Who provides the data or makes the call]
“Improved brand awareness” is not an outcome. “Brand awareness survey score increases from 34% to 45% in target segment by Month 6, measured by the quarterly survey Sarah runs” is an outcome. The difference is whether you can settle a dispute with it.
A Completed Success Definition Document: Real Example
Project: Brand and content strategy for a B2B SaaS company
Outcome 1: Lead quality improvement Baseline: 22% of inbound leads meet Sales’ minimum qualification criteria Target: 35%+ of inbound leads meet minimum qualification criteria by Month 4 Verification: Monthly sales lead quality report from CRM (owner: Head of Sales) Review date: Month 4 check-in
Outcome 2: Content engagement Baseline: Average blog post reads 340 (last 6-month average) Target: Average blog post reads 600+ for posts published under new strategy Verification: HubSpot analytics report (owner: Content Manager) Review date: Month 3 check-in
Outcome 3: Sales team adoption Baseline: Sales deck used in 0-1 pitches per rep per month (informal tracking) Target: New deck used in 3+ pitches per rep per month Verification: Sales rep survey in Month 2 (owner: Head of Sales) Review date: Month 2 check-in
Outcome 4: Competitive differentiation Baseline: No clear competitive positioning statement in use Target: All customer-facing materials (website, deck, email signatures) use the agreed positioning statement by Month 1 Verification: Content audit by [Your Name] at end of Month 1 Review date: Month 1 sign-off
Four outcomes. Each has a baseline, a target, a verification method, and an owner for the data. This document removes every ambiguity from the project evaluation.
How to Handle “We Don’t Have Baseline Data”
Many clients won’t know their baseline numbers. That’s not a reason to skip the exercise, it’s a reason to either estimate or make the baseline-gathering itself an early deliverable.
Options:
- Estimate the baseline: “Based on industry benchmarks for companies your size, email open rates are typically 18-22%. Can we use 20% as a proxy baseline?” Most clients accept reasonable estimates.
- Make measurement an early task: “Before we can set a target, we need to establish where you are. I’ll run a baseline audit in Week 1 and we’ll set the target in Week 2.”
- Use observable conditions instead of metrics: When hard numbers are unavailable, use conditions you can verify: “Sales reps use the deck without prompting” or “Legal approves all website copy on first submission.” These aren’t perfect, but they’re better than “improved positioning.”
Protecting Yourself When Clients Move Goalposts
The success definition document is primarily a client-service tool, it helps you deliver the right thing. But it’s also your protection when projects get evaluated against standards that weren’t set at the start.
When a client expresses dissatisfaction at project end, the first thing you do is open the success definition document. Walk through each outcome:
“Outcome 1: lead quality. The target was 35%+ by Month 4. Our Month 4 report shows 38%. That’s above target.
Outcome 2: content engagement. Target was 600+ average reads. We’re at 570, slightly below. The gap appears to be in the first two months when we were establishing the new format, the last six weeks average 680.
Outcome 3: sales deck adoption. We set a verification survey for Month 2. I don’t see that we ran it, should we do that now?”
This conversation is completely different from defending your work against vague dissatisfaction. You’re reviewing a document you co-created against data you agreed to collect. That’s a professional evaluation, not a dispute.
The Facilitation Script for Conflicting Stakeholders
If stakeholders have genuinely competing priorities and can’t reach agreement in the 30-minute session, don’t push for forced consensus. Instead:
“It sounds like we have two valid views here that need a bit more internal discussion before we can agree on the priority. I’d suggest [Name] and [Name] take 15 minutes before our next sync to align on which outcome takes precedence. I’ll hold the document in draft until then, I don’t want to start work optimizing for the wrong thing.”
This protects you and signals maturity. The client takes you more seriously when you push back on internal misalignment rather than accepting a contradictory brief.
Most of the time, they’ll have the conversation and come back with a clear answer within 24 hours. The 15 minutes you lost waiting is nothing compared to the weeks you’d lose reworking based on conflicting feedback.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
