Best Practice Report

Why Roles Fail — Seven Common Reasons And Remedies

Part 1 Of A Three-Part Series On Why Key IT Roles Failed

Marc Cecere
 and  two contributors
May 03, 2011

Summary

A number of roles in IT can significantly change the organization for good or bad. When they fail, the consequences are severe. From a combination of surveys, interviews, and consulting engagements, we found that each role has its own reasons for failure, but several reasons span all roles. In this first report of a three-part series, we analyze the common reasons for failure across all IT roles and what you can do about them. In the second and third reports in the series, we will determine why specific roles failed and how to mitigate or avoid failure. The roles we analyzed were leaders of applications, infrastructure, and the program management office (PMO), as well as vendor managers, architects, planners, relationship managers, security experts, and demand managers.

Log in to continue reading
Client log in
Welcome back. Log in to your account to continue reading this research.
Become a client
Become a client today for these benefits:
  • Stay ahead of changing market and customer dynamics with the latest insights.
  • Partner with expert analysts to make progress on your top initiatives.
  • Get answers from trusted research using Izola, Forrester's genAI tool.
Purchase this report
This report is available for individual purchase ($1495).