In part 10 of “Memoirs of an Enterprise Architect” I discussed why when implementing EA in your organization, you need everyone involved to know what’s in it for them. This week I will discuss what Governance is and how it is a necessity in order to be successful with Enterprise Architecture.
What is Governance?
What do you think of when you hear the word governance? I used to think it just meant there would be more hoops to jump through to get things done in my organization. Governance is the opposite of that notion. It is a set of processes, roles, standards and metrics that enable an organization to achieve its goals by using data and information efficiently. Think of Governance as a good thing and a way to make your job easier.
So what does this have to do with the price of tea in China or EA?
Governance has everything to do with Enterprise Architecture. Follow me for a moment. When I started this blog series I said that EA manages complexity and delivers business value. It does this by integrating disparate data sources together into a central system that enables you to analyze the data, how it relates and make strategic business decisions. When done properly, this can transform your organization and it can become a key differentiator in your industry.
What’s my point?
The point is that without governance, there would be no way to ensure the data is complete and correct. Below is a list of goals and objectives that governance sets out to accomplish within an organization in the areas of policies, standards, strategies, and metrics.
- Track Compliance
- Resolve Data Issues
- Correct Data – signed off approval that data is correct
- Complete Data – required attributes filled in
- Valuable Data – answer questions about your business
Remember, when adopting governance in your organization, you don’t need to try and implement everything under the sun. It is an iterative approach and as you become more mature as an organization, you can implement the policies, standards, and strategies applicable for the level of maturity you are trying to attain.
Troux has a very robust governance, workflow, and policy engine. One of the struggles with implementing governance is where to do it. Do you implement governance native to each source repository or do you centralize it? If you centralize it, then how do you govern all of the source data?
The easiest and most efficient way is to have centralized governance. Not only should you select a single solution if possible, but also centralize the team to manage the policies, standards, strategies, and metrics.
If you choose to use Troux or are using it now as your Enterprise Architecture solution, then implementing governance while using it as the vehicle lends itself quite well.
Once you have identified key data sources that need to be integrated to allow you to answer any business questions senior management is asking for, you can put the processes and policies in place as the data feeds into Troux. Then the data owners can receive tasks and/or emails informing them what needs to be done to correct the data in question.
There is so much more to talk about with governance, but I just wanted to highlight some key points and why it is not optional if you want to have a successful EA program in your organization.
What are your thoughts on centralized governance? Please join the conversation.
See you next week, same time, same place where I will discuss the IT Chargeback Model.