Best Practice Report

Why Roles Fail — Seven Common Reasons And Remedies

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

May 3rd, 2011
Marc Cecere, null
Marc Cecere
With contributors:
Khalid Kark , Lauren Blackburn

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.

Want to read the full report?

Contact us to become a client

This report is available for individual purchase ($1495).

Forrester helps business and technology leaders use customer obsession to accelerate growth. That means empowering you to put the customer at the center of everything you do: your leadership strategy, and operations. Becoming a customer-obsessed organization requires change — it requires being bold. We give business and technology leaders the confidence to put bold into action, shaping and guiding how to navigate today's unprecedented change in order to succeed.