Though perhaps another way to put it is that EA needs to be interested in everything. BPM is a distinct discipline in its own right, with its own distinct skillsets: but enterprise-level problems do arise if it isn’t properly connected with everything else. Given that BPM is a specialist discipline, it’s not really its job (or often its competence) to think in terms of overall cross-enterprise impacts: that’s what EA is there to do. All that we need to ask of BPM is that they respect the need for cross-enterprise integration, and at least listen to the advice and suggestions from elsewhere that we bring to them from other specialisms in the enterprise.

That’s also what I meant by the Enterprise Canvas as ‘one map to bind them all’: it’s not a panacea, ‘Life The Universe, Everything’, it’s just a really useful way to bind together all manner of other models, highlight the gaps, and provide pointers as to how to fill those gaps. That’s what I hope this shows, anyway.

Thanks again, of course.

I was particularly intrigued by the BPMN one as it demonstrates what a BPMN diagram doesn’t show us.
It indirectly also illustrates why there is a need for BPM to be part of EA rather than something separate as some blogs have proposed – i.e. because you need EA to complete the missing parts of the picture.