# IT landscape discovery: how to map an IT estate without blank factsheets

> Canonical: https://decisionpen.com/blog/it-landscape-discovery-guide  
> Published: 2026-10-22  
> Author: DecisionPen Team  
> Category: Automated Landscape Modelling

## Short answer

Define a bounded scope, combine a CMDB or inventory extract with documents and expert evidence, match evidence to canonical entities, validate conflicts and unknowns, curate a trusted landscape slice, and maintain it continuously. Discovery should create a living decision asset — not a static baseline that expires on delivery.

## Six steps

### 1. Define a bounded scope

Choose a domain, capability, platform, geography or transformation boundary. Define the decisions the landscape must support.

### 2. Gather structured and unstructured evidence

Structured sources include CMDB extracts, application inventories, EA factsheets, interface registers and technology catalogues. Unstructured sources include HLDs, ADRs, runbooks, migration documents, transcripts, diagrams and SME narratives.

### 3. Match evidence to entities

Resolve names, acronyms and project labels. Match documents to existing entities first and create new entities only where evidence exposes a genuine gap.

### 4. Validate conflicts and unknowns

Make missing systems, duplicates, stale records, unsupported relationships, unclear ownership and purpose gaps explicit.

### 5. Curate a trusted landscape slice

Architects and owners accept, correct, reject or defer entities, relationships and context. Preserve provenance.

### 6. Maintain continuously

Feed new designs, decisions, transcripts and inventory updates back into the same model so discovery compounds rather than restarting for every programme.

## Discovery outputs

- Canonical application and technology landscape
- Capabilities and business context
- Integrations and dependencies
- How-and-Why evidence attached to entities
- Conflicts, orphans and evidence gaps
- Owners and curators
- Decision-ready views
- A maintenance process

## How DecisionPen solves this

DecisionPen supports document-first modelling and CMDB-seeded modelling. It can import an existing catalogue from a spreadsheet or begin from documents and dialogue. It proposes metamodel-aware entities and relationships, retains evidence, supports human curation, and makes the landscape available to Enterprise Ask and generated artefacts.

DecisionPen can start from a CMDB or inventory spreadsheet extract. It is not a network scanner, operational CMDB or freeform diagramming product.

## FAQ

### What is IT landscape discovery?

Establishing a trustworthy view of applications, technologies, capabilities, integrations, owners, dependencies and unknowns across a defined estate using inventories, documents, operational evidence and expert validation.

### What are the discovery steps?

Bound the scope, gather evidence, match it to entities, validate conflicts and unknowns, curate a slice, and maintain it.

### How does DecisionPen support discovery?

Spreadsheet-seeded or document-first intake, metamodel-aware proposals, evidence, human curation, Ask and generated views.

## Related reading

- https://decisionpen.com/blog/automated-it-landscape-modelling-from-unstructured-data
- https://decisionpen.com/blog/how-to-enrich-ea-factsheets-with-unstructured-documents
- https://decisionpen.com/blog/what-is-the-discovery-tax-in-it-transformations
- https://decisionpen.com/use-cases/it-landscape-mapper