The need for a blueprint

In recent blogs I addressed the importance of a blueprint many times. For many companies, it goes far beyond usefulness, it is crucial to survive. In large corporations, the ICT has become very complex. Changes can come from new user requirements, laws and regulations or ICT as a particular system requires an upgrade to maintain support.
Next, the internal struggle begins. Requirements, risk analysis, budgets and priorities need to be completed. Lack of a blueprint and supporting software results in a long and complex process. If the competitor does is decisive, it can cost you the head. A CEO of a former mobile phone manufacturer has once called "our competitors bring a new phone on the market quicker than that we can adjust a PowerPoint." So if you want to become "agile" and want the failure costs to go down: make a blueprint and use supporting architecture software!