Launching EA Initiatives

When an organization is launching any EA initiative program there are major considerations to be made. Typically the top two items to consider are how to link the EA program with facets of the organization and communication.

Figuring out how to utilize existing (and possibly new) technology to help an organization perform more efficiently while working towards goals is laborious. Typically there is such division in standard organizations that identifying the operations plan separate from the IT plan is necessary in order to see where there are opportunities to add or improve function.

There are many saying that elude to how important communication is- one being "communication is key." Communication is a tool that must be utilized in the proper way to ensure clear understanding. Effective communication must be present between the EA architect, team members, stakeholders and consumers. Communication from the EA architect may need to be adapted based on the target audience. To be able to maintain the same message despite the recipients is not at all an easy feat. Targeted messaging further requires the messenger to be able to interpret responses and make any necessary changes while standing on message.

Flat organizations tend to be more collaborative and open to ideas such at EA program implementation. In hierarchical organizations such as mine it may b necessary to win over members of leadership. If this is true there will be a greater need for communication. Most people must have the relative why behind something to help them best see benefits. The why behind something may be different for different groups of people and this will need too be expressed. Using communication as a tool to provide the why and generate EA program buy-in, linking the ops and IT components and effectively communicating the plan is the best bet for organizations such as mine.

Comments

Post a Comment

Popular posts from this blog

Future-State Architecture: Conceptual Level

Building an EA program is not simply evaluating where your organization is and identifying how to put Band-Aids on your current state. A very large part of implementing an EA program is conception- perceiving what will be. An EA Architect must outline the future-state to create the roadmap that will be followed to get there. There are numerous items for consideration in the conceptual phase including principles, process patterns, process typologies, information patterns, application architecture, and data stewardship requirements.   In organizations that do not take the time to envision their future state and consider the elements within the conceptual phase there are typically very poorly implemented EA programs. At times organizations implement programs in haste out of necessity and this leads to inability to implement properly. My organization often implements in haste and runs into these types of issues and the product is not well known, well received or utilized well. The
Read more

IT Strategy

Image
Enterprise Architecture IT strategy is yet another area of the EA program that requires documentation. Document development is instrumental to the success of an EA program because it gives the structure and rules that are needed for the organization to follow. When developing the IT strategy document an organization must form the plan of action needed to reinforce and sustain the mission, strategy and objectives of the organization. Fig. 1- Support Image (http://www.okclipart.com/Support-Group-Clip-Art30jdhthnii/) The document is specific to the contributory efforts of the IT department and be relatively brief. To help with illustrating what will be done, there are change requirement matrix that can be developed. One axis will show IT strategies and business change requirements. The other axis will show enterprise business strategies. How the items listed on both axis relate to each other is denoted by a marking in the corresponding intersecting box. With the aid of this matrix
Read more

Future State Architecture: Logical Level

Image
There are levels to future state architecture. The logical level incorporates communication tools. The logical level is evident in more than just a specific area; it is seen over various business functions. The logical level supports strategy and therefore includes information flows to executive leadership, information architect and EA teams.  In the logical level of future state architecture the logical information flow the customer is at the center of the diagram. This is important to note because with the customer at the center, you ensure that the along with the information that needs to flow out from the customers the appropriate information comes to the customer as well. Being involved in the  EA process embeds the customer in the program and gives them the appropriate amount accountability.  Risk management and  satisfaction are managed through information flow. Proper updates go across banking, underwriting, credit reporting agency, fraud management, information security, m
Read more