RSS

Tag Archives: Project Team

Comms Principle #5: Engaging Senior Management

Having not blogged since early March (well over 4 months ago), I’d like to start by saying that this next post has been several months in the making.  That would imply that there’s going to be lots of good stuff in it.

Unfortunately, though I’d like to say it, I can’t.  I just got real busy starting a new job and the blog slipped off the radar for a few months.  Last week however, a colleague whose opinions I value said she’d enjoyed reading this and that I really should find time to continue.  She was right and so here I am, back at the keyboard on a Sunday morning.  (You know who you are – thank you).

So while I clearly haven’t been researching and writing this next post for months, I can however say that it has been many years in the making.  In fact, this particular post was prompted by a message I received from Project Management Hut in response to Principle #2, where I alluded to a previous experience that I will now describe in detail.

In the nearly two decades that I’ve been creating and giving communications and presentations to and for senior management, I’ve tried a few things that have failed, and a few that worked, and I like to think that the more I do it the better I know how to do it.

So let me say, first of all, that this post is not about how to engage properly with a group of senior stakeholders that your project needs to convince to follow a management-instituted program of change.  It is about engaging with the senior executive within your project, and allowing him or her to engage in a meaningful way with those whose permission he or she needs to run the project.  I feel that I’ve covered the former group in an earlier post.  The latter group are different beasts.

A number of years ago, I got the chance to work for a man who went on to become my personal business hero.  I’m not going to mention his name since that would be indiscreet, so for now let’s just call him Bob (and before anyone goes running to LinkedIn, he’s not one of my contacts).

Bob took over a project that had cost a small fortune to run, had produced next to nothing of value, and whose executive level sponsors were growing impatient.

One of his first tasks – we all knew this – was going to be to trim the project team.  I was absolutely certain that I would be in the firing line since Comms is always an easy sacrificial lamb and, if I’m honest, I had achieved nothing of value either.

However, as I went through the first couple of weeks and he pulled his plans together (barely speaking to me at all), I became impressed with his clarity of vision, his no bullshit attitude and his absolute focus on coming up with a recommendation that made sense, irrespective of who it annoyed, or indeed whose career it impacted.

Finally, he gathered his extended senior team (about 15 of us) together.  That team nominally included me, but ironically I’m damn certain he didn’t know my name.

He presented his goals, objectives and plans, with such simplicity of thought that the conclusion he led us all to was inescapable.  Then he went round the table, asking everyone in turn if they were happy.  Yes, yes, yes came the replies, one after another.

Knowing that the plan of the previous project leader had bogged down due to a lack of air-cover from senior management, I still had doubts.  But I’d heard good things about him, and I liked his vision so (figuring that I was going to be fired anyway), when he turned to me and said “Are you happy?”, I decided to simply put my cards on the table.

I told him that I wasn’t happy.  I said that I’d seen a lot of plans which made sense and that failed to deliver.  I informed him that even if this plan turned out to be better, the road ahead would still be long and hard, and the challenges were no less real with his leadership that they had been before.  The room went very quiet.

Your country needs you!

Your country needs you!

Then I added that I had asked colleagues whose opinions I respected for their views of him, and had heard that he never set an objective that he didn’t truly believe he could deliver and that his focus once an objective was established was intense.  I concluded that, while still being unable to proclaim myself happy, I was perhaps somewhat more optimistic.  I was painfully aware that I was the only person who had said they were not happy but, as my father used to say, faint heart never won fair lady.

Bob pointed his finger at me, and fired me.

Just kidding.  He banged his fist on the table and (literally) shouted “You are on my team”.

Four weeks later, the project team of nearly 100 had been cut to about 15 and over the next two years, this man became an inspiration to me.

Our first six months were essentially spent pulling together a recommendation for the Corporate Executive Board.  With so much money spent already, it was hard to do anything other than continue, rework the strategy, bring in fresh thinking/energy and charge at the brick wall again.

Bob had different ideas.  And as I spent hour after hour, week after week, working with him and pulling the essence of his proposal into a presentation (or in reality a series of them), I grew to understand the importance of engagement and syndication.

He took his ideas to each board member individually, and listened to their responses.  He edited the proposal.  He engaged with other key stakeholders, and edited it again (or rather I did).  He crunched masses of data, but only with a view of reducing everything to a simple expression.  He syndicated with the board again.

The proposal, in essence, was to kill the project.  And this proposal was going to be a shock since the amount spent was already – well – think of a really huge number and then double it.

