Most cross-functional programs have a goals list somewhere. It lives in a strategy deck, a charter document, or a set of meeting notes from the kickoff. The goals exist. The problem is that they exist as a flat list of aspirations with no structure to reveal whether the people who stated them actually agree on priority, sequence, or what success looks like. A goals list tells you what people said. A Goals & Success Criteria table tells you where they agree, where they diverge, and what needs resolution before planning can proceed. The difference is between collecting inputs and building an alignment instrument.
What a Goals List Actually Captures (and What It Leaves Out)
A typical goals list looks like this: five to eight bullets, each describing an outcome the program should achieve. “Reduce time-to-market by 30%.” “Consolidate three platforms into one.” “Improve cross-functional coordination.” Each bullet came from someone, but the list rarely records who. Each has an implied priority, but the list rarely makes it explicit. And when two bullets point in different directions (i.e., consolidation requires slowing down while speed-to-market requires moving fast), the list offers no mechanism to reveal the tension. The goals list captures what was said. It does not capture:
- Who said it and from what authority. A goal from the CFO and a goal from a director carry different organizational weight, but the list treats them equally.
- What evidence supports it. Some goals originate from board mandates with documented rationale. Others originate from a hallway conversation that became institutional memory. The list doesn’t distinguish between the two.
- Whether the stakeholders who stated these goals agree on their relative priority. Three VPs may each describe the primary objective differently. The list presents all three as equally valid.
- What “success” actually means in measurable terms. “Improve cross-functional coordination” could mean anything from reducing handoff delays to eliminating duplicate meetings. Without criteria, the team can’t evaluate whether the goal has been met.
These aren’t cosmetic gaps. They’re structural gaps that shape every downstream planning decision. When the team starts with what already exists but doesn’t assess the alignment beneath it, the plan inherits contradictions that surface during execution.
What a Goals & Success Criteria Table Contains
The Goals & Success Criteria table is the first section of the Landscape Brief. It structures goals into five fields:
- Stated Goal: The goal as articulated by the stakeholder, in their language.
- Source Document: Where this goal is documented (i.e., which deck, charter, or memo).
- Stakeholder Owner: The person who stated it or is accountable for it.
- Priority: High, Medium, or Low, assigned by the stakeholder.
- Alignment Status: Aligned (stakeholders agree), Divergent (stakeholders emphasize different things), or Contested (stakeholders actively disagree).
The table doesn’t editorialize. It compiles. When three VPs each describe the program’s primary objective differently, the table makes that visible in a single view. The planning team doesn’t need to resolve the divergence at this stage; they need to see it, document it, and carry it forward as an input to the stakeholder conversations that follow. Each goal eventually flows into a Workstream Charter that translates program-level objectives into workstream-level accountability. The quality bar for this section: goals are specific enough to evaluate, sources are documented, and alignment gaps between stakeholders are explicit. If the table can’t answer “who said this, where is it written, and does everyone agree,” it’s incomplete.
The Synthesis Question the Table Forces
Beyond the capture structure, the Goals & Success Criteria table produces a synthesis question: Where do stated goals conflict, and what is the real priority hierarchy when you read between the documents? This question matters because organizations frequently operate with stated goals and operative goals that differ. The stated goal is what appears in the strategy deck. The operative goal is what drives resource allocation and executive attention. When the two diverge, the program inherits a gap between what the plan says and what the organization actually rewards. The synthesis prompt forces us to name that gap. The output is a narrative takeaway: “The initiative has X stated goals. Y are aligned across stakeholders. Z require resolution before planning proceeds.” That sentence, drawn from the table, becomes the opening of the board narrative for the Landscape Brief. Without the synthesis step, the table is a spreadsheet. With it, the table becomes a diagnostic instrument that tells the planning team where alignment is real and where it’s assumed. Programs that never identified this distinction discovered it later, during execution, when the cost of resolution was significantly higher.
How the Gap Shows Up During Execution
The distance between a goals list and a Goals & Success Criteria table produces two execution-stage costs that account for most of the downstream damage. Priority collisions. Two workstreams optimize for different goals because the priority hierarchy was never established. The consolidation workstream slows deployment to reduce technical debt; the speed-to-market workstream accelerates deployment to hit a launch window. Both are executing faithfully against goals that were never reconciled. The collision arrives at the integration point (i.e., a shared deployment window), and now the program is arbitrating priority under time pressure instead of during planning. Success criteria drift and invisible ownership gaps. Without documented criteria, each stakeholder evaluates progress against their own definition of success. The program hits a milestone, but people disagree about whether it was achieved. The resulting re-evaluation consumes collaborative time and erodes confidence in the plan. Meanwhile, goals without named owners sit in the plan as aspirations no one is accountable for. When execution stalls on one of these goals, the team discovers that no single person has the authority to unblock it. The escalation path is unclear because ownership was never assigned. Both costs trace back to the same structural gap: the goals were listed but not assessed. The information existed; the instrument to evaluate it did not.
What “Complete” Looks Like
A complete Goals & Success Criteria table passes four tests: 1. Every goal has a source. If someone can’t point to where the goal is documented, it’s an assumption, not a goal. Assumptions belong in a different conversation. 2. Every goal has an owner. A goal without an owner is a wish. The table names the person accountable for each goal so that priority conflicts have a resolution path. 3. Priority is explicit and attributed. The table doesn’t average priorities across stakeholders. It records each stakeholder’s priority assessment so that divergences are visible. 4. Alignment status is assessed, not assumed. “Aligned” means we’ve verified agreement. “Divergent” means stakeholders emphasize different aspects. “Contested” means active disagreement exists. The distinction matters because divergent goals may resolve naturally during planning while contested goals require deliberate intervention. The practical test is whether your goals have been structured, sourced, and assessed for alignment, or whether the planning effort is built on a list nobody has examined.
Go Deeper: The Landscape Brief
This article covers one dimension of the Landscape Brief, the first of nine artifacts in the Planning & Roadmapping method. The Landscape Brief answers the board question: “What did we find?” Explore the full Landscape Brief → Want us to build this with you? Book a consultation →
Keep Reading
New to the Landscape Brief? Start with the foundations:
- What a Landscape Brief Is and Why Planning Fails Without One
Ready to benchmark your work against best-in-class? See what excellence looks like:
- The Landscape Brief as Quality Benchmark