The engagement started the way most do: the executive sponsor described the program as “mostly on track with some coordination challenges,” and the intake that changes everything told a different story. The landscape brief synthesizes the current state of a program into a single document: what exists, what’s been tried, what’s working, what has stalled, and where the gaps sit between what the plan says and what’s actually happening. For many leadership teams, it’s the first time they’ve seen an honest, cross-functional view of their own program.
What a Landscape Brief Contains
The landscape brief is structured around five sections, each drawing from intake interviews, artifact review, and stakeholder conversations.
Program inventory: a catalog of active workstreams, their stated scope, timelines, leads, and status. It also includes prior initiatives that addressed similar goals, what they produced, and why they succeeded or stalled. Most programs have more history than anyone remembers; the inventory surfaces that history so the team can learn from it.
Dependency map: a view of which workstreams depend on each other, which functions need to coordinate, and where shared resources or systems create bottlenecks. In one engagement, the dependency map revealed that two workstreams both required a configuration change to the same platform with conflicting timelines, and the platform team had capacity for one change but not both in the same quarter. This information existed in the organization but had never been compiled into a view leadership could act on.
Constraints inventory: a compilation of the organizational, operational, and political constraints that will shape execution. Budget cycle timelines, operational blackouts, technology freeze windows, regulatory deadlines, and leadership transitions. These constraints are well-known within each function but rarely assembled cross-functionally.
Gap analysis: a comparison of the stated plan against observed reality. Where the plan assumes a resource that hasn’t been committed. Where the timeline depends on a decision that hasn’t been made. Where the scope has been defined at the executive level but not decomposed into workstream-level specifications. The gap analysis maps what needs to be resolved before planning can proceed on solid ground.
Stakeholder view: a summary of how key stakeholders perceive the program, where there’s alignment and where there’s disagreement that hasn’t been surfaced publicly. In the same engagement, three of four workstream leads believed the program’s primary goal was cost reduction while the executive sponsor described it as customer experience improvement. This misalignment had never been discussed because each stakeholder assumed their understanding was shared. The stakeholder mapping that goes beyond the org chart later built on this view to surface the informal influence networks that shaped decision-making.
Why Your Board Needs This
Most steering committees receive program updates in a format that obscures the cross-functional reality. Each function presents its own status: on track, at risk, or behind. The aggregated view is a collection of function-level reports that may individually be accurate but collectively miss the interactions between them. The dependency connecting workstream A’s milestone to workstream B’s resource allocation does not appear in either function’s report.
The landscape brief provides the view that function-level reporting can’t. It says: here is the program as a whole, here is how the pieces connect, here is where the gaps are, and here is what needs to be true for planning to proceed. It’s the kind of document that, when distilled into a final readout a CFO will actually read, changes the quality of executive decision-making.
The brief also establishes a shared baseline. Before planning begins, every stakeholder has the same picture of where things stand. Disagreements about scope, timeline, or priorities can be surfaced against a common set of facts rather than competing narratives from different functions.
How It Gets Built
The landscape brief is compiled during the first two weeks of an engagement, drawing from three sources: artifact review (i.e., existing plans, charters, status reports, and prior initiative documentation) and stakeholder interviews with workstream leads and functional heads, plus the executive sponsor. We present the brief to leadership in a session designed to be clarifying rather than confrontational. Most leaders react with a mix of “yes, we knew that” and relief that someone finally wrote it down in a way the team can act on.