Not only did the proposal recommend killing the project, it clearly articulated the reasons.

The reasons were varied and complex, but were expressed as simple, direct sentences.  And much as they pointed the finger at the project team, they were also very clearly about the failings of the senior executives, many of whom sat in that room.

I’m paraphrasing, but basically the recommendation ran as follows.

Protect your ground troops

Protect your ground troops

You guys keep asking us to spin gold out of straw.  While this is difficult, we all know that it is also possible.  Others know it’s possible too.  But it’s going to require a lot of change and a lot of people don’t like that.  The key issue is that you tell us to deliver it but you don’t share your direction with the rest of the organization, you don’t take ownership of the outcome, and you don’t stake your credibility on its success.  I therefore recommend we kill this right now, write the money off and let everyone go because until you are prepared to show commitment, your approval has no value.

He then went on to reveal that the pre-syndication of the presentation showed that half the board agreed with this position, and supported the recommendation, a fact that surprised the board but was entirely accurate.

The presentation was, of course, a double-bluff.  He knew they could not be seen to just chalk this up to experience and close it down, but he equally knew that without air cover the project was doomed to failure.  The repeated requests from some board members to “prove it” (as opposed to approve it or kill it) were a smokescreen for a lack of either understanding or courage.  He even produced an airline ticket, dated for the next day, to demonstrate that he fully expected to be fired as a result of having the temerity to point this out and was ready to fly home into retirement.

As he had hoped, the board than asked what he would ask of them.  What was the level of commitment needed?

Alexander and the Gordian Knot

Alexander and the Gordian Knot

He shared details of what would be required, what the benefits were, and what the huge challenges would be that needed to be addressed.  And then he told them the story of Alexander and the Gordian Knot, and said that great leaders with true sense of purpose will not shrink from enforcing the difficult decisions.

I’m sure you’ve found this little story fascinating.  Or maybe you haven’t.  But it was a story I thought was worth telling because I personally learned so much from it.  The lessons, which I find hold true to this day, break down into four simple but powerful requirements:

Air Cover – Your executive sponsors must be made to understand that if they make a decision, they have to stand by it, display visible commitment to it, and put their own credibility on the line.  Approving something and then abdicating responsibility for delivery is a copout and your change program is likely to crumble at the first sign of resistance because it has no foundation.

Enforcement – Every now and again you will meet a naysayer who is very senior, maybe even a board member.  Do what you can to find out their views, why they dispute your strategy, and try to convince them.  However, if it proves impossible, that is the time the head honchos earn their salaries.  Are the objections reasonable?  If so they must be considered carefully.  If not, the principals of the company need to be prepared to use Alexander’s solution to sever that which cannot be unravelled.

Incentives – There is no clearer way of displaying commitment to something than by tying your bonus to its delivery.  It takes a very brave person to suggest this to a senior executive team (as Bob did) and it takes an even braver executive to agree, but no signal can be sent that is more impactful.

Syndication – Until I met Bob, I had always believed that keeping your powder dry was the best way to ensure maximum effect.  And it is.  But it is not a way of ensuring maximum consensus.  By soliciting responses, you not only understand what the objections are,  you also develop a map of who supports you and why.  This knowledge is invaluable if you know you are going to need to make some direct comments.

Bob has been retired for several years now.  I still hear from him every couple of years.  But I will never forget the 24 months I worked for him.  He taught me more about listening than anyone I have ever known.

Listening is the key to any successful change program.  Many people think that listening is an entirely passive activity, but they couldn’t be more wrong.  Listening is the single most proactive step you can take towards understanding.  It is therefore a particular shame that so many senior managers mistake listening for inactivity.  In my entire career, I have never been busier than the first six months Bob and I spent listening, adjusting, and listening again.

Sometime in hopefully the near future, I will get around to the next post, which will be the last in this series about Communications Principles.

 

Tags: , , , , , , ,

Comms Principle #4: Multi Faceted Communications

Yes, they are all different

Yes, they are all different

With the multiple forms of communication that are at our disposal these days, it is inexcusable not to engage with stakeholders to determine whether communications are being well received, or whether they are leaving gaps. The problem in many cases though is that if you have several hundred, or even thousands of stakeholders to manage, catering to such a broad range of feedback, requests or issues is going to be tough.

And this is where we begin to see the exhaustively detailed work done during the stakeholder mapping and segmentation process start to pay dividends.

A thorough understanding of who your stakeholders are, their level of influence, their background and who they interact with will provide you with a clear picture of the form or forms that your response needs to take.

Once you have all your stakeholders mapped, you need to set up properly in order to provide a streamlined approach to handling responses.  By “streamlined”, I mean considering the development of a number of potential channels and matrix structures.  So let’s take a look at how this can be achieved.

Firstly, you need to make sure that the obvious issues are well in hand.  Assuming you are a member of an experienced and knowledgable Project Team, the first steps should be self evident – development of a list of terminologies or acronyms commonly used, and a list of Frequently Asked Questions.

specialist_versus_generalistNot only will the development of these two vital communications pieces provide you with a sound platform for understanding the scope of the communications challenge, they will also help you personally to understand the detail.  Most Comms Managers are generalists, not specialists, but in order to make the best use of your time you need to develop at least a reasonable grasp of your subject matter.

Use the experts on you project team to help with this.  Initially, they will probably be quite willing to help, but may become a bit more resistant as you push them to provide you with better answers.  And don’t forget, the answers they provide will not be the end of the story – many stakeholders may not believe the answers, or believe that they are wrong, incomplete, or miss a number of issues.  Only once you have got the position recorded can you start to build a picture of where the gaps exist, but at least you can make a start on trying to get everyone onto the same page.

One other point on this.  People tend to view a new Comms Manager as someone who will communicate innately, someone capable of filling a gap while operating in a vacuum.  This, of course, is a pipe dream.  You will need their help and their expertise in order to develop messages that resonate.  As you increase your own understanding they will expect you to be able to do more on your own, but of course your greater understanding will also mean that you will notice gaps or inconsistencies more readily, and when this happens you will start to challenge the answers your peers have provided.

At this point, it is likely that you will start to experience some push back, and be told “Oh, don’t worry about that” or “That’s not really an issue”, or perhaps “You’re going into this in too much depth”.

A necessary evil

A necessary evil

Don’t EVER accept that.  It is your job not only to represent their views to the stakeholders but just as importantly to represent the views of the stakeholders to the project team.  Like an interviewer, your job is to consider both sides of the story.  Ignoring stakeholder concerns and questions because they are inconvenient is the quickest route to failure.

Playing devil’s advocate is often a tiresome activity, and one that may on occasion provoke a degree of frustration within the project team, but it is an entirely necessary process, so make a point of explaining why you’re doing it.  If the answers you get don’t convince you, they won’t convince your stakeholders either.

Next, you need to designate comms representatives and build alliances.  If you have several hundred stakeholders to manage, there is no way you can manage them all personally.  However, there will be individuals across the stakeholder landscape who are predisposed to support your project.  Nurture them.  Find out who they interact with and who they may be able to influence.  Providing them with the opportunity to feed back to you any issues that they may have or that they may have heard others have is going to improve the relevance of the communications you provide immeasurably.

Recognize the fact that in many cases the communications you provide will not come directly from you.  They may be cascaded through the organization, and in fact this cascade process may well be a part of your design.  However, communications often follow relationship or expertise pathways, rather than reporting lines.  I have known communications materials to be shared across continents by people who work in entirely different departments and roles.  Why?  Well, perhaps they used to work together.  Perhaps they met on a training course.  Maybe they have the same personal interests.  Relationships form in all kinds of ways that you may not understand.

It is therefore critical to remember that while communications can certainly cascade along hard reporting lines, they can also cascade functionally, among dotted line reports, and along completely informal interpersonal lines.  Where you are able to build relationships, find out who people are talking to, and what they are hearing.  See whether these relationships can be leveraged to become a living part of the comms process.

The materials you will provide need to resonate with each audience.  That does not mean that every comms piece has to be produced to an extreme level of functional granularity, but rather that nobody should ever directly receive a comms piece and, having read it, think to themselves “Why the hell did they think that I would have any interest in that?”.  Every piece of information that they receive directly from you must have something that is of value to them.  These are busy people.  If they are suspicious of the objectives of the project then any comms piece that they feel wastes their time is a nail in your personal comms coffin.

Don't assume your audience listens when you want it to

Don’t assume your audience will be listening when you want them to listen.

In addition to the comms channels that you select, and these will vary based on your organization, it is important to remember that most stakeholders will at best only glance at the materials you send them at the time they receive them, but will quite possibly want to return to them when they have the time or the inclination to find out more.

