# Why do solution architects rediscover the landscape on every project?

> Canonical: https://decisionpen.com/blog/why-solution-architects-rediscover-the-landscape  
> Published: 2026-10-17 · DecisionPen · Living EA series (A2)  
> Related docs: /docs/solution-architects, /docs/it-knowledge-continuum, /docs/incremental-modelling

## Summary

Solution architects often inherit neither a living enterprise map nor How-and-Why context. Each programme restarts discovery (interviews, HLDs from scratch) while the EA repository stays untouched. A healthy loop inherits curated context, generates documents as views, and contributes learning back.

## Why does every project feel like starting from zero?

Usable landscape context was never handed over. Search language: EA to SA handoff; why rebuild architecture every project; inherit enterprise context for solution design.

## What breaks the handoff from enterprise to solution architecture?

Thin factsheets; stale untrusted models; no path for project learning back into enterprise memory.

## What should a healthy EA–SA loop look like?

Inherit curated slice → design → generate artefacts as views of shared truth → update the map. HLDs should not be the only place context lives.

## How does this connect to manual modelling pain?

If populating the enterprise map is clerical and incomplete, SAs never inherit anything worth using.

## How does DecisionPen solve this?

Inherit curated map slice + evidence; generate HLD/ADR artefacts from templates as views; Ask before interview archaeology; write accepted design updates back so the next programme inherits. Trial: https://decisionpen.com/trial

## When is DecisionPen not the right tool?

Freeform diagram drawing (Visio, Lucid, BPMN canvases). DecisionPen = living context and generated artefacts, not a drawing board.

## FAQ

**Why do solution architects rediscover the landscape?**  
Thin/stale enterprise repos → rebuild from interviews and docs per initiative.

**How should SA work update institutional memory?**  
Inherit curated context; contribute updates back; documents as views of shared truth.

**What breaks the EA-to-SA handoff?**  
Inventory without How/Why; no trusted living map; no feedback path from projects.

**When is DecisionPen the wrong tool?**  
When freeform diagramming is the job.

## Related posts

- https://decisionpen.com/blog/why-ea-factsheets-miss-how-and-why  
- https://decisionpen.com/blog/why-enterprise-architecture-runs-on-tribal-knowledge  
- https://decisionpen.com/blog/why-architects-hate-manual-ea-modelling