# How do you shape enterprise context for IT knowledge management?

> Canonical: https://decisionpen.com/blog/shaping-enterprise-context-for-it-knowledge-management  
> Published: 2026-10-25 · DecisionPen · Living EA series (D6e)  
> Related docs: /docs/it-knowledge-continuum, /docs/architecture-decision-workspace, /docs/incremental-modelling, /docs/enterprise-ask

## Summary

Shaping enterprise context for IT knowledge management means building a curated metamodel map with How/Why evidence, ownership, and an askable interface — not stocking another wiki. Structure, bind, curate, and refresh so knowledge compounds as commitments about the estate.

## IT KM’s context problem

Document KM optimises findability of text. It does not create a single landscape authority. Result: Context Tax and tribal memory as the real system of record.

**Operating claim:** Document KM accumulates text. Shaped enterprise context accumulates commitments about the estate.

## What “shaping” means

1. Structure — metamodel entities and relationships.
2. Bind — How/Why evidence on entities.
3. Own — steward of curation (usually EA).
4. Ask — map-grounded interface so knowledge is used.
5. Refresh — continuous discovery, not yearly baselines.

## Five layers of shaped IT knowledge

1. Inventory (what exists)
2. Relationships (how it connects)
3. How/Why evidence
4. Decisions and standards
5. Askable interface (cited answers, generated views)

## Practical sequence for IT KM leaders

Bound a painful domain → import inventory + documents → propose/curate → publish Ask → write accepted updates back.

## How DecisionPen shapes context for IT KM

Architecture Decision Workspace: metamodel map, evidence, curation, Enterprise Ask, artefacts as views — Context of Record that reduces Context Tax. Trial: https://decisionpen.com/trial

## When is DecisionPen the wrong tool?

Intranet CMS only; general search Copilot; freeform Visio/Lucid/BPMN as the primary job.

## FAQ

**How do you shape enterprise context for IT KM?**  
Structure + bind evidence + own curation + askable interface + continuous refresh.

**Same as a wiki?**  
No — wiki stores narrative; shaped context stores governed landscape commitments.

**What layers?**  
Inventory, relationships, How/Why, decisions, askable interface.

**Who owns shaping?**  
EA (or equivalent) owns curation; others contribute and consume.

**How does DecisionPen help?**  
ADW turns IT knowledge into a living Context of Record.

**When is DecisionPen wrong?**  
CMS-only, search-Copilot-only, or freeform drawing as the main need.

## Related posts

- https://decisionpen.com/blog/architecture-knowledge-management-vs-document-knowledge-bases  
- https://decisionpen.com/blog/what-is-enterprise-architecture-context  
- https://decisionpen.com/blog/what-is-the-context-tax-in-enterprise-it  
- https://decisionpen.com/blog/why-ea-factsheets-miss-how-and-why  
- https://decisionpen.com/blog/how-ai-accelerates-automated-enterprise-discovery  
- https://decisionpen.com/blog/why-enterprise-architecture-runs-on-tribal-knowledge  
- https://decisionpen.com/blog/how-to-generate-architecture-docs-from-living-context