It is imperative to provide them with a means of accessing these materials in their own time, and making sure that they know where to go to find them.

The internet makes this possible almost without exception.  Everyone you want to interact with will have access to a database, or an intranet site, or a dropbox.  Communicate the location of this information and how it can be accessed consistently.  Make sure they know where to go.  Make sure the only versions of documents that appear in this ‘database’ are the current versions.  Make sure that the database is structured in a manner that makes the relevant information easy to locate.

There are a host of other observations that I could add on this subject, but this post is already quite long and therefore I will add only one further piece of advice.  Please, please, please make an effort to actively seek feedback that can inform the process.

thumb_surveymonkeyFacilities such as ‘Survey Monkey’ make it possible to solicit feedback from widely dispersed groups of stakeholders.  Structuring a survey correctly will allow you to see how well your comms strategy is working, and to get a feel for areas where there are issues to be overcome.

However, it is important to remember that initiating a survey is first and foremost for the purpose of improving the comms process.  Far too many people use it as a means to cover their ass, structuring the questions so as to be able to deflect criticism of the comms process and make themselves look better.

I understand the reason for this – as I believe I recall saying in my first post of this series comms usually gets little of the credit when things go right and the lion’s share of the blame when things go wrong.  However, if you are truly looking to improve the comms process then taking a dispassionate approach to surveys must be paramount.

In the next post, I’m going to be blogging about engagement with Senior Management.  I’ve seen many examples of where this critical element was mismanaged.  But I’ve also seen examples where it was done exceptionally well, and I’ll share some of these experiences in Principle #5.

 
1 Comment

Posted by on March 2, 2013 in Change Management, Communications

 

Tags: , , , , , , , , , , , , , ,

Comms Principle #3: The Importance of Dialog

Comms channels and stakeholders

Hooray – ‘Oliver’ is getting the message, so put your feet up and wait for the change program to succeed

In the first two Comms Principles of this series, I’ve talked about channel selection and stakeholder segmentation.

Now, let’s imagine that one of the key stakeholders your segmentation process has identified is a cat, ‘Oliver’, and that the channel you have selected to deliver the message is a train, a train that can be verified as one that will reach Oliver.

The message is consistent.  Delivery is always complete.  So the comms strategy must be succeeding.  Right?

Now that may seem like a rhetorical question but it’s not, and those of you that answered “no” are wrong.  On the other hand, anyone who answered “yes” (and there may be one or two) is also wrong.  The correct answer is “we have no idea”.

What do we know about ‘Oliver’.  It’s true that he’s getting the message, but what is his reaction to it?  Does he like it?  Is it annoying?  Why isn’t he moving?  In fact let’s make the question even simpler.  Has Oliver looked at it, or is he ignoring it? The answer is still “we have no idea”. Hmmmm.

Incomplete Comms Process Flow

A Comms Process Flow….sort of

OK, let’s have a look at our Comms Process flow chart – maybe that will tell us what’s going wrong.  As we can see, the Comms Manager sits within the Project Team.  Communications are developed via his interaction with other project team members.

The Comms Manager is not an IT expert.  He’s not a member of the Management Board, he doesn’t get involved in financial planning, and when it comes to Supply Chain processes, he can’t see the Forrester Effect for the trees.   Because of this, he needs access to the people who are specialists – the workstream leads; the senior user and supplier; the Project Manager.

In partnership with the workstream leads, he develops multiple pieces of communication.  He talks to the IT lead, discussing the challenges they face with the legacy systems.  He talks to Operations to learn about inventory visibility.  He talks to finance to understand what the key reporting metrics are and whether there are any that conflict across functions or business units.

With the help of all these experts, he develops a suite of communications materials – some high level and aimed at Senior Management, some in greater functional detail.  All are designed to give each stakeholder the information they need, built with the input of experts, validated across other key project streams and with the Project Manager, and delivered by channels that are proven to reach the target audience effectively.

Yet something is lacking, and if you look closely at the chart you can see why. Despite the fact that the communications pieces themselves are excellent, the process itself is flawed.

Just because you served it up doesn't mean they'll swallow it.

Just because you served it up doesn’t mean they’ll swallow it

The communications are developed within the project team as an iterative process, seeking feedback, involving experts, using their expertise, building layer upon layer.

Then a hatch is opened, the comms pieces are thrown out to the stakeholders, and the hatch closed again.

Now, if the comms materials are raw meat and the stakeholders are ravenous lions this process may work, up to a point.  But as we’ve already discussed in an earlier post, people usually don’t like change, so there’s a good chance that you will not see a feeding frenzy when you serve up a nice plate of Raw Comms.  In fact, this approach has been known to result in the lions eating the Comms Manager.

And so we return to Oliver and we think “If we asked Oliver what he thought about all this, would he have something to say?”.  We look at the process flow chart and we say to ourselves “Why are we seeking feedback within the project to increase our understanding, and yet not soliciting feedback from the stakeholders – the very people that we are supposed to be influencing? Why are the arrows only going one way?”

Engaging with Oliver would tell us whether he (a) knows what is going on and supports it completely without needing more information, (b) doesn’t know what is going on and knows he needs to understand it more, but is afraid to admit he doesn’t understand it and is therefore being stubborn, or (c) knows exactly what it means and disagrees so completely that he is stopping the message getting any further, hoping that eventually it will derail.  There are reasons (d) through (w) as well, but you get my point.

If I was asked to put money on the main reason that project communications strategies fail, this would be it. The feedback of stakeholders is not sought, not valued, not discussed or not addressed.

Some great lessons for communications

Some great lessons for communications

This shouldn’t be a surprise to anyone, but frequently it is.  A fairly senior adman that my wife worked for a few years ago used to live by the mantra that if you say something a minimum of three times people will get it. How he rose to his exalted position with such a facile view of communications is beyond me, but the main point that he fails to take into account is that ‘getting it’ is not the same as ‘believing it’.

In his book ‘The Righteous Mind – Why Good People are Divided about Politics and Religion’, psychologist Jonathan Haidt, a Professor at NYU’s Stern School for Business provides a rationale for this key difference. Expanding on observations originally made by Plato that human beings weigh evidence in the search for knowledge, Haidt says that we are hardwired to make snap judgements based on our emotions, and then we manipulate the manner in which we process facts in order to justify the largely emotional conclusions that we had already reached.

Ah, you may say, but the people we are seeking to influence are experts in their respective fields.  They are the ones whose experience needs to be leveraged in order for the change to be successful.  This being the case, surely these are the very people that will weigh the evidence to arrive at “knowledge”?

Well, no, or at least not as far as I have observed in my career.  While it is possible that these people are experts, let’s not forget the other ingredients that make successful communications such a difficult recipe, some of which I discussed in Principle #2 – reasons which in many cases are significantly more personal in nature than they are professional:

  • Despite the fact that they are experts, they are first and foremost human
  • Their personal career objectives may not align with your corporate ones
  • There are usually several ways to skin a cat (sorry Oliver) and they may think that the efficiency of their way outweighs the effectiveness of yours
  • They may already have too much to do, and you’re asking them to relearn it
  • The change that you are proposing may make their current role redundant, or require a change in reporting or remuneration with which they are extremely uncomfortable

Of course there are other potential reasons as well, but while not one of the reasons above could be said to disprove any of the theory, invalidate any of the process changes or discredit the new IT solution or organization structure that you are intending to build, any one of them is a very good reason for a stakeholder to not support the change.  They are selfish reasons to be sure, but that fact does not make them any less real, or valid, and as a Comms Manager it is your role to find out what the reasons for the lack of engagement are, and to see what can be done to address them.

Without engaging with your stakeholders, it is unlikely that you will be able to combat these issues.  Certainly there may be ways in which you can address some of them by talking about best practice, pointing to improvements made by other companies or organizations, or talking about changes in the marketplace, but these are somewhat sterile responses and don’t go very far towards addressing what may be intensely personal concerns.  Your stakeholders know that they are personal issues, and may therefore be reluctant to discuss them openly.  And of course if one of your stakeholders feels this way there may be others.

Find a way to discuss the facts, not the conjecture

Find a way to discuss the facts, not the conjecture

To engage with them, you have to make them truly believe that you value their feedback, that you want to hear their concerns or suggestions.  They must have the means to review the documentation as and when they have time, and have a number of clear channels via which issues can be raised.

If you don’t give them the opportunity to air their opinions with you, and thereby have the opportunity to address them, you will usually find that they share them with their colleagues, but that they do so in a manner that undermines the change program, starts rumors and leads to a much greater volume of negative feeling.

So how do you engage with literally hundreds of stakeholders?  I’ll be offering some suggestions in Comms Principle #4 – A Multi-Faceted approach.

 
 

Tags: , , , , , , , , , , , , , , ,

 
%d bloggers like this: