Change at an architectural level is always transformational. But too often architects have struggled to demonstrate or realize this potential for making a significant, positive difference at the enterprise level. Instead, big changes are more frequently driven by the architectural opportunities from new technologies.
This is starting to change, and leading enterprises are planning architectural change that genuinely combines the organizational, business, and technology perspectives. Enterprise transformation that successfully unites all three viewpoints requires a new technique to raise the architectural debate to the level of senior decision makers.
Enterprise Patterns elevate the debate by:
* Providing a means for aggregating viewpoints and lower level patterns into a holistic visualization of architectural possibilities.
* Focusing debate at the architectural and enterprise level by summarizing and synthesizing a mass of detail into a small number of succinct Enterprise Patterns.
* Highlighting relevant information for key decision makers in a consistent, concise, and comprehensive summary.
* Grounding discussion around solid choices and measurable outcomes by adding metrics to show the value, costs, risks and options enabled or constrained by an Enterprise Pattern.
The upcoming issue of Cutter IT Journal invites practical insight and guidance on how Enterprise Patterns are being used to drive transformational change. We invite article submissions from those who have experience in using Enterprise Patterns, as well as from skeptics with an alternative point of view. We encourage insight that goes beyond the theory — providing our readers with best practices for initiating and implementing Enterprise Patterns in their own organizations.
Topics may include but are not limited to the following:
* What are the benefits and pitfalls in using Enterprise Patterns?
* In which business scenarios have you found Enterprise Patterns helpful?
* How have Enterprise Patterns made a difference to decision making, especially at senior levels, or in collaboration across business divisions?
* What difference have Enterprise Patterns made to the role and structure of the EA team?
* What organizational barriers have you faced in using Enterprise Patterns, and how have these been resolved?
* What lessons learned have pioneers in this field uncovered? What best practices would they urge the rest of us to follow?
* How do Enterprise Patterns augment other EA techniques and approaches?
Additionally, if you have a story to share about your own use of Enterprise Patterns we would love to hear it. If necessary, sanitized versions are welcomed. And if possible, please include the business case describing the operational and financial objectives.
TO SUBMIT AN ARTICLE IDEA
Please respond to Roger Evernden at revernden[at]cutter[dot]com, with a copy to itjournal[at]cutter[dot]com, no later than 5 October 2012 and include an extended abstract and a short article outline showing major discussion points.
Articles are due on 9 November 2012.