We architects like creating models, but do we ever ask ourselves what exact questions users have? Who will be the users of the model, what’s important to them, what are their use cases? What does a good model do that allows them to get the answers they need more easily?
For people who come from a software architecture background and have used UML as their primary visual language to describe technology systems, ArchiMate can sometimes seem like a sort of inferior cousin - kind of the same family, but not quite.
We make great use of pictures in all types of architecture work, whether it is in the form of component diagrams in detailed solution architectures or core diagrams in the more abstract enterprise architecture domain.