There is often a tendency for companies to prioritize action and delivery over planning and analysis. More “Deliver the widgets!” and less “What does our company actually do?”
This can be seen in places where decision making is driven by technology and timelines instead of desired business outcomes, where the “How” and “When” is obsessed over while the “Why” is practically forgotten.
But friends! It doesn’t have to be this way!
In the world of effective Business Architecture, understanding the “Why” actually enables and accelerates the “How” and the “When”. In other words, if people on Project XYZ actually see and understand what the company does, why it does it, what business problem is being solved by their project and how the thing they’re delivering helps move the entire enterprise toward its goals… well… things go faster, smoother, cheaper and end up better for everyone.
My 100,000-foot view sounds easy. To dig into the right level of detail and understand Business Architecture, how it works and what it can really do, I turned to my smart friends Whynde Kuehn, Oliver Cronk and Phil Yanov.
(By the way, Whynde is a globally recognized expert, consultant and educator in this space. A quick peek at her LinkedIn profile will give you the scoop…)
In this Episode:
- What the heck IS Business Architecture anyway?
- How is it practiced? What are the methods and frameworks?
- What benefits does it provide? Who in the company should care?
- What are good examples of Business Architecture practice? What are bad ones?
- How does Business Architecture relate to Enterprise Architecture?
- How can you, yes YOU, get started in Business Architecture either as an employee in a company or as a consultant?
Add your thoughts to the conversation on LinkedIn or YouTube.
Be sure to sign up for email updates whenever we post new content. It’s right over there on the right hand side of the page >>>>>
You can also like and subscribe on the YouTube Channel (and you should!)
