Architecture Governance

Many companies that I talk to are trying to up-level their architecture governance. It seems to be a new trend to prioritize architecture governance and it’s great to see!

I get a lot of questions about architecture governance such as:

• what are best practices
• what approaches have we put in place in Salesforce IT
• what should be avoided
• how do you measure success of governance

First let me start with WHY you want to create a level of architecture governance in all companies.

In a nutshell, good architecture governance helps increase business agility.

Yes, I know it seems counter-intuitive but governance done well can actually speed things up. If you know how to easily find architecture standards, principles, reference and implementation architectures, you can move more quickly to create solution architectures that are fast, efficient, secure and manageable. The opposite is true — if you need to hunt around to find architecture information, you can waste a lot of time, get frustrated and worst of all, create poor solution architectures.

So what should architecture governance look like? I recommend the following architecture governance components: