The Cloud Process Kit includes a full eco-system diagram for exactly that reason.
Below are three things that the eco-system view gives you that a set of individual process maps cannot:
Improved Visibility & Control:
When we implement cloud solutions, we need a one-stop shop of the processes to account for what hand-ins, hand-outs and nested processes are called upon and when. We do this so we can authenticate that we haven’t unwittingly created dead-ends for our data to run in to.
If following a series of fine lines on an A1 sized PDF proves too much, then you can revert to the mapping exercise versions of the processes which act like jigsaw pieces to the singular ecosystem.
We also number the connections between the processes, so that in the Visio version of the Mapping Master file, searching for numbers should reveal the hand ins and hand outs between processes that supports the creation of the eco-system.
Improving Maturity:
Don’t be the organisation that says: “We have a CMP installed – our job is done”. You could be hitting performance ceilings with given processes, and it’s only by tracing those processes through the eco-system that you realise a preceding process isn’t as mature as it needs to be and is therefore impacting downstream process performance.
Highlighting Complexity:
Most senior stakeholders underestimate the scope of a cloud management implementation until they see the full eco-system in a single view. That moment — when 26 interconnected processes are visible at once — is consistently what converts a “nice to have” conversation into a resourcing one. The equivalent maps exist for HAM and SAM; the reaction is the same.
As with the processes that ship with the Cloud Process Kit, the greatest value you can derive from this eco-system is when you make it your own – stress test the connections that we have modelled, make sure they work for you and your organisation.
Build that better mousetrap!
Good Luck!