The Landscape Brief has three layers. The first is data capture: structured tables populated during intake. The second is synthesis: our interpretation of what the data means. The third is the narrative beat: the board-ready statement that opens the presentation. Most Landscape Briefs execute the first layer well. The synthesis layer is where the quality gap appears. Synthesis is the work of turning a table full of data into a statement a board can act on. It requires pattern recognition, judgment about what matters most, and the discipline to compress complex findings into language that’s precise without being reductive. This article examines how the synthesis layer works across each section of the Landscape Brief and what distinguishes the narrative takeaways that land from the ones that fall flat.
The Three Layers of the Landscape Brief
Every section of the Landscape Brief follows the same architecture. Layer 1 captures structured data from intake activities: goals, current-state assessments, artifact catalogs, scope tables. Layer 2 synthesizes: we answer a guiding question that forces interpretation beyond what the raw data shows. Layer 3 produces the narrative takeaway: a single statement summarizing what the section found and what it means for the program. The layers are sequential. Synthesis without data is opinion; data without synthesis is a spreadsheet. The narrative takeaway without synthesis is a summary rather than a diagnosis. The progression from capture to synthesis to narrative is what converts the Landscape Brief from a reference document into the first beat of a board-ready narrative.
How Synthesis Works in Each Section
Goals & Success Criteria. The capture table records stated goals, source documents, stakeholder owners, priorities, and alignment status. The synthesis prompt: Where do stated goals conflict, and what is the real priority hierarchy when you read between the documents? The synthesis work here is distinguishing between stated goals and operative goals. Stated goals appear in the strategy deck. Operative goals drive resource allocation and executive attention. When the two diverge, the program inherits a gap between what the plan says and what the organization rewards. The strongest version of this work names that gap in the narrative takeaway: “The initiative has seven stated goals. Four are aligned across stakeholders. Three require resolution: specific goals], where [specific stakeholders] hold divergent views on priority.” The narrative takeaway is actionable because it names the specific goals and the specific divergences. A weak takeaway says “some alignment gaps exist.” A strong takeaway says exactly where and between whom. Current-State Landscape. The capture table maps domains and functions against their current state, gaps, overlaps, and conflicts. The synthesis prompt: What is the dominant pattern: fragmentation, duplication, or misalignment? This diagnosis shapes the entire program architecture. Fragmentation means pieces exist but aren’t connected, which implies integration work. Duplication means multiple teams are building the same thing, which implies consolidation. Misalignment means teams are working toward different objectives, which implies a more fundamental intervention before planning proceeds. Each diagnosis shapes how the [Workstream Hierarchy is structured and how teams are organized around the work. The strongest version commits to a diagnosis and names the evidence: “The dominant pattern across the six functional areas is fragmentation. Three functions have independent roadmaps that share no milestones, dependencies, or success metrics. The most consequential gap is [specific gap], which, if unaddressed, would prevent workstream integration during roadmap sessions.” Artifact Inventory. The capture table catalogs artifacts with relevance ratings and key takeaways. The synthesis prompt: What prior work is still valid, and what assumptions have been overtaken by events? The synthesis work here is temporal: evaluating each artifact against current conditions rather than the conditions that existed when it was created. The strongest version produces a clear sort: these artifacts inform the plan, these require revision, and these should be set aside. The narrative takeaway names the number and the split: “Fourteen artifacts reviewed. Eight remain relevant. Three require revision due to [specific changes]. Three should be set aside because [specific reasons].” Scope Boundaries. The capture tables define in-scope, out-of-scope, and gray-area items. The synthesis prompt: Where is scope likely to creep, and which gray areas need resolution before roadmap sessions? The synthesis work here is predictive: looking at the gray-area table and assessing which items carry the most downstream risk if left unresolved. The strongest version triages the gray areas into categories by urgency: must resolve before roadmap sessions, can resolve during roadmap sessions, and can remain open into early execution. The narrative takeaway gives the board a concrete picture: “Scope is bounded by [key boundaries]. Four gray areas require resolution by Week 3 to avoid downstream delays in workstream scoping.”
What Distinguishes Narrative Takeaways That Land
Across all four sections, the narrative takeaways that land with a board share two characteristics. They are specific. “Some alignment gaps exist” doesn’t help a board make decisions. “Three of seven goals have contested priority between the VP of Operations and the VP of Technology” gives the board something to act on. Specificity requires committing to a finding, which requires the synthesis layer to have been completed rigorously. They connect to the next step. Each narrative takeaway implies an action that maps to a subsequent step in the methodology. The goals takeaway implies stakeholder conversations to resolve divergences (Step 2). The current-state takeaway implies architectural decisions to address the dominant pattern (Step 3). The scope takeaway implies resolution deadlines that gate roadmap sessions (Step 5), feeding directly into the Workstream Roadmap that sequences the work. The board-ready narrative works because each beat sets up the next one. Good takeaways are also explicit about what remains uncertain. A board can act on certainty and allocate resources to resolve open questions, but it can’t act on ambiguity disguised as certainty.
The Common Failure: Summarizing Instead of Synthesizing
The most common failure in the synthesis layer is producing summaries rather than diagnoses. A summary restates what the data shows; a synthesis interprets what it means. Summary: “We reviewed twelve artifacts from five functional areas. Most are from the past eighteen months. Several contain relevant findings.” Synthesis: “Twelve artifacts reviewed. Eight remain operative. The critical finding across the artifact set is that prior planning assumed a centralized deployment model, but three of the eight operative artifacts contradict that assumption. This contradiction needs resolution before roadmap sessions because the deployment model determines workstream boundaries.” The difference is that the synthesis identifies a pattern (contradictory assumptions about the deployment model), names the consequence (it gates workstream boundaries), and implies an action (resolve before roadmap sessions). The summary describes the data without interpreting it. Teams that produce summaries instead of syntheses typically do so for one of two reasons: they haven’t spent enough time with the data to identify patterns, or they’re avoiding commitment to a finding that could be challenged. Both produce the same result: a Landscape Brief that looks complete but doesn’t give the planning team or the board a basis for action. The practical test is whether your Landscape Brief converts inherited context into an assessed foundation the board can act on, or whether it remains a filing system that documents what the team already knew.
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: