Section F
Politics in Projects

“Politics is not an exact science …but an art. The art of the possible.”

Composite from speeches by Otto Von Bismarck, 1863 and 1884

“Politics are almost as exciting as war, and quite as dangerous. In war you can only be killed once, but in politics many times.”

Remark by Sir Winston Churchill, 1920

Like it or not, as a project manager, you will be involved in politics, and whatever your view, you cannot avoid it. Politics will be far more prevalent in a multi‐project business environment than in companies in the technological industries with strong project cultures. This section tries to address both environments.

Here are a few ways of looking at politics:

  • The art of winning (the argument)
  • The art of getting things done through people
  • How to block or stop things getting done
  • The pursuit of power
  • A waste of my time
  • Using different forms of power to get your way
  • Playing the game
  • Avoiding confronting difficult issues
  • Getting people with different and hidden agendas to agree
  • Understanding and influencing key players to bring them around to your way of thinking

There are two ways of approaching politics on a project. If the objective is to meet one's own need at the expense of another, then you are likely to be engaged in political manipulation. If, on the other hand, you are attempting to meet project needs, as well as the other person's need, you are likely to be engaged in influencing.

Effective project managers develop their political skills and influence in organizations. Without authoritative power, the project manager must find other ways to persuade, cajole, buy‐in, and ‘kick’ others to achieve their objectives. Examples of this include:

  • Understanding who the key players are and who makes the decisions
  • Knowing what switches key players on and off
  • Recognising which projects carry sufficient power and profile to stand a chance of succeeding and getting the right resources
  • Choosing which battles to fight and when to go with the flow or, as a colleague and I used to say to each other, when to lower your periscope and ‘run silent, run deep’.
  • Being seen achieving
  • Being involved in achieving corporate objectives
  • Making a point at the right time
  • Recognising who can delay or block a project
  • Building trust by helping others to win
  • Building alliances with functional managers in order to receive favourable treatment in the allocation of resources
  • Building a strong alliance with a senior manager but also some back‐up alliances for when the senior manager loses favour
  • Understanding the characteristics of the different cultural units

In order to determine the political forces affecting your project, one of your earliest actions should be to plot the power and influence of all stakeholders against their attitude. A stakeholder is anyone who interacts with the project in any form. You need to decide who you need to influence to make your project succeed. Plot each individual within a grid using 1 to 10 scales on both the X and Y axes. See Figure VI.F.1.

All of senior management should be supporters. However, they have been shown as partly in a negative role, since it is entirely possible for an internal business project not to have the support of all the senior management team.

Illustration plotting each individual (Opposers, Supporters, Observers, Co-operators) within a grid using 1 to 10 scales on both the X and Y axes.

Figure VI.F.1

Perform a NICE analysis: What do they need? What interests them? What are they concerned about? What do they expect (from us)? Plans then need to be developed for each stakeholder who needs to be persuaded.

The opposers need to be kept informed. Monitor the observers. Involve the cooperators, and leverage the supporters.

1 Typical Destructive Behaviour

  1. Lack of agreement on the need for the project or its objectives
  2. Attempts to steer projects to meet one individual's needs above those of the whole project
  3. Fights over resources
  4. Lip service paid to decisions but individual actions not implemented. How often have you left a meeting, saying to a colleague in ‘sotto voce’: “Well, that was a waste of time”?
  5. Lack of decisions
  6. Disowning problems and solutions
  7. Blocking of suggestions and ideas
  8. Inflated budgets and deadlines
  9. Offering unsuitable staff for secondment onto projects
  10. Blocking ideas and hard plans to escape accountability
  11. Delaying projects through a lack of decisions
  12. Looking for a scapegoat when things go wrong
  13. Claiming credit when things go right
  14. Concealing or withholding information

2 Dubious Behaviour?

2.1

Canvassing project team members and decision takers to get them to agree

2.2

Consulting others to get them to buy into the project's goals

2.3

Spending time and socializing with people who have power and influence

2.4

When decisions have to be made and you are providing options for the boss, always include one that is easy/obvious (not too obvious!) for them to reject.

2.5

Copying memos to your manager's boss

2.6

If you have to have an argument with the client, try doing it through someone else. For example, use your project controls manager to argue with their opposite number.

2.7

Managing the client's expectations to achieve Success: S=D/E, (deliverable/expectation). At the start of the project, tell the client how tough the targets are that they have set. Complain that the changes will delay the project. Tell them all your problems. Manage their expectations downwards. At the end of the project, give the key users something that is important to them; do a bit more than usual for the client. Increase the deliverables where possible, provided it costs only a little money.

2.8

Using ‘clever’ language. For example: one construction manager when asked: “How are things?” always said: “Fantastic.” He never said if they were fantastically good or fantastically bad!

Reasonable is a word that is usually interpreted by the receiver within their own mental context and, consequently, the issue being discussed is received favourably.

2.8.1

Be wary of people using phrases that usually mean the opposite of what is actually said:

  1. I wouldn't worry if I were you; this is no criticism of you personally.
  2. I'm sure nobody will notice.
  3. It's no problem at all.
  4. I'm sure you're right.
  5. I'd love to help you if I could.
  6. It's really very simple.
  7. I'll attend if I possibly can.

3 How Politics Can Affect a Project

Lack of political awareness on projects can cause problems in each stage of the project life cycle. For example:

3.1

Terms of Reference:

  1. No agreement to project objectives
  2. Wrong people seconded onto the project team
  3. Unrealistic deadlines or constraints; for example the budget

3.2

Feasibility Study:

  1. Favouring an individual's preferred solution
  2. Blocking new and different ideas
  3. Constantly changing the objectives

3.3

Planning:

  1. Artificially extending deadlines
  2. Overestimating resource requirements
  3. Planning and re‐planning to fit individual steering group members' wants, irrespective of whether this achieves anything

3.4

Developing, Executing, and Setting to Work:

  1. Avoiding taking on actions, always delegating them to the rest of the team
  2. Using the operational position as an excuse for lack of delivery on project actions
  3. Changing the objectives and priorities
  4. Going back on decisions

3.5 Evaluating/Post Project Appraisal:

  1. Making things look better than they were
  2. Criticising all of the things that went wrong without recognising the things that went well
  3. Not evaluating projects to avoid confronting poor performance or results

4 Some Advice

4.1

As Churchill said: “In politics you don't have time. You only have moments.” Pick your moments carefully.

4.2

Be bold, make decisions, and do things that achieve results. Remember that it is much easier to apologise than to ask for permission.

4.3

Know the company procedures well, not necessarily because you are going to use them, but because you are going to use the cracks between them to achieve what you want to do.

4.4

Don't take on a more senior person unless you are prepared to go for broke and accept that you may have to resign. Remember senior management will always support the supervisor (as a project manager, this may sometimes put you in a stronger position – depending on the company's project management culture).

4.5

Remember there are always at least three sides to a story.

4.6

If you lack knowledge of a particular subject area, back the proposition from the team member who has the most logical and clearly presented argument. Choose the simplest proposition or solution.18

4.7

Never get the contract out in front of the client.

4.8

If you want to get promoted or move onto a better assignment, start looking for your replacement early and train them.

4.9

Train all your people through the Blanchard management cycle. See Section B Leadership and Motivation, subsection 3.

4.9.1

Nominate a different person from your direct reports (unless you have a deputy project manager) to take over for you every time you have to be absent from the project.

4.10

If, as part of your MBWA (see Section B, subsection 6), you talk directly to junior team members always stop off and tell their supervisor what it was all about. However, before wandering into their domain it is sensible to advise the supervisor of a group that that is what you propose to do.

4.11

Have a regular updating meeting with your boss; keep them informed. Before leaving, be sure that they have bought in and agreed to your proposals.

4.12

Train people to keep written records of conversations with the client and always report them to you, the project manager.

4.13

Don't forget to have your ‘lift speech’ ready for a senior manager that you want to influence. See also Section E Personal Skills, paragraph 14.3

4.14

CYA. Keep a project journal.

5 Something to Think About

5.1

‘The squeaky wheel gets the oil.’

5.2

You may think that the route to success is to keep your head down, work hard, overcome problems, and deliver competent work. This won't necessarily get you promoted. The reward for hard work is more work, rather than appreciation! You may even find colleagues offloading some of their work onto you because you are ‘obviously the right person to do it, and you are so much better at doing it than we are.’

5.2.1

You need to make sure management are aware of your achievements. It is hard not to respond positively to someone's enthusiasm at their achievements. If you want to get on, get noticed.

5.2.2

Those who keep the business running tend to be left alone to get on with it. The ones who move up the organization are the ones who boast about their successes and who demand more out of their jobs.

Note

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset