You have a Landscape Brief. The goals are documented, the current state is mapped, the artifacts are collected, and the scope is defined. The question is whether what you have meets the quality bar that separates a useful planning input from an artifact that looks complete but leaves critical gaps unexposed. Most Landscape Briefs pass the completeness test. They have all four sections with content in each one. What they often lack is the rigor that makes each section an instrument the planning team can build on without second-guessing. This article walks through the quality bar for each section and identifies the patterns that distinguish excellent from adequate.
Goals & Success Criteria: The Quality Bar
An adequate Goals & Success Criteria section lists the program’s goals with owners and priorities. An excellent one passes four tests that most adequate versions fail. Test 1: Goals are specific enough to evaluate. “Improve operational efficiency” is a goal. It’s also unmeasurable. An excellent table includes criteria that two independent observers could use to assess whether the goal has been achieved. If the success criteria can’t support a yes-or-no evaluation at program close, they’re aspirations, not criteria. Test 2: Sources are documented and traceable. Each goal traces to a specific document, meeting, or decision. The source matters because it establishes provenance: a goal from a board resolution carries different weight than a goal from a brainstorming session. When priorities conflict later, the source record provides the basis for resolution. This traceability is what the Workstream Charter later relies on to assign workstream-level ownership to each goal. Test 3: Alignment gaps are explicit, not smoothed over. The most common failure in this section is false consensus. The table shows all goals as “Aligned” because we recorded agreement at a shallow level without probing for divergence in interpretation. An excellent table distinguishes between Aligned (verified agreement on meaning and priority), Divergent (stakeholders emphasize different aspects of the same goal), and Contested (stakeholders actively disagree). The distinction matters because divergent goals may resolve naturally during planning while contested goals require deliberate intervention. Test 4: The synthesis question has been answered. The table produces a synthesis prompt: where do stated goals conflict, and what is the real priority hierarchy? An excellent Goals section includes a narrative takeaway that answers this question. The narrative doesn’t resolve the conflicts; it names them so the planning team knows what needs resolution before roadmap sessions. The Landscape Brief the board needs opens with this section. If the goals are documented but the alignment status is untested, the brief opens with a false foundation.
Current-State Landscape: The Quality Bar
An adequate Current-State Landscape describes what each function is doing. An excellent one diagnoses the pattern. The diagnostic question: Is the dominant pattern fragmentation (pieces exist but aren’t connected), duplication (multiple teams are building the same thing), or misalignment (teams are working toward different objectives)? Each diagnosis implies a different program architecture. Fragmentation suggests integration work. Duplication suggests consolidation. Misalignment suggests a more fundamental realignment of objectives before planning can proceed. An excellent Current-State section does two things most adequate versions don’t: 1. Distinguishes between gaps, overlaps, and conflicts. A gap is something missing. An overlap is something redundant. A conflict is something contradictory. Most current-state sections identify gaps but miss overlaps and conflicts because they survey each function in isolation rather than comparing across functions. 2. Names the most consequential gaps and triages them. An excellent section identifies the gaps that, if unaddressed, would undermine the roadmap. It also maps adjacent functions whose work intersects with the program, since those functions often hold constraints or dependencies that are invisible if the current-state mapping stops at the program boundary. This triage tells the planning team where to focus during architecture sessions.
Artifact Inventory: The Quality Bar
An adequate Artifact Inventory catalogs existing documents. An excellent one assesses them. The quality gap usually appears in two places: Relevance is assumed rather than evaluated. An adequate inventory lists artifacts with their dates and sources. An excellent inventory rates each artifact’s relevance to the current initiative: High (still operative, should inform the plan), Medium (partially relevant, some assumptions may have changed), or Low (context has shifted enough that referencing it would mislead). The relevance assessment transforms a catalog into a decision tool. Contradictions aren’t flagged. When two artifacts say different things about the same topic (e.g., two roadmaps with different timelines, or two assessments with different conclusions about the same capability gap), an excellent inventory notes both positions and carries the contradiction forward as a question to resolve. An adequate inventory presents both artifacts without noting the tension, leaving the planning team to discover the contradiction during a session when two workstream leads reference different source documents. The two traps from the intake methodology remain relevant at the quality benchmark level. The archaeology trap (i.e., collecting everything) produces inventories too large to assess. The recency trap (i.e., assuming the newest is the most accurate) produces inventories that miss the operational detail preserved in earlier versions. An excellent inventory avoids both by focusing on sufficiency over completeness and checking provenance rather than defaulting to the most recent document. Starting with what already exists means starting with what is still valid, which requires evaluation.
Scope Boundaries: The Quality Bar
An adequate Scope Boundaries section lists what is in scope and what is out. An excellent one manages the gray areas. The quality bar for this section centers on the gray-area table. Most scope sections include an in/out table. The distinction between adequate and excellent is whether the items that fall between in and out have been identified, assigned an owner, and given a resolution deadline. Test 1: Exclusions are specific enough to enforce. “International markets are out of scope” is an exclusion. It’s also too vague to enforce when a workstream lead argues that their deliverable affects a shared platform used by international teams. An excellent exclusion names the specific deliverable, system, or function being excluded, with enough specificity that two people could independently assess whether a particular request crosses the boundary. Test 2: Every gray area has an owner and a deadline tied to a downstream milestone. A gray area without an owner is unmanaged ambiguity. A gray area with an owner but no deadline is a decision that will be deferred until it becomes a crisis. An excellent scope section ties resolution deadlines to the planning milestones they gate: “This gray area must be resolved before workstream scoping begins in Week 4.” The Constraints Calendar is the instrument that makes these timing dependencies visible across the entire program. Test 3: The table has been pressure-tested by the stakeholders most likely to challenge it. Scope boundaries built by the program team and reviewed only within the program team have not been tested. An excellent scope section has been reviewed by the workstream leads, functional leaders, and executive sponsors whose work intersects with the boundaries. The intake process reveals the constraints that make boundaries real, but only if we seek out the people most likely to push.
The Pattern That Separates Excellent from Adequate
Across all four sections, the pattern is the same. An adequate Landscape Brief captures data. An excellent one synthesizes it. Capture without synthesis produces tables that look complete but don’t tell the planning team what to do with the information. The synthesis layer (i.e., the narrative takeaways and the diagnostic triage of which gaps matter most) is what converts the Landscape Brief from a reference document into a planning instrument. The practical test is whether each section of your Landscape Brief produces a statement the board can act on, or whether it reads as a reference document the planning team files and never revisits.
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
Explore the foundations and common gaps:
- What a Landscape Brief Is and Why Planning Fails Without One
- You Have a Goals List but Not a Goals & Success Criteria Table