I like and use the idea of creating 'early' diagrams when an initiative begins and these artifacts can take the form of lists of things so they do not need to be visual. The core idea is that most stakeholders cannot see the whole picture and listing out elements that could be affected (processes, connection applications, strategies, business metrics, etc.) is a useful way to bring the teams together and 'hook' them into revealing other elements.
That's exactly it and you can do it in many ways. I tend to think of it as a checklist of things to consider in more detail. For some stakeholders, the list may be obvious but there are always some who do not see the complete picture without, at least early enough.
I like and use the idea of creating 'early' diagrams when an initiative begins and these artifacts can take the form of lists of things so they do not need to be visual. The core idea is that most stakeholders cannot see the whole picture and listing out elements that could be affected (processes, connection applications, strategies, business metrics, etc.) is a useful way to bring the teams together and 'hook' them into revealing other elements.
That's exactly it and you can do it in many ways. I tend to think of it as a checklist of things to consider in more detail. For some stakeholders, the list may be obvious but there are always some who do not see the complete picture without, at least early enough.