Sunday, 13 September 2015 17:47

IT: We Don't Need No Stinking Leadership

Rate this item
(2 votes)

I have never posted email marketing results, because... well, let's face it... it is kind of tacky. Now and then, however, there is a story to be told. In my opinion, this set of statistics is a little over-the-top in what it shows. I can only see one way to interpret it other than Information Technology "leaders" simply do not care about leadership.

To understand how I can make such a brash statement, you need a little background...

Leadership Drives Project Success

As any of the readers of my 100 plus posts in this blog know, I am continually harping on fact that we are short on leadership. I feel that middle management over the last decade or two have been promoted for reasons other than their leadership qualities and there is little desire in corporate America to remedy this problem. I know that statement sounds harsh, and this post goes a long way in disproving this statement, but I am only going to refine the statement with data.

One of our business goals in 2015 was to fix an issue in our offerings. I felt it was a little hypocritical to dwell on this subject of weak leadership without offering a solution. To address this, we have invested a few months reviewing various programs so that we could offer recommendations on good leadership programs. Our view of the best program would:

  • Be long lasting: The first step was to find a program that was not a "flash in the pan." Something that felt like it was offering a long-term solution to the problem. This ruled out many of the one-day and one-week courses.
  • Be directed at the people doing the work: The second requirement was that it had to be directed toward the people who directly make an influence on project success rate. These would be IT managers, PMO managers and their staff, and senior project managers.
  • Create a leadership cohort: Every leadership book says that you need to build a cohort of peers to help you when you reach a tough spot. Hence, the program had to build a strong bond between the attendees so that over the coming years they could rely on one another for advice and to hold each other accountable to their ethics and morals.
  • Tried and tested: The program had to be established with hundreds of references across the country.

After long deliberation we settle on the Society for Information Management's (SIM) Regional Leadership Forum. As it spans nine months with numerous programs across the country and has graduated over 4,000 attendees, we felt that it had the credibility we needed. It is targeted at up-and-coming leaders in an organization, which addresses our demographic. And, most importantly, as the cohort interacts 6 times over the course of nine-months, so students would build intimate relationships with their peers.

Who Listened

Proud of our selection the next step is to market the idea. This is where the story takes an odd turn. But to be sure I am clear I must bore you with a few marketing concepts. As you know the internet provides many tools to see when people open emails and click on links. It is also standard practice to segment your audience based on the message you want to send. These tools are so common any of you with marketing knowledge are yawning in boredom. We segmented our marketing into three groups—PMO managers and senior project leaders, IT leaders (CIO, IT Director, and the like), and other executives (CEOs, COO, CFO, VP, etc.). Changing a few sentences in the middle of the generic email to properly address the audience we sent out the emails last week. If you want to see the content of the email, let me know and I will send them to you. However, I think you will be missing the point going that route.

Table 1: Mailing Analysis
Group MailingCountOpen %Click %
PMO16530%18%
Other Executives21032%12%
IT Executives15626%0%

IT Did What?

As I write this post, about 48 hours from the email blast, I am still drop jawed at the results. They are copied into Table 1. With a little marketing knowledge you might know that a 25-30% open rate is at the upper end of respectable (see benchmarks on Mailchimp or Constant Contact). As for 12-18% click rates? To put it simply, there might be a few marketing folks out there who don't believe those number as they are pretty darn good. But, again, that is not where focus needs to be drawn. The glaring issue is the IT click-through rate:

Zero. Nada. Zilch. Null.

Seriously? Maybe these folks should talk to their bosses who ARE clicking though and reading about the program (and, by the way, taking the next step). What is it with our IT folks? Are they above leadership? Or, do they just have their head in the sand?

I am sure you are looking for the logical answer... "It was the difference in the emails," "IT knows better than to click on links in emails" (baloney!), I am sure you can come up with a dozen other reasons. I doubt they will hold up to scrutiny, Plain and simple this is sad.

Projects Need Leaders & IT Has Horrid Success Rates

If there is any group in the organization that needs to improve project success rates it would be IT. "IT Projects," or should I say projects that have a large IT component, fail at rates estimated at 60-80%. These projects need leaders more than any other. IT's bosses know that, their PMO managers know that. By their click rate they are hungry for leadership options.

I know from experience that many IT leaders understand there is a leadership problem to solve. But, I cannot help looking at this data in awe and wonder how it can happen.

I want to yell at the top of my lungs, "Hey, IT, your business partners need you to be business leaders. You need to talk like a business leaders. You need to act like a business leader. You need to step up to the plate."

Read 6934 times

Related items

  • Success vs Culture

    The other day a Latvian student contacted me for my views the connection between culture and success criteria—an important and intriguing topic. After working in Taiwan, Singapore, Korea, Japan, Israel, United States, and Canada, I wear many scars of both blatant and subtle cultural violations. I also know that within a culture one person's success is often another person's failure. So, after dispelling concerns about clicking on some random email link, I completed her survey (please feel free to take it yourself). In the process, I struck up a friendship with the student, Kristine Briežkalne, who is studying at Riga International School of Economics and Business Administration . She has some interesting views and presented me with a Venn diagram showing four frames to a project (business, client, project management, and growth perspectives) and how they intersected. As the diagram is part of her Master's thesis, I will let you ponder the how to label the overlapping areas (an eye-opening exercise).

  • Kill The White Knight

    There is a reason we do not teach classes on fixing failing projects. Many a cynic feels that we simply do not want to teach our trade, however, our reason is far nobler—we should be teaching prevention rather trying to create white knights to save the day. It is the same philosophy as building a fence at the cliff's edge rather than an emergency room at its base. Our language is replete with idioms telling us to look past the symptom and address problems at their root cause. 'An ounce of prevention versus a pound of cure' or 'a stitch in time saves nine.' Please, feel free to supply your own in the comments. Unfortunately, most of our businesses loathe this philosophy, waiting to address an issue until it is irrefutably broken.

  • The Executive-Project Manager Gap

    It was such an innocuous question, "Working on an article; what is the biggest problem you see with project governance at orgs? Can you comment?" Can I comment? Really? That is like cheese to a mouse. Where could I start—bureaucracy, draconian process, poor executive sponsorship, disengaged leaders? Plenty of fodder, because they all lead to project failure. I fired off, "Creating an over bureaucratic morass stifling innovation & implementing process instead of cultivating leaders." Then the maelstrom started and it went directly to the gap between the executives and projects managers. Naomi Caietti, Robert Kelly and I had a great conversation. Most of the thread is below.

  • Disband Your PMO

    After nearly 30 years of project work, I struggle to understand the role of a project management office (PMO). Even though, I have written of the pros and cons, and read a plethora of articles, opinions, and how-to guides little has been done to convince me that the PMO is reducing project failure. It seems to be nothing more than a tool to fill a void in leadership? Even the acronym, which is so widely thrown around, has little meaning as the "P" has no less than four meanings. It is an executive's crutch for their lack of understanding in how projects work. These, like other, unattended holes in the corporate accountability create opportunities for new and greater bureaucracies and empires that further obfuscate accountability.

  • The Catch-22 of Organizational Change Management

    "Kotter, ADKAR, or CAP which methodology should we be using to build our approach to improving project adoption?" I hear this question repeatedly from people trying to implement an organizational change management (OCM) program. The problem is that is the wrong question. Take a perfunctory peek at any of the models and you will see that in the quest for an answer people have mistakenly jumped over the first few steps and they head down the road of failure. It is a Catch-22; unless you already have an OCM process in place, you will most likely fail at implementing it. Putting one in place, however, is a change—one of the most difficult cultural transformations your company will undertake. As a result, people jump to the solution stage, which is well down the change management process path (which, they did not know, ironically, since there was no procedure in place).

More in this category: « Extensibility

Leave a comment

More Info on Project Recovery

Tell me More!

Please send me more information
on fixing a failing project.

Rescue The Problem Project

Internationally acclaimed

Image of RPP

For a signed and personalized copy in the US visit the our eCommerce website.

Amazon logo
Buy it in the United States Buy it in Canada Buy it in the United Kingdom
Buy it in Ireland Buy it in Germany Buy it in France
Buy it in Italy Buy it in the PRC
Buy it in Japan
Book sellers worldwide.

Upcoming Events

Other's References

Sitemap