7 years, 6 months ago

EA Roadmap for success: Consultants

<p><span style="color: #505050; font-size: 11px; line-height: 19px;">In this 9th posting we will cover the topic of using consultants in your Enterprise Architecture practice. This may seem like a strange topic to address. After all, we do offer consultancy, so </span><em style="color: #505050; font-size: 11px; line-height: 19px;">of course</em><span style="color: #505050; font-size: 11px; line-height: 19px;"> we can help. That’s our job. There is more to be said about this topic, though, especially in the context of enterprise architecture.</span></p><p></p><div class="captionImage left" style="width: 600px;"><img class="left" src="http://www.bizzdesign.com/assets/BlogDocuments-2/_resampled/resizedimage600375-Roadmap-for-success-Consultancy.png" alt="Part 9. Consultancy" title="Roadmap for succes part 9: consultancy" width="600" height="375"/><p class="caption">Consultancy for Enterprise Architecture</p></div><h2>What Enterprise Architecture is all about</h2><p>In our view, enterprise architecture is all about answering the question: how do we want to organize ourselves? It is a conceptual tool that helps you to get from where you are, to where you want to be. As a discipline, we frequently make use of <em>models</em> that describe – with respect to a set of concerns from a stakeholder – where we are, and/or where we want to go.</p><p>All of this requires an organization to answer some tough questions: who are we? Who do we want to be?</p><p></p><div class="captionImage left" style="width: 400px;"><img class="left" src="http://www.bizzdesign.com/assets/BlogDocuments-2/Consultancy-face-the-reality.png" alt="Facing reallity " title="Consultancy is facing reality" width="400" height="364"/><p class="caption">Facing reality</p></div><p>As most of us know, looking in the mirror can be really hard. It is tempting to only see the good things. Not only that, there’s more that must be taken into account. For example: the principle of bounded rationality (Simon) comes into play when taking into account that we just cannot know everything and thus outside help may be needed. The same goes for group-think: it is a well-known fact that in many organizations the desire for harmony overrides the realistic view of a situation leading to a very slanted perspective of the real world. This typically tends to hamper decision making. Again, consultants may help by providing a fresh pair of eyes.</p><h2>New developments in the market</h2><p>Enterprise Architecture is a relatively young (management) discipline, and we see a lot of development in the field still. It sometimes seems that new (versions of) frameworks and approaches are published every week. A new trend, though, is the publication of case studies, filled with best practices, suggestions for aligning with other frameworks (data management, risk management, security, strategic management, project management and so on).</p><p>Staying up to speed with development in the field is hard and requires time. In our experience: consultants are often asked because of their extensive experience with frameworks and approaches, and therefore have more incentive to stay up to speed.</p><h2>Level of involvement</h2><p>Whether you are requesting help from consultants to avoid / break through the limits of bounded rationality or group think, or because you need specific expertise not available in your organization: stop to think about the level of involvement that you need.</p><p>One thing seems obvious: since architecture touches upon the essence of your organization it makes sense to avoid a situation where consultants are <em>responsible</em> and <em>accountable</em> for your architecture, unless you really know what you’re doing.</p><p>In general, consultants should do what their name says: consult. Give advice. Train. Tutor. Coach. Ultimately, the organization hiring the consultant should remain in charge of their own destiny, after all!</p><h2>Next posting</h2><p>If you’d like to know more, please contact the authors directly at <a title="E-mail Bas van Gils" href="mailto:b.vangils@bizzdesign.com">b.vangils@bizzdesign.com</a> / <a title="E-mail Sven van Dijk" href="mailto:s.vandijk@bizzdesign.com">s.vandijk@bizzdesign.com</a>, or leave a comment. The next post in this series is about using architecture principles and models. It is scheduled to be posted in between 25<sup>th</sup> and the 29<sup>th</sup> of march. </p>