Every cross-functional program inherits artifacts. Strategy decks from the last consulting engagement. A current-state assessment someone commissioned eighteen months ago. A roadmap that was built for a different scope with different assumptions. These artifacts exist. They live in a SharePoint site, a Google Drive, or a Confluence space that was stood up for a prior initiative and never decommissioned. The problem is not that the artifacts are missing; it’s that nobody has assessed whether any of them are still true. A shared folder full of prior deliverables is not an artifact inventory. It’s a filing cabinet that the planning team has to sift through manually, guessing at what’s current and what’s been overtaken by events.
What a Shared Folder Actually Gives You
A shared folder tells the team what was created. It does not tell the team what is still usable. Someone drops a link in Slack: “Here’s the folder from the last engagement.” The folder contains forty-seven files: decks, spreadsheets, PDFs, interview transcripts. Some are final deliverables. Some are working drafts that were never finalized. Some are duplicates saved under different file names by different people. The folder structure, if it has one, reflects the organizational logic of the team that created it, which may or may not match the current program’s structure. The consulting team opens the folder and starts reading. They spend the first week of the engagement figuring out what’s in there. They find an assessment that contradicts a roadmap. They find two versions of a stakeholder analysis, one from April and one from September, with different conclusions. They can’t tell which one the organization acted on. They ask the client, who doesn’t remember because the person who led that engagement left six months ago. This is the archaeology trap in practice: collecting everything without assessing anything. The team satisfies the instinct to be thorough while producing nothing actionable. The folder grows. The team’s understanding of what’s actually reliable does not. Starting with what already exists is the right instinct; the failure is in stopping at collection and never moving to assessment.
What the Artifact Inventory Section Contains
The Artifact Inventory section of the Landscape Brief is a scored catalog, not a file index. Each row captures six fields:
- Artifact Name: The document’s title, normalized so the team can find it.
- Type: What kind of artifact it is (roadmap, charter, assessment, governance document, stakeholder analysis).
- Source: Which team or consulting firm produced it, and for what purpose.
- Date: When it was created or last substantively updated.
- Relevance Rating: A structured assessment of whether the artifact is still current, still operative, and consistent with other artifacts in the inventory.
- Key Takeaway: The one or two findings from this artifact that matter for the current engagement.
The relevance rating is the field that separates the inventory from the folder. A folder treats all artifacts as equally valid by default. The inventory forces the team to assess each one against three questions: Is the information still accurate? Is this the version the organization is actually operating from? And does it align with or contradict other artifacts we’ve cataloged? That assessment produces a scored view of the inherited landscape. When we compile the inventory, we can see at a glance: twelve artifacts cataloged, seven rated as current and operative, three rated as outdated but still referenced by stakeholders, and two that contradict each other on a material point. That’s a diagnostic picture. A folder gives you forty-seven files; the inventory gives you a map of what the team can rely on.
Two Traps the Inventory Is Designed to Prevent
The artifact inventory catches two failure patterns that derail planning teams who skip the assessment step. The archaeology trap. The team collects everything. They build a comprehensive archive that satisfies the impulse to be thorough, but the archive becomes its own project. Someone spends three days reading through old interview transcripts that were already synthesized into a report that’s sitting in the same folder. The volume of material creates the illusion of rigor while consuming time that should go toward synthesis. The inventory prevents this by forcing the team to score each artifact’s relevance before reading it in detail. If the assessment from two years ago was superseded by a more recent one and the organization is operating from the newer version, the older one gets a low relevance rating and the team moves on. The intake process exists to prevent this kind of unbounded collection: we need enough to understand the inherited context, not a museum of prior work. The recency trap. The team assumes the most recent document is the most accurate. Sometimes it is. Sometimes the most recent deck was a rushed executive update that glossed over real constraints to tell a palatable story. The artifact inventory forces the question: who created this, for what audience, and is it still the operative version? A polished board deck from last quarter and a working draft assessment from the prior engagement may cover the same territory, but the working draft may be more honest about the program’s actual constraints. The inventory captures both, rates both, and makes the divergence visible so the planning team can decide which version to treat as authoritative. Both traps share a root cause: the team treated the artifacts as a collection rather than as evidence that needs evaluation. The inventory is the evaluation instrument.
How the Inventory Feeds the Rest of the Landscape Brief
The artifact inventory does not exist in isolation. It feeds two downstream sections of the Landscape Brief and shapes the program’s planning foundation. The first connection is to the current-state landscape. The current-state section synthesizes what the team found across all functional areas: where capabilities exist, where there are gaps, and where overlaps create confusion. The artifact inventory is the evidentiary base for that synthesis. When the current-state section says “the organization has a data governance framework but it isn’t consistently applied across business units,” that claim should trace back to specific artifacts in the inventory: the governance document itself, the compliance audit that found inconsistent application, and the stakeholder interviews that confirmed the gap. Without the inventory, the current-state section rests on impressions rather than documented sources. The second connection is to scope boundaries. The artifact inventory often reveals scope assumptions from prior engagements that the current program has inherited without examination. A roadmap from the previous consulting team may have scoped a particular function as out of bounds. The current engagement may have a different scope, but if nobody reviewed the prior roadmap’s assumptions, the team may unconsciously carry those boundaries forward. The inventory surfaces these inherited assumptions by cataloging the artifacts that contain them and flagging where prior scope decisions may conflict with current program objectives. The Constraints Calendar captures the timing dependencies that determine when these inherited assumptions need to be revisited or formally resolved. The synthesis question the inventory answers: what prior work is still valid, and what assumptions from prior work have been overtaken by events? That question produces the narrative takeaway for the board: “We cataloged [X] prior artifacts. [Y] are current and form the foundation for planning. [Z] require revisiting because the program’s scope, timeline, or organizational context has changed since they were created.” That sentence tells leadership the team is building on assessed evidence, not inherited assumptions.
How to Know Whether You Have an Inventory or a Folder
Four tests distinguish a structured artifact inventory from a document collection. 1. Every artifact has a relevance rating. If the team hasn’t assessed whether each artifact is current, operative, and consistent with other artifacts, they have a folder. The rating doesn’t need to be elaborate; it needs to exist and be defensible. 2. Contradictions are flagged, not buried. When two artifacts tell different stories about the same topic, the inventory makes the contradiction visible. A folder buries it: the team discovers the conflict only when someone happens to read both documents and notices the discrepancy. 3. The inventory distinguishes between versions. If a stakeholder analysis exists in two versions and the team can’t identify which one the organization acted on, the inventory records both and notes the ambiguity. A folder just has two files with similar names. 4. The catalog produces a synthesis, not a summary. A summary restates what each artifact contains. A synthesis tells the team what the artifacts collectively reveal: where the foundation is solid, where it’s cracked, and where there are gaps the current engagement needs to fill. The practical test is whether your team can answer “what prior work is still reliable?” by looking at a single assessed catalog, or whether the answer requires someone to open forty-seven files and read through them again.
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:
- The Four Sections Every Landscape Brief Needs
Ready to close specific gaps? These articles show you how:
- Scope Boundaries That Actually Hold