One of the problems of enterprise architects is kind of an inherent urge to see or look for problems in the current situation and strong conviction that a change is needed. Well… Sometimes the best course of action is no change at all. Or what we see as a problem might not be a problem at all. It might even be a desired state (however you might disagree with that, and trust me, I know how it feels:).
So in order to justify that the current state is actually problematic and leads to future that’s not accepted by the stakeholders I started to explicitely put “default scenario” in all discussions and assessments. The default scenario is nothing more than the characteristics of the current state and expected future trajectory/consequences.
This seems really trivial, but the effect is not all that small. First of all, accepting the current state as a valid option for the company makes stakeholders more open for discussion (because otherwise when you point out to problems, your stakeholders are for sure ready to advocate or explain the reasons and more in defense style even though they might not like the situation themselves). Second of all, it makes the situation transparent, so it can be discussed and explicitly compared to change options. And third of all, the kicker: should there be no decision for any change, it’s in fact a decision to stay on the current track with all the consequences. This gives you an all new dimension in argumentations.
It’s really important to note that I am talking about characteristics of the state – as objective as possible description of how the “things” look like and behave. It’s not judging, so watch out for putting your preference or negative undertone to what you write or say. It’s up to your stakeholders to tell you whether it’s desired (with all the consequences) or problematic and should be tackled.
More often than not, you are about to interfere with someone’s interests and turfs, so really try hard to be as objective as possible, this game can be quite tricky.