“Toilet in the Kitchen” Analogy
Just recently we managed to define guiding principles for managing development of corporate architecture. For one of them we found an analogy that not only beautifully links architecture issues to real life experience, but that actually sticks in mind so well that people are actively using it (not only architects!) so I thought I would share.
The underlying principle is boringly uninteresting “Separation of Concerns”, in my naive language saying “Put things where they logically belong” – you know, addressing the kind of discussions you have when you insist on implementing certain functionality or placing data in a concrete application simply because it’s just logical. Without going into the formal definition of the principle, we are just saying “Please, be so kind and use your BPMS to implement your processes, client related functionality mostly does belong to the CRM and when talking about the CRM, no it’s not the place for your mortgage simulation just because you’ve got full client profile there (by that logic you would end up with just one system anyway:)”.
At last, the reasoning analogy says
“I guess you don’t have a toilet in the kitchen either, eventhough there’s drain and water”.