ArchiMate Stakeholder Communication and Model Application
Stakeholders drive the model
ArchiMate is a communication language. Start from the stakeholder and their concern, then pick the viewpoint, then the elements. Executives want capability and value views; architects want layered and cooperation views; operations want technology and implementation views. A model that answers no stakeholder concern is decoration.
Tailoring for audience
Use abstraction deliberately: hide technology detail from business audiences, hide business nuance from infrastructure audiences. Keep element names in the stakeholders' vocabulary. Use grouping to visually organize without adding semantics. Color and layout are conventions, not language semantics - a question that hinges on color is testing convention, not the metamodel.
Model quality in communication
Good models are consistent (one name per concept), complete for the concern (not for the whole enterprise), and unambiguous (relationships labeled by type). Avoid modeling every relationship; show the ones the audience must reason about.
Traps
- Choosing a viewpoint because it is familiar rather than because it fits the concern.
- Over-modeling: including elements irrelevant to the stakeholder's decision.
- Assuming color or notation style carries metamodel meaning.
- Confusing a deliverable (a work product) with a view (a model projection).
Rule of thumb
Before answering a stakeholder-communication question, ask: who is reading this, and what decision are they making? The answer usually eliminates two or three distractors immediately. If an option optimizes for completeness over the audience's concern, it is usually wrong.