Model Value Chain

Based on my experiences with the Business Transformation Grid, the idea popped up that all artefacts that one stores inside the framework often will be models. In architecture, we often use models to communicate to stakeholders. If considered from an IT-development perspective, you could also discuss that models therefore need to add value when communicated in the development chain. A models adds value because it is a part of knowledge transfer. So the knowledge transfer inside a typical IT development organisation can be considered a Model Value Chain. The challenge now is, how can we design models that effectively add value inside such a chain, i.e. that are designed to close the competence gaps between parties involved inside the IT development chain, since that seems an important reason why we communicate using models. The picture shows a high-level (fictive) example where the arrows represents models that are designed to transfer knowledge during IT development & IT operations.