Most cross-functional programs begin with some version of a plan already in place: a strategy deck from six months ago, functional calendars with blackout windows, a prior roadmap another team built that some people reference and others have never seen. Constraints are buried in emails, assumptions documented in a Confluence page nobody has opened since Q2, and scope boundaries live in the heads of four different VPs who each believe their version is the shared one. The program has inputs. What it lacks is a single assessed inventory of those inputs that tells leadership: here is what we have, here is where it conflicts, and here is what is missing. That inventory is the Landscape Brief.
Why Planning Stalls When You Already Have a Strategy Deck and a Project Charter
A strategy deck and a project charter answer important questions, but they answer different questions than the ones that determine whether planning will produce a credible roadmap. The strategy deck states aspirations: where the organization wants to go, what capabilities it wants to build. The charter defines scope at a high level: who is sponsoring the initiative, what functions are involved, and what the timeline looks like. Both are useful starting points. Neither compiles the factual foundation the planning team needs to build on. Four questions remain unanswered:
- What artifacts already exist, and are they still valid? Prior roadmaps, assessments, and governance documents contain decisions that were made for reasons. Some are still operative; some have been overtaken by events. Until someone inventories them and assesses their current relevance, the planning team is building on a foundation it has not examined.
- What constraints are already known, and which are hard stops versus assumptions? A code freeze in November is a hard constraint. A preference to avoid launching during back-to-school is a negotiable assumption. The planning team needs to know the difference before sequencing milestones, which is exactly what the Constraints Calendar is designed to capture.
- Who shaped the prior work, and whose perspective is missing? The people who built the existing artifacts have assumptions baked in. The people who were absent may hold constraints or dependencies that have never been identified.
- What coordination infrastructure exists to sustain alignment? A weekly ops sync that could absorb program updates, a monthly leadership forum that could serve as an escalation path, or nothing at all. The planning team needs to know what it’s working with before building a new rhythm. The Program Cadence Inventory captures exactly this kind of coordination infrastructure.
These four questions are proxies for whether the organization has a shared factual foundation or is planning on top of inherited assumptions nobody has examined. The strategy deck and the charter do not answer them. The Landscape Brief does.
What a Landscape Brief Is and What It Contains
The Landscape Brief is the first output artifact in a nine-step planning methodology. It answers the board question: “What did we find?” It’s structured around four sections, each designed to compile a different dimension of the program’s inherited context into a format leadership can act on. Goals & Success Criteria. A table of every stated goal, with its source document, the stakeholder who owns it, its priority, and its alignment status across stakeholders. The quality bar: goals are specific enough to evaluate, sources are documented, and alignment gaps between stakeholders are made explicit. When three VPs each describe the program’s primary objective differently, the Goals & Success Criteria table makes that visible in one view. Current-State Landscape. A table organized by domain or function showing the current state, gaps, overlaps, and conflicts. The synthesis question we answer: 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)? The answer shapes the entire program architecture. Artifact Inventory. A scored catalog of every existing document, plan, roadmap, and assessment the organization has produced. Each artifact is assessed for relevance (i.e., is it still current, is it still operative, does it contradict other artifacts). This section produces an assessed inventory rather than a folder dump. A folder dump tells the team what exists; an artifact inventory tells the team what is still valid. Scope Boundaries. An explicit table of what is in scope, what is out of scope, and what is in the gray area. Gray-area items have an owner and a resolution deadline. The quality bar: no ambiguity about boundaries. When scope creep occurs later in the engagement, the team can point to a documented boundary and evaluate the change against it. Each section produces a narrative takeaway for the board: a single statement summarizing what the section found and what it means. Stacked together, the four takeaways compose the first beat of a board-ready narrative that runs across all nine steps.
The Cost of Planning Without One
Programs that skip the Landscape Brief, or compress it into a half-day exercise, build the rest of the engagement on an incomplete foundation. Two failure patterns recur consistently. Collaborative time wasted on rediscovery. Without a compiled inventory, stakeholders raise constraints during roadmap sessions that were documented months ago. The constraint embedded in a prior roadmap (i.e., an operational blackout that blocks a deployment window) appears during execution instead of during planning. The team replans under pressure instead of designing around the constraint from the start. The intake step exists to prevent this, but it requires producing a structured output (the kind that tells the planning team what to do with the documents, not where to find them). Contradictions go undetected, and invisible decisions get inherited. Overlapping scope boundaries between workstreams persist because nobody compiled them into a single view. Conflicting assumptions about the program’s primary goal persist because each VP’s version was documented separately. These contradictions emerge during execution when two workstreams collide at the same deployment window. Meanwhile, prior work contains embedded choices (i.e., scope boundaries, resource allocations, sequencing decisions) that were made for reasons nobody remembers. The organization either re-argues those decisions later (expensive, because the team has already built on them) or inherits them without realizing it (dangerous, because the original context may no longer apply). The Landscape Brief reveals those embedded decisions so the team can choose deliberately what to keep and what to discard. Programs that failed with good plans frequently trace the failure back to contradictions that were visible in the existing artifacts but never compiled. Each failure pattern maps to one of those unanswered questions. Rediscovery happens because nobody inventoried what exists. Contradictions and invisible decisions persist because nobody compiled the constraints or asked who shaped the prior work and whether the choices embedded in it are still valid.
How the Landscape Brief Connects to the Rest of the Program Plan
The Landscape Brief is Beat 1 of a nine-beat board narrative. It establishes the factual foundation: what exists, where it conflicts, and where the gaps are. Beat 2, the Stakeholder Map, adds the human dimension: who sees what, and where do their perspectives diverge from what the documents say. Together, Beats 1 and 2 provide the foundation for program architecture in Beat 3. The two artifacts are designed to work together: the landscape brief gives the board the documented reality, and the stakeholder map reveals where that reality is contested. The pre-mortem pressure-tests the foundation. The roadmap operationalizes it. The operating model sustains it. The practical question is whether your program’s foundation has been compiled and assessed, or whether you’re planning on inherited assumptions 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
Ready to close specific gaps in your Landscape Brief? These articles show you how:
- You Have a Goals List but Not a Goals & Success Criteria Table
- Scope Boundaries That Actually Hold
- From Artifact Dump to Artifact Inventory