The first cause of failure is the silos in many of today’s organizations. There are often too many stakeholders involved in APM decision-making ranging from application support, server teams, network teams, database teams (DBAs), application developers, and various architects across the organization. We’re also seeing more non-technical users, such as the business owner of an application interested in seeing usage and performance data on critical Business Transactions within the application. These business users will become a more central user of APM in the future. It’s critical to identify the primary user of the product, and determine requirements focused on those primary users. Secondary users can have input but should not be the ones driving the key decision points. As products mature, they can sell into multiple areas or even cross sell through teams, but it shouldn’t be the focus of the initial implementation.