Shaping a Vision for Where you are Going
How can architecture create results?
If you have questions like these below, we can help :
- My users are clamoring for iPads or access to Facebook, how do I make decisions like this?
- What kind of stuff do I put in the cloud, and how do it without breaking things?
- Is this SOA thing real? How do I build things once and then actually reuse them?
- I think someone is about to implement a new application that is very similar to one we have...how do I handle this?
- Where is my industry going to be five years from now? And how do I ensure that I’m on the right path?
- How do I identify business processes that can be improved and made more efficient?
- How do I increase access to my users' data, while maintaining quality and keeping costs down?
- I need to do more (work) with less (resources)...where do I start?
Our approach to Enterprise Architecture is simple - there are three distinct points of view, or value propositions, that are found in EA and it is critical that the value and output of your program is in line with what is being expected. This is why so many EA programs struggle - they are being sold as one thing, but are delivering something else all together different. "EA for Executives" is about supporting strategic thinking for executives; it is about setting the target-state, not the current-state. "EA for Management" is about optimizing the current-state and doing more-with-less; it is all about the current-state, and not about where you want to be 5 years from now. And "EA for Users" is about supporting development of better solutions and applications for users; it is the APPLICATION of EA to a business problem, and is closely linked to Solution Architecture. If you don't know which of these 3 points of view you are serving, it is difficult to know what kind or artifacts and value you will produce.