{"id":1432,"date":"2015-02-25T00:00:18","date_gmt":"2015-02-25T00:00:18","guid":{"rendered":"https:\/\/blog.planview.com\/?p=1432"},"modified":"2022-04-08T09:07:25","modified_gmt":"2022-04-08T14:07:25","slug":"secret-behind-selecting-right-enterprise-architecture-tool-0","status":"publish","type":"post","link":"https:\/\/blog.planview.com\/secret-behind-selecting-right-enterprise-architecture-tool-0\/","title":{"rendered":"The Secret Behind Selecting the Right Enterprise Architecture Tool"},"content":{"rendered":"

Implementing an effective enterprise architecture<\/a> program is about more than just selecting a tool to aggregate and visualize data. As an EA solutions provider, we talk to a lot of organizations in the early stages of implementation, which gives us a unique, clean-slate perspective on the selection process. Frankly, the most obvious misstep that we see is an emphasis on the functionality of the tool versus what it can ultimately accomplish toward real business success.<\/p>\n

Often, when we get into the room with an organization in the evaluation phase, they tell us about how the EA tool(s) they have used in the past delivered little value and poor insights. They want to jump right into the functionality our tools provide as if the functions themselves are the missing puzzle piece. Yes, it\u2019s important to access the metamodel and to be able to load and manage the data repository. But it\u2019s also integral to understand data reports and analytics as well as ensure security and scalability. The tools can almost always collect the data; it\u2019s what you do with the data that creates value. That value can only be measured against goals, so that is typically the first bridge to cross.<\/p>\n

\n
\n

Table of Contents<\/p>\nToggle<\/span><\/path><\/svg><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n